The Hypothis Team · August 19, 2026 · Updated September 10, 2026 · 3 min read
Willingness to pay: survey questions that predict real spend
"How much would you pay for this?" is the single most misleading question in idea validation. People answer it with a number that costs them nothing to say, and founders build pricing models on top of it. Measuring willingness to pay well means anchoring every question on something real — a past purchase, an existing budget, a concrete trade-off.
Here's how to do it in a survey.
Start with what they already pay
Before any pricing question about your product, establish the baseline:
- "What do you currently spend to handle [problem], counting subscriptions, contractors, and your own time?"
- "What's the most you've paid for a tool in this category?"
- "Is there a budget line this would come out of, or would it be a new expense?"
- "When you last bought a tool like this, who approved it?"
A respondent who has never paid for anything adjacent is telling you something important, regardless of what they say later. Stated willingness to pay with no purchase history behind it is the weakest signal in customer research.
Van Westendorp price sensitivity
Four questions that map the acceptable price range without ever asking "what would you pay":
- "At what monthly price would this be too expensive to consider?"
- "At what price would it be expensive, but you'd still think about it?"
- "At what price is it a good deal?"
- "At what price is it so cheap you'd doubt the quality?"
Plot the responses and the range between the "getting expensive" and "too expensive" crossover points is your viable band. It's directional, not precise, but it beats a single open-ended guess by a wide margin.
Gabor-Granger for a specific number
If you already have a candidate price and want to test it, ask purchase intent at several price points:
- "How likely are you to subscribe at $19/month?" (5-point)
- Then repeat at $29, $39, $49.
The curve of "likely" and "very likely" responses against price gives you a rough demand curve and a revenue-maximizing point. Discount the absolute numbers — intent overstates action — but the shape is informative.
The commitment questions
Stated intent is inflated. You can partly correct for it by adding friction:
- "Would you join a paid pilot at [price] starting this month?" (yes / no / need more info)
- "Can I follow up with a checkout link?" (a yes here is worth ten survey yeses)
- "Would you pre-pay three months for early access at a discount?"
Any question where "yes" implies a near-term action gets you closer to real willingness to pay than any hypothetical scale.
Segment the willingness-to-pay data
Cross the pricing answers against the screener and problem questions. Willingness to pay from people who deal with the problem weekly and already pay for a workaround is real. The same number from people who see it as a minor annoyance is aspirational. Reporting one blended average hides that.
Common questions
Is van Westendorp reliable for early-stage products?
It's reliable for finding a plausible range and catching pricing that's wildly off. Don't treat the exact crossover numbers as your final price — treat them as the boundaries of where to experiment.
How many responses do I need for pricing questions?
More than for problem validation — aim for 40 to 60 qualified responses so the price distribution isn't dominated by a few outliers.
Should I show pricing before or after the value proposition?
After. People need to understand what they'd be paying for. But keep the description to one sentence so you're testing the price, not your copywriting.
What if willingness to pay is high but nobody converts later?
That's the expected gap between stated and revealed preference, and it's exactly why the commitment questions matter. Weight a "send me a checkout link" far above a "7 out of 7 likely."
Test pricing as a hypothesis
Hypothis treats willingness to pay as one of the five hypotheses it builds and scores — anchored on past spend, tested with real respondents, and reported next to the problem signal rather than blended into it. It's free during early access. See how it works, or read idea validation survey questions for the full survey structure.
Run this on your own idea.
Hypothis turns your idea into testable hypotheses and a real customer research round — then gives you an honest verdict. Free during early access.
Related reading
- How many customer interviews do you need before building?
A straight answer on how many customer interviews you need to validate a startup idea — why the number is smaller than you think, and what actually determines it.
- Idea validation survey questions that don't just collect yeses
How to write idea validation survey questions that measure real behavior and demand, not politeness — with a question bank and a scoring approach.
- 30 customer discovery interview questions that actually test something
A field-tested set of customer discovery interview questions organized by what they test — problem, workaround, willingness to pay, and behavior — plus the questions to never ask.