SaaS Price Increase for Existing Customers | Do It Right

Photo by Tamanna Rumee on Unsplash

To raise prices on existing SaaS customers without losing them, grandfather your current customers for a defined period, give at least 30 to 60 days of clear notice, and lead the announcement with added value rather than the new number. The customers who churn over a price increase almost never leave because of the dollars — they leave because they felt ambushed, or because they'd already stopped getting value and the invoice reminded them. Get the communication right and a well-run increase raises revenue while barely moving churn. Get it wrong and you can trigger a cancellation wave that costs more than the raise brings in. This post covers the whole playbook: who to grandfather, how long to wait, exactly what the email says, and which mistakes do the real damage.

TL;DR

• Grandfather existing customers on their current price, at least temporarily — it's the single biggest lever for keeping churn low.
• Give 30–60 days of notice. A customer who learns about the increase from a charge, not an email, hears "you didn't tell me."
• Lead with value: what got better since they signed up. The price is the last thing in the message, not the first.
• Segment your base — loyal legacy users, recent signups, and power users each need a different treatment.
• Have a "save" offer ready for the handful who reply upset. Most of them stay when you give them a path.

Why customers actually churn over a price increase

Start with the counterintuitive part, because it changes every decision downstream: people rarely cancel because the new price is objectively too high. They cancel because of how the change arrived.

The Baremetrics guide to raising SaaS prices makes the point that a price increase, handled well, is one of the most reliable ways to grow revenue — and that the fear of losing customers is usually overblown relative to the upside. The damage comes from surprise and from a value gap, not from the arithmetic.

Two failure modes drive nearly all of it. The first is the ambush: the customer sees a charge that's higher than last month's, with no warning, and the trust breaks. It's not the money — it's the feeling of having a relationship changed without a conversation. The second is the value gap: the customer had already drifted, stopped logging in, forgot why they subscribed, and the new invoice is simply the prompt that makes them finally cancel. That customer was leaving anyway; the increase just set the date.

Both are fixable. The ambush is fixed by notice. The value gap is fixed by leading with what got better — and by accepting that some of those customers were never going to stay, which is fine. Understanding the difference between the two is the whole game, and it's why I treat a price increase as a communication project first and a billing change second. If you haven't looked closely at why your customers leave in the first place, churn analysis for non-tech founders is the prerequisite for this entire exercise.

Grandfathering: the strongest lever you have

Grandfathering means keeping existing customers on their old price while new signups pay the new one. It is the most effective single move for protecting your base during a price change, and it's popular for a plain reason: it removes the ambush entirely for the people most likely to feel it.

The Baremetrics framing calls this the "lock-in rates" method — you tell existing users the price is going up for new customers, but theirs won't change. That message does something powerful: it reframes the increase from a threat into a perk. Your loyal customers aren't losing anything; they're keeping something new people can't get.

There are three ways to run it, and the right one depends on how big the raise is.

| Approach | How it works | Best when | | --- | --- | --- | | Grandfather forever | Existing customers keep the old price permanently | Small base, modest raise, loyalty matters more than ARPU | | Phased migration | Old price held 6–12 months, then move to new rate with notice | Most situations — balances goodwill and revenue | | Forced migration | Everyone moves to the new price on a set date | Legacy pricing is unsustainable, or the raise is small |

Permanent grandfathering feels generous, and for a small indie SaaS it can be the right call — the goodwill compounds and the lost revenue is marginal. The tradeoff is that your average revenue per user gets dragged down by a growing pool of customers on old rates, and eventually you're running two or three price books at once.

For most founders the phased approach wins: hold the old price for six to twelve months so nobody feels rushed, then transition legacy customers to the new rate with the same clear notice you'd give anyone. It captures most of the revenue upside without the shock. If your increase is dramatic — more than 15 to 20 percent — some form of grandfathering or phasing isn't optional, it's the thing standing between you and a churn spike.

Segment before you send anything

Not every customer should get the same message, because not every customer represents the same risk or the same value. Before you write a word, split your base into at least three groups.

Legacy users are your long-tenured customers — the ones who signed up early, often at your lowest-ever price. They carry the most goodwill and the most reputational risk if they feel betrayed. These are the people to grandfather most generously. Losing one costs you more than the revenue; early customers talk, and a loud cancellation from a founding customer is expensive publicity.

Recent signups — anyone who joined in the last three to six months — are the easiest group to move to new pricing. They haven't anchored on the old number for long, and many signed up during your pricing transition anyway. In a lot of cases you can simply apply the new price to this cohort with light notice.

Power users and high-volume accounts deserve individual attention. These are the customers extracting the most value, which usually means they can absorb an increase — but they're also the ones a competitor would love to poach. A personal email from you, not an automated blast, is worth the time here.

Segmenting also protects you from a self-inflicted wound: sending a scary "prices are going up" email to a customer whose price isn't actually changing because they're grandfathered. That email generates cancellations for no reason. Say clearly, to each group, exactly what is and isn't changing for them. This is the same discipline that separates a good pricing experiment from a guess — I get into the mechanics of testing changes safely in pricing experiments for indie SaaS.

The notice period and the rollout timeline

Thirty to sixty days is the floor for notice on an increase that affects existing customers. Less than that and even a fair raise reads as abrupt. The notice period is not a courtesy — it's the mechanism that converts an ambush into a decision the customer gets to make on their own terms.

Here's the rollout sequence I'd run for a phased increase:

timeline
    title Price increase rollout
    Day -60 : Announcement email : Explain the change and the value : State the new price and the effective date
    Day -30 : Reminder email : Restate what is changing for this customer : Offer to talk to anyone with concerns
    Day -7  : Final reminder : Last chance to lock in the old rate if you are offering one
    Day 0   : New price takes effect : Confirmation on next invoice
    Day +7  : Save offers : Reach out personally to anyone who cancelled or replied upset

A few things make this timeline work. The 60-day lead gives annual customers time to plan and gives you time to hear objections before the change is live, not after. The mid-point reminder catches the people who read the first email and forgot. The one-week final notice creates a clean, honest deadline — especially valuable if you're offering existing customers a chance to lock in the old rate by upgrading to an annual plan.

That annual-lock offer is one of my favorite moves inside a price increase, because it turns a defensive moment into a retention win. "Lock in your current monthly rate for a full year by switching to annual before the change" gives price-sensitive customers a concrete, positive action instead of a cancel button. It also improves your cash position. I broke the tradeoffs down in annual vs monthly billing.

The announcement email, line by line

The email is where most increases succeed or fail. The structure that works inverts the instinct to lead with the news. You lead with value, state the change plainly in the middle, and close with respect for the customer's choice.

Here's the skeleton I'd use:

Subject: A change to your pricing on [date] — and what's new since you joined

Opening — value first. Two or three sentences on what's genuinely improved since this customer signed up. New features, better reliability, things you've shipped. This isn't spin; it's the honest answer to "why is this worth more now?" If you can't fill this paragraph truthfully, you're not ready to raise prices.

The change — plain and specific. One clean sentence: your price is moving from $X to $Y, effective [date]. No hedging, no burying it, no corporate fog. The customer respects directness far more than a paragraph of cushioning.

What it means for them. Spell out their exact situation. Grandfathered? Say so and say for how long. Getting a window to lock in the old rate? Give the deadline and the one-click way to do it. The customer should never have to do math to figure out what happens to their account.

The close — their choice, respected. Thank them, make it easy to reach a human with questions, and don't beg them to stay. Confidence reads as value; desperation reads as weakness.

The tone throughout is founder-to-customer, not corporation-to-user. "I've decided to raise the price because we've added X and Y" beats "We are writing to inform you of an adjustment to your subscription." You're a person they can reply to. Write like it. This is the same voice principle I use everywhere, and it's covered more broadly in SaaS pricing for non-tech founders.

On the mechanics: if you're on Stripe, changing a subscription price is a supported, well-documented operation — you create the new price and migrate subscriptions to it, and Stripe's billing documentation covers proration and effective dates so the customer's next invoice reflects the change cleanly. Do the communication first, then flip the billing switch. Never the reverse.

Have a save strategy ready

Some customers will reply upset. That's not failure; it's the cost of doing the thing at all, and it's smaller than you fear. What matters is having a plan for that handful before the emails go out.

The Baremetrics playbook and most pricing writers converge on the same idea: empower a simple save offer. For a solo founder that might be a one-time extension of the old rate, a couple of months free, or a small loyalty discount for customers who reach out. The goal isn't to cave on the whole increase — it's to give the specific people who care enough to email a graceful path to stay.

Most of them do stay. A customer who bothers to reply is a customer who still values the product enough to argue about it, which is the opposite of a lost cause. Treat those replies as retention conversations, not complaints. Answer them yourself, personally, quickly. The founder replying within the hour is a save mechanism no automated flow can match — it's the same edge I lean on in founder-led support.

Track what actually happens, too. Watch your cancellation rate for the 60 days around the change and compare it to a normal period. If churn barely moves, you priced and communicated well, and you now know you can do it again. If it spikes, you learned something about your value gap that matters far more than this one increase. Either way, the data tells you the truth that pre-launch anxiety cannot.

Frequently asked questions

How much notice should I give before a SaaS price increase?

At least 30 days, and 60 is better for customers on annual plans. The notice period is what turns a surprise charge into a decision the customer makes on their own terms. Anything less than a month reads as abrupt even when the raise itself is fair.

Should I grandfather existing customers or move everyone to the new price?

Grandfather, at least temporarily. Holding existing customers on their old price — permanently for a small loyal base, or for 6–12 months in a phased migration — is the strongest single lever for keeping churn low. Reserve forced migration for cases where legacy pricing is genuinely unsustainable.

How big a price increase is safe for existing customers?

Modest increases under 15–20 percent can often be applied with clear notice and little churn. Above that threshold, use grandfathering or a phased migration to avoid shock. The magnitude matters less than the communication, but large jumps compound the risk of the ones you don't warn.

What should the price increase announcement email actually say?

Lead with what's improved since the customer joined, state the old and new price and the effective date in one plain sentence, spell out exactly what changes for their account, and close by making it easy to reach a human. Put the value first and the number in the middle — never open with the increase.

What if customers reply angry about the increase?

Answer personally and fast, and have a save offer ready — a temporary extension of the old rate, a couple of months free, or a small loyalty discount. Customers who reply usually still value the product; most stay when you give them a graceful path. Treat the replies as retention conversations, not complaints.

Will a price increase hurt my churn rate?

Usually far less than founders fear, if you grandfather, give notice, and lead with value. Most churn around a price change comes from customers who'd already stopped getting value, not from the price itself. Measure your cancellation rate for 60 days around the change so you know the real impact instead of guessing.

Raise the price — carefully, once you've earned it

A price increase is not a betrayal of your existing customers. It's a normal part of running a business that keeps getting better, and the ones who've gotten value will mostly understand that — especially when you grandfather them, warn them, and lead with what they're getting rather than what they're paying. The founders who get burned are the ones who treat it as a billing task instead of a conversation.

If you're running your billing on Stripe and want a setup where price changes, proration, and the customer portal are already wired in so the mechanics never get in the way of the communication, Coding Capybaras is the free boilerplate I built for exactly this — Next.js, Supabase, and Stripe assembled so that when you're ready to raise prices, the hard part is the email, not the code.