Most advice on how to announce a price increase stops at the moment you hit send. That is the easy part. The hard part starts about four minutes later, when the first reply lands asking whether the old rate still applies. This covers both halves: the message itself, and the week of questions that follows it.
Settle the hard questions before you write anything
Most awkward price increases go the same way. The owner writes a lovely note, sends it, and then invents policy in real time as the replies come in. Decide these four things first and the writing gets easy.
- Who is exempt, if anyone. Existing customers at the old rate forever, existing customers until their next renewal, or nobody. Pick one and write it down. Changing your mind later, customer by customer, is how you end up with four different prices for the same thing.
- The exact date it starts. Not "next quarter." A date. It goes in the message, on the invoice, and into the answer to every question about timing.
- The number, in dollars. Give people the old price and the new price. "A 9% adjustment" makes everyone do arithmetic, and some of them will do it wrong and get annoyed at a number you never charged.
- What you will say to someone who asks for an exception. You will get asked. Decide now whether the answer is a flat no, a short price lock, or a move to a cheaper tier.
That last one matters more than the wording of the email. A polite message followed by five inconsistent answers does more damage than a blunt message followed by five identical ones.
How to announce a price increase: what the message has to contain
A price increase notice is a short, factual document. Six things belong in it and almost nothing else does.
- The person's name. Never "Dear Customer."
- What is changing, in dollars, old price and new price.
- The date the new price applies.
- Whether it affects them now or at renewal.
- One honest sentence about why.
- A direct way to reply to a human.
Send it on its own. Not inside a newsletter, not tucked under a product announcement, not as a surprise line on an invoice. If it arrives buried, people feel handled, and the reply you get back will be about the burying rather than about the price.
What to put in the price increase email, and what to cut
Cut the paragraph about your commitment to excellence. Cut the list of everything you shipped this year unless it is short and genuinely relevant to what they pay for. Cut the apology. Raising prices is a normal business event, and apologising for it invites an argument about whether you are allowed to.
Keep the reason to one sentence and make it true. "Our costs have gone up" is fine. "We are adding a second person to answer support" is better, if it is real. A reason you cannot back up comes straight back at you in the replies, and then you are defending the reason instead of stating the price.
A price increase letter you can actually send
Fill in the blanks and delete anything that does not apply. Short is good.
Subject: Your price is changing on (date)
Hi (name),
I am writing to let you know that (service) is going from (old price) to (new price), starting (date).
Any invoice before that date is unchanged. The new price applies from your first renewal on or after it.
Our costs have gone up over the past year and we have held this price since (year). The new rate keeps the same service running properly.
If you have questions, reply to this email and it comes straight to me.
Thanks for being a customer.
(signature)
That is about ninety words. Longer versions do not land better. They just give people more surface to argue with.
When raising prices is the right call
The usual signal is that your costs moved and your prices did not. If you have not looked at your rates in more than a year, you have probably already taken a quiet pay cut without noticing.
Two other signals are worth taking seriously. The first is that you are booked solid and turning work away, which almost always means you are under market. The second is that nobody ever questions your price. A little friction on price is healthy. Zero friction usually means you are the cheap option, and being the cheap option is a hard place to stay.
Inflation figures are published monthly by the Bureau of Labor Statistics, which is a decent sanity check on whether your increase is roughly tracking the cost of running the business or running well ahead of it.
The part nobody plans for: the replies
Here is where this stops being a writing problem and becomes a support problem. The announcement is one message from you. The response is a cluster of messages back, most of them in the first few days, and most of them asking the same five things.
The five questions that come back
- "Does this apply to me?"
- "When exactly does it hit my card?"
- "Can I lock in the old rate if I pay for a year now?"
- "What am I getting for the extra money?"
- "How do I cancel?"
That last one is often not a cancellation at all. It is a negotiating move, or someone checking that leaving is possible before they decide to stay. Answer it plainly and without drama. Making it hard to cancel at that exact moment is the quickest way to turn a wobble into a departure, which is the opposite of what you want if you are trying to reduce customer churn.
Answering the "can I keep my old rate" question
Three answers work. A flat no with a short reason. A price lock, where they pay twelve months upfront at the old rate. Or a move down to a cheaper tier that suits what they actually use.
Any of the three is fine. Giving different customers different ones is not. Pick one before you send, give the same answer to everybody who asks, and put an end date on it so the exception does not quietly become permanent.
Write the answers before you hit send
Draft a reply to each of those five questions, save them somewhere your team can reach in one click, and a stressful week turns into a twenty-minute task. If you already use saved replies, this is exactly what they exist for. Everyone answers the same question the same way, which is the entire point.
Then put those same answers on a public page. A short pricing-update article in your help center gives you something to link to in every reply, and it lets the people who would rather not email you find the answer on their own.
That page does a second job if you run a chat widget. Ours works by rules that search your own articles first, and then a model writes the answer in plain sentences from what those articles say. It can only use what you have written down, and it hands over to a person when it does not know. So the day you publish the pricing update is the day your chat starts answering "does this affect me" correctly at two in the morning. Skip the article and it has nothing to work from.
Stagger the send so your inbox can keep up
If you have two hundred customers and one person answering email, choosing to announce a price increase to all two hundred at nine on Monday morning is a decision to have a bad Monday.
Send in batches across three or four days instead. Start with your smallest or least price-sensitive group. You will find out which sentence people misread, fix it, and send the clearer version to everyone else. Leave your largest accounts until last, and if there are only a handful of them, phone those people rather than emailing.
Batching keeps your reply times sane, and that matters more than it sounds. A customer who waits two days for an answer about money has plenty of time to talk themselves into leaving.
A worked example
Say you run a cleaning business with 60 monthly clients at $120 each. That is $7,200 a month. You raise to $132, a 10% increase.
If four clients leave, you have 56 at $132, which is $7,392. You are up $192 a month and doing four fewer jobs for it. If eight leave, you have 52 at $132, or $6,864, so you are down $336 a month but you have freed eight slots worth $1,056 at the new rate if you can refill them.
The point of writing it out is that the scary version and the real version are rarely the same number. A 10% increase that loses 3% of customers still leaves you roughly 7% better off. Most owners imagine losing a third of their book, and almost nobody does.
What to watch in the two weeks after
Every time you announce a price increase you get a free piece of market research, and most businesses throw it away. For two weeks, tag every reply that mentions the new price. Then look at three things.
Who pushed back. If the complaints cluster in one group, the problem may be that the increase is aimed at the wrong tier rather than that it is too big.
What they compared you to. People name competitors when they are annoyed. That is research you would otherwise pay for.
What they said they would miss. Whatever customers bring up while deciding to stay is the thing to protect. It is rarely the feature you would have guessed.
Then count who actually left, not who threatened to. The gap between those two numbers is usually wide, and knowing your real number makes the next increase far less frightening. If you track customer lifetime value, run it again afterwards, because a modest increase with a small amount of churn often improves it.
Check your contracts first
Before any of this, read your own terms. If you promised a notice period in a contract or a service agreement, that period is a floor rather than a suggestion. Thirty days is the common minimum for month-to-month work. Sixty to ninety days is more usual for annual or contracted arrangements.
If you are not sure whether a change is allowed mid-term, that is a question for a lawyer and not for a blog post. It is a cheap conversation compared with unwinding a bad announcement.
Where we stand on this
We think pricing should be boring and predictable, which is why SupportifyGPT runs at $15, $39 and $79 a month with every feature on every plan and no per-answer fees. The tiers differ by how many seats you get and nothing else. You can see the whole thing on our pricing page, or start a free trial and watch how the inbox copes with a busy week before you commit.
For more on keeping customers through changes like this one, the rest of our small business posts covers the ground around it.
Ready to make customer support simple?
Start a free 14-day trial of SupportifyGPT. Every feature included, no setup fee, live in minutes.
Start your free trial