Why Price Increases Feel So Risky

Ask any commercial director at a mid-sized company about raising prices and you'll hear the same concerns: "We'll lose our biggest customer," "Competitors will undercut us," "The sales team will revolt." These fears aren't irrational—poorly executed price increases do destroy value.

But the risk calculus changes dramatically when you can quantify the expected impact before making any changes. If your data shows that a specific product has an elasticity of -0.6, you know that a 5% price increase will likely reduce volume by only 3%—resulting in a net revenue increase of about 1.9% and a significant margin improvement. That's a very different conversation than "let's try raising prices and see what happens."

Building Your First Scenario

A good pricing scenario starts with a clear hypothesis and a defined scope. Rather than "raise all prices by 5%," think in segments:

Scenario A: Surgical increase on inelastic products. Select the 20-30 SKUs where elasticity data shows low price sensitivity (elasticity between 0 and -0.8). Model a 4-7% increase on just these products. This is the lowest-risk, highest-impact starting point.

Scenario B: Moderate increase across the board. Model a 2-3% increase on your full catalog. This is common for annual price adjustments that track inflation. The scenario model will show you the net impact after accounting for volume losses on elastic products.

Scenario C: Strategic repricing. Increase prices on inelastic products (5-8%), hold prices on unit-elastic products, and potentially lower prices on highly elastic products where volume gains would more than offset the margin reduction. This is the most sophisticated approach and typically yields the highest net margin improvement.

For each scenario, the key outputs are: projected revenue change, projected volume change, projected margin impact, and the confidence interval around each estimate.

Reading the Results

The power of scenario analysis is in comparing alternatives side by side. A well-structured comparison table might look like this:

Scenario A (surgical) might show: +1.8% revenue, -1.2% volume, +6.4% margin improvement. Scenario B (across the board) might show: +0.9% revenue, -2.8% volume, +2.1% margin improvement. Scenario C (strategic) might show: +2.4% revenue, +0.3% volume, +7.8% margin improvement.

The numbers make the decision obvious: Scenario C generates the best outcome on every metric. But without the scenario model, most companies would default to Scenario B because it feels safest—and leave significant value on the table.

Pay attention to the confidence intervals. A scenario that projects +2% revenue with a confidence interval of ±0.5% is actionable. A scenario that projects +2% with a confidence interval of ±4% is not—it means the model isn't sure whether you'll gain or lose money.

From Model to Implementation

Once you've selected a scenario, implementation should be phased. Start with your highest-confidence recommendations—the products where the elasticity estimate has the narrowest confidence interval and the most historical data supporting it.

Implement the first batch of price changes and monitor actual results weekly for the first month. Compare actual volume changes against the model's predictions. If the model predicted a 3% volume drop on a product and you're seeing a 2.5% drop, the model is calibrated well and you can proceed with confidence on the remaining changes.

If actual results diverge significantly from predictions (say, a 10% volume drop instead of 3%), pause and investigate. It might mean the competitive landscape has shifted, a substitute product has entered the market, or there's a customer concentration risk the model didn't capture.

The goal isn't to get every prediction exactly right—it's to replace guesswork with informed estimates that are directionally correct and continuously improving as more data flows through the system.