How mid-market manufacturers and distributors move from textbook elasticity to discount discipline, measurement rigor, and durable margin lift.

By Enrico Sieni · Revify Analytics · Published May 27, 2026 · 14 min read

A regional VP at a mid-market distributor walked into a Monday pricing call last quarter with a request. Discount a sole-source filtration assembly 7% for a key account, because the buyer was, in his words, getting noisy. The part had no substitute. The customer had been buying it for nine years. The competitive bid the buyer waved around was for a different, lower-spec product. The VP wanted the discount anyway, and he wanted it that morning.

That moment is where most of the literature on price elastic and inelastic demand goes silent. The textbook explains the coefficient. It does not explain how to push back at 9 a.m. without losing the relationship, or how to tell whether the buyer is actually price-sensitive or just running a playbook he runs every March. This guide is for pricing, finance, and commercial leaders at manufacturers and distributors who need elasticity to function beyond an academic concept. It covers what elasticity means, why it is genuinely hard to measure in B2B, which estimation methods work at which level of maturity, how cross-elasticity reshapes assortment decisions, and how a pricing capability turns the coefficient into behavior. McKinsey, Bain, BCG, and Simon-Kucher have all converged on the same point from different angles: of every commercial lever a business owns, pricing produces the largest profit move per percentage point, and elasticity is the input that tells you where to pull it.

Quick answer. The difference between price-elastic and inelastic demand comes down to a single coefficient. Elastic demand has a price elasticity coefficient greater than 1 in absolute value (|PED| > 1): a 1% price change moves quantity by more than 1% in the opposite direction. Inelastic demand has |PED| < 1: quantity moves less than price. Unit elastic sits at |PED| = 1. A typical B2B portfolio contains both, which is exactly why blanket discounts and blanket increases both leak margin.

What price elastic and inelastic demand actually mean

The simple definition of elasticity

Price elasticity of demand (PED) measures how responsive buyers are to price. The formula is straightforward:

PED = % change in quantity demanded ÷ % change in price

For finite price changes, which is what a real pricing manager actually evaluates, the midpoint or arc method is more reliable. It produces the same coefficient whether you move from $100 to $105 or from $105 to $100:

PED = [(Q₂ − Q₁) ÷ ((Q₂ + Q₁)/2)] ÷ [(P₂ − P₁) ÷ ((P₁ + P₂)/2)]

Because the elasticity of demand for normal goods is negative (price up, quantity down), most operators work with the absolute value to avoid sign confusion. Throughout this article, when we say a coefficient is greater than 1 or less than 1, we mean |PED|.

How to read elastic, inelastic, and unit elastic demand

Three classifications cover almost every commercial situation a manufacturer or distributor encounters. Elastic demand (|PED| > 1) describes products where buyers are price-sensitive, typically because alternatives exist or the purchase is large relative to the budget. Inelastic demand (|PED| < 1) describes products where buyers stay put when price moves: specialized components, sole-source parts, emergency replacements, and products where switching cost is high. Unit elastic (|PED| = 1) is the boundary case where revenue is the same before and after the price change. McKinsey’s research on big-data pricing pegs average brand price elasticity at around −2.5, though the dispersion around that average is what every real pricing decision actually depends on. Many industrial categories exhibit lower elasticity than consumer markets, suggesting that many B2B firms have greater pricing flexibility than their sales teams assume.

Elastic vs. inelastic vs. unit elastic at a glance

Elastic	|PED| > 1	Volume moves more than price	Commodity inputs, multi-vendor MRO supplies
Unit elastic	|PED| = 1	Volume moves exactly in proportion	Rare in practice, a boundary case
Inelastic	|PED| < 1	Volume barely moves when price does	Sole-source components, emergency replacements, specialty parts

Why B2B elasticity estimates fail

If you read the introductory literature on price elastic and inelastic demand, you might come away thinking elasticity is something you compute. In B2B, the harder work is figuring out whether what you computed is actually elasticity, or some confounder wearing elasticity’s clothing. Most failed pricing programs we see did not fail on governance. They failed on a number that was never reliable in the first place.

Correlation is not elasticity.

A volume change that follows a price change does not mean the price change caused it. In B2B distribution and manufacturing, volume moves for at least a dozen reasons that have nothing to do with the list price:

• Seasonality and macroeconomic cycles (a Q4 surge often gets misread as an effect of an October price increase)
• Inventory availability, both yours and your competitors’ (a competitor stockout looks like elasticity if you do not control for it)
• Project timing on the customer side (a paper-mill turnaround drives a one-time spike that has nothing to do with price)
• Buying group changes, GPO renegotiations, and contract refresh cycles
• Freight programs, fuel surcharges, and other off-invoice movements that distort the realized price
• Sales rep turnover and territory realignment (a new rep often produces a step-change in volume independent of price)
• Promotional overhangs and stock-up behavior from prior periods
• Mix shifts within a SKU family that move blended volume without any single product responding to price.
• Customer onboarding lags and pipeline-led volume that lags price decisions by quarters.

Strip these out, and the estimated elasticity often changes by a factor of two or more. Leave them in, and the coefficient is a noise reading dressed up as a signal.

Observational bias and limited price variation

Most B2B pricing histories contain very little real price variation. List prices move once a year. Customer-level pricing drifts inside narrow corridors set by contract. When the price you observe barely moves, the coefficient you compute is statistically fragile, regardless of how clean the regression looks. This is why consumer-goods elasticity estimates from POS data are more reliable than B2B estimates from invoice data: B2C has thousands of price points per SKU per year, whereas B2B often has only a dozen.

Negotiated pricing distorts what you can observe.

In a heavily negotiated environment, the realized price is itself an outcome of price sensitivity. The reps discount prices more for price-sensitive customers and hold prices with price-insensitive customers. The resulting transactional data is therefore not a clean record of how customers respond to price. It is a record of how customers responded to a price the rep had already adjusted. Run a naive elasticity regression on that data, and the coefficient comes back artificially low, because all the elastic customers got pre-discounted and look like inelastic buyers who paid less.

Sparse transactions and long-tail SKUs

A distributor with 80,000 SKUs typically has fewer than 50 transactions per year on more than half of them. There is no honest elasticity coefficient for a SKU that sold seven times last year. You can borrow strength from product families, customer cohorts, or hierarchical models, and you should. What you cannot do is treat the borrowed estimate as if it were measured directly on the SKU.

The takeaway: any serious pricing function reports both the elasticity estimate and its confidence, and refuses to treat low-confidence estimates the same as high-confidence ones. More on that in the KPI section below.

Methods pricing teams actually use to estimate elasticity.

Elasticity estimation is a maturity ladder. Teams that try to start at the top rung usually fail because the data infrastructure does not support it. Teams that stay at the bottom rung indefinitely never get past portfolio averages. Most mid-market pricing functions fall at Level 2, with some growing toward Level 3.

Level 1: midpoint method and before/after analysis

The midpoint formula above is Level 1. So is comparing volume before and after a known price move on a single SKU, controlling for the most obvious confounders by eye. It is appropriate for newly launched SKUs, for SKUs with a single clean natural experiment, or for a first-pass sanity check before more rigorous work. It is not appropriate as the basis for portfolio-wide pricing decisions, because the noise dominates the signal at this level of rigor.

Level 2: log-log regression

Level 2 is the workhorse for most mid-market pricing teams. The log-log specification estimates a constant elasticity by regressing log volume on log price:

ln(Q) = a + b · ln(P) + controls

Here, b is the elasticity coefficient directly. The controls absorb the confounders described in the prior section: seasonality dummies, customer segment fixed effects, stock-out indicators, competitor price proxies, freight surcharges, and so on. A well-specified Level 2 model typically produces elasticity estimates with usable confidence intervals for SKUs with at least 100 transactions per year. It also produces a clean diagnostic for which SKUs the model is underpowered to estimate, which feeds directly into the elasticity coverage ratio discussed later.

Level 3: panel models, hierarchical models, and causal ML

Level 3 is where serious mid-market pricing programs end up after eighteen months of maturity. Panel models exploit variation across customers and across time. Hierarchical (multi-level) models borrow strength across SKU families so that long-tail SKUs inherit a sensible prior from their family while still updating on their own (limited) data. Causal machine-learning approaches (double machine learning, causal forests) handle the non-linear interactions that linear regressions miss, especially when elasticity varies by customer segment or by competitive context. None of these are exotic in 2026, and most are accessible through Python or R packages that a competent analytics team can operate.

Level 4: controlled price tests

Level 4 is the gold standard. Pick a SKU, randomize price treatments across matched customer cohorts, hold all other variables fixed, and measure the response directly. Level 4 is rare in B2B for organizational rather than analytical reasons. Sales teams resist randomized testing on real customers. Legal teams flag potential Robinson-Patman exposure when price differences are not tied to documentable cost-to-serve or volume-tier rationales. The practical compromise is geo-based or channel-based price testing, where the variation is justifiable on grounds other than experimentation. Done carefully, even a handful of well-designed tests per year produces the cleanest elasticity numbers in the portfolio and calibrates the Level 3 model against ground truth.

Cross-elasticity, substitution, and assortment effects

Own-price elasticity tells you how a SKU responds to its own price. Cross-price elasticity tells you how a SKU responds to a different SKU’s price, either yours or a competitor’s. For manufacturers with premium and value lines in the same category, cross-elasticity is often where the larger margin question lives:

XED = % change in quantity of A ÷ % change in price of B

A positive cross-price elasticity means A and B are substitutes (raise B’s price, A’s volume goes up). A negative cross-price elasticity means they are complements (raise B’s price, A’s volume goes down). In manufacturing portfolios, three patterns recur often enough to be worth naming.

Premium-to-value cannibalization

Raise the premium adhesive 5%, and the value adhesive picks up some of the lost volume rather than the competitor capturing it. The own-price elasticity on the premium line, taken alone, makes the increase look painful. The combined effect, accounting for cannibalization toward your own value line, often makes the increase clearly profitable. Pricing teams that ignore cross-elasticity routinely undershoot premium price increases.

Channel substitution

Raise the price through the distributor channel, and some of the volume shifts to direct, or vice versa. This is a within-portfolio cross-elasticity dressed up as a channel question. Manufacturers with multiple paths to market need to estimate it explicitly, or they will misread channel-mix shifts as signals of product-level elasticity.

Assortment gaps and competitor entry

When a competitor introduces a substitute, the own-price elasticity on the affected SKU rises (sometimes sharply), and the cross-price elasticity with the competitor’s offering becomes the dominant factor. This is where Revify’s competitive pricing analytics work pays back: a quarterly read on competitor moves, paired with cross-elasticity estimates from transactional data, prevents the embarrassing scenario where a 3% list-price increase coincides with a competitor’s quiet 5% promotional reduction and the pricing team learns about it from the field three quarters later.

Portfolio elasticity architecture: where to estimate at what level

Pricing programs fail when they estimate elasticity at the wrong level of granularity. Too high (portfolio average), and the number describes no real decision. Too low (every customer-product-quote triple), and the data is too sparse to support honest inference. The architecture below is what we use in client engagements, top to bottom:

Company level	Useful only for board-level sanity checks. Never use as a pricing decision input.
Business unit level	Useful for capital allocation and price-positioning strategy across BUs.
Product family level	The level at which most hierarchical models start. Long-tail SKUs borrow strength from this level.
Segment level (customer or channel)	Where most operational pricing decisions actually live. Elastic vs. inelastic varies dramatically across segments.
Customer level	Needed for strategic accounts and any negotiation above a defined threshold.
Customer-product (SKU) cell	The right level for deal-desk decisions and discount matrix design. Sparse data; needs hierarchical borrowing.
Quote level	Not an estimation level. A scoring level: how does this specific quote score against the corridor implied by the layers above?

Most mid-market pricing failures occur when the team estimates at the segment or product-family level and then applies the result at the quote level without a corridor or a confidence band. The estimate is fine. The application is broken. The fix is architectural: estimate at each layer, store the result along with its confidence, and use the deepest layer with enough data for the decision at hand.

The elasticity lifecycle: why the coefficient changes over time

Treating elasticity as a constant is one of the most expensive analytical errors in B2B pricing. A SKU’s elasticity changes across its lifecycle, and the changes are often large enough to flip a pricing decision that was correct three years ago into a value-destroying one today.

Launch	Unknown, high variance	No historical price variation; estimates are mostly priors
Growth	Stabilizing, often elastic	Customers comparing alternatives; substitutes still emerging
Mature	Lower, often inelastic	Switching cost has accumulated; specifications are locked in
Decline	Often rises again	Newer substitutes pull price-sensitive customers away
Sole-source replacement	Very low (near zero)	No alternative in the market; emergency-procurement dynamics dominate

The practical implication is operational. Elasticity estimates need to be refreshed regularly, not produced once and trusted forever. A quarterly refresh on the top 20% of SKUs by revenue, with an annual refresh on the long tail, is the cadence we recommend for most mid-market manufacturers. The cycle also lets the pricing function spot lifecycle transitions early: a SKU whose elasticity has moved from −0.5 to −1.2 over two refreshes is signaling that the moat is thinning and the value-defense story needs revisiting.

Elasticity is not destiny: how pricing teams shape it.

Most articles on price elastic and inelastic demand treat the coefficient as something that happens to you. A serious pricing function treats it as something it influences. Elasticity is a function of the alternatives available to the buyer, the switching cost of moving to them, and the way value is communicated. Each of those is partly inside management’s control.

• Branding and category leadership reduce elasticity by shifting the comparison from price to perceived value.
• Service levels, response-time SLAs, and technical support raise switching costs and reduce elasticity over time.
• Bundling adjacent products and services moves the buying decision from line-item price comparison to total-solution evaluation, which is structurally less elastic.
• Exclusivity, certified status, and approved-vendor positioning eliminate substitutes for buyers operating under procurement rules that restrict alternatives.
• Technical differentiation, especially anything specified in a customer’s drawing or bill of materials, locks in inelasticity until the next redesign cycle.
• Installed-base lock-in (consumables, replacement parts, and accessories) is the most powerful lever for reducing elasticity. The original-equipment sale earns the right to the aftermarket annuity.

Pricing teams that internalize this are doing two jobs at once: measuring elasticity where it is today, and identifying the SKUs where deliberate commercial action could move it. A SKU classified as elastic this year is often one whose value story has gone stale, not one that is permanently price-sensitive.

Why manufacturers and distributors get elasticity wrong

Cost-plus habits that ignore customer response

Most mid-market price lists were not built. They accumulated. A cost figure plus a target margin, plus or minus whatever last year’s discounting trained customers to expect. Cost-plus is internally consistent and politically defensible, which is why it persists. It is also blind to the distinction between price-elastic and inelastic demand. A cost-plus price tells you nothing about whether the customer would pay 5% more without flinching or walk to a competitor at 1% more. Simon-Kucher’s research is blunt on this point: B2B elasticity must be inferred from transactional data and structured tests, not derived from textbook formulas applied to cost-plus lists. The 2024 Global Pricing Study makes the consequence concrete. Only about 65% of companies worldwide possess what Simon-Kucher defines as pricing power, meaning the ability to raise prices to fully offset cost increases. The other 35% are pricing without confidence, and elasticity is what closes that gap.

Discounting without governance and control

The second failure mode is structural. Even when leadership knows that certain SKUs are inelastic, sales teams still discount them. The deal desk does not exist, the discount matrix is a suggestion, and the compensation plan rewards bookings over margin. Bain’s survey of 1,700 B2B companies captured this pattern precisely: managers criticize sales reps for losing a deal but rarely for pricing one too low, so reps learn to concede on price to close. Pre-program discount exception rates of 40–60% are common in B2B distribution and manufacturing. They yield to a discount matrix, a deal desk on an SLA, and a monthly exception review, not to a better elasticity model.

What changes operationally when pricing capability improves

When pricing capability is built deliberately, three things shift in how the commercial organization handles price elastic and inelastic demand: segmentation gets sharper, governance gets tighter, and the exception log becomes a feedback loop.

Segmenting products, customers, and channels by response to price

The first operational shift is moving from one elasticity to many. Treating the portfolio as a single number, our products are price-sensitive, which is the analytical equivalent of a cost-plus approach. Real elasticity varies by segment, channel, season, and competitive context. A capable pricing function classifies SKUs into key value items (KVIs) (the 20% of products customers actively shop and benchmark) and non-KVIs (the longer tail where elasticity is meaningfully lower). McKinsey’s distributor research is consistent on this point: price discipline on KVIs defends share; non-KVI optimization captures value. Different elasticities, different playbooks, same portfolio.

Pricing guardrails, approval paths, and deal-desk workflows

Once segments exist, guardrails make them operational. A discount matrix by segment-SKU cell, two-stage approval above a defined threshold, and a 24-hour deal desk SLA convert elasticity into behavior. Guardrails are how the elasticity insight survives contact with a quote. Without them, the analytics file sits on a shared drive, and the deals continue to get done as they always have. BCG’s unified theory of pricing makes the same point structurally: the elasticity framework lives at the intersection of cost and customer value, and translating that intersection into prices requires a price corridor and an approval workflow, not just a coefficient.

Turning sales exceptions into pricing discipline

Every exception is a data point. When the deal desk reviews 40 exception requests in a month and 28 of them cluster on the same three inelastic SKUs, that is a list-price problem the field has been correcting on its own. A mature pricing function reads the exception log as a feedback loop. It surfaces where the guardrails are wrong, where elasticity has shifted, and where competitive context demands a structural answer. The first hundred days of governance produce as much elasticity insight as the analytics workstream does.

Worked examples: how the same 5% move plays out differently

Theory is cheaper than examples. Consider a baseline SKU: list price $100, unit cost $70, 1,000 units per period, gross profit $30,000 at a 30% gross margin. Watch how four different elasticity assumptions reshape the same 5% price move.

Scenario PED New price Units Gross profit vs. baseline

1. Discount 5% on an inelastic SKU −0.4 $95 1,020 (+2%) $25,500 −15.0%
2. Raise 5% on the same inelastic SKU −0.4 $105 980 (−2%) $34,300 +14.3%
3. Raise 5% on a moderately elastic SKU −1.8 $105 910 (−9%) $31,850 +6.2%
4. Raise 5% on a highly elastic SKU −2.5 $105 875 (−12.5%) $30,625 +2.1%

Scenario 1 is the single most common margin leak we encounter in mid-market manufacturing and distribution: a 5% discount on an inelastic SKU sacrifices $4,500 of gross profit to chase 20 units of volume the customer would have bought anyway. Scenario 2, the opposite move on the same SKU, adds $4,300. That is an $8,800 swing on a single SKU, decided entirely by the direction of the price move.

Scenarios 3 and 4 are the more interesting cases for sophisticated pricing readers. The moderately elastic SKU still rewards a price increase because the margin-per-unit gain outpaces the volume loss. The highly elastic SKU at −2.5 is approaching the break-even threshold, beyond which the increase stops working.

ΔQ = PED × ΔP

A 5% price increase combined with a −2.5 elasticity produces a 12.5% volume loss. At the baseline 30% gross margin, the volume loss almost exactly offsets the margin gain, leaving Scenario 4 only marginally profitable. Move the elasticity to −3.0 or higher, or thin the starting margin to 20%, and the same 5% increase actively destroys gross profit. This is the calculation a value-defense playbook is supposed to substitute for a blanket increase.

Bain’s B2B pricing benchmarks peg the typical margin lift from a disciplined pricing program at roughly 415 basis points with payback inside a year. Almost all of it comes from correctly reading scenarios like these, especially the asymmetry between Scenario 1 and Scenario 2.

KPIs that show whether the elasticity work is paying off

Changing pricing behavior matters only if you can measure that it has changed. The KPI set splits into two layers. The first three are commercial outcomes (the things finance cares about). The next three are capability metrics (the things that tell you whether the pricing function itself is maturing).

Price realization

Price realization is the percentage of the list price that survives to the bottom line after every discount, rebate, allowance, and chargeback. It is the single most diagnostic pricing KPI because it captures every on- and off-invoice concession in a single number.

Price Realization (%) = (Net Realized Price ÷ List Price) × 100

Realization gains compound. According to Revology Analytics’ 2025 study of 2,000 global companies (Revenue Growth Analytics Maturity in 2025: Why Pricing Still Packs a Punch), a 1% improvement in price realization lifts operating profit by roughly 6–7% on average across industries, and by 10–11% once highly regulated sectors are excluded. The lift runs from about 8.7% in tech to 17.4% in automotive.

Discount leakage and exception rates

Discount exception rate is the simplest governance KPI and the one most directly tied to elasticity discipline.

Discount Exception Rate (%) = (Deals priced outside guardrails ÷ Total deals in period) × 100

A healthy mid-market target after 90 days of governance is below 15%. Pre-program rates of 40–60% are common. The trajectory matters more than the absolute number; anything sitting above 30% after six months indicates the guardrails are decorative. Mix-adjusted price realization separates pricing performance from pure mix shifts when composition changes quarter over quarter, and quote turnaround (median and 90th percentile) exposes the deal-desk bottlenecks that push reps to route around governance because the process is too slow.

Gross margin improvement by segment

Portfolio-level margin can hide a great deal. The honest measure is gross margin improvement by segment-SKU cell, broken out specifically for inelastic SKUs. If pricing capability is working, the inelastic-SKU cohort should show the largest absolute lift in the first 90 days, because that is where the diagnostic identified the biggest mismatch. Customer-level margin diagnostics decompose lift by segment, product, and rep, and pair pricing actions with churn risk so retention offers do not silently destroy more value than the revenue they save.

Capability metrics: coverage, confidence, and test velocity

Three additional metrics tell you whether the underlying pricing capability is maturing. They are leading indicators; the commercial KPIs above are lagging ones.

Elasticity coverage ratio: the percentage of revenue (not SKU count) for which the pricing function has a measured elasticity estimate, as opposed to a borrowed family-level prior. A mature program runs with more than 70% of revenue covered by SKU- or customer-product-specific estimates. Anything below 40% means the deal desk is operating on portfolio averages, which is not much of a deal desk.

Estimate confidence score: a high/medium/low classification on each elasticity estimate, based on the underlying transaction count, R-squared of the regression, and consistency across refresh cycles. The point is not to publish the score externally. The point is to ensure that the discount matrix, deal-desk thresholds, and value-defense playbooks differentiate between high- and low-confidence estimates. Treating a low-confidence estimate as if it were a measured truth is one of the most common ways pricing programs lose credibility with sales.

Price test velocity: the number of structured price tests (geo, channel, A/B at the customer-cohort level) the pricing function runs per quarter. A program running zero tests per quarter calibrates its elasticity estimates solely to historical data, which is exactly the data most distorted by negotiated pricing and confounders. A program running three to five tests per quarter is generating clean elasticity data that improves the model faster than the data drifts.

Common mistakes when using elasticity in pricing decisions

Three failure patterns recur often enough to be worth naming.

Treating all products as equally sensitive to price

Portfolio-wide elasticity is an arithmetic average that describes no single SKU. Applied as a decision rule, it discounts inelasticity while underpricing elasticity. The remedy is segment-SKU cell estimation, not a better portfolio number.

Ignoring competitive context and customer alternatives

Elasticity is not a fixed product trait. It varies by customer, channel, season, and competitive context. A specialty component is inelastic when the customer has no substitute and elastic when a competitor enters the bid. Measure it at the customer-product level and update it as competitive context shifts. The deal that looked safe last quarter may not be safe this quarter.

Confusing volume changes with profitable growth.

If volume went up after a discount, it is tempting to declare the discount worked. On inelastic demand, that conclusion is almost always wrong. The volume gain was small, the margin hit was large, and the unit count moved partly for reasons unrelated to price (a competitor’s stockout, a customer’s project timing, a buying-group push). Scenario 1 in the worked example above is the algebraic version of this mistake.

Sales compensation alignment is the lever most pricing programs avoid

Governance can be designed perfectly and still collapse the moment it meets a sales comp plan that pays purely on bookings. If variable compensation rewards revenue without margin quality, reps will trade margin for volume on every deal where the choice is available. No discount matrix survives that incentive structure. Bain’s pricing research makes this explicit and traces it back to the same root cause across hundreds of B2B engagements: even an optimal price strategy fails when incentives reinforce the wrong behavior. The math is simple. A rep paid 100% on revenue gets paid more for a $1.2M deal at a 40% discount than for a $1.0M deal at no discount, even though the second one is materially more profitable for the company.

The compensation fix is concrete:

• Stop using revenue as the sole variable-comp metric. Even a small margin component (20–30% of variable pay) reshapes rep behavior within two quarters.

• Publish price realization by rep monthly. The transparency alone closes a meaningful share of the gap, because the laggards see themselves on the same dashboard as the leaders.

• Tie exception-approval authority to a rep’s trailing-twelve-month margin discipline. Reps with strong margin behavior earn wider authority; reps with weak behavior need supervisor sign-off for longer.

• Move the most senior commercial roles (strategic account managers, key OEM owners) to a hybrid construct: a base, a revenue component, a gross-profit-dollar component, and a strategic-account-growth component.

A pricing operating model rolled out without the compensation conversation is, in practice, a draft. The mid-market clients who get this right almost always do it in the same quarter as the deal-desk launch, not eighteen months later when the resistance has already calcified.

How Revify applies elasticity in the real world

Insight into price-elastic and inelastic demand earns its keep only when engagement converts it into behavior. Revify’s structure has four named phases, and the elasticity work threads through all of them. The two phases that matter most for clients new to disciplined pricing are the Profit Diagnostic at the start and Managed Services at the end. The middle two (Margin Stabilizer and Growth Commander) translate the diagnostic findings into operating discipline and segment-level optimization.

Profit Diagnostic: where the elasticity work begins

A four-week sprint that quantifies leakage and sizes the prize. On the elasticity side, this means estimating response at the segment-SKU level using twelve-to-eighteen months of transactional history, controlling for the confounders described earlier, classifying each SKU by elasticity tier, estimating confidence, and producing a prioritized list of the three to five highest-impact opportunities. Most of those opportunities are inelastic SKUs being discounted as if they were elastic, which is where the first-quarter margin lift comes from.

Margin Stabilizer and Growth Commander: discipline, then optimization

Stabilizer installs the segment-level discount matrix, the two-stage approval thresholds, the deal-desk SLA, and the monthly exception governance. Growth Commander follows once the guardrails are holding. It rebuilds the segment-level price matrix, deploys customer-level pricing on strategic accounts, and equips sales with value-based playbooks tied to the elasticity tiers from the diagnostic. The sequence matters. Optimization without governance leaks faster than it lifts, because the field keeps discounting its way around the analytics.

Managed Services: the persistence layer

Pricing initiatives lose momentum about 90 days after launch. The new behaviors are not yet habitual, and the next quarter’s deals demand the old shortcuts. A virtual pricing team is the persistence layer that prevents the slide. It sets the cadence, refreshes the elasticity estimates as new transactional data accumulates, re-trains reps on the playbooks, and maintains discipline long after the project plan ends. Elasticity is not a one-time calibration. Competitive context shifts and the coefficient that was right in January is approximately by July.

Quick wins and timeline

Mid-market leaders often wait for a complete pricing transformation before acting on price elastic and inelastic demand. That instinct is expensive. A capable engagement produces measurable wins inside the first quarter.

First 30 days: identify high-risk discount patterns

Inside the first month, the diagnostic produces three deliverables: a quantified leakage map by segment-SKU cell, a prioritized list of the three to five inelastic SKUs being discounted most aggressively, and a draft decision-rights matrix that names an owner for every type of pricing call. None of these requires a platform. All of them survive a change in leadership.

Next 60–90 days: tighten guardrails and improve pricing confidence

By day 90, guardrails are live, the deal desk is operational, the exception review has been chaired at least twice, and sales has seen its first round of coaching using real deal data. The KPI dashboard reports price realization and exception rate weekly. Visible margin gains usually appear in this window, typically 50 to 150 basis points of gross margin recovery on the inelastic-SKU subset, before the optimization phase has even begun.

Getting started with a Profit Diagnostic

What Revify reviews first

The diagnostic is intentionally low-friction. Four weeks. Data the client already has. A quantified action plan is the deliverable, not another deck. Revify reviews twelve-to-eighteen months of transactional data, the current discount and approval policy (written or implicit), customer and product margin distributions, and the deal-desk workflow if one exists. The output includes a leakage map by segment-SKU cell, a prioritized opportunity list anchored in the inelastic SKUs being discounted most aggressively, and a draft governance design to make the first 90 days operational.

What your team needs to prepare

A transactional data extract, two hours of CFO/COO time, and access to two or three sales leaders. Revify handles the rest. Start Your Profit Diagnostic.

Frequently asked questions about price elastic and inelastic demand.

Key takeaways

• Elasticity classifies demand by sensitivity: |PED| > 1 elastic, < 1 inelastic, = 1 unit elastic. Most B2B portfolios contain both, and the mix makes one pricing approach inadequate for the entire catalog.

• In B2B, the hard work is not the formula. It is separating elasticity from confounders: seasonality, competitor stockouts, mix shifts, sales rep turnover, and the negotiated pricing history that distorts the data itself.

• Match the estimation method to the maturity of the data: midpoint and before/after for natural experiments, log-log regression with controls for most operational decisions, hierarchical and causal-ML methods once the data infrastructure supports them, controlled tests as the gold standard.

• Estimate at the segment-product cell level, not portfolio-wide. Track coverage and confidence alongside the coefficient.

• Cross-elasticity reshapes premium-to-value and channel decisions. Ignoring it is the most common reason premium price increases get undershot.

• Elasticity is not destiny. Branding, service levels, switching costs, bundling, exclusivity, and installed-base lock-in are levers that reshape the coefficient over time.

• A 1% improvement in price realization lifts operating profit by roughly 6–7% on average across industries (Revology Analytics, 2025), and by 10–11% once regulated sectors are excluded.

• Insight only pays off with capability. Guardrails, governance, deal-desk cadence, and compensation alignment are how elasticity becomes behavior. Without them, the analytics file is wallpaper.

About the author

Enrico Sieni leads pricing thought leadership at Revify Analytics. He has spent two decades within pricing functions at mid-market manufacturers and distributors, focusing on translating elasticity work into deal-desk behavior and margin recovery.