How to run a price sensitivity analysis from method to pricing decision

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.

White outline of Goldie, the SurveyMonkey mascot

Summary:

  • Choose the appropriate analysis method based on your goals: Van Westendorp for price ranges, Gabor-Granger for revenue-maximizing price points, or conjoint analysis for bundled or tiered pricing.
  • Ensure clean, reliable results by screening respondents to match your actual buyers, isolating pricing questions to avoid context-effect bias, and segmenting data by customer type rather than relying on aggregate averages.
  • Treat the analysis as a time-sensitive snapshot and use the results to identify specific price points or ranges that can be defended by the pricing committee.

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.

  • Use the Van Westendorp Price Sensitivity Meter when you need a psychologically acceptable price range for a new or repositioned product.
  • Use the Gabor-Granger method when you need a demand curve and a revenue-maximizing price point for a single product.
  • Use conjoint analysis when price is one of several features you're testing together, such as pricing a bundle or a tiered plan.

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:

  • "How reasonable do you find the current price of [product]?" (1–5 scale)
  • "At what price would you start looking for an alternative to [product]?"
  • "If the price increased by 10%, how likely would you be to continue using [product]?"
  • "What features would justify a higher price for [product]?"

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 pointWhat it marks
Point of marginal cheapnessLower edge of your acceptable pricing range
Point of marginal expensivenessUpper 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:

  • A specific number to defend, backed by a method they can explain
  • A documented baseline, so the next repricing decision starts from real data instead of another round of guessing

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.

MistakeWhy it matters
Stopping at the raw chart without a recommendationA 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 segmentingPrice 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 seeAn oversold description inflates stated willingness to pay in ways that won't hold up post-launch. Keep descriptions factual.
Treating the analysis as permanentResults 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:

  • Ask a qualifying question early (e.g., company size or current spend) to identify the respondent's segment
  • Route each segment to a different starting price point in the sequence — for example, a higher starting price for enterprise respondents than for self-serve respondents in a Gabor-Granger sequence

Why it's worth setting up:

  • Keeps the question sequence relevant to each respondent
  • Shortens the number of price points anyone has to answer through
  • What's the difference between price sensitivity and price elasticity?
  • Which method should I use if I only have time for one?
  • How many respondents does a price sensitivity analysis need?
  • Can price sensitivity analysis be run without a survey?

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.

Two marketing employees, one reviewing a paper with brand strategy, and the other holding a printout of charts

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

A man and woman looking at an article on their laptop, and writing information on sticky notes

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

Smiling man with glasses using a laptop

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

Woman reviewing information on her laptop

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.