How to Communicate a Price Change to Existing Customers

The email you send announcing a price increase matters far less than three decisions you make before you write a single word: how much notice you give, whether existing customers get grandfathered or migrated, and whether the increase comes with a visible reason. Get those three decisions right and a mediocre email will land fine. Get them wrong and the most beautifully written email in the world will still generate a wave of cancellations and support tickets.

Price increases feel like a communications problem, so companies default to treating them as one — hire a good copywriter, workshop the subject line, A/B test the send time. That’s optimizing the wrong layer. The actual driver of customer reaction is the structure of the change itself: how much runway customers have to react, whether they feel like they’re being punished for loyalty, and whether the price change is legible as fair or arbitrary.

Give real notice, not legal-minimum notice

Most subscription agreements require 30 days’ notice for a price change, and most companies send exactly 30 days’ notice because that’s the compliance floor. But the legal minimum and the goodwill-preserving minimum are different numbers. Thirty days feels, to a customer, like being informed of a decision that’s already final and non-negotiable — because functionally, it is. There’s no time to budget for it, escalate internally if they’re a B2B buyer needing approval, or seriously evaluate alternatives before the new price hits their card.

Sixty to ninety days of notice changes the emotional register of the announcement from “this is happening to you” to “we’re giving you time to plan for this.” For B2B customers specifically, 90 days often aligns with a budget cycle, which matters enormously — a customer whose finance team needs to approve a renewed higher spend can actually get that approval in 90 days. They usually can’t in 30. The extra notice costs you nothing except the willingness to announce the change before you strictly have to, and it consistently reduces the reflexive cancellation response that comes from feeling ambushed.

Decide on grandfathering deliberately, not by default

Whether long-tenured customers keep their old price or migrate to the new one is the single highest-leverage decision in the entire process, and it’s often made by default (usually “everyone migrates”) rather than deliberately. Grandfathering existing customers at their current price while raising prices only for new signups protects your most valuable relationships — the customers who’ve stuck around, who have the most switching cost already sunk into your product, and who talk about you to prospects and peers. Losing one of those customers over a price increase does disproportionate damage relative to losing a newer, less-invested customer.

The tradeoff is real: grandfathering forever means your average revenue per account creeps upward slower than it could, and you end up running multiple price tiers indefinitely, which adds operational complexity to billing and support. A middle path that works well for many SaaS companies is grandfathering for a defined window — say, honoring the old price for 12 more months, with clear communication that the new price applies after that — which gives long-tenured customers a meaningful transition period without permanently forking your pricing structure.

Whatever you decide, decide it before you write the customer email, because the framing of the email depends entirely on which group a given customer is in. An email announcing a price change to a grandfathered customer should read completely differently — more like a heads-up about the future — than one going to a customer whose price changes in 60 days.

A worked example: what grandfathering actually costs versus what it saves

Say a SaaS company with 4,000 existing customers on a $99/month plan raises new pricing to $129/month, a 30% increase. Full migration of every existing customer to the new price, effective in 60 days, adds roughly $1.44M in incremental annual recurring revenue if nobody churns. But price increases do cause churn — for a change of this size, even a well-communicated one, expect somewhere in the range of 3-6% of the affected base to cancel within two billing cycles who wouldn’t have otherwise, meaning the realistic net gain is closer to $1.15M-$1.28M once churn is netted out, concentrated disproportionately among newer, less-invested customers who have the least switching cost.

Compare that to grandfathering the existing 4,000 at $99/month indefinitely and applying $129 only to new signups: the immediate revenue gain is $0, but the avoided churn (and the account management cost of handling several hundred cancellation conversations) is real money too, and the long-tenured customer base — typically the highest-margin, most-referring segment — stays fully intact. The 12-month defined grandfather window sits between these: existing customers get a concrete date (say, 12 months out) at which their price becomes $129, giving the business the full $1.44M eventually while giving customers enough runway that the churn rate on the eventual migration tends to land closer to 1-2% instead of 3-6%, because nobody feels ambushed by a change with a full year of advance notice. Modeled over 24 months, the defined-window approach usually nets out ahead of both a full immediate migration and permanent grandfathering, which is why it’s the default a lot of experienced pricing teams reach for rather than treating grandfathering as strictly binary.

Anchor the increase to something visible

A price increase that arrives with no explanation reads as pure extraction, and customers respond to unexplained extraction with suspicion, even if the increase is entirely reasonable. A price increase that arrives paired with a specific, visible improvement — a new feature set, a capacity increase, a support tier upgrade — reads as a value exchange, even if the customer doesn’t personally use the new feature.

This doesn’t require the new feature to be the actual reason for the price change (increases are often driven by cost structure, market repositioning, or margin targets that have nothing to do with any single feature). But pairing the announcement with something tangible gives customers a mental hook to hang the change on, rather than leaving them to conclude the company is just charging more for the same thing. If you have a roadmap item shipping in the next quarter, timing the price announcement to land alongside it — even loosely — does real work in how the increase is received.

Segment the message by relationship, not just by plan

A single blast email to every customer treats a two-month-old trial convert the same as a five-year enterprise account, and that’s a mistake. At minimum, split communication into three tracks:

• High-value, long-tenured accounts get a direct outreach from their account manager or a senior team member before the mass email goes out — a phone call or personal note that gets ahead of the announcement, explains the reasoning, and gives the customer a chance to ask questions privately rather than reacting publicly or via a support ticket.
• Standard active accounts get the well-crafted email, sent with maximum notice, clearly stating the new price, the effective date, and (if applicable) any grandfathering terms.
• At-risk or low-engagement accounts — customers already showing usage decline or support friction — need extra handling, because a price increase is often the trigger that turns a slow-fade churn risk into an immediate cancellation. Consider a specific save offer or a proactive check-in for this segment before the price change email goes out broadly.

What to actually put in the email

The email itself should do four things in this order, without burying any of them in corporate hedging: state clearly and immediately what’s changing and when; state the new price in dollar terms, not just a percentage (customers do the math themselves anyway, so do it for them); give the reason in one or two sentences without over-justifying (over-explaining reads as defensive); and give a clear, easy path to ask questions or talk to a human, especially for larger accounts.

Avoid two common mistakes in the copy itself. First, don’t bury the price change beneath paragraphs about “exciting improvements” — customers scan for the number and the date, and if they have to hunt for it, the email reads as evasive. Second, don’t apologize excessively. A brief, confident explanation lands better than a long, apologetic one, because over-apologizing signals that even you think the increase is hard to justify.

Handling the immediate aftermath

Expect a spike in support volume and cancellation requests in the days immediately following the announcement, even if the overall churn impact ends up being small. Staff support and success teams for this in advance rather than reacting to it live — a customer who emails with a cancellation threat and waits three days for a response is far more likely to actually leave than one who gets a same-day, empathetic reply from someone empowered to offer a resolution (whether that’s a temporary discount, an extended grandfather period, or simply a clear explanation).

Track cancellation requests specifically tagged to the price change separately from your baseline churn rate for at least one full billing cycle after the change takes effect. This gives you a clean read on the actual impact, rather than folding it into a monthly churn number where it becomes hard to isolate from unrelated churn causes.

The failure mode that undoes all of the above: a leaky rollout

The single most common way a well-designed price increase still goes badly is sequencing failure — the announcement leaking or landing unevenly before the company controls the narrative. This happens more often than it should: a support agent mentions the new price to a customer who asks, days before the official email goes out; a pricing page updates before the notice email sends, so a customer checking the site sees the new number with zero context; an account manager tells one enterprise customer in a casual call before the broader segment communication is ready. Any of these creates a version of the announcement where customers find out from the wrong source, at the wrong time, without the framing the company intended — and a customer who discovers a price increase secondhand almost always assumes the worst about the reasoning, regardless of how fair the actual increase is.

Guard against this with a hard internal freeze: nothing customer-facing (pricing pages, support scripts, sales collateral, account manager conversations) changes until a specific announced go-live moment, and every customer-facing team gets briefed with the final messaging 24-48 hours before that moment, not left to find out from a customer asking about it. The account manager and support playbook should exist and be trained on before a single email goes to a single customer, because the highest-value conversations (the ones described in the segmented approach above) are exactly the ones most likely to happen ad hoc and off-script if the team isn’t prepared in advance.

Measuring whether the rollout actually worked

Beyond the cancellation-request tracking already mentioned, put a small number of specific metrics on a dashboard for the 90 days following the announcement rather than relying on a gut read of “it seems fine.” Track: the cancellation rate for the affected cohort specifically, compared against that same cohort’s historical baseline churn rate (not the company’s overall churn rate, which will dilute the signal); the volume and sentiment of support tickets tagged to the price change, reviewed weekly for the first month; the save rate on any retention offers extended to at-risk accounts during the rollout; and, for B2B accounts specifically, the renewal outcome at the account’s next natural renewal date, since B2B reactions to a price change are often delayed until the actual renewal conversation rather than showing up immediately.

A rollout that’s working shows cancellation-request volume declining week over week after an initial spike, support sentiment shifting from confusion to acceptance within two to three weeks, and renewal outcomes at or above the pre-increase baseline once the affected cohort actually reaches its renewal date. A rollout that isn’t working shows sustained (not declining) cancellation requests past the third week, or a renewal cohort converting meaningfully below baseline — either of which is a signal to intervene (extended grandfather periods, proactive account manager outreach, or in extreme cases revisiting the size of the increase) before the next cohort hits the same wall.

The long-term signal

How a price increase is handled becomes part of how existing customers perceive the company going forward, independent of whether they personally cancel. A price change communicated with real notice, a fair grandfathering policy, and a visible reason reinforces that the company treats its existing customers as partners rather than a captive revenue base to be squeezed whenever convenient. One handled with minimum notice, no grandfathering, and no explanation does lasting damage to trust that shows up in renewal conversations for years, long after the immediate cancellation spike has passed.