Price Increase Announcement Email to Customers: 12 Templates

A price increase announcement email is one of the hardest messages a company sends all year, and most of them fail for the same three reasons: too little notice, no real explanation, and no distinction between customers who are affected differently. The result is a wave of cancellations arriving in the same 48-hour window, a support backlog that takes weeks to clear, and churn that a better-written announcement would have cut significantly.

This is a broadcast announcement — a company-wide price increase notification to an entire customer base — which is a different problem from the per-client rate letters you might send individually. The 12 templates below cover every scenario a company-wide change can take: a full base increase with and without a grandfather window, existing customers grandfathered while new signups pay the new rate, annual uplift clause invocations, CPI-linked adjustments, tier restructures, and the three objection reply scripts you need ready before the announcement goes out. Each template includes the subject line, all bracket placeholders with [OLD PRICE], [NEW PRICE], [EFFECTIVE DATE], and [GRANDFATHER WINDOW] where applicable, and a note on what makes this variant work.

When should you send a price increase announcement email?#

The single most common mistake is sending with too little notice. A customer who learns their bill is going up in seven days has no time to budget, no time to evaluate alternatives, and little reason to feel respected. Notice is not a courtesy — it is how a price increase lands as a considered business decision rather than an unpleasant surprise.

Thirty days is the workable floor for a modest, routine increase. Sixty days is more comfortable and appropriate for anything above 10 to 15 percent. For tier restructures or the retirement of a legacy plan — where some customers face a meaningful change to what they have, not just what they pay — sixty to ninety days gives customers time to make a deliberate decision. If your subscription contract specifies a notice period, follow it; if it does not, thirty days is the minimum, not the target.

Timing relative to the customer's billing cycle also matters. A price increase notice landing three days before renewal gives the customer no practical window to act, even if you technically gave thirty days from the announcement date. Set the effective date to a full billing cycle from when the announcement sends.

What does a good price increase announcement email contain?#

Every effective price increase email, regardless of scenario, needs the same five elements in roughly this order. Skipping one is usually where the email breaks down.

1. 1

   The new price and effective date, in the first two sentences

   Customers scan a price increase email for one thing: the number and when it hits. Burying it in paragraph three, after a long explanation of product investment, reads as evasive. State the fact plainly and early, then give context.

2. 2

   One honest reason, in one sentence

   Infrastructure costs have risen. The product has added significant capability since the price was last set. The team has expanded to support a growing customer base. Pick the one that is true and state it directly. Three paragraphs of justification invite more debate than a confident, brief explanation.

3. 3

   What existing customers should do, if anything

   If there is a grandfather window, a lock-in option, or a plan migration path, say so clearly with the deadline. If there is nothing for them to do except expect the new rate on their next invoice, say that too. Ambiguity generates more follow-up questions than clarity.

4. 4

   A direct channel for questions

   Give customers a way to ask questions or flag concerns: a reply-to address that someone monitors, a support link, or a name they can reach directly. A price increase email with no reply path forces customers to churn rather than ask.

5. 5

   What is not changing

   Close by naming what stays the same — their data, integrations, support tier, point of contact. A message that only addresses what is going up, with no anchor to continuity, reads as purely extractive.

Template 1: Existing customers grandfathered — new customers pay the new rate#

Use this when you are raising prices for new signups only and existing customers keep their current rate indefinitely. This is the highest-trust variant and typically the lowest-churn scenario: the email delivers good news to the reader, framing them as valued long-term customers. One risk is customers sharing the announcement and creating expectations you cannot honor at scale — include a clear cutoff date and state that the grandfather rate is for accounts active before that date.

Template 2: Full base price increase for all existing customers#

The most direct variant — no exceptions, no grandfather window, everyone moves to the new price on the same date. This works best when the increase is modest and well-justified, and when the product has added meaningful capability since the last price change. Keep the email short: longer justifications invite more scrutiny, not more acceptance.

Template 3: Grandfather window — lock in the current rate before the deadline#

A grandfather window gives existing customers a fixed period to lock in the old price — typically by committing to an annual plan or prepaying before the deadline. It converts anxious customers into annual subscribers and substantially reduces churn from the announcement. Keep the window short enough to create urgency: ten to twenty-one days typically outperforms longer windows, where the decision gets deferred until it is too late.

Template 4: Annual uplift clause — invoking your subscription contract terms#

For B2B subscriptions with an annual uplift or CPI adjustment clause written into the contract, this template invokes that clause without pretending the increase is something else. The tone is matter-of-fact, references the specific clause, and does not over-explain. Customers who signed a contract with this clause are expecting it. An overly apologetic tone for a contractual provision actually reads as stranger than a plain, professional notification.

Template 5: CPI-linked or inflation-tied price increase#

A CPI-linked increase ties the price change to a published index rather than an internal decision, which makes the reason external and verifiable. This works well for businesses whose own costs scale with inflation and who want to communicate that the increase is not discretionary. Name the specific index and the calculation so customers can verify it themselves — transparency here earns more goodwill than a vague reference to inflation.

Template 6: Tier restructure — your plan is changing shape, not just price#

A tier restructure is harder to communicate than a straight price increase because you are changing what the customer has, not only what they pay. The email must tell each customer which new plan they are moving to, what they gain or lose, and what the new price is. If some customers are moving to a nominally higher-priced tier but receiving a net benefit — more seats, higher limits, features they had been requesting — lead with the gain. If it is a price increase bundled with a plan rename, say so honestly.

Template 7: Feature expansion — the new price reflects what the product now does#

When a significant feature release justifies a price change, the announcement can link the two explicitly. This works when the features are real and the customer would, on reflection, agree the product today is meaningfully more capable than it was at the original price. Be specific about what has shipped — generic references to having invested in the product are substantially weaker than naming the actual capabilities.

Template 8: Legacy plan being retired — customers must choose#

When a grandfathered or legacy plan is being sunset, the email is a migration notice more than a price increase announcement. Customers need to know which plan they are moving to, when the old plan stops working, and what their options are. Give them a default migration path — where their account lands automatically if they do not choose — so inaction has a defined outcome rather than an ambiguous one.

Template 9: Annual or enterprise contract renewal at the new rate#

For B2B customers renewing an annual or multi-year contract, a price change lands differently than a month-to-month increase. The buyer often has a budget cycle, a procurement process, and a champion who needs to defend the renewal internally. Send this email early enough that the buyer has time to get approval before the renewal date — not the week before it.

Templates 10 to 12: The three objection scripts you need ready before the announcement goes out#

Three objections arrive in almost every price increase announcement: a threat to cancel, a request to be grandfathered individually, and a statement that the customer plans to downgrade. Each needs a different response. Treating all three the same — typically a defensive re-justification of the decision — either caves on customers who were never going to leave, or fails to address the real concern of a customer who has a legitimate one.

The key across all three replies: state your position once, calmly. Do not re-justify multiple times. Customers testing whether the number is negotiable will keep probing as long as you keep re-explaining.

Template 10: Reply when a customer threatens to cancel#

Template 11: Reply when a customer asks to be individually grandfathered#

Template 12: Reply when a customer says they will downgrade#

The hard version: announcing a price increase in the same quarter as an outage#

The timing of a price increase is almost always a business decision made independently of whatever else is happening in the product. The problem is that customers do not experience these events in isolation — they experience them in sequence. A price increase announcement landing in the same quarter as a major outage or a run of visible reliability problems is not read as two separate events. It is read as a company that had a difficult month asking to be paid more for it.

There is no template that makes this situation comfortable, because no template can undo the sequencing. What a company can control is the framing and the decision of whether to proceed at the original timing.

1. 1

   Delay the announcement if the outage is recent

   If the incident happened within the last 30 days and you have any flexibility on the effective date, delay the announcement by one billing cycle. The price increase still happens; it just does not arrive before customers have finished processing the service failure.

2. 2

   Acknowledge both in the same email if you cannot delay

   If the effective date is fixed and delaying is not an option, acknowledge the reliability issues explicitly in the price increase email rather than pretending customers have not noticed. A sentence like 'We know this quarter has had reliability issues we are still working through, and we understand if this timing feels off — here is what we are doing about it' does more work than any amount of positive framing around the increase itself.

3. 3

   Separate the credit and the announcement if customers were materially affected

   If an outage breached your SLA or caused significant disruption, separate the two issues completely: send the credit or resolution first, let that land, then send the price increase announcement as a separate email on a different day. Bundling 'here is your outage credit and also your price went up' in one message makes both pieces of news land worse than they would separately.

What to do when customers do not reply after the announcement#

Silence after a price increase announcement is not always acceptance. Some customers intend to act, get interrupted, and forget. Others are waiting to see if a follow-up clarifies their options before they decide. A short, single follow-up email sent three to five days before the effective date reduces last-minute cancellations by catching the customers who missed the first email or deferred the decision longer than they meant to.

The follow-up is not a second pitch or a repeated justification of the increase. It is a practical reminder: the price changes on this date, here is what to do if anything needs to change on your end. Keep it to three sentences. Customers who needed more information already replied; this email is for the ones who need a deadline to act, not a second explanation of why the price changed.

How AI Emaily helps send price increase announcements at scale#

Everything above is manual work: segment the customer list by plan type, draft a different email per scenario, fill in each customer's actual current price and new price and effective date, sequence the sends with enough notice, then track who replied, who is heading toward churn, and who still needs the follow-up. For a company with a few hundred customers or more, this is a multi-day project if it is done correctly — and when it is done incorrectly, with a single generic blast, the churn cost is substantially higher than the time saved.

We build AI Emaily, an AI-native email client that connects to Gmail, Outlook/Microsoft 365, and standard IMAP. For a broadcast like this one, you set the scenario per customer segment once — which template variant applies, what the old price was, what the new price is, when the effective date lands — and AI Emaily drafts a personalized email per customer using those variables and the voice you have set in your Personal Context brain and client profiles. Nothing about that process involves reading through your sent mail history; you define the parameters, and the drafts reflect them. In Copilot mode, every draft is queued for your review and nothing sends until you approve it — the right default for a message this commercially sensitive. Every send is logged with a full audit trail and can be undone. The practical result is that the announcement reaches every customer with the right template and the right numbers, without the manual copy-paste session that inevitably produces one email with the wrong price in it.