How should a SaaS company announce a price increase?

How should a SaaS company announce a price increase?

Announce it early, plainly, and personally. Tell existing customers what changes, when it takes effect, why, and what they can do before then, such as locking in the current rate on an annual plan. Lead with the facts, not with a feature list. Give enough notice that nobody is surprised by an invoice.

Price increases are one of the most nervous moments in a SaaS company's life. Founders worry about churn, angry replies, and public complaints. So they often do the worst thing possible: they bury the change in a long email full of new features and hope nobody reads to the end.

That approach backfires because customers always find out. They find out on the invoice. And a price change discovered on an invoice feels like a trick, even when the new price is fair.

Why do price increase announcements go wrong?

They go wrong because the company writes for its own comfort instead of the customer's clarity. Vague subject lines, soft language, and feature lists before the number all signal that the company is uneasy. Customers read that unease as a reason to be suspicious. Clear facts, stated calmly, read as confidence.

Timing is the other common failure. A two-week notice before a renewal gives a finance team no room to plan. Even customers who would happily pay the new price get annoyed when the budget surprise lands without warning.

And then there is inconsistency. The email says one thing, the pricing page says another, and the support team has not been told. Customers who ask a simple question get three different answers.

What should the announcement email say first?

The first lines should state the change and the date. Something like: "On a specific date, the price of your plan will change from the old amount to the new amount per month. Here is why, and here is what you can do before then." Put the number in the first paragraph, not the fifth.

Use a plain subject line. "Pricing update for your account, effective on a given date" is better than "Exciting news about your plan." The second one makes people feel managed. The first one respects their time.

Personalize what you can. If the customer is on a legacy plan, a discount, or an annual contract, say exactly how the change affects them. A generic email that ignores their actual situation creates support tickets.

How much notice should customers get?

Give at least one full billing cycle of notice, and more for annual customers and larger accounts. Monthly customers need time to budget. Annual customers need the change to land before their renewal conversation, not during it. The larger the account, the earlier the conversation should start, ideally from their account owner directly.

I would treat notice as a function of the customer's planning cycle, not your billing system. A small team paying monthly can absorb a change with a few weeks' notice. A company with a procurement process may need a quarter.

The renewal sequence is where this lands for annual customers. I covered how that sequence should read in what an annual renewal email sequence should say. A price change should fit into that sequence, not interrupt it.

How do you explain why prices are going up?

Give the real reason in one or two sentences. If the product has grown, name the specific improvements customers already use. If costs rose, say so. Avoid inflated claims about "delivering more value than ever." Customers can tell the difference between an explanation and a sales pitch, and they respect the explanation.

The strongest reasons point to things the customer has already benefited from. "Since you signed up, the product added a reporting module and doubled the integrations you rely on" is concrete. "The team has been working hard" is not a reason to pay more.

Do not apologize excessively either. A price increase is a normal business decision. One clear sentence of acknowledgment that it is a change for them is enough. Grovelling makes the decision sound weaker than it is.

Should you offer a grandfather period or a lock-in?

Usually yes. Letting existing customers keep the old price for a set period, or lock it in by switching to an annual plan, rewards loyalty and softens the change. The trade-off is revenue delay. For most early-stage SaaS companies, the goodwill is worth more than a few months of higher prices from the base.

An annual lock-in offer has a useful side effect. It turns a price increase into a reason to commit for longer, which improves retention and cash flow. Some customers will take it who would otherwise have stayed monthly.

Whatever you offer, give it a clear deadline. Open-ended grandfathering tends to become permanent, and a few years later you have a messy set of legacy prices that complicate billing and reporting.

What should change on the website and in the product?

Update the pricing page on the same day the announcement goes out, and make sure billing, in-app messages, and help docs match. If the new pricing applies only to new customers at first, say so on the pricing page. Every place a customer might check should give the same answer.

The pricing page is also where prospects will notice the change. If you are changing packaging at the same time, think carefully about how the page presents plans. I wrote about one of those decisions in whether to show annual or monthly first on a SaaS pricing page.

Public changelogs deserve a mention too. If you publish product updates, a short, factual pricing note there keeps the record clear for anyone researching you later. I covered how to write those for outside readers in what a SaaS changelog should say to non-customers.

How should support and sales prepare?

Brief them before the email goes out. Give support a short answer sheet covering the change, the date, the reason, the lock-in offer, and how to handle cancellation requests. Give account owners a list of their customers affected and a suggested talking point. Nobody customer-facing should learn about the change from a customer.

Decide in advance how much flexibility the team has. Can support offer an extra month at the old price to an unhappy customer? Who approves exceptions? Clear rules prevent inconsistent deals that cause problems later.

Track replies in a simple tag in your help desk. In the first two weeks, read every one. The patterns tell you whether the message landed, and whether a follow-up clarification is needed.

What should you do next?

Before announcing, write down the change, the effective date, the reason in two sentences, and any lock-in offer. Draft a plain email with the number in the first paragraph. Update the pricing page, billing, and help docs to match, brief support and sales, then send with at least a full billing cycle of notice.

After it goes out, watch replies and cancellation reasons closely for a month. A few unhappy customers are normal. A wave of confused ones means the message needs a follow-up.

If you are planning a pricing change and want help with the messaging, the pricing page, and the lifecycle emails around it, reach out. I am happy to look at your plan and tell you honestly where it might land badly.