How to research willingness to pay without asking for a guess

“What would you pay for this?” can start a conversation, but it cannot establish what someone will buy. The answer may reflect politeness, a rough comparison, or a budget the person does not control. Treat it as something to investigate, not a price backed by demand.

A more useful approach has two parts: reconstruct a relevant purchase or workaround, then test a specific offer with a person who can take the next buying action. Keep evidence from those parts separate. Past spending explains context; a current commitment examines the offer in front of the buyer.

Reconstruct a purchase before discussing your price

Ask about the most recent occasion when the organization tried to solve a comparable problem. A comparable purchase need not be competing software. It might be contractor help, an internal project, or a decision to keep the existing process.

An original interview sequence you can adapt:

1. “What triggered the search for a different approach?”
2. “What options did you seriously consider?”
3. “What did you personally do in the decision?”
4. “What spending or internal effort was approved?”
5. “What had to happen before approval?”
6. “What happened after you started using the chosen approach?”

Clarify whether a number refers to a quote, an approved amount, actual spending, or a rough recollection. A range may be enough for the research question. Do not pressure someone to disclose confidential commercial details.

GOV.UK’s interview guidance favors specific accounts and real examples over general statements about what people ought to do. Applied here, the point is to reconstruct a purchase event before asking someone to forecast a future decision. Read the in-depth interview guidance.

Separate burden, value, budget, and authority

These four subjects are related, but none is a substitute for the others.

Burden is what the current process demands: time, attention, rework, delays, or unpleasant coordination. Value is what would improve if the outcome changed. Budget concerns resources available for this kind of change. Authority concerns who can approve the next action.

Suppose a fictional agency coordinator reports spending eight hours a month reconciling staffing updates. Your proposed service costs $300 per month. Both figures are illustrative, not a pricing recommendation or a customer result.

It is tempting to multiply the hours by a salary estimate and conclude that $300 is an easy purchase. That calculation leaves major questions unanswered. Would the service actually remove those hours? Does the agency value the released capacity? Who would perform setup? Is this coordinator authorized to buy it? Would another existing tool solve enough of the problem?

Record the time estimate as reported evidence. Investigate the mechanism of improvement and the buying process separately. A spreadsheet of assumed savings is a hypothesis, even when its arithmetic is correct.

Turn the proposal into an offer someone can evaluate

An offer needs more detail than a price. Write a short offer card that makes the proposed exchange concrete:

The sample describes an offer to develop, not a service currently available from Instant Expert. Replace every field with something your team can actually deliver. Explain whether it is a manual pilot, a prototype, or an operational product. The buyer should understand what exists today.

Keep the package stable while you investigate a price unless the package itself is the uncertainty. If you change the price, scope, delivery, and customer effort together, a different response will be difficult to interpret.

Ask for a relevant action and record what happens

Strategyzer distinguishes what people say from the actions used to test a value proposition. Its guidance recommends combining interviews with behavioral evidence for critical assumptions. That does not make every click a purchase or every payment a durable business. Read Strategyzer’s explanation of testing methods.

Choose a next action that matches the buyer’s real process. A user may be able to introduce the approver. A team lead may be able to arrange a review. An authorized buyer may be able to approve a clearly defined pilot. Do not pretend all three people can make the same commitment.

Use an evidence log rather than a confidence score:

Include the date, role, exact offer, action requested, and action observed. If someone says they will introduce an approver but has not done so, write “introduction offered; not yet observed.” That is more precise than labeling the account qualified.

Investigate a stalled action without inventing a reason

A missing reply can have several explanations. The problem may be low priority; the offer may be unclear; the person may be busy; the requested step may exceed their authority. Silence alone does not distinguish them.

Follow up with a specific, low-pressure question about the stalled step. If someone explains that they cannot evaluate until the next planning cycle, record that constraint and any agreed next date. Do not silently convert it into either a rejection or a future sale.

Likewise, a successful pilot is evidence about a particular package and buyer. A handful of willing participants does not establish a market-wide purchase rate. Keep track of how they were recruited and what relationship they already had with your team.

At the end of the research round, you should be able to describe the current alternative, the buyer’s decision process, the exact offer, and the action actually taken. That record gives you a defensible next experiment. An average of hypothetical price guesses does not provide the same foundation.