Run a price sensitivity analysis end to end: pick the right method, build the survey, read the results, and turn them into a pricing decision.
Summary:
Knowing that a product is "price sensitive" isn't the same as knowing what to do about it. A price sensitivity analysis only earns its place in a pricing decision when it goes all the way through: picking the right method for your situation, fielding a survey that produces clean data, reading the results correctly, and translating them into a specific number your team can commit to.
This guide walks through that full sequence. If you need a primer on what price sensitivity is and what drives it, see understanding price sensitivity and its impact on consumers first. This guide picks up where that one leaves off: execution.
Three methods cover most pricing situations, and picking the wrong one wastes a research cycle.
Price sensitivity data from people who wouldn't realistically buy the product tells you very little about your actual market. Screen for category familiarity and purchase intent before respondents reach the pricing questions, and segment your sample by the customer types you price differently for, since price sensitivity often varies sharply between segments.
Whichever method you choose, keep the pricing question sequence on its own section of the survey, separate from satisfaction or feature questions.
Mixing pricing questions into a longer survey introduces context effects that skew the results, since a respondent's answer to a price question can shift depending on what they just answered before it.
If you're not using Van Westendorp or Gabor-Granger's built-in analysis, calculate baseline price sensitivity directly: percentage change in quantity demanded divided by percentage change in price.
A result greater than 1 in absolute value means demand is elastic (sensitive to price); a result closer to 0 means demand is inelastic.
Run this calculation per segment, not just in aggregate, since an average across segments can mask a highly sensitive group being offset by an insensitive one.
For Van Westendorp, plot the four cumulative frequency curves to find the point of marginal cheapness, the point of marginal expensiveness, and the indifference price point.
For Gabor-Granger, plot the demand curve and identify where cumulative willingness to buy drops off sharply.
Either way, you're looking for the specific price, or narrow range, where the data stops supporting a higher number.
A price sensitivity analysis that ends at "customers are somewhat price sensitive" hasn't finished its job.
Convert the output into a specific number or range, note which segment it applies to, and flag any segment where the data was too thin to draw a confident conclusion.
Price sensitivity shifts with the broader market, competitor moves, and your own product changes. Treat the analysis as a snapshot with a shelf life, not a permanent answer, and rerun it when a major pricing decision is on the table again.
For a direct price sensitivity check outside of the Van Westendorp or Gabor-Granger frameworks, consider:
Every method plots the same two axes: price on the x-axis, and acceptance or demand on the y-axis. What differs is the shape of the line and where you look for the signal.
Van Westendorp
Four lines cross at several points. Two crossings matter most:
| Crossing point | What it marks |
| Point of marginal cheapness | Lower edge of your acceptable pricing range |
| Point of marginal expensiveness | Upper edge of your acceptable pricing range |
Together, these two points define your acceptable pricing range.
Gabor-Granger
A single downward-sloping line shows cumulative willingness to buy at each price point. The steepest drop on that line usually marks the price where you're most at risk of losing volume from a marginal price increase.
Running this analysis end to end—not just gathering the data—matters because pricing decisions made on partial information tend to get revisited within a year, at real cost to revenue and internal credibility.
A completed price sensitivity analysis gives a pricing committee two things:
Without it, you're left defending pricing with "customers seem okay with it," not a position that holds up under scrutiny.
These four mistakes show up most often once teams move from running the analysis to acting on it. Watching for them keeps the number you land on defensible.
| Mistake | Why it matters |
| Stopping at the raw chart without a recommendation | A demand curve or Van Westendorp plot is an input, not a decision. Someone still has to translate it into a specific price and document the reasoning. |
| Analyzing the full sample without segmenting | Price sensitivity nearly always differs by segment. An aggregate number can hide a segment that's far more sensitive than the average suggests. |
| Letting product enthusiasm bias the description respondents see | An oversold description inflates stated willingness to pay in ways that won't hold up post-launch. Keep descriptions factual. |
| Treating the analysis as permanent | Results reflect market conditions at the time of the study. Competitor pricing changes, inflation, and shifts in your own product all move the number over time. |
If you're running this analysis across multiple customer segments in one survey, use branching logic so each segment sees pricing questions calibrated to their likely price range — not one generic ladder for everyone.
How it works:
Why it's worth setting up:
Price sensitivity is the broader concept: how much price matters to a buyer's decision. Price elasticity of demand is the specific, calculated measure of that sensitivity, expressed as the ratio of the percentage change in quantity demanded to the percentage change in price.
Van Westendorp if you need a price range for a new or repositioned product and don't yet have a specific number in mind. Gabor-Granger if you already have a small set of candidate prices and need to know which one maximizes revenue.
At least 100 completed responses per segment you plan to analyze separately. Below that, the resulting curve tends to carry too much noise to support a confident pricing decision.
Historical sales data can approximate price elasticity if you have enough price variation in your own sales history to work with. Most companies don't have that variation, which is why a survey-based method is the more common starting point.
Fielding the survey is the fastest way to move from method selection to a real answer. Start from a pricing survey template and adapt it to the method you chose above, then use SurveyMonkey Audience if you need a screened, targeted panel to reach the segments your analysis depends on.

SurveyMonkey can help you do your job better. Discover how to make a bigger impact with winning strategies, products, experiences, and more.

A target market is the group likely to buy your product. Learn how to identify yours using demographics and behavioral traits to boost conversions.

Learn the difference between consumer, market, and customer segmentation. Discover how to target the right buyers before you have a customer base.

See real product bundling examples across SaaS, retail, and B2B, what makes each one work, and how to validate a bundle before you launch it.