To plan a price increase, work out how much churn the increase can absorb before it loses money, decide which customers it applies to and by how much, check what your contracts allow, and send notice early enough for the new price to apply at renewal. The finance work is a one-page model and a timetable; most of the risk comes from skipping either and announcing a number that nobody has tested against the customer base.
October is when this matters. Many B2B contracts renew on 1 January, notice periods of 30 to 90 days are common, and next year's budget is being set right now. If the price increase is not decided this month, it usually slips a full year, and the budget gets built on prices you already think are too low.
Why is a price increase a finance decision, not just a sales one?
Because it is the one lever that changes revenue without changing cost. A 10% price increase on customers who stay goes straight to gross profit: no extra hires, no extra hosting, no extra marketing. Few other decisions a founder makes in a year have that profile.
A mistake is expensive in both directions. Raise too little, too late, and a year of inflation in salaries and suppliers erodes your gross margin. Raise too much, to the wrong customers, with too little notice, and you lose accounts you spent real money acquiring, along with the referrals and expansion they would have brought.
Sales and product teams tend to treat a price increase as a messaging problem. Finance should frame it as a trade-off: revenue gained from customers who stay, revenue lost from those who leave, and how sure we are about each. The broader case for treating pricing as a financial lever is in SaaS pricing strategy and its financial impact; this post is about the mechanics of actually doing it.
How much churn can a price increase absorb?
Start with break-even churn: the share of affected revenue you could lose and still end up where you started.
On revenue alone, the formula is simple. If you raise prices by p, the customers who stay must account for at least 1 / (1 + p) of today's revenue.
| Price increase | Break-even revenue churn (on revenue) | Break-even churn (on gross profit, 75% margin) |
|---|---|---|
| 5% | 4.8% | 6.3% |
| 10% | 9.1% | 11.8% |
| 15% | 13.0% | 16.7% |
| 20% | 16.7% | 21.1% |
The gross-profit column is the more useful one. When a customer leaves, you also stop paying the cost of serving them (hosting, support, payment fees), so you can afford to lose a little more. With a gross margin of m, break-even on gross profit is reached when the retained share is m / (m + p). At a 75% gross margin, a 10% increase breaks even if you keep 88.2% of affected revenue.
These figures are arithmetic, not predictions. The question for the founder and the sales lead is whether they believe incremental churn caused by the increase will be well below break-even. If the honest answer for a segment is "we don't know", that segment needs a smaller increase, a longer runway, or a test before a full rollout.
Two cautions. Break-even churn is measured against churn you would have had anyway, so only losses above your normal baseline count. And gross-profit break-even ignores the cost of replacing a lost customer: with a long CAC payback, losing customers costs more than the table suggests (see unit economics and SaaS metrics for how to measure it).
Which customers should the increase apply to?
Rarely all of them, and rarely by the same amount. Pull a customer list with, for each account, current price, list price, discount, contract end date, product usage, support load and gross margin. Then sort them into a few groups.
Legacy customers far below list price. Usually the biggest opportunity and the biggest risk. A customer paying 40% below today's list price is often your oldest and most loyal, and also your least profitable. Closing the whole gap in one step tends to feel like a punishment. Closing half of it this year and half next year, with a clear explanation, usually lands better.
Customers at or near list price. A standard increase applies. This is where an inflation-linked or annual uplift is easiest to justify.
Heavy users on flat plans. If a customer uses far more than the plan was designed for, the conversation is about moving to the right plan or tier, not about a percentage increase. This often changes the pricing architecture, not just the price.
Strategic or at-risk accounts. A handful of accounts where the relationship, a renewal already in negotiation or a reference value matters more than the uplift. Decide deliberately, write the decision down, and set a date to revisit it. Exempting them silently is how legacy pricing becomes permanent.
A simple illustrative segmentation for a company with €2.4M ARR might look like this:
| Segment | ARR (illustrative) | Proposed increase | Assumed extra churn | Net ARR effect |
|---|---|---|---|---|
| Legacy, deep discount | €600k | +15% | 6% | +€49k |
| At list price | €1,300k | +8% | 2% | +€76k |
| Heavy users, wrong plan | €300k | Move to higher tier, ~+25% | 8% | +€45k |
| Strategic / at-risk | €200k | 0% this year | 0% | €0 |
| Total | €2,400k | +€170k |
Net ARR effect is calculated as ARR × (1 − churn) × (1 + increase) − ARR. All numbers are illustrative; the point is that each line has its own assumption, and each can be challenged separately. Run the same table with churn at double your estimate as a downside case. If the downside is still positive or only slightly negative, the plan is robust.
What do your contracts actually allow?
Before modelling anything further, someone needs to read the contracts. Price increase plans fail more often on paper than on customer reaction.
Check, for each contract type you use:
- Fixed-price term. Most annual and multi-year B2B contracts fix the price for the term. The increase can apply at renewal, not before.
- Notice period for price changes. Many contracts require written notice before renewal, typically 30, 60 or 90 days. Miss the window and the old price rolls over for another year.
- Auto-renewal terms. Whether the contract renews automatically at the new price, or whether the customer has to sign something.
- Indexation clauses. Some contracts allow an annual uplift linked to a published inflation index (a national CPI, or the euro-area HICP) or a fixed percentage, without renegotiation. If you have one, use it consistently: an uplift you don't apply for three years is hard to reintroduce.
- Caps. Enterprise customers often negotiate a cap on annual increases, for example "no more than 5% or CPI, whichever is lower".
- Most-favoured-customer or price-protection clauses that tie one customer's price to what you charge others.
If you sell to consumers, the rules are stricter. In the EU, unilateral price changes in consumer contracts generally need a clear contractual basis and often give the customer the right to cancel; several US states have automatic-renewal laws with specific notice requirements. Take local legal advice before changing consumer prices; this post is about B2B.
For new contracts going forward, add a standard annual uplift or indexation clause now. It is the cheapest way to make next year's price review a non-event.
When should you announce it?
Work backwards from the renewal date and the notice period, then add time for the conversations.
| Step | For a 1 January renewal with 60 days' notice |
|---|---|
| Decide segments, increases and exemptions | By mid-October |
| Prepare customer list, letters, sales talking points, billing changes | Second half of October |
| Notify customers (in writing, per contract) | By end of October, well before the 2 November deadline |
| Account conversations for top customers and objections | November |
| New prices live in the billing system | Before the first January invoices run |
| First read on churn and downgrades | February to March |
Some practical points on timing:
- Tell your largest customers personally before the letter arrives. A call from the account owner or the founder turns a surprise into a conversation.
- Spread renewals, spread risk. If all contracts renew on 1 January, every churn decision happens in the same month. For contracts that renew throughout the year, apply the increase at each renewal date; cash and churn arrive gradually and you learn as you go.
- Give a reason, briefly. Product improvements delivered this year, higher costs, a move to align old plans with current pricing. Customers rarely accept "because we can", and they rarely need a three-page justification.
How do you put it into the budget?
This is where the finance discipline matters most. The temptation is to take the gross uplift, add it to next year's revenue line and move on. That overstates revenue twice: it ignores the churn assumption and it ignores timing.
Build the price increase into the annual budget as its own driver, not buried in the revenue growth rate:
- Revenue from existing customers at today's prices, with your normal churn and expansion assumptions.
- Price uplift by segment, applied from each customer's renewal date, not from 1 January for everyone.
- Incremental churn from the increase, by segment, also from the renewal date.
- Discount and concession allowance, because some customers will negotiate and sales will sometimes concede part of the increase to keep the account.
Keeping these separate lets you see, month by month, whether the increase delivered what you planned. If the budget assumed +€170k of net ARR and actuals show +€120k, you want to know whether that came from more churn, more concessions or fewer customers in scope than planned. A single blended growth rate cannot tell you.
On the accounting side, an increase that applies at renewal is simply the price on the new contract term; revenue is recognised at the new rate over that term. A change agreed in the middle of a contract is a contract modification under IFRS 15 and ASC 606 and should be handled by whoever runs your accounting, especially if there are discounts or bundled services involved.
How do you know if it worked?
Agree the scorecard before the increase goes out, so nobody reinterprets the result afterwards. For the first two renewal cycles after the increase, track:
- Gross revenue retention and net revenue retention of the affected cohort, against the same period last year.
- Churn and downgrades by segment, with the reason recorded at the time the customer leaves.
- Realised increase versus planned increase: how much of the list increase survived negotiation.
- Effective average price per customer (net of discounts), the number that tells you whether the increase stuck.
Report these monthly. If one segment's churn approaches break-even, you know what to adjust next year.
Common mistakes
- Raising prices only for new customers. Easy and painless, but it widens the gap between legacy and list prices every year, and the eventual correction gets harder.
- The same percentage for everyone. A uniform 10% is too much for some accounts and far too little for others.
- Letting sales grant exemptions case by case. Exemptions should be a list, approved once, with a reason and an expiry date.
- Forgetting the billing system. Price increases that are decided but not loaded into Stripe, Chargebee or the ERP before invoices run do not happen.
- Treating it as a one-off. A small annual review is far easier for customers to accept than a large correction every four years.
FAQ
How much should a B2B company raise prices?
There is no universal number. Start from break-even churn for each segment, then pick an increase where you are confident extra churn will stay well below it. For customers already at list price, increases in the mid-single digits are usually easier to land than large one-off jumps.
How much notice should you give customers before a price increase?
At least what the contract requires, and for annual B2B contracts 60 to 90 days is a sensible minimum even when the contract is silent. Key accounts should hear it personally before the written notice.
Should existing customers be grandfathered at old prices?
Temporarily, sometimes; permanently, rarely. Grandfathering makes sense as a transition, for example closing half the gap this year and half next year, but legacy prices that never move leave the oldest customers as the least profitable ones.
Is a price increase better than cutting costs?
They solve different problems, and many companies need both. A price increase that sticks improves margin on every future renewal without reducing capacity, which is why it belongs in the annual plan alongside cost decisions rather than as an afterthought.
Where to start
Pull this week's customer list with price, discount, renewal date and gross margin per account. That one spreadsheet answers most of the questions in this post: who is far below list price, who renews when, and how much churn each segment could absorb. If the notice window for 1 January renewals is still open, you have a few weeks to act on it.
If you want an outside view of where your pricing, margins and planning stand, the free financial diagnostic takes five minutes. If you would rather work through the model and the timetable together before next year's budget is locked, get in touch.