On this page
Price elasticity is not a permanent property of your market. It is a response measured under a set of conditions: which customers were observed, what they paid before, how satisfied they were, what the seller changed, and how long the observation lasted. The coefficient is useful only when those conditions travel with it.
That is why a price increase can be accepted by one customer, rejected by another and absorbed by a third without any of the three contradicting the same demand curve. The first question is not “What is our elasticity?” It is “Which mechanism made this buyer sensitive now?”
Why does price elasticity shift when buyer reference points change?
In business-to-business transactions, the price paid last time is often the most immediate reference for the next price. Bruno, Che and Dutta found reference-price effects in both quantity and the transaction price in a large transaction record, and they also found that salespeople carry reference prices of their own. A buyer is not comparing your new quote with an abstract market average. The buyer is comparing it with a remembered event.
The same increase can therefore be a small move from a recent high price, or a large loss against a recent concession. The percentage change is identical. The psychological and commercial state is not. That distinction is already visible in the price increase that is judged before it is paid, where the reception of a change is treated as a question of justification rather than as a fixed property of the product.
| Condition beside the price change | What moves | What the evidence can support | What it cannot support |
|---|---|---|---|
| Satisfaction with the relationship | The customer’s reaction to the magnitude of the increase | A satisfied customer can react less negatively than a dissatisfied customer under the tested conditions | Satisfaction makes a price increase safe |
| Last price paid | The buyer’s reference point | A prior loss or gain can shape the next quantity and price response | A single reference price predicts every renewal |
| Seller’s pricing history | The buyer’s latent state | Repeated pricing decisions can move a buyer between more relaxed and more vigilant states | A model counterfactual is a measured profit uplift |
| Salesperson’s own discount reference | The quote offered to the next customer | Seller-side anchors can shape the discount, and incentives can reduce the effect | A compensation change fixes every pricing problem |
Table 1Four reasons the same increase can mean different things
An elasticity coefficient is an output of a setting. The setting is part of the result.
Source: Author's synthesis of the cited studies. Each row's scope is stated in the text.
Why is customer satisfaction an imperfect buffer against price resistance?
Homburg, Hoyer and Koschate measured reactions to price increases in three experiments. Their result is valuable precisely because it is narrower than the sentence usually built from it: satisfaction weakens the negative effect of the increase on repurchase intentions. Under the tested conditions, the study finds a different response pattern for lower- and higher-satisfaction customers.
The study does not show that satisfied customers will keep buying. Its dependent variable is repurchase intention, the setting is consumer services, and the authors show that the buffer thins as the increase becomes larger. The correct commercial use is therefore diagnostic. Before asking whether a price increase is affordable, identify the part of the base whose satisfaction is already fragile.
That is different from saying “raise prices on loyal customers.” Loyalty can be attached to the firm, to the salesperson or to the value the customer receives. The retention number is measured from your side of the table for a reason: an aggregate renewal rate does not tell you which relationship is carrying the willingness to pay.
How does the quoting process act as an experimental treatment in B2B transactions?
Zhang, Netzer and Ansari model B2B buyers as moving between two latent states: a more relaxed state and a more vigilant state. Their result is not a universal taxonomy of buyers. It is a mechanism inside one longitudinal setting: the seller’s pricing decisions can move buyers between states.
That makes the quote itself part of the treatment. A discount that looks like a one-time acquisition cost can also teach a reference price. A sharp increase that is poorly explained can do more than reduce this month’s quantity. It can move the buyer into a state in which every future quote is read defensively.
The same logic applies on the seller’s side. Bergers and colleagues4 found that a salesperson’s reference discount shapes the discount granted to a new customer, and that incentives reduce the effect. As a synthesis of the customer-side and seller-side findings, a commercial team can create two reference prices at once: the customer’s memory of what was paid and the seller’s memory of what was given away.
| Question before the increase | Record this | If the answer is missing |
|---|---|---|
| What is the comparison price? | Last paid price, list price and last approved discount | Do not call the result elasticity yet |
| Who selected the account? | Inbound, rep-qualified, partner, deal desk or renewal-only | Separate selection from willingness to pay |
| What changed besides price? | Scope, service level, term, implementation or sponsor | Price is not the only treatment |
| What was the customer’s recent experience? | Satisfaction signal, escalation, service incident or expansion | Treat the coefficient as conditional |
| What would falsify the story? | A matched account with the same change and a different outcome | Pre-specify the comparison before reading the result |
Table 2The elasticity reading sheet
The first output is not a coefficient. It is a list of conditions that make the coefficient interpretable.
Source: Author's worksheet, informed by the cited pricing and reference-price literature.
Why price elasticity fails when the dashboard looks complete
A complete-looking dashboard can still compare the wrong price object, the wrong cohort, or the wrong time window. It can mix list price with negotiated price, omit a service or scope change, or treat a selected discount cohort as the market. The failure is a measurement and decision-design problem before it is an elasticity result.
Test the record before interpreting the coefficient: freeze the population, price and quantity definitions, reference point, non-price changes, observation window, and comparison rule. If one of those moves between periods, label the output exploratory and reopen the design.
How to improve price elasticity before changing the price
Improvement starts with a decision, not another dashboard. State whether the team is deciding on an increase, a discount, a contract change, or a test. Then attach the relevant cohort, net transaction price, quantity or renewal outcome, contribution boundary, and falsifier to that decision. This keeps price sensitivity separate from selection, service failure, and reference-price effects.
A practical review can use the existing reading sheet and add one release rule: no coefficient steers a price change until an owner has signed the population, comparison, non-price treatment, time window, and intended action. The rule is an operating control, not a universal statistical threshold.
AI price elasticity: what remains human?
An AI-assisted pricing workflow may flag an unusual price-quantity pattern, suggest a comparison cohort, or propose a candidate elasticity estimate. That output is a candidate analysis, not a measured market constant. Preserve the population, price object, quantity definition, model or rule version, non-price changes, reviewer, disposition, and timestamp.
Jarrahi (2018)5 draws a useful boundary here: AI can extend analytical processing and pattern recognition, while people retain contextual judgment and responsibility. For price elasticity, a human owner must decide whether the comparison is credible, whether confounding changes were recorded, and whether the result is fit for a commercial action. This does not establish an AI performance result.
Price elasticity evidence: what is strong enough for a decision?
Descriptive evidence can show what prices and quantities co-occurred. Comparative evidence can show how aligned cohorts or rule versions differed. A causal claim needs a comparison design that identifies what would have happened without the price change. These are different propositions, even when one dashboard displays them together.
Preserve the source, population, price and quantity definitions, reference point, period, non-price treatment, comparison, uncertainty, model or rule version, action, outcome, and decision. If those fields are missing, the result may guide exploration, but it is not evidence for a causal price decision. The formal definitions and finance mechanics are set out in the article “What is price elasticity of demand?”
What should a price elasticity dashboard show for B2B decisions?
A price elasticity dashboard should make the measured price object, quantity or renewal outcome, population, segment, reference point, period, and non-price treatment visible in one reviewable row. The dashboard is an evidence register, not a coefficient display.
For price elasticity for B2B, the crucial correction is to record the net transaction price and negotiated scope rather than treating list price as the complete treatment. Keep the account or buying situation visible as well. A segment label cannot repair a missing reference price, selection rule, or contract change.
| Dashboard field | Review question | Risk if missing |
|---|---|---|
| Price object | Is the measure list, quoted, net invoice, or negotiated price? | A list-price movement is mistaken for the customer’s treatment |
| Population and segment | Which accounts, renewals, or transactions enter the view? | Selection is read as willingness to pay |
| Reference point | What prior price, discount, or comparison does the buyer carry? | The change has no interpretable baseline |
| Non-price treatment | Did scope, service, term, implementation, or sponsor change? | Price is treated as the only intervention |
| Period and outcome | Which window and quantity, renewal, or exit outcome close the row? | Different horizons are compared as one result |
| Decision and owner | Which action may the dashboard inform, and who reviews it? | A descriptive coefficient steers an unbounded action |
Table 3What should a price elasticity dashboard show for B2B decisions?
Source: Table from this essay. Sources and interpretation are given in the article.
How should teams calculate, govern, and checklist price elasticity?
Price elasticity is an estimand for a named decision and segment, not a market property. Name the price object and comparison set before calculating or interpreting results. Failures cluster when SaaS entitlements or cohorts are pooled without a unit. A checklist is a diagnostic prompt. Refuse portable coefficients as proof.
How should commercial teams apply elasticity estimates in strategic decisions?
Use elasticity as a comparison inside a controlled decision, not as a market constant. Compare accounts that share the relevant conditions, keep the reference price visible, and record whether the change was accompanied by a reason the customer could evaluate.
When the outcome is bad, do not immediately conclude that the coefficient was wrong. The coefficient may have been answering a different question. A base with a high share of rep-owned relationships may be sensitive to reassignment, not just to price. A base acquired through heavy discounting may be sensitive to the reference price the seller created, not to the nominal list price. A renewal cohort with a recent service failure may be sensitive to fairness.
The practical test is the same one used in pricing as a positioning decision: what is the price meant to signal, and what does the buyer think it signals? If the answer is “nothing, it is only a number,” the organisation is asking elasticity to carry a positioning problem.
And remember the seller’s side of the record. The discount that outlives the deal shows why an unrecorded concession can become the benchmark for the next negotiation. The price increase is not the first event. It is often the first event the spreadsheet notices.
The final discipline is modest: attach the setting to every elasticity claim. Name the sample, the reference point, the outcome, the time window and the mechanism that changed. If those details cannot be named, the number may still be useful for exploration. It is not ready to steer a price increase.
References
- Homburg, C., Hoyer, W. D., & Koschate, N. (2005). Customers' reactions to price increases: Do customer satisfaction and perceived motive fairness matter? Journal of the Academy of Marketing Science, 33(1), 36–49. https://doi.org/10.1177/0092070304269953
- Bruno, H. A., Che, H., & Dutta, S. (2012). Role of reference price on price and quantity: Insights from business-to-business markets. Journal of Marketing Research, 49(5), 640–654. https://doi.org/10.1509/jmr.09.0334
- Zhang, J. Z., Netzer, O., & Ansari, A. (2014). Dynamic targeted pricing in B2B relationships. Marketing Science, 33(3), 317–337. https://doi.org/10.1287/mksc.2013.0842
- Bergers, D., Ghaffari, M., Viglia, G., & Filieri, R. (2023). Choosing the discount size in the software industry: How to incentivise the salesforce. Industrial Marketing Management, 109, 232–244. https://doi.org/10.1016/j.indmarman.2023.02.002
- Jarrahi, M. H. (2018). Artificial intelligence and the future of work: Human-AI symbiosis in organizational decision making. Business Horizons, 61(4), 577–586. https://doi.org/10.1016/j.bushor.2018.03.007
Updated 2 changes
- Added bounded dashboard and B2B sections that keep the measured price object, population, segment, reference point, period, and non-price treatment visible. No portable coefficient, B2B benchmark, or causal price effect was added.
- Added bounded failure-diagnosis, improvement, AI, and evidence sections for the price-elasticity expansion routes. Jarrahi (2018) supports only the human-AI responsibility boundary; the diagnostic and evidence controls remain author frameworks. No elasticity benchmark, AI performance result, or causal price effect was added.