KoltrixHow to Announce a Price Increase by Email
Raising prices without losing trust comes down to notice, clarity and choice. How to structure the email, what to offer current customers, and handling replies.
On this page(8 sections)
- Decide the policy before you write the email
- Who is affected, and when
- How much notice
- Grandfathering choices
- What they get for the money
- The structure of the email
- Subject lines
- Sending it
- Send from a person, to the billing contact and the admin
- Stagger large sends
- Follow up with a reminder
- Handling the replies
- A short FAQ follow-up
- Pre-send checklist
- Key takeaways
Customers rarely leave because a price went up. They leave because the increase arrived as a surprise, read like a trick, or came with no reason they could repeat to their own boss. The email you send is most of the difference between those outcomes.
This is a practical guide to writing that email: how much notice to give, what to decide before you write a word, how to structure the message, and what to do when the replies start coming in.
Decide the policy before you write the email
Most bad price-increase emails are bad because the policy behind them was never settled. The writer is trying to sound confident about decisions nobody made. Settle these first.
Who is affected, and when
Write down exactly which customers see a change and on what date. New customers only? Everyone at their next renewal? Monthly plans on a fixed date and annual plans at renewal? Each group may need its own version of the email.
How much notice
There is no universal rule, but longer notice reads as respect. A common pattern is at least 30 days for monthly plans and at least one full billing cycle, often 60 to 90 days, for annual customers. Some contracts specify a notice period, and some jurisdictions have rules about changing subscription terms. Check your own terms and, if the stakes are high, ask a lawyer. This post is not legal advice.
Grandfathering choices
You have roughly four options for existing customers:
| Option | What it means | Good for |
|---|---|---|
| Full grandfathering | Existing customers keep the old price indefinitely | Small increases, early-adopter goodwill |
| Time-limited grandfathering | Old price for 6 or 12 more months, then the new one | Most SaaS increases |
| Lock-in offer | Switch to annual now at the old rate | Improving cash flow and retention at once |
| No grandfathering | Everyone moves on the same date | Increases tied to rising costs everyone understands |
There is no single right answer. What matters is that you choose one, apply it consistently, and can explain it in one sentence.
What they get for the money
If the price is going up because the product got better, list what changed since they signed up. If it is going up because your costs went up, say that plainly. Customers accept "it costs us more to run" more readily than vague talk about "investing in the future."
The structure of the email
Keep it short. One screen, plain formatting, from a real person's address. The structure that works almost every time:
- What is changing, in the first two sentences. No warm-up paragraph.
- When it takes effect for them specifically, as a date, not "next quarter."
- Why, in two or three honest sentences.
- What they keep, including any grandfathering or lock-in offer.
- What they can do, including switching plans or cancelling, with links.
- How to reach a person, with a reply-to that someone reads.
Here is an outline in that order:
Subject: Your plan price changes on November 1
Hi Priya,
On November 1, the Team plan moves from $40 to $49 per month. Because you've been with us since 2024, your account keeps the current price until May 1, 2027.
Why: since you joined we've added shared mailboxes, audit logs and a second region, and our hosting costs have risen. We'd rather raise the price once, clearly, than cut corners.
If you'd prefer to lock in today's rate for a year, you can switch to annual billing at $40 per month before October 31.
You can change or cancel your plan any time from Billing settings. And if this creates a real problem for your team, reply to this email. It comes to me.
Sam, co-founder
Notice what's missing: no "exciting news," no wall of feature bullets, no countdown timer. The numbers are in the body, not hidden behind a link.
Subject lines
The subject should tell the truth about the content. People search their inbox for billing emails later, and a subject that hides the change makes you look like you were hoping they'd miss it.
- "Your plan price changes on November 1"
- "Pricing update for your Team plan"
- "A change to our pricing, and what it means for your account"
Avoid "Important update about your account" with no details. It reads like phishing and gets ignored.
Sending it
Send from a person, to the billing contact and the admin
The account owner and whoever pays the invoices may be different people. Send to both if you have both. Send it as an individual email from a named person, and make sure replies reach your team rather than a noreply@ address.
Stagger large sends
If you have thousands of customers, send in batches over a day or two. That spreads the replies so your team can answer them properly, and it gives you a chance to catch a mistake in the first batch.
Follow up with a reminder
Send a short reminder about a week before the change takes effect: same facts, fewer words. Customers who missed the first email shouldn't learn about the increase from their card statement.
Handling the replies
Expect replies, and plan for them before you send.
Prepare short, honest answers to the predictable questions: Can I keep the old price? Why so much? Is there a discount for nonprofits or startups? What if I downgrade?
Decide your discretion in advance. Who can offer an extension? Up to how long? Write it down so the answer doesn't depend on who picks up the thread.
Answer every reply personally. A customer who took the time to object is telling you they care enough to argue. A thoughtful response, even a no, keeps many of them.
Track the themes. If ten customers say the same feature isn't worth the new price, that's product feedback, not just churn risk.
A shared inbox helps here. When the replies land somewhere the whole team can see, nobody answers the same customer twice and nothing waits in one founder's inbox over a weekend.
A short FAQ follow-up
For larger changes, a public FAQ page linked from the email cuts repeat questions. Keep it factual: the dates, the grandfathering rules, how to switch plans, and how to contact you. Link it once, near the end of the email, not as a replacement for the facts in the body.
Pre-send checklist
- Affected customer groups and dates written down
- Grandfathering policy chosen and documented
- Notice period meets your terms of service
- Each segment's email states its own date and price
- Sent from a named person, replies routed to a monitored inbox
- Reply playbook and discretion limits agreed
- Reminder email scheduled about a week before the change
- Billing system actually configured with the new price on the right date
Key takeaways
- Settle the policy (who, when, grandfathering) before writing a single line.
- Put the change, the date and the reason in the first few sentences, with real numbers.
- Give generous notice, offer a choice, and send a reminder before it takes effect.
- Treat replies as a conversation, not a support queue. Answer each one, and look for patterns.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
