How to Announce a Price Increase Without Losing Customers
The price rise rarely drives customers out. How you announce it does. Here is how to raise B2B prices and keep the accounts already paying you.
You decide to raise prices. The increase is justified: your costs are up, and the service does more than it did two years ago. Then three accounts cancel within the month, and two more go quiet before renewal. The rise was reasonable. The announcement is what cost you the revenue.
A price increase handled badly is one of the most preventable causes of churn. The customer was already paying you. You had already spent the money to win them. When they leave over how the change was delivered, you lose that revenue and you pay again to replace it. Winning a new customer costs five to 25 times more than keeping one you have (Bain, via Harvard Business Review, 2014). Every account you lose to a poor announcement is an account you now refill at full acquisition cost.
The increase is not the problem. The surprise is.
Customers expect prices to move. What they do not forgive is finding out at the invoice, with no warning and no context. By then the only signal they get is a higher number, and the only decision in front of them is whether to pay it or leave.
Advance notice changes the conversation. Told early, the customer has time to plan, raise questions, and get internal sign-off. Told at billing, they feel managed, and a frustrated buyer with a renewal coming up is the easiest account a competitor will ever take.
Tell them why, in specific terms
A price change with no reason reads as a grab. A price change with a clear reason reads as a business decision the customer can understand. HBR research (2021) found that customers accept increases more readily when the company explains why, rather than leaving them to guess.
"Rising costs" is not a reason; it is a shrug. Name what changed: the capability you added, the support you expanded, the input cost you absorbed for two years and no longer can. Specific reasons hold up. Vague ones invite the customer to decide you are simply charging more because you can.
Sequence the announcement by account value
The default move is one email to the whole base at once. It is also the riskiest. Your largest and your most fragile accounts get the same templated note as everyone else, and the ones you can least afford to lose are the ones most likely to react.
Sort your accounts first. Your highest-value contracts and any account already showing strain hear the news first, from a person, by call or meeting. The rest can follow by written notice. The cost of a personal conversation with twenty key accounts is nothing against the cost of losing one of them.
Lead with the value already delivered
You are not asking permission. You are informing a customer, and the stronger the evidence behind the change, the easier it lands. Before the price conversation, remind the account what they have got: results delivered, usage to date, problems solved since the last renewal.
A customer who can see the value has a reason to stay through a price change. A customer who has heard nothing from you since onboarding has only the new number to judge you on. The work of holding the account starts months before the announcement, in the communication that keeps the relationship warm.
Handle the pushback before it becomes a cancellation
Some customers will push back. That is not a failure; it is the moment that decides retention. Give your team the answers in advance: why the change, what stays the same, what the customer gets, what options exist for early renewal at the current rate.
Route every concern to a named person, not a form or a no-reply inbox. A buyer who feels heard renews. A buyer who feels processed starts taking the competitor's call. The accounts that go silent after the announcement are the ones to chase first, because silence before a renewal is rarely agreement.
What to do next
Sort your accounts by value and by risk before you write a word of the announcement. Decide who hears it first and how. Write the reason in specific terms, set the notice period to land well before each renewal, and brief your team on the objections they will face.
To size what is at stake, use your own figures: your account count, your average contract value, and the share you expect to resist the change. The accounts you lose to a clumsy rollout are revenue you keep with a planned one. That is the work: find where the experience breaks, build the fix, and stay until the number holds.
