# Van Westendorp price sensitivity explorer > Explore four stated-price response distributions from a survey sample. The tool calculates explicitly labelled curve crossings and preserves flat crossings as ranges. These describe price perceptions, not a profit-maximizing price or guaranteed purchase behavior. Source: https://saas-marketing.net/calculators/van-westendorp-analyzer/ Topic: SaaS Pricing Type: calculator Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/calculators/van-westendorp-analyzer/ ## Short answer Explore four stated-price response distributions from a survey sample. The tool calculates explicitly labelled curve crossings and preserves flat crossings as ranges. These describe price perceptions, not a profit-maximizing price or guaranteed purchase behavior. ## Key takeaways - 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. - 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. - Inputs are processed in your browser and are not submitted with lead forms. --- Use this tool with the [saas pricing guide](/saas-pricing/). The useful result is a transparent working calculation or statement whose assumptions can be inspected. ## 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](/tools/price-testing-and-research-tools/) 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](https://www.qualtrics.com/articles/strategy-research/van-westendorp-pricing-studies-explained/). Survey perceptions should be followed by validation in the actual buying context. ## Related reading - [SaaS Pricing Models Compared](/guides/saas-pricing-models/) - [How to Choose a Value Metric](/guides/value-metric-pricing/) - [Usage Based Pricing for SaaS](/guides/usage-based-pricing-for-saas/) - [Good Better Best Packaging for SaaS](/guides/good-better-best-packaging/) - [How to Raise SaaS Prices](/guides/saas-price-increases/) Browse [all calculators](/calculators/) and [working resources](/resources/) for related tasks. {/* expanded-practice-2026-09 */} ## 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. | Review field | What to record | | --- | --- | | Topic | Van Westendorp price sensitivity explorer | | Decision | The specific action this explanation should help you choose | | Working evidence | offer scope, charging unit and scenario assumptions | | Unit and scope | a defined customer segment and comparable commercial offer | | Responsible people | pricing owner with finance, product and customer-facing input | | Remaining uncertainty | The missing fact that could change the decision | ### 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](/guides/willingness-to-pay-sample-has-no-segment/) 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](/guides/pricing-model-ignores-support-cost/) 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](/topics/saas-pricing/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied. ## Frequently asked questions ### Does this tool include current market benchmark data? No. It uses only the inputs you provide. Default numbers are constructed examples and must not be presented as industry observations. ### What should I enter? 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. ### How should I interpret the result? 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. ### Are these inputs sent to a server? No. The calculation runs locally in your browser. A separate resource or contact form sends only the information entered into that form and its disclosed attribution fields.