How Do I Know What Price My Customers Are Actually Willing to Pay?
The most direct way to know is to ask, using a short four-question survey called the Van Westendorp Price Sensitivity Meter, which turns customer answers into a specific acceptable price range and an optimal price point. This is a different signal than reading elasticity from your past sales, and it's especially useful when you don't have much sales history to read yet, since it works even for a brand-new product with zero orders.
Key Takeaways
- The Van Westendorp Price Sensitivity Meter asks customers four questions about a specific product and calculates an acceptable price range plus an optimal price point from their answers.
- It measures stated preference, what people say they'd accept, which is a different signal from elasticity, which measures revealed preference, what people actually did when the price changed.
- It works with zero sales history, making it especially useful for new products, unlike elasticity, which needs real price-and-quantity data to calculate.
- Reliability scales with response count: fewer than 5 responses gives no usable read, 5 to 19 gives a low-confidence estimate, and 20 or more gives a good-confidence one.
- Stated and revealed preference answer related but different questions, and the two are best read side by side, not blended into a single number.
Two Different Ways to Answer the Same Question
There are really two ways to find out what a customer will pay for something: watch what they actually do across your sales history, or ask them directly. Reading elasticity from sales history is the first approach, it's precise and grounded in real behavior, but it requires that behavior to already exist, meaning real orders across some price variation. Asking directly is the second approach, and it works even before a single sale has happened, which is exactly the gap it's built to close.
What the Van Westendorp Method Actually Asks
The method asks a customer four specific questions about one product:
| Question | What it's measuring |
|---|---|
| At what price would this be so cheap you'd doubt its quality? | The lower bound where price starts to feel suspiciously low |
| At what price would this be a bargain, great value for the money? | A price the customer would feel good about paying |
| At what price would this start to feel expensive, but you'd still consider buying it? | The upper edge of what still feels justifiable |
| At what price would this be too expensive to consider buying? | The upper bound where the customer walks away entirely |
Each answer is a single dollar figure, no ranking, no multiple choice, just four prices reflecting how one person perceives the product's value.
How Four Prices From Many People Turn Into One Answer
A single response is just four numbers. The method becomes useful once enough responses accumulate: each question's answers are treated as a curve (the share of respondents who said "too cheap" at or above a given price, the share who said "too expensive" at or below a given price, and so on), and the method finds where specific curves cross. Two crossings matter most: the Optimal Price Point, where the "too cheap" and "too expensive" curves intersect, representing the price the fewest people reject in either direction, and the Indifference Price Point, where "good value" and "getting expensive" cross, representing the price where opinion is most evenly split between a bargain and a stretch. A third pair of crossings defines the acceptable range itself, the Point of Marginal Cheapness and Point of Marginal Expensiveness, the practical floor and ceiling most customers won't reject outright.
How Confident Should You Be in the Result
The math runs on any number of responses above zero, but a result from 3 responses and a result from 30 don't deserve the same trust. Fewer than 5 responses produces no usable read at all. Five to 19 responses gives a low-confidence estimate, worth treating as directional. Twenty or more gives a good-confidence estimate you can lean on with more certainty. This mirrors the same honesty principle already used for elasticity confidence scoring: show the result plainly, but label how much data actually supports it, rather than hiding a thin-data estimate behind a wall until it magically becomes trustworthy.
Where This Beats Reading Sales History
The clearest case is a brand-new product with no sales history yet, where elasticity simply can't be calculated because there's no price-and-quantity variation to read. A short survey sent to a beta list, a social audience, or even a handful of existing customers gives you a real, if early, read on acceptable pricing before you've committed to a launch number. It's also useful for validating a price increase before you make it, or for checking a new product line against customer expectations before it's built.
Why It's Not a Replacement for Elasticity
What people say they'd pay and what they actually pay aren't always the same number. A stated-preference survey asks someone to imagine a hypothetical purchase decision in the abstract, with none of the context, urgency, or comparison shopping that shapes a real one. Elasticity, calculated from actual sales history, reflects what customers did when a real price was in front of them with real money on the line, which is a stronger signal once it exists. This is exactly why the two are kept as separate, side-by-side readings rather than merged into one blended number, they're answering related but genuinely different questions, and collapsing them into a single score would hide which kind of evidence a given recommendation is actually built on.
How to Actually Run One
From a product's page, generate a shareable survey link, no account or login required for the customer to respond. Share it however you already reach customers, an email you're already sending, a social post, a QR code on packaging, since Zorin doesn't send survey invitations itself or collect an email list from responses. Each response is just four price fields, no name, email, or IP address stored alongside it, so the response data itself carries no customer PII. Once at least 5 responses come in, a chart appears showing the acceptable range and the two key price points, with the confidence label updating as more responses arrive.
A Practical Sequence
- Generate a survey link for a product you're genuinely unsure about, a new launch, a planned increase, or an established item you've never validated.
- Share it somewhere real customers will actually see it, an existing email list, a social audience, or a QR code, rather than only internal team members.
- Wait for at least 5 responses before reading anything into the result, and treat 5 to 19 as directional rather than final.
- Compare it against elasticity if you have sales history for the product too. Agreement between the two is a strong signal; disagreement is worth investigating rather than picking one arbitrarily.
- Use the result as a starting anchor, especially for a new product, then let real sales data take over once it exists.
If you haven't calculated your own catalog's elasticity from actual sales yet, here's how that side of the picture works. And if you're pricing something with no sales history at all, connect your store and generate a survey link for it directly from the product page.
Frequently Asked Questions
How do I know what price my customers are willing to pay?
Two ways: read elasticity from your own sales history if you have it, or ask directly with a short four-question survey (the Van Westendorp Price Sensitivity Meter), which works even with zero sales history.
What is the Van Westendorp Price Sensitivity Meter?
A pricing research method that asks customers four questions about a specific product, too cheap, good value, getting expensive, too expensive, and calculates an acceptable price range and an optimal price point from the answers.
Can I use this before I have any sales?
Yes. Unlike elasticity, which requires real price-and-quantity history to calculate, a price sensitivity survey works from customer responses alone, making it useful for a brand-new product with no sales yet.
How many responses do I need before I can trust the result?
Fewer than 5 gives no usable read. 5 to 19 gives a low-confidence estimate worth treating as directional. 20 or more gives a good-confidence estimate you can lean on with more certainty.
Does this replace calculating elasticity from my sales history?
No. It measures what customers say they'd pay, elasticity measures what they actually did when a real price was in front of them. They're different signals worth reading side by side, not merged into one number.
Does the survey collect customer emails or personal information?
No. A response is just four price answers, with no name, email, or IP address stored alongside it. The survey link itself doesn't require the customer to log in or create an account.
What do I do if the survey result and my elasticity estimate disagree?
Treat it as worth investigating rather than picking one arbitrarily. Stated and revealed preference can diverge for real reasons, worth understanding before committing to a price either result alone would suggest.
Reading your own sales history tells you what customers actually did. A short, direct survey tells you what they say they'd accept, and it works even before you have any sales to read. Neither replaces the other. Used together, they give you a fuller, more honest picture than either signal alone.
Written by Dexter
Dexter is part of the team at Zorin, building tools that help ecommerce merchants price with data instead of guesswork.