# A SaaS Price Increase Email Template

> A SaaS price increase email template with guidance on notice periods, explaining reasons, offering options, segment variations, follow-up and preparing support for questions.

Source: https://comppound.com/blog/a-saas-price-increase-email-template (published 2026-09-27)

Announcing a price increase is one of the most sensitive emails a SaaS company sends. Customers may feel frustrated, worried about their budget, or caught off guard, and a badly worded message can turn a reasonable change into a reason to shop around. A clear, respectful email reduces confusion, keeps support volume manageable and limits churn. This guide gives you a SaaS price increase email template you can adapt, explains the reasoning behind each part, and covers the work around the email that decides whether the change lands well.

## The principles behind a good announcement

Five ideas shape every good price increase email. Give customers notice, be clear about what is changing, explain why, offer options, and make help easy to reach. They sound obvious, but most of the angry replies companies receive trace back to skipping one of them.

Notice matters because B2B customers rarely control their budgets alone. A team lead who learns about a price change a week before it takes effect may need to justify it to finance, which takes time they do not have. Clarity matters because vague language ("we're updating our pricing structure") makes people assume the worst and then go hunting for the real number. The explanation matters because customers accept change more easily when they can see what they are paying for. Options matter because a customer who feels trapped is far more likely to cancel than one who can choose a different path. And support matters because some customers will have questions or genuine hardship, and they need a human to talk to.

## How much notice to give

Give customers enough time to plan. Many SaaS companies provide somewhere between 30 and 90 days of notice, with longer periods for annual plans and larger accounts. The right number for you depends on your contracts, your customers' buying process and any rules that apply in the regions where you sell. Before you choose a date, read your terms of service and any signed agreements. Some contracts specify a minimum notice period, and some lock pricing for the length of the term.

As a rule of thumb, the bigger the change and the bigger the customer, the more notice you should give. A small increase on a monthly self-serve plan can work with a shorter window. A large increase for a customer who needs procurement approval needs months. If you are unsure, err longer. Extra notice costs you a little revenue in the short term and buys a lot of goodwill.

## The template

Here is a base template. It is written for a monthly self-serve customer and can be adjusted for the segments covered later.

> **Subject:** Changes to your [Product] pricing on [date]
>
> Hi [Name],
>
> We're writing to let you know about an upcoming change to your [Product] subscription.
>
> Starting [date], the price of your [plan] will change from [old price] to [new price] per [period].
>
> **Why we're making this change**
>
> Over the past year, we've [added specific improvements]. To keep investing in [areas customers care about], we're updating our pricing.
>
> **What this means for you**
>
> Your current price stays the same until [date]. Your first charge at the new price will be on [date].
>
> **Your options**
>
> You can switch to annual billing before [date] to lock in [benefit]. You can also change plans anytime from your billing settings, or contact us if you have questions about which plan fits.
>
> If you have questions, just reply to this email.
>
> Thank you for being a customer,
> [Name]

## Why each part of the template is there

### The subject line

The subject line states what the email is about and when it happens. Resist the temptation to soften it with something like "An update from the [Product] team." Customers who discover a price increase buried in a vague email feel misled, and that feeling sticks. A direct subject line also makes the email easy to find later, when someone in finance asks about it.

### The opening and the numbers

The first two sentences tell the customer that something is changing and exactly what it is: the old price, the new price, the period and the date. Putting the numbers near the top respects the reader's time. Most people open this kind of email looking for one thing, how much more they will pay, and making them scroll for it creates irritation before they have read your reasons.

### The reason

The reason is where many companies go wrong. "Rising costs" or "to continue delivering value" tells the customer nothing. Be specific. Name the features you shipped, the integrations you added, the support hours you extended or the infrastructure you upgraded since their price was set. If the honest reason is that the original price was too low for a sustainable business, it is fine to say so plainly. Customers are generally more forgiving of honesty than of corporate phrasing.

Only list improvements that are real and relevant to the customer's plan. Listing features they cannot access on their tier reads as padding, and listing something that has not shipped yet invites a reply asking where it is.

### What this means for you

This section translates the change into practical terms: until when they pay the old price and when the first new charge will happen. It removes the most common follow-up question. For customers with add-ons, seats or usage charges, consider calculating their actual new total, since "your plan will change from $X to $Y" can be misleading if they pay for extra seats on top.

### Options

Options give the customer some control. Annual billing at a locked rate is a common choice because it benefits both sides: the customer delays the full impact and the company gets cash up front and a longer commitment. Plan changes, including downgrades, should also be easy. It may feel counterintuitive to invite downgrades in a price increase email, but a customer who downgrades is still a customer. One who cannot find a cheaper option often cancels instead.

### The sign-off

A reply-to address that reaches a real person signals that you are willing to talk. Sending the email from a named person, often a founder or head of customer success, rather than a no-reply address changes how it reads.

## Variations by segment

The base template works for most monthly customers, but some groups need different wording.

### Grandfathered customers

If some customers will keep their current price for a period, say exactly how long, and when and how you will notify them before it ends. "You'll keep your current price until [date]. We'll remind you 60 days before it changes" is clearer than "you'll keep your price for now." Open-ended grandfathering creates confusion later, so if you do intend to keep someone's price indefinitely, say that clearly too.

### Annual customers

Annual customers usually see the new price at renewal, not mid-term. Your email should state the renewal date and the amount they will pay at that renewal, and remind them they can review their plan before then. If you offer a multi-year option to lock in pricing, this is the place to mention it.

### Large accounts

Your largest customers should not learn about a price increase from a bulk email. Send a personal note from someone they know, ideally their account owner or a founder, and offer a call. These accounts often have procurement processes, budget cycles and contract terms that a generic email cannot address. A conversation also gives you a chance to understand their plans and discuss a longer commitment or plan change that works for both sides.

## Send reminders

One email is rarely enough. People miss messages, forward them to someone who forgets, or remember the change only when the invoice arrives. Send at least one reminder closer to the effective date that repeats the key facts: the new price, the date and the options. A final reminder showing the customer's exact new amount, a few weeks before the change, prevents most "I never heard about this" complaints.

## Prepare your support team

Your support team will receive replies, and the quality of those replies shapes how customers remember the change. Before you send anything, write a short FAQ that covers the questions you expect: why now, whether prices will change again soon, how to move to a smaller plan, and what happens to existing discounts. Give the team response templates for each, written in a calm, human tone.

Just as important are escalation rules for exceptions. Decide in advance which situations might justify an exception, such as nonprofits, customers in hardship or accounts with a specific contract history. Decide who can approve them and what the limits are. Without these rules, support either refuses everything, which frustrates good customers, or grants exceptions inconsistently, which becomes unfair and hard to unwind.

## Track the impact

After the announcement, watch churn, downgrades, support ticket volume and revenue. Look at these by segment and by cohort rather than as one blended number. A spike in cancellations from one plan may mean the increase was too steep for that tier. A wave of downgrades may mean the new price pushed customers below the value line, which is a packaging question as much as a pricing one.

Give the data time. Some customers cancel immediately in reaction to the email, while others wait until the new charge hits. Comparing the full quarter after the increase with a normal quarter gives a better picture than reacting to the first week.

## Common mistakes

Short notice is the most damaging mistake because it leaves customers no room to plan and makes the company look careless. Vague reasons come next, since they invite suspicion. Hidden price changes, where the new amount only appears on an invoice or in small print, are worse than either, because they break trust in a way an honest email never does. Offering no options makes customers feel cornered, and an unprepared support team turns a manageable change into a backlog of frustrated tickets.

## A worked example (illustrative)

A SaaS company planned to raise its Team plan price after two years without changes. Instead of sending a single email, the team prepared a sequence.

Ninety days before the change, they sent the main announcement using the template above. It included a specific list of improvements shipped since customers had joined and an offer to lock in the current price for another year by switching to annual billing before the effective date.

Sixty days before, they sent a short reminder with the same details and a link to an FAQ page. The FAQ answered the questions they expected most: why now, whether prices would change again soon, and whether customers could move to a smaller plan.

Thirty days before, they sent a final reminder showing each customer's exact new monthly amount. For their largest accounts, the founder sent personal emails and offered a call instead of relying on the bulk sequence.

Support received prepared answers and clear guidance on when exceptions could be offered, such as for nonprofits or customers facing hardship, and who approved them. Most customers accepted the change. A noticeable share switched to annual billing, which improved cash flow. Churn in the following quarter was only slightly higher than usual, and the additional revenue from customers who stayed more than offset it.

## Pre-send checklist

Before you send, confirm the notice period against your contracts and terms. Read the email as a customer would and check that the old price, new price and effective date are stated clearly near the top. Make sure the reason is specific and honest, and that the options, whether annual billing or a plan change, are easy to act on with a working link. Finally, confirm that support has the FAQ, the response templates and the exception rules in hand before the first reply arrives.

## The takeaway

A price increase email should explain what changes, when, why and what options customers have. Give enough notice, segment the message for different customer types, prepare your support team and follow up with reminders. Customers will not love paying more, but most will accept a change that is explained honestly and handled with respect.

## Frequently asked questions

### How much notice should SaaS customers get before a price increase?

Commonly 30 to 90 days, with longer notice for annual and larger customers. Check contract terms.

### Should I explain why prices are increasing?

Yes. Honest explanations help customers understand the change.

### Should price increase emails offer options?

Yes. Options such as annual billing or plan changes reduce frustration.

## About Comppound

Comppound runs SEO and AI search for B2B SaaS companies: a person sets the plan and reviews samples and every high-risk page, and AI speeds up production.

- [Get the free report](https://comppound.com/ai-visibility-report): When buyers ask ChatGPT about your category, are you in the answer?
- [Book a call](https://comppound.com/contact): Most of this works better when buyers can find you first