Before you publish a price. Ideally after you've talked to 20+ people in your buyer segment. If you've been agonizing over whether to charge $29, $49, or $99/mo and you don't have hard data, run this before you ship the pricing page.
How to apply Van Westendorp Price Sensitivity Meter
- 1
Recruit respondents from your actual buyer segment
This only works if the people answering would plausibly buy. Not your friends, not your Twitter followers. People in the target ICP. 30+ respondents is the floor for any signal; 100+ is where the curves stabilize. If you can't get 30 people in your target ICP to take a 4-question survey, your validation problem is bigger than pricing.
- 2
Ask the 4 core questions (exact wording matters)
1. At what price would you consider this product **too expensive**. So expensive you would not consider buying it? 2. At what price would you consider this product **expensive, but still worth considering**? 3. At what price would you consider this product a **bargain. A great buy**? 4. At what price would you consider this product **so cheap that you would question the quality**? Use the product's real name, a one-line description, and force a single-number response (not a range). Anchors ruin results. No 'here are typical prices' preamble.
- 3
Plot 4 cumulative curves
For each question, plot the cumulative percentage of respondents at each price point. 'Too expensive' and 'cheap. Bargain' cross at the Optimal Price Point (OPP). 'Too expensive' and 'so cheap as to be suspect' cross at the Point of Marginal Cheapness (PMC). 'Expensive but worth it' and 'bargain' cross at the Indifference Price Point (IPP). 'Too expensive' and 'so cheap as to be suspect' define the Acceptable Price Range.
- 4
Read the range, not a single number
Van Westendorp produces a range (PMC → OPP → IPP), not a magic price. Price somewhere in that range based on your brand positioning (premium = higher end, value = lower end). Outside the range you'll either leave money on the table or scare off the market.
- 5
Triangulate with actual willingness to pay
Van Westendorp captures *stated* preferences. Always cross-check with *revealed* preferences: run a pricing A/B test, or better yet, do a Wizard-of-Oz pre-sale at 2 prices to a split audience. Real credit cards beat survey answers every time.
Why founders get pricing wrong
Most founders price their product one of three ways: (1) what the closest competitor charges (lazy), (2) what feels right (worse), (3) what the founder wishes they could charge (worst). Van Westendorp exists because none of those are pricing strategies. They’re guesses wearing professional clothing.
The framework works because it doesn’t ask “what would you pay?” (a terrible question that gets useless answers). It asks four specific questions that triangulate the boundary between cheap-enough-to-be-suspect and expensive-enough-to-be-out. The answer emerges from the overlap.
Worked example: SaaS pricing for a scheduling tool
Product: a calendar scheduling tool for freelancers.
Respondents: 80 freelancers recruited via targeted Reddit + LinkedIn (filtered to people who charge for their time).
The 4 questions (asked in randomized order):
- At what monthly price would this scheduling tool be so expensive that you would not consider buying it?
- At what monthly price would it be expensive, but you would still consider buying it?
- At what monthly price would it be a bargain. A great buy for the money?
- At what monthly price would it be so cheap that you would question the quality?
Illustrative results (plotted as cumulative curves):
- Point of Marginal Cheapness (PMC): $7/mo. Below this, respondents doubt the quality
- Optimal Price Point (OPP): $14/mo. Intersection of “too expensive” and “bargain”
- Indifference Price Point (IPP): $19/mo. Intersection of “expensive but worth it” and “bargain”
- Ceiling: $29/mo. Where “too expensive” hits 50%+
Defensible range: $7–$29. Recommended: $14–$19.
A founder who launched this tool at $9/mo “to seem cheap” would leave 50–100% of their ARR on the table. A founder who launched at $39/mo because their competitor was $35 would lose half their addressable market. The range tells you where to play; your brand positioning tells you where in the range.
The 5-minute version
If you don’t have a survey tool and just need a quick read: ask 10 people in your ICP the 4 questions via DM, average the numbers, and use that as a starting hypothesis. Not precise, but a 10-person directional read beats a 0-person guess.
ShipFit and Van Westendorp
ShipFit applies Van Westendorp at the “How to Charge” stage of the 9-question flow. Feed in your buyer and product description, and the tool produces a starter range with reasoning. If you have real survey data, you input it; if you don’t, you get a first-pass range to validate. Either way, you leave with a price you can defend. Not one you pulled out of a hat.
Further reading
- Peter van Westendorp, NSS. Price Sensitivity Meter (PSM), ESOMAR Congress, 1976 (original paper)
- The Mom Test. The framework you use before Van Westendorp, to make sure you’re pricing something people actually need
- Jobs to be Done. Pairs with Van Westendorp to understand what your buyer is paying for vs. what your product does
Common mistakes
- Anchoring the respondent. Saying 'similar products cost $49/mo' before asking the questions. Never do this; anchors contaminate every answer.
- Asking in ranges. 'between $20–$40' responses break the cumulative-curve math. Force a single number.
- Surveying friends or general audiences. You need people in your actual ICP, or the curves are meaningless.
- Reading a single price point from the chart. Van Westendorp produces a range, not a single answer. If your CEO wants one number, pick the Optimal Price Point (OPP) and own it.
- Using Van Westendorp alone. It's stated preference. Pair it with actual conversion data from a test price.
- Assuming it scales to enterprise pricing. Van Westendorp works cleanly up to ~$500/mo decisions. Enterprise procurement is a different animal with value-based pricing, multi-stakeholder budgets, and negotiated terms.
How ShipFit operationalizes this
ShipFit's 'How to Charge' stage uses Van Westendorp as the default pricing framework. You input your target buyer, product description, and (optionally) survey results. ShipFit produces a defensible price range with the reasoning written out. If you don't have survey data yet, the tool generates a buyer-appropriate starter range from your product concept and asks you to validate it against real respondents before launch. Either way, you exit with a price and a 'why' you can defend to a skeptical advisor.
ShipFit runs 55 frameworks across 9 decision stages
Van Westendorp Price Sensitivity Meter is one tool in a bigger toolkit. The full library covers market sizing, buyer discovery, MVP scoping, pricing, and launch.
The Mom Test
Q3Rob Fitzpatrick
Validation question methodology — real interviews, not theater
Jobs-to-be-Done
Q2-Q4Clayton Christensen
Functional, social, and emotional jobs your product fulfills
7 Powers
Q4Hamilton Helmer
Strategic moats: Scale, Network, Counter-positioning, Switching, Brand, Cornered Resource, Process
Van Westendorp PSM
Q6Feature-weighted price sensitivity analysis without guessing
Blue Ocean Strategy
Q4Kim & Mauborgne
ERRC framework: Eliminate, Reduce, Raise, Create
Fake Door Testing
Q7Pre-build behavioral validation with landing pages and apology modals
+ 49 more: TAM/SAM/SOM Analysis, Porter's Five Forces, Market Timing Analysis, Unit Economics (LTV/CAC)...
Frequently asked questions
How many respondents do I need for Van Westendorp to be meaningful?
Can I run Van Westendorp on Twitter / Reddit / LinkedIn?
What if my respondents don't know what the product is?
Does Van Westendorp work for one-time purchases vs. subscriptions?
My Van Westendorp range came back huge ($9–$99). What now?
Is Van Westendorp still the best pricing framework in 2026?
How does Van Westendorp compare to A/B price testing?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.
Jobs to be Done reframes every product decision: customers don't buy features, they hire products to get a job done. Here's how to apply it without faking it.
Most founder market research is a TAM slide that nobody believes. The numbers that actually matter are smaller, harder to defend, and tell you whether the market exists for the ten-customer version of your business.
Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.
Does each customer make you money? Or cost you money?
Run nine framework-backed decisions in order before writing code: define the buyer, prove the pain is painful, name the winning angle, scope V1 to the smallest test of the hypothesis, get behavioral evidence (paid pre-orders, signed letters of intent, or credit cards on file from a Fake Door Test), then ship. Most failed startups skipped at least three of those nine. Plan to spend two to four weeks on this. It saves six to nine months of building the wrong thing.
For indie hackers who've wasted months on dead ideas. ShipFit forces 9 decisions before you write a line of code. Proven frameworks, exports to Cursor.
If you want a conversation partner, Buildpad. If you want to stop researching and ship, ShipFit. Both solve different problems for different founders. Don't pick on hype.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.