Pricing Research Interviews: How to Test Willingness to Pay Without Asking Bad Pricing Questions
Learn how to run pricing interviews that reveal value, urgency, and price sensitivity without asking unreliable pricing questions.
Stop asking what people would pay
The fastest way to get bad pricing data is to ask, What would you pay for this? In an interview, most people are not making a real purchase decision. They are being polite, guessing, or anchoring on the first number that sounds plausible. You get an opinion, not evidence.
Pricing interviews are more useful when you treat them as context-gathering, not price-setting. Your job is to learn what the problem costs today, what alternatives people already pay for, what risk they need removed, and what makes a price feel fair or too high. That gives you better inputs for later pricing tests.
If you need a refresher on building a solid interview guide, start with How to Write a User Interview Guide That Produces Better Insights.
What to ask instead
Good pricing interviews stay anchored in real behavior and tradeoffs. Ask about money already spent, decisions already made, and the conditions that trigger action.
Use questions like these:
- What are you using today to solve this problem?
- What does that cost each month in budget, time, or headcount?
- When does this problem become urgent enough to pay to fix?
- Who is involved in approving this purchase?
- What outcome would make this feel obviously worth paying for?
- What would make the price feel risky?
- If this cost more than your current approach, what would need to be true for that to still make sense?
- What would you compare this price against?
- At what point would you stop considering it and look for another option?
These questions uncover willingness to pay indirectly, which is usually more reliable than asking for a number. They also help you separate true price sensitivity from other issues like low urgency, unclear value, missing capabilities, or procurement friction.
For more examples, see Customer Interview Questions: 40 Examples for Discovery, Retention, and Pricing Research.
What strong pricing interviews actually reveal
A useful pricing interview should help you answer four things:
| Signal | What to learn | Why it matters |
|---|---|---|
| Current spend | What they already pay in money, time, or labor | Gives you a real benchmark |
| Value driver | Which outcome matters most | Helps with packaging and positioning |
| Purchase conditions | What has to be true before they buy | Shows readiness and objections |
| Comparison set | What they evaluate you against | Prevents pricing against the wrong alternative |
For example, a founder might hear “$200/month is too expensive” and assume the market is price-sensitive. But if the same buyer is already paying an agency $2,000/month, the real issue is probably trust, switching cost, or unclear ROI. That is exactly the kind of distinction interviews are good at surfacing.
When to pair interviews with surveys
Interviews are for forming pricing hypotheses. Surveys are for measuring them.
Run interviews first when you need to understand:
- which outcomes customers value most
- which buyer segments think differently
- what language customers use to describe value
- why prospects stall or churn on price
Then use a survey when you need to estimate thresholds across a larger sample. Common methods include Van Westendorp for price perception, Gabor-Granger for purchase intent at different price points, and conjoint when packaging and feature tradeoffs are part of the decision.
A simple rule: if you still do not know what customers are comparing you to, you are not ready for a pricing survey.
For a broader framework, read When to Use Surveys vs Interviews for Product Decisions.
Common mistakes that distort pricing signals
Talking to the wrong people. Free users, early fans, and non-buyers often give weak pricing signals. Prioritize recent buyers, serious evaluators, lost deals, and customers who chose an alternative.
Showing the product too early. If the concept is still fuzzy, people react to your explanation skills, not the offer itself.
Ignoring the buying process. In B2B, the user, budget owner, and approver may be different people. A user saying the price sounds fair does not mean the company will buy.
Treating every “too expensive” response as price sensitivity. Often it means weak onboarding, unclear ROI, or too much perceived switching cost.
A practical interview flow
Keep pricing interviews short and structured:
- Start with the current workflow and problem severity.
- Explore what they use now and what it costs.
- Ask about the last time they paid to solve this problem.
- Introduce your offer and ask what value stands out.
- Probe for comparison points, objections, and deal-breakers.
- End with thresholds: what would make this a no-brainer, a maybe, or a non-starter?
The goal is not to extract a price guess in the interview. The goal is to learn what conditions make a price believable.