Van Westendorp price sensitivity explorer

Use this tool with the saas pricing guide. The useful result is a transparent working calculation or statement whose assumptions can be inspected.

Your inputs stay in this browser. Example values are constructed, not market data.

Survey rows: too cheap, cheap, expensive, too expensive 10,20,45,70 15,25,50,80 10,30,55,90 20,35,60,100 15,30,50,85 20,40,65,110 10,25,45,75 15,35,55,95 Calculate from this sample

Prepare the inputs

Enter one respondent per line with four nonnegative prices in order: too cheap, cheap, expensive, too expensive. Use the same defined offer and currency for every response. Five rows are enough to demonstrate the tool, not to establish a representative sample.

Keep the source and scope beside the inputs. If you are practicing without real evidence, label the case as illustrative. Do not add private customer or employee identifiers; the calculation does not need them.

Method and interpretation

At each observed price, too-cheap and cheap curves count thresholds at or above that price; expensive and too-expensive curves count thresholds at or below it. Crossings between observed prices use linear interpolation. A flat equality is reported as a range rather than false precision.

The output cannot repair an unrepresentative sample, an unclear offer or inconsistent definitions. Before sharing a conclusion, explain where the inputs came from and what population or customer situation they describe.

Validate the next decision

Use the related worksheet or research guide to record the evidence. Identify the assumption most likely to change the result and test it before making a larger commitment. A useful planning tool makes uncertainty visible instead of replacing it with a precise-looking number.

Further methodology reading

Qualtrics explains the four-question price sensitivity approach. Survey perceptions should be followed by validation in the actual buying context.

Related reading

• SaaS Pricing Models Compared
• How to Choose a Value Metric
• Usage Based Pricing for SaaS
• Good Better Best Packaging for SaaS
• How to Raise SaaS Prices

Browse all calculators and working resources for related tasks.

Apply van westendorp price sensitivity explorer in a working review

Record the source and unit of every input before using the result. Change one assumption at a time to understand which inputs matter most. Keep outputs that describe money, time and percentages distinct, and preserve undefined cases rather than converting them into plausible-looking zeroes.

For this topic, involve the pricing owner with finance, product and customer-facing input and work from offer scope, charging unit and scenario assumptions. The relevant unit is a defined customer segment and comparable commercial offer. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

Evidence to prepare

A price is meaningful only with its package, quantity, terms and serving requirements. Test whether buyers can predict the bill and whether the charging unit supports useful adoption. Keep willingness-to-pay statements separate from observed purchasing behavior.

Two situations that can change the interpretation

When pricing research ignores the respondent segment

A solo user’s reaction to a simple tool should not directly set the price of an enterprise deployment with different requirements.

Use this check: Record the respondent’s relevant workflow, purchase role and offer context. A stated price reaction is not the same as observed purchasing behavior.

The focused diagnostic guide provides the correction process and a working evidence sheet.

When the pricing model ignores assisted delivery

A product that needs repeated specialist intervention may have different economics from a self-serve offer at the same advertised price.

Use this check: Estimate the actual support, implementation and maintenance effort for comparable cohorts. Do not treat every employee hour as removable cash cost.

The focused diagnostic guide provides the correction process and a working evidence sheet.

Record the decision and the limit

An account may object to price because the required integration or implementation support is unclear. Discounting without resolving that concern can create a lower-priced failure. Compare the complete offer and the customer’s actual alternatives before treating every objection as a request for a concession.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the complete topic collection for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.