# How to raise your SaaS prices without losing customers (with email templates)

Source: https://leverprice.com/blog/how-to-raise-saas-prices
Updated: 2026-11-17

> Test the new price on new visitors first. Moving from P1 to P2 keeps revenue flat if you lose at most 1 − P1/P2 of buyers, so $29 to $39 survives losing 25.6%. Then pick a grandfathering policy, give notice that lands on renewal dates, offer an annual pre-buy at the old price and track churn against the break-even.

Going from $29 to $39 a month keeps your revenue flat even if a quarter of your buyers walk away. The exact figure is 25.6%, and it takes one line of algebra to get there. Put your own prices into the [price increase calculator](https://leverprice.com/tools/price-increase-calculator) before you draft a single customer email, because that one number decides how careful the rest of the rollout has to be.

## How many customers can you lose when you raise prices?

You can lose up to 1 − P1/P2 of your buyers before an increase from P1 to P2 costs you revenue. Revenue is price times buyers, so the new price breaks even when P2 × (1 − loss) = P1. Solve for the loss and you get the formula.

```text title="Break-even loss after a price increase"
break-even loss = 1 - P1 / P2

$29 to $39:  1 - 29 / 39 = 0.256  ->  you can lose 25.6% of buyers
```

| Price move | Increase | Buyers you can lose before revenue drops |
|---|---|---|
| $9 to $12 | +33.3% | 25.0% |
| $19 to $24 | +26.3% | 20.8% |
| $29 to $35 | +20.7% | 17.1% |
| $29 to $39 | +34.5% | 25.6% |
| $49 to $59 | +20.4% | 16.9% |
| $99 to $129 | +30.3% | 23.3% |

*Figure: Line chart: the share of buyers you can lose after a price increase grows with the size of the increase, from 9.1% at +10% to 50% at +100%, with $29 to $39 marked at 25.6%. The share of buyers a price increase can lose before revenue falls. The curve flattens: doubling the price only survives losing half.*

Two refinements make the number more honest. If every customer costs you something to serve, such as hosting or model calls, use margin instead of price: break-even loss = 1 − (P1 − c) / (P2 − c). With $5 of cost per customer, $29 to $39 survives losing 29.4%, because the extra $10 is almost pure margin. Card fees barely move it. With Stripe's US rate of 2.9% + 30¢ as of November 2026 ([Stripe pricing](https://stripe.com/us/pricing)), the threshold goes from 25.6% to 25.9%.

The second refinement is time. A simple [customer lifetime value](https://leverprice.com/glossary/customer-lifetime-value) is monthly price divided by monthly churn: $29 at 3% churn is $967. That holds after the increase as long as the new churn stays below old churn × P2/P1. At 3% monthly churn, a $29 to $39 move still wins on lifetime value if churn stays under 4.0% (3% × 39 / 29). Write that number down; it is the one to watch after the change.

## Should you raise prices for new customers first?

Yes. New visitors have never seen your old price, so nobody loses a deal, and you learn what the new price does before any existing customer hears about it. Run the old and new prices side by side on new traffic, keep each visitor on the price they saw first, and compare revenue per visitor: everything you earned at a price divided by everyone who saw it. A higher price that converts a little worse can still earn more per visitor, and that is the number that pays you.

This settles the question that matters most, which is whether the market accepts $39. If $39 beats $29 per visitor after a few full weeks, you raise the price for everyone new and only then decide about existing customers. If it loses, you found out without sending one email. The time it takes depends on your traffic; [how long a price test should run](https://leverprice.com/blog/how-long-should-a-price-test-run) has the numbers, and [testing with low traffic](https://leverprice.com/blog/price-testing-low-traffic) covers small sites.

[Leverprice](https://leverprice.com/price-testing) does this step for you. You set a range such as $29 to $39, your server shows each new visitor one price from it, Leverprice follows them to a paid order confirmed by your payment provider's webhook and moves traffic toward the price with the highest revenue per visitor. Existing subscribers keep paying what their subscription says, because only new checkouts are priced.

If you bill through Stripe, the mechanics already favor this order. Stripe's API won't change the amount of an existing Price; the docs say to create a new Price, switch to its ID and deactivate the old one, and archiving a Price leaves every subscription on it active until it is canceled ([Stripe docs](https://docs.stripe.com/products-prices/manage-prices)). New checkouts get the new Price, existing customers stay put until you move them, and a subscription schedule can make that move at the end of their billing period ([Stripe docs](https://docs.stripe.com/billing/subscriptions/change-price)).

## Should you grandfather existing customers?

Grandfather existing customers when they will be a small share of next year's revenue, and move them, with notice, when they are most of it. [Grandfathering](https://leverprice.com/glossary/grandfathering) comes in three forms:

| Option | How it works | Fits when | What it costs you |
|---|---|---|---|
| Forever | Existing subscribers keep their price while they stay subscribed, often until they change plans | New customers will soon outnumber old ones, or trust is part of what you sell | The increase only reaches new customers, and legacy plans pile up |
| Time-limited | Existing subscribers keep the old price for 3 to 12 months, then move at their next renewal | Most SaaS products, and the default if you are unsure | A second announcement and a migration date to manage |
| None | The new price applies from each customer's next renewal after a notice period | Existing customers are most of your revenue and already get the value the new price reflects | The most cancellations in the short run, so the email has to be good |

Public examples cover the range. Pagecord, a small blogging platform, raised its annual Premium plan from $29 to $39 in March 2026 and kept existing subscribers at their rate for as long as their subscription stays active ([Pagecord](https://blog.pagecord.com/pagecord-premium-pricing-is-changing-on-march-16th)). TelemetryDeck kept paying customers on their plan at the original price until they switch plans or get auto-upgraded, a common condition worth copying ([TelemetryDeck](https://telemetrydeck.com/blog/pricing-update-2026/)). Buffer shows how long forever lasts: it launched new pricing in mid-2021 without forcing anyone to migrate, and at the end of 2023 its legacy plans still brought in $5.46 million of ARR, about 30% of the total ([Joel Gascoigne](https://joel.is/notes/Legacy_to_New_Buffer_MRR_transition_during_2023/)).

Example, with made-up but plausible numbers: 300 customers pay $29 a month ($8,700 MRR) and you move to $39.

- No grandfathering: if 8% cancel because of the increase, 276 customers pay $39, or $10,764 MRR, up 23.7%. You would have to lose 77 customers (25.6%) to end up behind.
- Six months of grandfathering: the same result half a year later, so you give up about $2,064 a month for six months, roughly $12,400, in exchange for goodwill and probably fewer cancellations.
- Forever: existing MRR stays at $8,700 minus normal churn, and the increase only shows up as new customers arrive.

A rule of thumb: if you expect to add more new revenue in the next 12 months than you have today, forever is cheap and buys a lot of goodwill. If you don't, use a time-limited window, and say exactly what ends it: a date, a plan change, or both.

## How much notice should you give before a price increase?

Give at least one full billing cycle, and make the new price start at each customer's next renewal instead of in the middle of a period they already paid for. For monthly plans that means 30 days or more. For annual plans, tell customers well before their renewal date so they can plan for it or renew early.

Large B2B vendors give more room. On August 19, 2021, Microsoft announced its first substantive Microsoft 365 commercial price change since Office 365 launched in 2011, effective March 1, 2022: six months of notice ([Microsoft](https://www.microsoft.com/en-us/copilot/blog/2021/08/19/new-pricing-for-microsoft-365/)). Slack announced its first increase since its 2014 launch in July 2022, about six weeks before it took effect on September 1 ([TechCrunch](https://techcrunch.com/2022/07/18/slack-is-increasing-prices-and-changing-the-way-its-free-plan-works/)).

Some notice rules are law. If you sell subscriptions to consumers in California, AB 2863 requires a clear notice of a fee change at least 7 and no more than 30 days before it takes effect, including how to cancel, for contracts entered into, amended or extended on or after July 1, 2025 ([AB 2863](https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202320240AB2863)). So if you announce 60 days ahead, plan a second notice inside that window. Other states and countries have their own rules, and this is not legal advice.

> [!TIP]
> Put a working cancel link in every price-change email, even where no law asks for it. A customer who can't find the cancel button may dispute the charge instead, and in the US Stripe charges $15 for each dispute on top of the refund (as of November 2026, [Stripe pricing](https://stripe.com/us/pricing)).

## Should you offer an annual pre-buy before the increase?

Yes, to monthly customers, with a deadline on the day the new price starts: pay for a year now at the old price and keep it for 12 months. Slack ran a version of this in 2022: Pro went from $8 to $8.75 per user per month on monthly billing and from $6.67 to $7.25 on annual billing, and customers could lock in the existing price for another year by renewing before September ([TechCrunch](https://techcrunch.com/2022/07/18/slack-is-increasing-prices-and-changing-the-way-its-free-plan-works/)).

Example: your monthly price goes from $29 to $39, and your annual plan was $290 (two months free). A customer who takes the pre-buy pays $290 today, an effective $24.17 a month, against $468 for a year at the new monthly price. You get the cash up front, and that customer has no cancel decision to make for 12 months, right when the increase makes cancelling most tempting.

It isn't free. At 3% monthly churn, a $39 monthly customer pays for about 10.2 of the next 12 months, around $398, so each pre-buy gives up about $108 of expected first-year revenue compared with a customer who would have stayed monthly and paid the new price. At 5% churn the expected year is 9.2 months ($358) and the pre-buy costs about $68. That is the price of taking churn risk off the table for your most engaged customers, paid in exchange for cash today. [What discount to give on annual plans](https://leverprice.com/blog/annual-vs-monthly-discount) has the full annual math.

Customers who already pay yearly get the same offer in a different shape: renew early, at the current price, for one more year.

## What should a price increase email say?

Say the new price and the date first, then the reason, then the options. Four rules cover most of it:

1. Put the old price, the new price and the date in the first two sentences. Nobody should scroll to find the number.
2. Give one concrete reason tied to what they use: features shipped since they joined, a cost that went up. "To keep delivering value" is not a reason.
3. Offer real options: the pre-buy, a cheaper plan if you have one, and a cancel link that works.
4. Send it from a person and let replies reach that person.

The three templates below cover the common cases. Replace everything in square brackets, and delete any line that isn't true for your product.

```text title="Email 1: existing customers, with grandfathering"
Subject: Our prices change on [date]. Yours doesn't.

Hi [first name],

On [date], the price of [Plan] for new customers goes from $29 to $39 a month.

Your price stays at $29 a month for as long as you stay on [Plan].
[Time-limited version: Your price stays at $29 a month until [end date].
From your first renewal after that date, it will be $39.]

Why we're raising it: since you joined, we've shipped [two or three
things this customer actually uses], and [one honest cost reason].
The new price pays for [what's next on the roadmap].

You don't need to do anything. If you move to another plan later,
that plan's current price will apply.

Questions? Just reply. This comes straight to me.

[Your name]
Founder, [Product]
```

```text title="Email 2: existing customers, no grandfathering"
Subject: Your [Product] price is changing on [date]

Hi [first name],

From your first renewal after [date], [Plan] will cost $39 a month
instead of $29. Until then, nothing changes.

Here's what the price covers now: [two or three shipped improvements].
[One honest cost reason.]

You have a few options:

- Keep $29 for a full year: switch to annual billing at $290 before
  [date]. [link]
- Move to [cheaper plan] at $[price] a month. [link]
- Cancel any time in Settings > Billing. You won't be charged again. [link]

If the new price doesn't work for you, reply and tell me why.
I read every answer.

[Your name]
Founder, [Product]
```

```text title="Email 3: annual customers"
Subject: Your [Product] renewal on [renewal date]: new price

Hi [first name],

Your yearly [Plan] subscription renews on [renewal date]. From that
renewal, the price is $390 a year instead of $290.

Want to keep $290 for one more year? Renew early before [date] and
your next 12 months stay at today's price. [link]

What's changed since your last renewal: [two or three improvements].

If you'd rather not renew, you can turn off auto-renewal in
Settings > Billing any time before [renewal date]. [link]

Any questions, reply here.

[Your name]
Founder, [Product]
```

## When should you raise prices?

Raise prices for new customers whenever you can measure the result, which means as soon as the test can run. Raise them for existing customers once the new price has held up on new traffic and you have something concrete to point to, such as features shipped since they joined or a cost that went up.

Then let the change land on each customer's own renewal date rather than on one big billing day. Cancellations spread out, your inbox stays manageable, and annual customers get the change at the moment they were going to think about renewing anyway.

Keep the increase on its own. If you raise prices and restructure your plans in the same month and churn jumps, you won't know which change caused it or which one to roll back.

## What should you measure after a price increase?

Measure churn and downgrades among existing customers against the break-even you computed, and revenue per visitor among new ones. Watch two windows closely: the days after the announcement lands and the days after the first charge at the new price.

| Metric | How to compute it | Compare with | Red flag |
|---|---|---|---|
| Churn, existing customers | Cancellations ÷ customers at the start of the month | Average of the three months before the announcement | Monthly churn heading past old churn × P2/P1 (4.0% if it was 3% on $29 to $39) |
| Cancellations that cite price | Exit-survey answers, from announcement to 60 days after the change | Your break-even loss (25.6% on $29 to $39) | Price-driven cancellations climbing toward the break-even |
| Downgrades | Customers moving to a cheaper plan ÷ customers | The same pre-announcement average | MRR after downgrades below what you had before |
| Refunds and disputes | Count and amount per week | The same pre-announcement average | A jump in the week of the first charge at the new price |
| New-customer [revenue per visitor](https://leverprice.com/glossary/revenue-per-visitor) | New revenue, net of refunds ÷ visitors who saw the price | The old price, ideally measured in a parallel test | Lower than the old price |

Before you announce anything, run through this list:

1. Compute the break-even loss and the break-even churn for your move.
2. Test the new price on new visitors and confirm it earns more per visitor.
3. Choose forever, time-limited or no grandfathering, and write down what ends it.
4. Set the date at least one billing cycle out, landing on renewals; for California consumers, plan a notice inside the 7 to 30 day window.
5. Prepare the annual pre-buy for monthly customers and early renewal for annual ones.
6. Send the email, then a reminder before the change.
7. Create the new price in your billing system and schedule existing subscriptions to move at the end of their period.
8. Track the metrics above for 90 days against your break-even numbers.

## Frequently asked questions

### How often should a SaaS company raise prices?

There's no fixed schedule. Raise the price for new customers whenever a test shows a higher price earns more per visitor, and change existing customers' prices no more than about once a year, so each increase can point to a year of shipped work.

### Can I raise the price in the middle of an annual subscription?

Usually not without the customer's agreement, because they prepaid for the term. Apply the new price at renewal, and check what your terms of service actually allow before you promise anything else.

### What if a large customer asks to keep the old price?

Offer the annual pre-buy or a longer prepaid term at the old price instead of an open-ended exception. Exceptions without an end date turn into a private price list you maintain for years.

### Should I tell customers why the price is going up?

Yes, in one or two sentences with specifics: what you shipped and what got more expensive. A vague reason reads as "because we can", and some customers will answer it with the cancel button.

### Do I need to email free users about a price increase?

Only if the change affects them, for example a new limit on the free plan. Otherwise update your pricing page and changelog, and new paid prices will reach free users when they upgrade.
