Raising the price of a SaaS subscription: how to announce it on the pricing page without losing customers

The price set at a SaaS's launch is never final: infrastructure costs rise, the product grows, the team grows. A price increase almost always ends up becoming necessary. The problem is almost never the amount itself — a few extra euros a month usually go unnoticed in a budget. The problem is how the increase gets announced: the exact same increase, on the exact same pricing page, can go through without a single cancellation or trigger a wave of departures, depending on whether it's perceived as justified or as a plain extra charge.

Why a price increase feels unfair (or doesn't)

A now-classic study in behavioral economics surveyed hundreds of people about price-increase scenarios — the best known being a hardware store that raises the price of a snow shovel from $15 to $20 the morning after a big snowstorm (Kahneman, Knetsch & Thaler, 1986). Over 80% of respondents judged this increase unfair. But the same study also shows the opposite case: a company that raises prices to absorb a genuine rise in its own costs (raw materials, wages, rent) is seen as perfectly legitimate by a large majority, even when the final amount is identical. The authors call this the "dual entitlement" principle: customers accept that a company protects its existing profit margin, but not that it uses a shift in leverage to expand it. Applied to a SaaS: a price increase framed as "we had to raise our prices to cover rising hosting and support costs" is digested far better than one framed as "we're optimizing our pricing structure" — even at the exact same euro amount.

What reduces the sense of unfairness: justify, don't apologize

A synthesis published a few years later in the Journal of Marketing spells out what customers actually weigh when judging a price "fair" or not: they compare the new price to a reference price (what they used to pay, what competitors charge), and they look for a coherent explanation for the gap (Xia, Monroe & Cox, 2004). A precise, verifiable explanation — new features shipped since launch, more responsive support, more reliable infrastructure — significantly reduces the sense of unfairness, even without hard numbers to back it up. No explanation at all, or a vague line like "to keep offering you the best experience," produces the opposite effect: the customer fills the gap with the least flattering explanation available — pure profit-seeking.

Grandfathering: the most effective lever, and the least used

The lever that reduces the damage the most is "grandfathering": keeping the old price for existing subscribers, and reserving the increase for new customers. The idea connects directly to what we cover in our article on the status quo bias: an existing customer perceives their current price as something already earned, not just one line item among others — touching it feels like a loss, not an adjustment. Leaving it untouched, conversely, turns a price increase into a signal of appreciation for early customers. The trade-off has a real cost (two pricing tiers to maintain, an average revenue per customer that takes longer to climb), but it avoids most of the immediate churn that an across-the-board, unannounced increase triggers.

Notice period: never let customers discover it on their bank statement

There's no universal rule on how many days of notice to give, but the most common practice among SaaS companies that handle price increases well is around 30 days before the first charge at the new rate, announced by direct email — never buried only in a low-open-rate newsletter or in the terms of service alone. For a small business (coach, agency, solo creator), a note signed by the founder explaining the reason for the increase does more for retention than a generic message sent by the billing tool. By far the worst scenario is the customer discovering the increase when their card gets declined because it hits a limit they didn't expect — a case we cover in our article on failed payments and dunning: the follow-up after such a surprise charge starts with trust already damaged.

Where and how to write it on the pricing page

On the pricing page itself, the announcement doesn't need to be dramatic — it mainly needs to be visible and honest. A short banner above the pricing table ("The Pro plan moves to $49/month starting November 1st — current subscribers keep their existing price") saves the visitor from comparing a displayed price to a remembered one without understanding the gap. Our article on the anchoring effect applies directly here: if the new price stays below or close to the competitors cited for comparison, anchoring works in your favor instead of against you. A dedicated FAQ entry ("Why did the price change?") completes the banner for visitors who land on the page later, without having seen the announcement email.

What not to do

• Announce the increase only in the terms of service. Technically transparent, perceived as deliberately quiet — the opposite of the intended effect.
• Use a vague euphemism. "Pricing optimization" or "aligning our pricing structure" sound like a justification you're avoiding naming, which reinforces suspicion instead of dispelling it.
• Raise the price with no delayed effective date. Charging the new rate right at the announcement leaves the customer no room to decide, and they feel presented with a fait accompli.
• Ignore annual subscribers still mid-term. Applying an increase before the end of an already-paid cycle breaks an implicit agreement and, rightly, generates the harshest complaints.

Coordinating the increase with the billing cycle

The billing cycle shown on the page directly affects the right timing for a price increase. Monthly subscribers can move to the new rate at their first renewal after the effective date; annual subscribers deserve to wait until the end of their already-paid period, which mechanically gives a longer notice window and feels more respectful. On a usage-based offer rather than a flat plan, the logic changes: our article on usage-based pricing explains why an increase there is usually rolled out differently, often through adjusted usage tiers rather than a revised sticker price.

Setting it up on a LanderKit template

On a template like saas-waitlist, shipped as Next.js source code, a price-increase banner above the pricing table or a footnote on each pricing card can be added directly in Page.tsx without depending on a locked-down visual editor. Our article on building a SaaS pricing page covers that page's general structure; adding an increase notice follows the exact same logic of transparency.

What to remember

A price increase is never the problem in itself: it's the lack of justification, of notice, or of consideration for existing customers that turns a reasonable adjustment into a reason to leave. Justifying the increase with a verifiable fact, giving enough notice through a channel the customer actually reads, and considering grandfathering for existing subscribers are usually enough, on their own, to get a price increase through without a wave of cancellations.