How to Raise SaaS Prices Without Losing Customers

The average SaaS price increase was 12% over the past year, per a Vertice study. You can raise yours without heavy churn if you sequence three decisions in the right order, the notice period, the segmentation, and the grandfathering call.

At consulting clients, I've watched a retention talk turn into a pricing talk in one question. Someone asks, "wait, how many customers are still on the old plan?" The increase itself is rarely the problem.

Most teams don't sort out the order of the other two decisions until a botched increase has already cost them the churn.

Key takeaways

• Sequence three decisions, notice period, segmentation, and grandfathering, before announcing any increase.
• SaaS prices rose 12% on average last year, per a Vertice study.
• That 12% is double the 6% average increase Vertice measured in 2019.
• Give monthly plans one full billing cycle of notice, annual plans one renewal term.
• Grandfathering avoids churn now but opens a permanent legacy-versus-new pay gap.

How much are SaaS companies raising prices?

SaaS companies raised prices by an average of 12% over the past year, roughly double the 6% average increase seen in 2019. That figure comes from a Vertice study of thousands of SaaS contracts, reported by CFO Dive.

Two forces are pushing the number up. Compute and AI costs are climbing, and vendors pass those costs straight through into what they charge.

At the same time, many SaaS companies are correcting years of plans they priced too low in the growth-at-any-cost era. Back then, winning the customer mattered more than the margin.

That 12% from the Vertice study is an average, and averages hide the spread. Some companies nudged prices up a few points. Others in AI-heavy categories raised them far more. The number describes the broad market, while your own customers decide what they will actually tolerate.

Two questions set your limit. How much have your own delivery costs risen, and how far below comparable tools are you priced today?

A vendor absorbing real compute-cost increases has firmer ground than one raising prices because the market moved. Customers accept an increase they can trace to a cost more readily than one that looks like pure margin-grabbing.

A plan already at the top of its category also has far less room than one that undercharged for years. So size the increase to your own cost structure and market position, and treat the headline number as context.

Does raising prices actually cause customers to churn?

Price increases are a top reason subscribers give for canceling, but how much churn any one causes depends on how you sequence it, not on the increase itself. That distinction is the whole point of this article.

A price increase makes every existing customer re-judge the subscription the moment it costs more. That's the same re-judgment a cancel-flow prompt creates on purpose, except a price increase triggers it for your whole base at once.

Think about that moment from the customer's side. Most of your subscribers aren't actively deciding whether to keep paying you. The charge clears every month and they move on.

A higher price interrupts that autopilot. Now they're looking at the line item, asking whether they still use the product enough to justify the new number, maybe checking what a competitor charges. You reopened a decision most customers had stopped making.

The three decisions ahead exist to manage that reopened moment instead of leaving it to chance.

Read the "price increases drive churn" finding carefully, though. It's a survey answer about why people say they left, not proof that every increase churns customers in proportion to its size. 

Someone already unhappy names the price as the last straw, and the exact figure comes with a caveat worth reading before you quote it.

The rest of this guide works the three levers you do control, which is the whole reason pricing decisions are retention decisions.

How much notice should you give before a price increase?

Give enough notice that the new price lands on the customer's next natural renewal. In practice that means one full billing cycle for monthly plans and one renewal term for annual plans.

The reason is about which decision moment the customer is in. Every subscriber already has a built-in checkpoint at renewal, when they half-consciously decide whether the product is still worth it.

Land the new price there and it becomes one input into a decision they were already making.

Spring it on them mid-cycle and you've done three things at once. You've created a decision they didn't ask for, taken away their room to budget, and made the change feel done to them.

A customer reacting to a surprise cancels more readily than one weighing a renewal.

Consider a customer on a monthly plan. Give them 45 days' notice before the next charge and they have a full cycle to plan with a clear head. Cut that to 5 days and they aren't evaluating a decision. They're reacting to a bill that changed without warning.

One caveat sits underneath all this. Some places set a legal floor on the notice you owe for auto-renewing subscriptions. The renewal-point advice sits on top of that floor, so check the legal minimum for you first.

Segmenting a price increase by customer value

A flat percentage increase treats, say, a $10-per-month account and a $500-per-month account as the same decision. They carry different churn risk and different revenue stakes, and segmenting by customer value fixes that mismatch.

Average revenue per account (ARPA) is your total recurring revenue divided by your customer count. It's a rough proxy for how entrenched a customer is.

Low-ARPA customers are more price-sensitive by definition. A small dollar increase is a big proportional hit to a small bill, and they're easy to replace with a cheaper tool.

High-ARPA customers tend to be locked in, with more integrations and onboarding sunk into your product. They can usually absorb a larger increase without leaving.

Say a business is planning a flat 15% increase across the board. Segmented by ARPA band, the same increase could look like this instead:

That captures more revenue from the segment that can carry it, while protecting the segment most likely to cancel.

Segmentation only works if your tiers already map to real customer value. A customer can sit in a high band because they pay for seats they never use, and then ARPA misleads you. Fix a tier structure that's out of step with usage first.

Otherwise you'll aim your biggest increases at customers who look entrenched but aren't.

Even a well-segmented increase will push some customers toward canceling. That's the moment a cancel flow is built to catch.

Should you grandfather existing customers?

Grandfathering existing customers at their old price removes the increase's churn risk for that group, but it opens a permanent pay gap between legacy and new customers. That's the core trade-off.

In practice, it keeps existing customers on their current price while new customers pay the new one. How long to hold that price, who to include, and when to sunset it is a separate call, laid out in grandfathering existing customers. This section covers only whether to grandfather at all.

And that gap doesn't stay small. Every time you raise the new-customer price, the distance between what a legacy account pays and a fresh one pays widens.

A few years of increases can leave two customers on the same product paying wildly different amounts. You avoided the churn, but capped what that group will ever contribute.

So the decision comes down to churn risk. Grandfather the price-sensitive accounts, where the churn you'd avoid is largest.

Migrate the entrenched, high-ARPA accounts, which are least likely to leave over the change anyway.

You can also pair grandfathering with segmentation. Freeze the old price for your most price-sensitive segment, migrate the rest, or offer a downgrade to a customer priced out by the change.

Churn.io's profit margin calculator can show which segment can absorb the change.

FAQ

Will raising prices push my best customers to a competitor?

The accounts most likely to defect are price-sensitive ones with a cheaper alternative already in reach. Your biggest customers carry high switching costs, so competitor risk really tracks how replaceable your product is, which is what your segmentation should key on.

Can I raise prices on customers mid-contract?

Usually not, because an existing contract or annual term typically locks the price until it renews. Whether you can raise it mid-term depends on that agreement, so the safe default is to apply the new price at the next renewal.

What if a customer threatens to cancel over the increase?

Treat it as a save opportunity rather than a lost account. Ask what changed, and offer a smaller-tier downgrade or a pause before you let them go entirely.

Does a price increase need customer re-consent?

Sometimes, depending on your jurisdiction and how your terms are written, since some rules treat a price change as a material change requiring fresh disclosure or consent. This is a legal question, so check the requirement that applies to your business before you announce.