You priced your SaaS in a hurry. Maybe it was $19 because a competitor charged $29 and you wanted to look like the safe choice, or maybe you just picked a number on a Sunday night so the Stripe checkout would work. A year later the product does three times as much, your hosting bill has crept up, and new customers keep telling you it is cheap. The obvious fix is to charge more. The scary part is the people already paying you.
This is a practical playbook for raising prices on existing customers when you are small: a few dozen to a few hundred accounts, no pricing team, and every cancellation feels personal. It covers when to do it, who the new price applies to, how much notice to give, the email itself, the billing steps, and what to say when people reply. It is not legal advice; if you sell to consumers or have unusual contracts, check the rules where your customers live.
The short answer
Raise prices for new customers first, then move existing customers with clear notice, a plain reason, and one fair way to keep the old price for a while. Small SaaS teams often lose fewer customers than they fear, as long as the email is honest, the date is clear, and nobody gets surprised by a charge.
New signups: switch them to the new price the day you decide.
Existing customers: give at least 30 days of notice for monthly plans and move annual plans at their next renewal.
Soften it once: offer an annual plan at the old price until the change date, or a few months at the old rate.
Bill carefully: change subscriptions at renewal, with no surprise proration charges.
Measure for 60 days: count cancels, downgrades and replies that mention price, not just MRR.
Signs it is time to raise prices (and signs it is not)
A price increase works best when it catches up with value you have already delivered. It goes badly when it is a patch for a product that people are quietly unhappy with. Before you write anything, be honest about which side you are on.
Good signs | Bad signs |
|---|---|
Prospects rarely push back on price in sales calls or emails | People already mention price when they cancel |
You have shipped real features since most customers signed up | The product has barely changed and support is slow |
Customers use it every week and would be stuck without it | Weekly active usage is falling |
Your costs per customer went up (AI calls, storage, support time) | You need cash next month and hope a price bump fixes it |
Competitors with similar depth charge noticeably more | You are cheaper because you are missing the basics |
If you set your first price without much data, the logic you used then still applies now. I wrote about pricing your first SaaS with almost no data, and most of the anchors in that post (what the job is worth, what the alternative costs) are the same ones you will lean on to explain the increase.
Step 1: Decide who the new price applies to
This is the biggest decision, and it is mostly about trust, not revenue. You have four realistic options.
Option | What it means | Good for | Watch out for |
|---|---|---|---|
New customers only | Everyone already paying keeps their price forever | Very early products, tiny increases, loyal first users | Your oldest customers end up paying the least for the most support, permanently |
Time-limited grandfathering | Existing customers keep the old price for 3 to 12 months, then move | Most small SaaS; it rewards loyalty without freezing your revenue | You must remember the date and tell people again before it lands |
Everyone, with notice | All customers move on one date after 30 to 60 days | Increases driven by real cost changes | Needs the clearest explanation; expect more replies |
Everyone, but a smaller step | Existing customers move to a middle price, new customers pay the full new price | Big jumps, like $19 to $39 | Two prices to track in billing and in your head |
For most founders reading this, time-limited grandfathering or a smaller step for existing customers is the sweet spot. Forever grandfathering feels generous, but three years later you will have a customer paying $9 a month on a plan you no longer sell, filing the most support tickets, and you will not have the heart to change it.
Step 2: Pick the number and do the break-even math
Founders usually under-raise because they imagine half their customers leaving. Do the arithmetic once and the fear gets smaller.
Here is an illustrative example. Say you run "Tallyroom", a made-up booking tool for small physio clinics. You have 140 customers paying $19 a month, so $2,660 in monthly recurring revenue. You decide new customers pay $29, and existing customers move to $24 after 90 days.
If every existing customer stays, revenue goes from $2,660 to $3,360 a month.
If 8 customers cancel because of the change, you have 132 at $24, which is $3,168. You are still $508 a month ahead.
To end up worse off, you would need to drop below 111 customers ($2,660 divided by $24 is about 110.8). That means losing 30 of 140, a little over 20 percent, from a single email.
Run the same math with your own numbers. If the break-even churn is far above anything you have seen in a normal month, the increase is probably safe. If it is close, raise less, or give a longer notice window.
Also write down the reason in one sentence before you write the email. Good reasons are specific: "We added team accounts, SMS reminders and the calendar sync you asked for, and our SMS costs doubled this year." Bad reasons are vague: "To continue delivering value." If you cannot write the specific version, wait until you can.
Step 3: Set the timeline and the notice period
Surprise is what makes customers angry, much more than the number itself. A simple timeline beats a clever one.
Day 0: change the price for new signups and update the pricing page.
Day 0 to 3: email every existing customer with the new price and the exact date it applies to them.
Change date minus 7 to 14 days: send a short reminder with the date, the new amount, and how to cancel or switch plans.
Change date: the new price applies at each customer's next renewal after that date.
Annual customers: they keep their current price until their renewal, and they get the notice well before it.
Thirty days is a sensible minimum for monthly plans, and 60 days is kinder for anything bigger than a small step. Read your own terms of service too: many say you can change prices with notice, and some promise a specific number of days. Keep that promise.
If you sell to consumers, the law may set the timing for you. In California, for example, the automatic renewal law was amended by AB 2863, effective for contracts entered into, amended or extended from July 1, 2025. For a fee change on an existing subscription it asks for a clear notice of the change, plus information on how to cancel, no less than 7 and no more than 30 days before the new fee takes effect. If you announce 60 days ahead, the reminder in step 3 lands inside that window. Rules differ elsewhere, and B2B contracts follow their own terms, so check what applies to you.
Step 4: Write the email like a person
The email does most of the work. It should be short, it should put the number in the first few lines, and it should come from you, not from "The Team". Here is a structure that works.
Subject line with the actual news: "Tallyroom pricing is changing on 15 January". Not "An update from Tallyroom".
The change in one sentence: old price, new price, the date it applies to them.
Why, in two or three concrete lines: what you shipped, what got more expensive.
What they can do: keep going and do nothing, lock in the old price on an annual plan before the date, move to a smaller plan, or cancel (with the link).
A real reply path: "Reply to this email and it comes straight to me."
A sample, again for the made-up Tallyroom:
Subject: Tallyroom pricing is changing on 15 January
Hi Dana,
Short version first: from 15 January, your Tallyroom plan moves from $19 to $24 a month. Nothing changes before then.
When you signed up, Tallyroom was a booking page and an email reminder. Since then we have added SMS reminders, Google and Outlook calendar sync, and team accounts for clinics with more than one practitioner. SMS alone now costs us about twice what it did a year ago. New clinics pay $29; you are moving to $24 because you were here early.
If you would like to keep today's price for another year, you can switch to the annual plan at the current rate ($190 a year, which works out cheaper than paying monthly) any time before 15 January from your billing page. If Tallyroom is no longer worth it at the new price, you can cancel from the same page and you will not be charged again.
If anything about this feels unfair for your clinic, just reply. It comes straight to me and I read every one.
Sam, founder of Tallyroom
Things to leave out: "We are excited to announce", a long paragraph before the number, and any line that makes canceling sound hard. People forgive a price increase. They do not forgive feeling tricked.
Step 5: Offer one fair way to soften it
One softener is enough. Three makes the email confusing and makes the increase look negotiable for everyone.
Annual at the old price: customers who commit for a year keep today's rate. You get cash up front and fewer cancels. If you do not have an annual option yet, here is my case for putting an annual plan on your pricing page early.
A loyalty step: existing customers pay a middle price for good, like the $24 in the example.
A delay: three or six more months at the old price, then the new one.
Whichever you pick, write the end date into the email and into your own calendar. A softener with no end date quietly becomes forever grandfathering.
Step 6: Change billing without surprise charges
A lot of the angry replies after a price change are not really about the price. They are about a weird charge: a prorated invoice in the middle of the month, a double charge, or a team plan that suddenly bills for one seat. Plan the billing side as carefully as the email.
If you bill with Stripe, a few details from the docs matter here:
Prices cannot be edited: you cannot change a price's amount through the API. Stripe recommends creating a new price and archiving the old one. Archiving keeps existing subscriptions on the old price active, which is exactly how grandfathering works in practice.
Archiving has a side effect: payment links that use that product are deactivated when you archive the price, so check any links in old emails, docs or your site.
Replace the item, do not add one: when you change the price of an existing subscription, you must pass the subscription item ID, or the new price is added next to the old one and the customer pays both.
Quantity resets: updating the price sets quantity back to 1 unless you pass it again. For seat-based plans, always include the current quantity.
Proration: changing the price mid-period usually creates a proration. For a price increase, either make the change at the start of the next billing period (subscription schedules are built for this) or turn proration off for the update.
Before touching real customers, run the whole change on one test subscription and on your own account. Then move customers in a small batch, check the next invoices look right, and only then do the rest. If you use Paddle, Lemon Squeezy or another billing provider, look up how it handles price changes on existing subscriptions before you send the email, because that decides what you can promise.
Step 7: Handle the replies
Expect replies within the first 48 hours. Most are calmer than you imagine. Answer them yourself, quickly, and keep a short list of the exceptions you make so you stay consistent.
What they say | A good response |
|---|---|
"Fair enough, thanks for the heads up" | Thank them. Ask what they would like next. These are your best interview candidates. |
"I can't afford this right now" | Offer the smaller plan or the annual option. For a genuine hardship case, a few extra months at the old price is cheap goodwill. |
"Competitor X is cheaper" | Do not argue. Say what you do differently in one line, and make canceling easy if they want to go. |
"I was an early supporter" | If they really were (beta user, gave feedback, referred others), a longer grandfather period is reasonable. Write it down. |
"Cancel my account" | Cancel it, confirm it, and ask one optional question about why. No save offer that was not in the original email. |
A useful rule: any exception you make for one person, you should be comfortable making for anyone in the same situation who asks.
Step 8: Measure what happened
MRR alone hides the story. For 60 days after the announcement, track a small sheet:
Cancellations where price was mentioned, compared with your normal monthly cancels.
Downgrades to a smaller plan.
Annual switches before the deadline.
Replies, sorted into fine, unhappy, and asked for an exception.
New-signup conversion on the pricing page, before and after the new price.
Monthly recurring revenue at day 30 and day 60.
With a small customer base these numbers are noisy, so read them as direction, not proof. If you have not set up basic tracking yet, start with the handful of product metrics that matter before your first 100 users and add the price-change columns to that same sheet.
A 30-day price increase plan
When | What to do |
|---|---|
Days 1 to 3 | Check the good and bad signs, pick who the change applies to, do the break-even math, write the one-sentence reason. |
Days 4 to 6 | Read your terms of service and any consumer rules that apply. Decide the change date and the one softener. |
Days 7 to 9 | Create the new price in billing, test the change on a test subscription and your own account, check payment links. |
Day 10 | Switch new signups and the pricing page. Send the email to existing customers. |
Days 10 to 14 | Answer every reply yourself. Log exceptions. |
7 to 14 days before the change date | Send the reminder with the date, the new amount, and how to cancel or switch. |
Change date | Move a small batch first, check invoices, then the rest. |
Day 30 and day 60 after the change | Review the sheet. Decide whether the new price stays, and what to change next time. |
Common traps
Hiding the number: burying the new price in paragraph four reads as a trick, even when it is not.
Raising everything at once: new plans, new limits and a new price in one email. Change one thing, so people understand it.
Vague reasons: "inflation" and "to keep improving" sound like excuses. Name what you built and what got more expensive.
Surprise proration charges: a mid-month invoice for $3.47 creates more angry emails than the increase itself.
Endless grandfathering: no end date means you will never move those customers.
Negotiating with everyone: if the loudest replies get the best deal, quiet loyal customers end up paying the most.
Waiting for the perfect moment: there is no month when nobody minds. Pick a date and keep it.
FAQ
How much can I raise prices on existing customers?
There is no safe percentage that fits every product. What matters is how the new price compares with the value customers get and with what they would pay elsewhere. Do the break-even math in step 2: if you could lose far more customers than you have ever lost in a month and still come out ahead, the step is probably fine. Big jumps are easier to accept as a middle step for existing customers.
Should I grandfather existing customers forever?
Usually not. A limited period, three to twelve months, rewards loyalty without leaving you with a group of customers on a price you can never change. Forever grandfathering makes the most sense for a tiny increase or a handful of true early supporters.
Do I have to tell annual customers now?
Tell them now that the change exists, and make clear their price stays the same until renewal. Then remind them before the renewal date with the new amount. Surprising someone with a much bigger annual charge is the fastest way to a chargeback.
What if a big customer threatens to leave?
Listen first. If their reason is about value, ask what would make the new price worth it; sometimes the answer is a feature you were already building. If you give them a longer grace period, treat it as a written exception with an end date, not a secret discount.
Should I announce the price increase publicly?
Update the pricing page and changelog, because new visitors should see the real price. A public post is optional. Your existing customers should hear it from you directly, by email, before they see it anywhere else.
The bottom line
A price increase is a message about your product, not just a number in Stripe. Tell people early, give a real reason, keep billing boring, and stay reachable while they react. Done that way, most customers will shrug, a few will thank you for the notice, and the ones who leave were probably on their way out anyway.
If you are getting ready to put a new price in front of more people, Aura++ is where founders launch and get discovered by early users who are already looking for tools like theirs.