Purpose
Determine the acceptable price range and optimal price point for a product by asking potential customers four carefully sequenced pricing questions—producing intersection curves that reveal where prices become “too cheap” (quality doubt), “cheap” (bargain), “expensive” (acceptable premium), and “too expensive” (purchase refusal).
The Van Westendorp PSM addresses A4.2's central pricing challenge: what price should we test in pilot? The method extracts willingness-to-pay directly from customer responses rather than relying on competitor-matching or cost-plus calculation, producing an empirically grounded price range for A4.3 pilot launch.
When to Use
Use the Van Westendorp PSM when:
- Determining initial pricing for a new product or service (A4.2).
- Validating whether assumed pricing from A4.1 aligns with customer perception.
- Comparing price sensitivity across customer segments.
- Setting the price range for subsequent conjoint analysis (the referenced method).
Do NOT use when:
- The product is not yet defined—respondents need to understand what they are pricing. Complete A3 first.
- Precise price optimisation is needed—Van Westendorp provides ranges, not exact optimal prices. Use conjoint analysis for precision.
- The market has established price anchors (commodity products)—customers will default to known prices. Use competitive analysis instead.
- B2B enterprise sales where procurement processes determine pricing—use customer development interviews (the referenced method) with decision-makers.
Sample Size and Duration
- Respondents: 50–200 per customer segment (minimum 50).
- Survey design: 2–4 hours.
- Data collection: 1–2 weeks.
- Analysis: 4–8 hours.
- Total: 2–3 weeks end-to-end.
Prerequisites
- Product description or demo from A3 prototype (respondents must understand the offering).
- Target customer segment defined (from A4.1 Business Model Canvas).
- Survey tool (Qualtrics, Typeform, Google Forms).
- 50–200 respondents from target segment (minimum 50 for reliable curves).
- Statistical analysis tool (Excel, R, Python) for curve plotting.
- Time: 1–2 weeks for survey design, distribution, and analysis.
Complete Procedure
Step~1: Survey Design (2–4 hours)
Present respondents with a clear product description (including features, benefits, and comparison to alternatives). Then ask four questions in this exact sequence:
- Too Cheap: “At what price would you consider this product so inexpensive that you would question its quality?”
- Cheap (Bargain): “At what price would you consider this product a bargain—a great buy for the money?”
- Expensive (Getting Expensive): “At what price would you consider this product starting to get expensive—so that it is not out of the question, but you would have to give some thought to buying it?”
- Too Expensive: “At what price would you consider this product so expensive that you would not consider buying it?”
Step~2: Data Collection (1–2 weeks)
Distribute survey to ≥50 respondents from target segment. Use open-ended price fields (not multiple choice)—respondents must generate their own price points. Screen for consistency: Too Cheap ≤ Cheap ≤ Expensive ≤ Too Expensive.
Step~3: Curve Construction
For each question, compute the cumulative frequency distribution:
- Too Cheap: Plot cumulative % who say “too cheap” at each price (descending—high % at low prices).
- Cheap: Plot cumulative % (descending).
- Expensive: Plot cumulative % (ascending—high % at high prices).
- Too Expensive: Plot cumulative % (ascending).
Step~4: Identify Intersection Points
The four curves produce key price points:
| p4cmp4cm Intersection | Name | Meaning |
|---|---|---|
| Too Cheap Expensive | Point of Marginal Cheapness (PMC) | Floor of acceptable range |
| Cheap Too Expensive | Point of Marginal Expensiveness (PME) | Ceiling of acceptable range |
| Too Cheap Too Expensive | Optimal Price Point (OPP) | Minimal purchase resistance |
| Cheap Expensive | Indifference Price Point (IDP) | Equal “cheap” and “expensive” perception |
The acceptable price range is PMC to PME. The optimal price point (OPP) is where the fewest customers object to the price.
Step~5: Interpret and Decide
- If A4.1 assumed price falls within PMC–PME range: pricing assumption validated. Proceed with A4.3 pilot at or near OPP.
- If A4.1 assumed price falls outside range: pricing assumption invalidated. Adjust pricing or reconsider unit economics (the referenced method).
- Segment analysis: run Van Westendorp separately per customer segment—price sensitivity often differs significantly.
Quality Criteria
- Sample adequacy: ≥50 respondents per segment.
- Clear product description: Respondents understood what they priced.
- Consistency screening: Responses where Too Cheap > Cheap removed.
- Segment-specific: Separate analysis per customer segment.
- Contextualised: Results compared to A4.1 assumptions and competitor pricing.
Theoretical Foundation
Seminal references
- Introduced the four-question framework at the 1976 ESOMAR Congress. Demonstrated that plotting cumulative distributions of the four responses yields four intersection points defining the acceptable price range and optimal price.
Contemporary references
- Included the Van Westendorp PSM as a recommended pricing experiment for business model validation, positioning it alongside conjoint analysis and A/B price testing.
Challenges and Solutions
Challenge~1: Hypothetical Bias
Symptoms: Respondents state willingness-to-pay higher than actual purchase behaviour.
Solutions: Treat Van Westendorp as directional, not definitive. Complement with A/B pricing tests (the referenced method) using real purchase decisions in A4.3 pilot.
Challenge~2: Narrow Range
Symptoms: PMC and PME very close together—almost no acceptable range.
Solutions: This signals strong market price anchoring. Consider differentiation (feature bundling, premium positioning) to expand acceptable range, or accept market-dictated pricing.
Challenge~3: Segment Conflation
Symptoms: Mixed segments produce wide, meaningless ranges.
Solutions: Always segment analysis. Run PSM per customer segment and analyse separately—this often reveals distinct pricing tiers.
Relationship to Other Methods
Van Westendorp PSM receives input from:
- Business Model Canvas (the referenced method)—pricing assumptions to validate.
- Value Proposition Canvas (the referenced method)—value perception informing what respondents are pricing.
Van Westendorp PSM provides input to:
- Conjoint Analysis (the referenced method)—acceptable price range constrains conjoint price levels.
- Unit Economics Modelling (the referenced method)—validated pricing feeds revenue assumptions.
- A/B Testing (the referenced method)—PSM range guides A/B test price variants.
Example: C001 Smart Checkout — A4.2 Pricing Validation
Context: A4.1 assumed 7.99/month. A4.2 Van Westendorp study with n=120$ returning e-commerce customers.
Results:
| p3cm Intersection | Price |
|---|---|
| Point of Marginal Cheapness (PMC) | $4.99 |
| Indifference Price Point (IDP) | $7.49 |
| Optimal Price Point (OPP) | $6.99 |
| Point of Marginal Expensiveness (PME) | $11.99 |
Interpretation: A4.1 assumed 7.99 falls within the acceptable range (4.99–11.99) but above the OPP (6.99). Recommendation: pilot at 6.99 for maximum adoption, with A4.3 A/B test of 6.99 vs. $7.99 to measure price elasticity.
Tools and Templates
- Survey: Qualtrics, Typeform, Google Forms.
- Analysis: Excel (cumulative distribution charts), R (pricesensitivitymeter package), Python (matplotlib).
- Visualisation: Line chart showing four curves with intersection points annotated.
- D. J. Bland & A. Osterwalder (2020). Testing Business Ideas. Wiley.
- P. H. van Westendorp (1976). NSS Price Sensitivity Meter (PSM) — A New Approach to Study Consumer Perception of Prices. In Proceedings of the 29th ESOMAR Congress.
Share how you use Van Westendorp Price Sensitivity Meter
This is where practitioners will be able to share field notes, variations, and additional templates for this method — what worked, what to watch for, and adaptations for different contexts.
Until the community space opens, we welcome contributions by email and will fold the best into the method page.