How to write a price increase notice
A structure that survives a customer reading it twice: what changes, when, why, and what stays the same for people already paying.
The four things a notice has to say
- What changes and by how much. The old price, the new price, the billing period, and whether it applies to existing subscribers or only to new ones. "Prices are changing" without a number creates the worst outcome: every customer assumes the largest number they can imagine.
- The date it takes effect. A date, not "in the coming weeks". If renewals are staggered, say which renewal it lands on.
- Why. One concrete sentence — added infrastructure, a new capability, a cost that moved. A reason is not a justification, and customers do not require it to be approved by them; they require it to be specific.
- What does not change. The features they use, the plan they are on, the support they get. This is the sentence that keeps a reader from scanning for the exit.
The order that works
Change first, reason second, grandfathering last. Leading with the reason reads as an argument the reader has to evaluate; leading with the number lets them react to the thing that affects them and then read the rest.
Grandfathering: decide before you write
Three patterns, each with a different cost:
- Everyone moves at renewal. Simplest to run, hardest to explain. Needs the clearest timing.
- Existing subscribers keep the old price for N months. Buys goodwill and a clean date; costs the difference for N months and creates two price tiers to support.
- Existing subscribers keep the old price permanently. Strongest retention signal, permanent revenue drag, and it accumulates: every later increase has to decide again.
Whichever you choose, write it as a rule, not a favour. "Your price stays at $29 for as long as your subscription remains active" is a rule; "we will try to keep you on the old price" is a promise nobody can hold.
A skeleton you can adapt
Subject: Your [product] price changes on [date] Hi [name], From [date], [plan] costs [new price] per [period] instead of [old price]. The change applies to [new subscriptions / all subscriptions at their next renewal]. [One sentence on why.] Everything else about your plan stays the same: [the two or three things they actually use], and your data stays where it is. [Grandfathering rule, in one sentence, or: "Nothing changes for you until your renewal on [date]."] If you have questions, reply to this email — it reaches the team that builds the product. [Name]
The announcement, the clause, the agreement, the approval
Four different artifacts get called "the price increase notice", and they are written for different readers:
- The announcement is the customer-facing message: email, in-app banner, and the pricing page updated on the same day. If the pricing page still shows the old number when the email lands, the customer reads the email as a mistake.
- The clause is the sentence in your terms or contract that allows the change: how much notice you owe, whether the change applies at renewal, and what happens to prepaid terms. It has to exist before the announcement does.
- The agreement is what an enterprise customer has signed — often with a fixed price for the term and a renewal uplift cap. A blanket announcement sent to those accounts is a contract problem, not a communication one; check the uplift language before the send list is built.
- The approval is internal: who signs off on the number, the segment exceptions and the grandfathering cost. One owner and one date beats a thread of approvals that produces three different numbers.
Words that make it worse
- "Slight" or "small" before the number. The reader decides whether it is small; calling it small first reads as an argument, and a 5% increase described as small is still 5% out of their budget.
- "Due to inflation" on its own. Every business faces it; the sentence carries no information about this product.
- "We're excited to announce" a price increase. Nobody is excited about paying more.
- A deadline that is not real. "Lock in the old price today" when the old price stays available next month teaches customers to ignore the next notice.
If you are on the other side of the notice
Price changes we have confirmed, with dates and readings, are on the moves page; the share of raises and the median increase are on SaaS price increases. If you were quoted a figure that no longer matches the pricing page, send it in.