Willingness to Pay: How to Measure It Before You Build
Willingness to pay (WTP) is the highest price a customer would accept for a product before they walk away. Price sits at or below it. For a new product, the useful question is not "what would people say they pay?" but "what are people already paying, in money or time, to solve this problem?"
There are two kinds of evidence:
- Stated willingness to pay is what people tell you, in surveys or interviews.
- Revealed willingness to pay is what people actually do: what they buy, cancel, pay someone else for, or spend hours working around.
Stated answers are cheap to collect and easy to inflate. Revealed behaviour is harder to find and much more reliable. This guide shows how to measure both, and how to weigh them, before you build anything.
Why willingness to pay matters more than demand
Lots of people can have a problem without anyone paying to fix it. Demand tells you that a problem exists; willingness to pay tells you whether there is a business.
For a new product it answers three questions at once:
- Is there a business at all? If nobody spends money or serious time on the problem today, a paid product will be a hard sell.
- What can you charge? Existing spending gives you price anchors.
- How many customers do you need? Customers needed = monthly revenue target ÷ price. A price that is too low can make an idea unworkable even when demand is real.
Why surveys overstate it
Ask "Would you pay $20 a month for this?" and many people say yes. Saying yes costs nothing, it feels polite, and the product in the question is imaginary and perfect. Researchers call the gap between what people say in hypothetical questions and what they later do hypothetical bias.
So treat any answer to a hypothetical price question as an upper bound, never as a forecast. Then look for behaviour that confirms it.
The evidence ladder: strongest to weakest
Rank every piece of evidence you collect on this ladder. One rung near the top outweighs a pile of evidence near the bottom.
- Payment for your product. A pre-order, a deposit or a paid pilot at your real price. You only get this in the final test, but nothing else counts as much.
- Payment for an alternative today. People who say they subscribe to, buy, renew or ask for a refund on a competing product. This tells you the category is paid and gives you a price anchor.
- Payment in time or labour. People who run the job by hand, keep a spreadsheet, or hire a freelancer or an assistant to do it. Hours × their hourly rate is a rough ceiling on what the problem is worth to them.
- Stated willingness with a number. "I'd happily pay $10 a month for something that just did X." It is better than a vague yes, but it is still talk.
- Indirect signals. High advertising cost per click on the problem's keywords, or paid products in a neighbouring category. These suggest money moves around the problem; they say little about your customers.
Separate the people who paid from the people who want it free
Complaints about price are easy to misread. Take a review that says "the subscription is a rip-off". It could come from:
- someone who paid, felt short-changed and would pay a fairer price; or
- someone who never intended to pay for anything.
The two mean opposite things. When you collect posts and reviews, label each one that mentions money with one stance:
- Paid: they say they subscribed, bought, renewed or asked for a refund.
- Willing to pay: they say they would pay, ideally with a number.
- Free only: they say they won't pay, or only want a free tool.
- No stance: money comes up, but they don't say where they stand.
Only "paid" supports willingness to pay strongly. A useful check: if "free only" posts outnumber "paid" posts by more than about two to one, the audience may be the wrong one, however many people share the problem.
Where to find public evidence of willingness to pay
You can collect most of the ladder's middle rungs without talking to anyone:
- Competitor pricing pages. Record the real listed prices of at least two products that do the same job. These are your anchors.
- App store and software reviews. Search them for "subscription", "refund", "worth it", "too expensive" and "cancelled". Note the stance of each one.
- Community threads. Search for "what do you pay for…", "is [product] worth it", "cheaper alternative to [product]" and "I'd pay for…".
- Freelance and job listings. If people hire someone to do the job by hand, the going rate shows what the problem is worth.
- Search advertising data. A high cost per click on problem-specific keywords suggests advertisers earn money there. Treat it as a weak signal only.
Keep a quote and a link for every item, so each number you use later can be traced back to a person.
If you run a pricing survey, use a structured method
Surveys still have a place once you know the category is paid and want to narrow down a price. Use a structured method instead of a single "would you pay X?" question:
- Van Westendorp Price Sensitivity Meter. Ask four questions: at what price would it be so cheap you'd doubt the quality, a bargain, getting expensive, and too expensive to consider. The places where the answer curves cross give you an acceptable price range.
- Gabor-Granger. Show one price at a time and ask how likely the person is to buy. Then raise or lower the price. The result is a rough demand curve and the price that maximises revenue.
- Conjoint analysis. Show bundles of features at different prices and ask people to choose. It reveals how much each feature is worth. It needs a larger sample and dedicated tools, so it suits later stages more than a first check.
Survey people who match your target customer, ideally ones who already pay for an alternative. Remember that all three methods still measure stated willingness, so confirm the result with behaviour.
Test it directly before you build
The strongest evidence comes from asking for money:
- A price on the landing page. Show the real price and a "buy" or "start" button, and measure how many visitors click it. If you don't have a product yet, say so honestly on the next screen and offer to notify them.
- A pre-sale or deposit. Offer early access at your real price, not a discount you couldn't sustain. Decide in advance how many payments count as a pass.
- A paid pilot or concierge version. Do the job by hand for a few customers and charge for it. You learn the price and the workflow at the same time.
Work out the bar from your revenue math before you start: the customers you need, the visitors your channel can bring, and therefore the conversion rate you must hit.
Turning willingness to pay into a price
Three anchors give you a starting range:
- Competitor prices: what the category already charges.
- Cost of the problem: hours lost × hourly rate, or money lost per month. Customers rarely pay more than a fraction of this.
- Your revenue math: the price at which the customers you can realistically reach add up to your target.
If the price your revenue math needs is far above both other anchors, no amount of demand will fix the idea. Change the audience, the scope or the business model.
Common mistakes
- Asking "would you pay?" and believing the answer.
- Reading every price complaint as willingness to pay. Separate "paid" from "free only".
- Using other founders' revenue screenshots as evidence. They say nothing about your customers, and they are often unverifiable.
- Testing with a launch discount. If people only pay at a price you can't keep, you haven't found willingness to pay.
- Surveying the wrong people. Friends, followers and other founders are not your customers.
How Worth a Shot measures it
When you describe an idea, Worth a Shot collects community posts and app store reviews with a fixed set of searches. It labels every one that mentions money as paid, willing to pay, free only or no stance, and records the listed prices of the competitors.
Payment evidence is one of the factors in the verdict:
- Third-party revenue claims never count.
- Advertising cost only counts as a weak signal.
- Every count in the report links back to the posts and reviews it came from.
Check your idea, or read how to validate a business idea for the whole process.
FAQ
How do you calculate willingness to pay?
There is no single formula. With surveys, the Van Westendorp method gives an acceptable price range, and Gabor-Granger gives the share of people who would buy at each price. With behaviour, look at what people already pay for alternatives, and at the cost of the time they spend on the problem. Use the two together, and trust behaviour when they disagree.
What is an example of willingness to pay?
Imagine a freelancer who pays $15 a month for a tool that half solves a problem, and spends two extra hours a week fixing what it misses. Their willingness to pay for a complete solution is likely above $15. It is also bounded by what those two hours are worth to them.
Is willingness to pay the same as price?
No. Willingness to pay is the most a customer would accept; price is what you charge. When the price is below a customer's willingness to pay, they buy and keep the difference as value. When it is above, they don't buy.
Can you measure willingness to pay without a product?
Yes. Competitor prices, reviews, community posts, manual workarounds, a priced landing page and a pre-sale all work before you write any code.