Price Increase Playbook

Executive summary

A price increase playbook is a plan for deciding how much to raise prices, for which customers, on what notice, and how to know afterward how much of the increase you kept. The last part is the one most companies skip. They announce 6%, ship the letter, and never measure whether the invoices in month four reflect 6%, 4%, or 2%.

Price falls straight to profit while volume loss only removes contribution margin, so a modest increase can absorb a meaningful volume loss before you are worse off. Compute that limit for your own margins before anyone argues about whether customers will accept the increase.

The operating problem is leakage. Between the announcement and the invoice, increases are reduced by sales exceptions, contracts with price protection, quotes issued before the effective date, legacy price lists in the ERP, and customers who simply do not pay the new price and nobody pushes back. This playbook treats the increase as a project with an owner, a segment-level plan, an exception budget, and a realization report, not a letter.

For diagnosis, read Price Waterfall Analysis and Why Price Realization Keeps Drifting. Use this page to run the increase itself.

When to use this

Use the playbook when:

• Input costs (materials, labor, freight, licensing, subcontractors) have risen and prices have not followed.
• Your last broad price action was more than 12 to 18 months ago, or you cannot say when it was.
• Margin is below plan and cost cutting has run out of easy targets.

If you have not reconciled list-to-invoice leakage, run the price waterfall first, because an increase on a price list that customers already bypass will not reach the invoice.

Diagnostic questions

Answer these before choosing a number. Most can be answered from the ERP, the CRM, and a handful of contracts.

1. When was the last price increase, what was announced, and what share of it can you trace to invoices three months later?
2. What has your cost per unit or per hour done since the last increase, by product or service line?
3. Which customers have price protection, fixed-price terms, most-favored-customer language, or an index clause, and when does each expire?
4. What is the contribution margin by product line and customer segment, not the blended margin?
5. Which customers buy on price alone and which buy on service, availability, or switching cost, and how do you know?
6. Who has authority to grant an exception to a published price, and is every exception recorded?
7. Are there multiple price sources (ERP list, CPQ, spreadsheets, rep-maintained quotes) that must all change on the effective date?
8. How many open quotes and backlog orders are priced at the old price, and for how long are quotes valid?
9. Do sales commissions pay on revenue, margin, or realized price?
10. Which of your agreements require notice, consent, or a specific mechanism for price changes, and has counsel reviewed that language?

Question 3 and question 10 deserve emphasis. Contract terms govern what you are allowed to do, and no pricing playbook overrides them.

Framework: size, segment, sequence, sustain

The playbook has four moves. Each has a distinct output.

1. Size: set the increase from cost and from breakeven

Two numbers frame the decision.

Cost gap % = (Unit cost now − Unit cost at last price action) ÷ Current price

For each product or service line, compute the cost increase per unit since the last price action, divide by current price, and call that the cost gap. A price increase equal to the cost gap restores margin dollars per unit only if volume holds, and restores the margin percentage only if the increase is larger than the gap. Decide which of the two you are trying to restore and say so in the plan.

The second number is the breakeven volume loss:

Breakeven volume loss % = Price increase % ÷ (Price increase % + Contribution margin %)

Contribution margin here is price minus variable cost, divided by price, before the increase. It tells you how much volume you can lose before the increase leaves total contribution dollars lower than if you had done nothing. A 5% increase on a product line with a 30% contribution margin breaks even at a volume loss of 5 ÷ 35 = 14.3%. At a 50% contribution margin the same increase breaks even at 9.1%. The thinner the margin, the more volume you can afford to lose, which is counterintuitive and worth showing the sales team.

Breakeven volume loss is a ceiling, not an expectation. It tells you whether the increase is robust. If your plausible loss sits well inside the breakeven, the increase is robust. If it sits near or above it, narrow the increase to the segments where it does not.

2. Segment: different customers get different increases

A uniform percentage is simple to announce and wasteful to execute. Customers differ on three dimensions that matter:

Build the segment table with three or four rows, not forty. Rows can be defined by customer type, margin band, or contract status. The point is to apply the increase where it is supportable and to give the largest increase to the accounts where price is lowest relative to cost to serve. For that, see Customer Profitability Analysis and B2B Customer Segmentation for Pricing and Sales.

3. Sequence: notice, exceptions, effective date

Sequence has four parts: who is told first, how much notice, what exceptions exist, and the date every system flips. Notice length is set by your contracts first and by custom second. Where a contract specifies a notice period or mechanism, follow it exactly, and have counsel review the language of any letter that modifies terms. Where it does not, choose a notice period your customers can plan around and that your own backlog can absorb.

Exceptions are the main source of leakage, so they are budgeted. Before launch, decide the total exception allowance as a percentage of the announced increase, who can approve an exception, and what the customer must give in return, such as a term commitment, a volume floor, or a quicker payment schedule. An exception that cost you something and bought something is a trade. An exception that cost you something and bought nothing is a leak.

4. Sustain: measure realization, not announcement

Price increase realization % = Realized price change on invoices ÷ Announced price change

Measure on a constant basket: the same products or services, the same customers, before and after, so that mix does not contaminate the answer. Report realization weekly for the first eight weeks and monthly thereafter, by segment and by sales owner. If realization decays between month one and month four, the increase is being given back through the doors described in Why Price Realization Keeps Drifting: rebates, renewals, free freight, and unbilled work.

Step-by-step process

Each step has an owner and an output. Durations assume a mid-market company with one pricing owner; compress or extend to fit.

Weeks 1 to 2: Facts

1. Build the cost gap by line. Cost per unit or per hour at the last price action versus now. Owner: FP&A. Output: cost gap table.
2. Compute contribution margin and breakeven volume loss by line. Owner: FP&A. Output: table.
3. Pull the realized-price baseline. Last 12 months of invoices by customer and line, with discounts, rebates, and freight allowances where available. Owner: Finance. Output: baseline realized price by segment.
4. Inventory contracts and clauses. Price protection, indexation, notice, renewal dates, most-favored-customer language. Owner: Commercial lead with Legal. Output: contract matrix with the earliest date each account can be repriced.

Weeks 3 to 4: Design

5. Define 3 to 4 segments using the three dimensions above. Owner: Commercial lead. Output: segment list with account counts and revenue.
6. Set the increase by segment from the cost gap and the breakeven ceiling. Owner: CFO and Commercial lead jointly. Output: increase table, with the expected loss assumption written next to each row.
7. Set the exception budget and approvers. Owner: CFO. Output: written exception policy: who, how much, and what must be traded.
8. Choose effective dates and notice per segment based on contracts. Owner: Commercial lead with Legal. Output: dated schedule.

Weeks 5 to 6: Prepare the machine

9. Update every price source. ERP price lists, CPQ, e-commerce catalog, rep spreadsheets, and standing quotes. Owner: Operations or Sales Ops. Output: a checklist signed off per source, with a single effective-date cutover.
10. Decide how to handle open quotes and backlog. State the rule: quotes valid until their expiry date, backlog ships at the order price, anything unpriced goes at the new price. Owner: Sales Ops. Output: written rule and the count of affected orders.
11. Brief the sales team. One page per segment: the number, the reason, the talking points, the allowed responses, the exception path. Owner: Head of Sales. Output: training done and a question log.
12. Prepare the customer communication. Letter or email by segment, and a short FAQ. Owner: Commercial lead. Output: approved communications. Counsel reviews anything that modifies contract terms.

Weeks 7 to 8: Launch

13. Notify top accounts personally before general notice, with a named owner for each conversation. Owner: Account owners. Output: call log.
14. Send the general notice on the planned date. Owner: Commercial lead. Output: delivery confirmation.
15. Open the exception queue and log every request, decision, and trade. Owner: Pricing owner. Output: exception register.

Weeks 9 to 20: Hold the number

16. Weekly realization review for the first eight weeks after the effective date: realized versus announced by segment, exceptions granted versus budget, volume versus the loss assumption. Owner: Pricing owner. Output: one-page dashboard.
17. Respond to volume signals. Where loss exceeds the assumption, review account by account and decide to hold, trade, or reverse. Owner: Head of Sales with CFO. Output: decision record.
18. Close the loop at 90 days. Compare plan, realized price, volume, and margin dollars against the do-nothing case. Owner: CFO. Output: results memo and what to change next cycle.

Templates

Segment increase plan (copy into a spreadsheet)

Exception register

Contract clause matrix

Metrics and KPIs

Targets by method. Set the realization target from your own history: your last increase's realization at 90 days is the baseline, your best segment's realization is the stretch, and the breakeven volume loss is a hard floor on volume performance. Do not adopt a realization or attrition figure from an article or a vendor deck.

Common mistakes

1. Announcing a number without a realization report. If nobody measures invoices, the real increase is whatever the exceptions left.
2. Uniform increases. A flat percentage under-prices thin accounts and loses accounts it need not.
3. Ignoring the price list nobody owns. The ERP list is updated, the CPQ is not, and reps quote from a spreadsheet. Realization tops out at the least-updated source.
4. Unbudgeted exceptions. Each one is small. Together they decide the outcome.
5. Concessions without a trade. A concession for a term commitment or volume floor is a negotiation. A concession for nothing teaches the customer to ask.
6. Skipping the contract check. Notice periods, index clauses, and price protection are binding. Involve counsel, and follow your own agreements.
7. Treating the first quarter as the result. Concessions settle on rebate and renewal calendars. Measure again at 90 and 180 days.
8. Leaving commission on revenue. If reps are paid on revenue, they will trade price for volume. Align the incentive or accept the leakage.

Worked example

Illustrative. All numbers are made up to demonstrate the method. They are not benchmarks.

A distributor has a $40.0M book across three segments. Contribution margin is price minus variable cost, as a percentage of price.

Announced increase in dollars. A: 8.0 × 3% = $0.24M. B: 22.0 × 6% = $1.32M. C: 10.0 × 9% = $0.90M. Total $2.46M, which is 6.15% of the $40.0M book.

Realized increase in dollars (before volume loss). A: 8.0 × 2% = $0.16M. B: 22.0 × 5% = $1.10M. C: 10.0 × 7% = $0.70M. Total $1.96M, or 4.9% of the book.

Realization. 1.96 ÷ 2.46 = 79.7% of the announced increase. The $0.50M gap is exceptions, protected contracts, and quotes at the old price.

Breakeven volume loss at the realized increase. A: 2 ÷ (2 + 35) = 5.4%. B: 5 ÷ (5 + 30) = 14.3%. C: 7 ÷ (7 + 25) = 21.9%. Expected losses of 0%, 1%, and 4% sit well inside those ceilings.

Net contribution change. For each segment, new revenue is revenue × (1 − volume loss) × (1 + realized increase), and new variable cost is the old variable cost × (1 − volume loss). A: +$0.160M. B: +$1.023M. C: +$0.572M. Total +$1.755M of contribution.

What this tells the operator:

• The plan announced $2.46M and delivered about $1.96M of price, or $1.755M of contribution after volume loss. Report the $1.755M to the board, not the $2.46M.
• Segment C carries the largest breakeven cushion because its contribution margin is lowest, and it contributes $0.57M. Tail accounts are where the increase pays for itself most.
• The largest realization gap in dollars is in B ($0.22M), because it is the largest segment, so exception control in B matters most.

AI prompt assistance

Supply your own data and verify the output against the ledger before acting.

1. Build the cost gap and breakeven table.

I will paste cost per unit at the time of our last price increase, current cost per unit, current price, and variable cost per unit for 25 product lines. Compute for each: cost gap as a percent of price, contribution margin %, and breakeven volume loss for increases of 3%, 5%, and 8%. Show the formulas and flag any line where variable cost data looks inconsistent.

Check: recompute two lines by hand and confirm the contribution margin ties to your margin report.

2. Classify exception requests.

Here are 60 customer emails and call notes responding to our price increase. Tag each as: accepts, asks for delay, asks for exception, price protected by contract, threatens to leave, or other. Return counts and a table. Quote the sentence that justifies each tag.

Check: spot-check ten tags against the source text and have the account owner confirm the five most important accounts.

3. Compare realized price to announced price.

Here is an invoice extract for the same 200 SKUs and 80 customers before and after the effective date. Calculate realized price change per customer and per SKU, the share of the announced increase realized by segment, and list the 15 customers with the biggest gap between announced and realized. Do not average across different SKU mixes.

Check: confirm that the basket is constant and total a sample of invoices manually.

Implementation guide

Governance: the CFO owns the target and the exception budget, the Commercial lead owns segments and notice, Sales owns customer conversations, Legal owns contract review, and Finance owns the realization report. Report realization, exception cost, and contribution versus do-nothing monthly alongside margin.

What to expect: realization settles over one to two quarters as rebates, renewals, and backlog roll through, so judge the increase at 90 and 180 days rather than at 30.

Downloadable assets

The segment increase plan, exception register, and contract clause matrix above are designed to be copied into a spreadsheet. The EBITDA improvement calculator can translate a realized price change into EBITDA. The price waterfall builder computes list-to-pocket leakage from your own figures.

Related resources

• Price Waterfall Analysis: Right on Revenue, Blind on Cost: where list price leaks before it reaches pocket price.
• Why Price Realization Keeps Drifting: why concessions relocate after discount fixes.
• Discount Approval Matrix and Governance: the approval rules that protect a new price list.
• Margin Expansion Playbook: where price sits among the margin levers.
• Customer Profitability Analysis: choosing which accounts get the largest increase.

Frequently asked questions

How much volume can I lose from a price increase before it hurts?

Use the breakeven formula: price increase percent divided by the sum of price increase percent and contribution margin percent. A 5% increase on a 30% contribution margin breaks even at a 14.3% volume loss. Compute it by product line from your own variable costs, then compare it to a realistic loss assumption for each customer segment.

How should I notify customers of a price increase?

Follow the notice terms in each agreement first, then use a personal call from the account owner for your largest accounts before a general letter. The notice should state the amount, the effective date, and the reason. Have counsel review any communication that changes contract terms, since your own agreements govern what is permitted.

What is price increase realization?

Price increase realization is the share of the announced increase that appears on invoices, measured on a constant basket of customers and products. If you announce $2.46M and invoices show $1.96M, realization is about 80%. Track it weekly for two months after launch, because exceptions and old-price quotes reduce it quickly.

Should every customer get the same increase?

No, uniform increases usually overcharge accounts that are price sensitive and undercharge accounts that are already unprofitable. Segment by price sensitivity, current margin, and contract position, then set the increase by segment. Keep the segments few, so sales can explain the plan in one page per segment.

How soon can I tell whether a price increase worked?

Early signals such as volume, exception requests, and complaints appear within weeks, but the true result takes one to two quarters because rebates, renewals, and backlog settle on slower calendars. Review realization and contribution dollars at 90 and 180 days against a do-nothing baseline, not against last month.

How this works in a System of Performance

A price increase is a decision with a measurable outcome, and the outcome is usually scattered across the ERP, the CRM, and a spreadsheet of exceptions. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. If you want to see how much of your last increase actually reached the invoice, bring it to us as a launch partner.