What is Price Sensitivity? (And What is a Price Sensitivity Meter?)

Written by Arnon Shimoni
✓ Expert
Last updated on:
Price sensitivity is how strongly a buyer's purchase behaviour reacts to a change in price. High sensitivity means a small increase costs you a lot of demand. Low sensitivity means you can move the price without losing much. It's the qualitative concept; price elasticity is its quantitative measurement.
A price sensitivity meter is a specific research instrument, not a general category: the Van Westendorp Price Sensitivity Meter, a four-question survey published in 1976 that produces a range of acceptable prices. If you came here looking for that, it has its own page.
Field | Detail |
|---|---|
Also known as | Price responsiveness, demand sensitivity |
Quantified as | |
Measured by | Van Westendorp PSM, Gabor-Granger, conjoint, price tests, transaction analysis |
Classic driver framework | The nine "effects" from Nagle and Holden's The Strategy and Tactics of Pricing |
High sensitivity signals | Many substitutes, easy comparison, low switching cost, large budget share |
Low sensitivity signals | Few substitutes, hard comparison, high switching cost, someone else pays |
Varies by | Segment, use case, deal size, buyer role, contract stage |
Common misreading | Assuming a loud objection means high sensitivity. Often it's a negotiation tactic |
The nine effects that drive price sensitivity
Nagle and Holden's Strategy and Tactics of Pricing lays out nine factors that move price sensitivity up or down. It's the most useful diagnostic list in pricing, because each effect maps to something you can actually change.
Reference price effect. Sensitivity rises with the number of perceived alternatives the buyer knows about. If they've seen three competitors' pricing pages this week, your price is being judged against them whether you like it or not.
Difficult comparison effect. Sensitivity falls when buyers can't easily compare offers. This is why so many enterprise vendors hide pricing, and why "contact sales" survives despite everyone claiming to hate it. It's also why per-unit pricing across incompatible units (per seat vs per workflow vs per credit) suppresses sensitivity: the buyer can't do the arithmetic quickly.
Switching cost effect. Sensitivity falls as the cost of changing rises. Migration effort, integration work, retraining, and data lock-in all reduce a customer's reaction to your renewal increase. This effect is why billing and infrastructure vendors can raise prices on existing accounts more easily than they can win new ones.
Price-quality effect. Sensitivity falls when a high price signals quality or exclusivity. In B2B software this cuts both ways: too cheap and procurement assumes you can't be serious. The Van Westendorp "too cheap" question exists precisely to measure this.
Expenditure effect. Sensitivity rises with the absolute size of the spend, and with its share of the buyer's budget. A €500/month tool gets waved through. A €500k/year contract gets a committee.
End-benefit effect. Sensitivity falls when your product is a small part of a much larger benefit the buyer cares about. Nobody haggles hard over the fraud tool that protects a €400m payment flow. This is the strongest lever most B2B companies have, and it's a positioning decision rather than a pricing one.
Shared-cost effect. Sensitivity falls when someone else pays. Corporate cards, departmental budgets, cloud credits from a hyperscaler, and pass-through billing to end customers all dampen reaction to price.
Fairness effect. Sensitivity rises when the price seems unfair relative to a reference the buyer has in mind. This is why per-seat price increases for a product the team already uses land badly, and why usage-based bills that spike without warning generate churn out of proportion to the amount.
Framing effect. Sensitivity depends on how the price is presented. A charge framed as a loss (an overage penalty) hurts more than the same money framed as a forgone gain (unused included volume). €0.008 per call and €8 per thousand calls are the same price and don't feel the same.
Three of these are levers you control directly: comparison difficulty, framing, and end-benefit positioning. Two of them (fairness and framing) are mostly about how the bill reads, which puts them squarely in the domain of your invoicing and billing portal rather than your pricing page. That's a less glamorous place to find pricing power, and it's real.
Price sensitivity vs price elasticity
They're often used interchangeably, and the distinction is worth keeping.
Price sensitivity | Price elasticity | |
|---|---|---|
Nature | Qualitative concept | Quantitative measurement |
Expressed as | High, low, moderate; a set of drivers | A number, e.g. -1.4 |
Answers | Why do buyers react the way they do? | By how much does demand move? |
Source | Judgment, research, the nine effects | Historical data or an experiment |
Useful for | Positioning, packaging, framing decisions | Modelling a specific price change |
You use sensitivity to reason about why a segment behaves the way it does, and elasticity to model what a particular move costs you. Companies that only have elasticity numbers make correct predictions about a market they don't understand. Companies that only have sensitivity narratives make confident arguments about numbers they've never checked.
Measuring price sensitivity
Before you have customers. Van Westendorp for a credible range, Gabor-Granger for a demand curve, conjoint if the question involves packaging. All three are stated preference and all three run high.
Once you're selling. Your own data is better than any survey. Four things to look at, roughly in order of signal quality:
Discount distribution. Where reps land relative to list, by segment and deal size. Deep, consistent discounting in a segment means high sensitivity there, or a list price that was never right.
Win/loss reasons. Price-cited losses are noisy (price is the polite reason for a lot of losses that were really about something else), so weight them by what the deal actually did next. A prospect who cited price and then bought a more expensive competitor was not price sensitive.
Conversion by price band. For self-serve, straightforward. For sales-led, look at quote-to-close by quoted amount.
Churn and downgrade following price changes. The most honest measurement you'll get, and the most expensive to obtain.
Deliberately. Price A/B tests in self-serve motions, or quoting a higher price to a defined slice of new business. The discipline that separates a test from a guess: instrument to retention, not to conversion. A price test measured on conversion alone will recommend cutting the price every time, because lower prices convert better and the customers you win that way churn later, outside your measurement window.
Price sensitivity in usage-based and AI pricing
Consumption pricing rearranges the picture, mostly because the buyer isn't reacting to a price, they're reacting to a bill they can't fully predict.
Sensitivity to the rate is lower than sensitivity to the bill. Buyers rarely push hard on a per-unit rate they can't convert into a monthly number. They push extremely hard on an invoice that came in 40% above last month. The framing and fairness effects dominate. This is why spend alerts, caps, and mid-cycle visibility do more for retention than a rate cut does.
Overage rates are where sensitivity concentrates. An overage charge is framed as a penalty, so it's evaluated as a loss, so it hurts more than the same money charged as base fee. Vendors who price overage aggressively on the theory that "customers who overage are getting more value" reliably discover the fairness effect the hard way. See overage charges.
Sensitivity rises sharply at renewal for usage products. By renewal the customer has 12 months of their own consumption data and can compute a blended per-unit cost. The difficult-comparison effect that protected you at signing has evaporated. Anyone selling consumption pricing should assume renewal is a genuine repricing event, not a formality.
In AI, the reference price moves under you. Model provider rate cards change, and buyers who follow them recalculate what your margin must be. The reference price effect is unusually live in this category. There's no clever fix, only the ability to reprice fast enough to stay ahead of it, which is a systems question more than a strategy one. More in there is no AI pricing playbook.
Related terms
Frequently asked questions
What is price sensitivity?
How strongly buyers change their behaviour when price changes. It's the qualitative version of the concept that price elasticity measures numerically.
What is a price sensitivity meter?
The Van Westendorp Price Sensitivity Meter, a 1976 survey technique using four open-ended price questions to identify a range of acceptable prices. It's a specific instrument rather than a general category of tool.
What's the difference between price sensitivity and price elasticity?
Sensitivity is the concept and its drivers. Elasticity is the measurement, expressed as a number. You use sensitivity to reason about behaviour and elasticity to model a specific change.
What makes buyers less price sensitive?
Few known alternatives, difficult comparison, high switching costs, a small share of their budget, someone else paying, and your product being a small input to a benefit they care a lot about.
Are B2B software buyers price sensitive?
Less than most vendors assume, and unevenly. Enterprise buyers with high switching costs and shared budgets are relatively insensitive; SMB self-serve buyers spending their own money are quite sensitive. Treating your market as one population hides both facts.
How do I measure price sensitivity without running a survey?
Look at discount distribution by segment, quote-to-close by quoted amount, win/loss reasons weighted by what the prospect actually did next, and any churn or downgrade following past price changes. All of it is already in your CRM and billing system.
Does high price sensitivity mean I should lower prices?
Not on its own. It means a price increase costs you more demand than it would elsewhere. Whether to cut depends on your margin, capacity, and whether the volume you'd gain retains. Lower prices reliably improve conversion and often worsen the customer base.
What is the fairness effect?
Buyers react to whether a price seems fair relative to a reference they hold, separately from whether it's affordable. It's why unexplained increases and surprise overage charges generate reactions out of proportion to the amount involved.
Why do overage charges feel more expensive than base fees?
Framing. An overage is presented as a penalty for exceeding a limit, so it's processed as a loss. The same money inside a base fee is processed as part of a purchase. Identical amounts, different reactions.
Does price sensitivity change over the customer lifecycle?
Substantially. It's highest at first purchase, drops as switching costs accumulate, and rises again at renewal, especially for usage-based products where the customer now has their own consumption data and can compute a blended rate.
How does price sensitivity affect packaging?
Difficult comparison lowers sensitivity, so packaging that doesn't map cleanly onto a competitor's makes buyers less price-reactive. This is a real effect and it degrades trust if you push it, so treat it as a constraint rather than a strategy.
Can I reduce price sensitivity without changing my price?
Yes, and it's usually the cheaper move. Reposition against a larger end benefit, reduce comparison ease through differentiated packaging, raise switching costs through integrations and workflow depth, and reframe how charges appear on the invoice.
Educational reference. A meaningful share of price sensitivity in usage-based products lives in how the bill reads: predictability, alerts, and whether the customer can see their spend before the invoice arrives. Solvimon runs metering, rating, and invoicing on one ledger so that's a setting rather than a project. See pricing methodology.
Ready for billing v2?
Solvimon is monetization infrastructure for companies that have outgrown billing v1. One system, entire lifecycle, built by the team that did this at Adyen.







