What Is Price Elasticity of Demand? Compare It with Price Sensitivity
Price elasticity of demand, price sensitivity, and willingness to pay sound like three ways to describe the same buyer reaction. They are not. Elasticity measures proportional demand response to a price change. Sensitivity is a broad label for price-related attitudes or behavior. Willingness to pay is the maximum amount a buyer would exchange for a specified offer.
Mixing these terms creates false precision. A sales team hears frequent price objections and calls demand elastic. A survey produces a willingness-to-pay answer and the result is treated as a market response curve. A measured elasticity is used to claim the team has found the best price. Each leap asks one kind of evidence to answer a different question.
Elasticity belongs to a particular comparison
OpenStax defines price elasticity of demand as proportional quantity response to a price change, with other relevant demand factors held constant. The estimate belongs to a defined offer, population, price point or interval, and time horizon.
Those boundaries are easy to lose in SaaS. If price changes alongside packaging, product capability, discounts, sales coverage, or the mix of eligible buyers, the difference is not a clean price-only relationship. Response among new prospects does not automatically describe renewals. An estimate over one interval does not describe every other price.
This article focuses on the conceptual boundary rather than repeating the formula. The separate price elasticity of demand framework covers calculation when a decision genuinely needs a bounded PED estimate.
“Price sensitive” often hides the real observation
Teams use the phrase for prospects who mention price, ask for discounts, delay, reduce seats, downgrade, switch, or leave. They also use it when conversion differs across segments or when salespeople believe price is the objection.
That collection includes attitudes, recorded behavior, market outcomes, and internal interpretation. It has no common denominator or comparison. The phrase can be a useful invitation to investigate, but it is not a measure until the team says whose behavior, around which offer, under what comparison, and over which horizon it means.
A buyer may complain about price because negotiation is expected while still accepting the offer. Another may never mention price and quietly choose a cheaper alternative. Words, choices, and market-level demand deserve separate records.
“Our customers are price sensitive” is usually the beginning of a pricing question, not the conclusion.
Willingness to pay names a maximum for one offer
OpenStax defines willingness to pay as the maximum amount a buyer is willing to pay for a good. In practice, the offer cannot be left vague. Plan, entitlements, service level, contract terms, currency, and procurement conditions can all change what the amount means.
The evidence may be stated, as in an interview or survey, or revealed through observed choices and transactions. An OECD valuation framework uses that stated-versus-revealed distinction. Its subject is environmental economics, so it does not validate a SaaS pricing survey or provide a benchmark; it supports the conceptual difference.
Stated answers can explore reasoning and scenarios that have not been offered, but wording, incentives, and the hypothetical nature of payment matter. Revealed behavior involves real choices, yet those choices are constrained by available alternatives, discounts, sales intervention, selection, and budget rules. “Observed” does not mean free of context.
The cited sources define willingness to pay for a specified good or benefit and distinguish stated from revealed preference. OpenStax Principles and the OECD study indicate that neither kind of evidence automatically supplies market-wide demand elasticity.
Choose the term from the question
| What the team wants to know | Best starting concept | What remains outside it |
|---|---|---|
| How did quantity respond across a defined price change? | Price elasticity of demand | An individual’s maximum willingness to pay |
| Why are buyers describing the offer as expensive? | Price-sensitivity research | Market demand response or a causal price effect |
| What maximum would a buyer exchange for this exact offer? | Willingness to pay | Elasticity over another interval or total demand |
| Did the change improve revenue? | Demand response plus revenue records | Profit, cash, retention, and longer-run effects |
| Does a segment need a different offer? | Several evidence types | A complete decision from price response alone |
The methods can inform one another without becoming interchangeable. Interviews may suggest why a measured demand response differs by segment. Real purchase behavior may challenge an overconfident survey. Willingness-to-pay research may identify a range worth investigating, while PED describes response to actual price variation.
Combining evidence does not mean averaging incompatible outputs. It means letting each source resolve the uncertainty it was built to address.
The most tempting conclusions are the ones to refuse
One elasticity estimate does not reveal every buyer’s willingness to pay; it summarizes response across its defined comparison. A willingness-to-pay distribution does not establish elasticity because it does not, by itself, show quantity response across a price change. Frequent objections do not establish high elasticity because negotiation, unclear value, poor fit, procurement, or packaging may produce the same conversation.
Even inelastic demand does not make a price increase automatically desirable. OpenStax’s discussion of elasticity and pricing relates elasticity to total revenue under economic assumptions and notes that response can differ by time horizon. Revenue is not profit, retention, substitution, customer trust, or long-run demand.
Elasticity can vary by point, interval, and horizon. According to the OpenStax Principles textbook, its revenue implications do not supply the other evidence needed for a full SaaS pricing decision.
Before accepting any confident price statement, ask what offer and population it covers, whether the evidence came from transactions, an experiment, a survey, interviews, or sales reports, what comparison was made, and how long the response was observed. If those details are unavailable, the claim is directional rather than precise.
Use elasticity for proportional demand response, sensitivity to describe a bounded price-related pattern worth explaining, and willingness to pay for a maximum exchange around a specified offer. The cleanest pricing analysis begins by refusing to let one term impersonate another.
Frequently asked questions
What do elastic, inelastic, and unit-elastic demand mean?
Using the absolute value of price elasticity of demand, a value above 1 is elastic, below 1 is inelastic, and exactly 1 is unit-elastic. OpenStax ties those categories to quantity changing by a greater, smaller, or equal percentage than price. The label describes responsiveness over the measured interval; it does not mean every buyer cares greatly, slightly, or equally about price.
Why is price elasticity of demand often reported without a minus sign?
Own-price demand usually moves in the opposite direction from price, so the raw ratio is negative; economists commonly report its absolute value to discuss response magnitude. The OpenStax elasticity chapter makes that convention explicit. Record the sign convention beside every estimate because -0.8 and 0.8 can denote the same own-price response under different reporting rules but cannot be compared safely without that context.
How is cross-price elasticity different from price elasticity of demand?
Own-price elasticity relates demand for an offer to that offer’s price; cross-price elasticity relates demand for offer A to a price change in offer B. OpenStax defines positive cross-price elasticity for substitutes and negative cross-price elasticity for complements. Specify both products, packaging states, population, and time window before estimation, and do not infer substitution or complementarity from an own-price estimate alone.