Most SaaS companies raise prices too late, and then do it in one rushed email. To raise SaaS prices without losing customers, change new-customer pricing first, then move existing customers with a clear reason, a defined grandfathering rule and enough notice. Measure the effect on conversion and on churn separately, because the two respond on different timelines and for different reasons.
Signs you are underpriced
Underpricing rarely shows up as a problem. It shows up as things that look like good news. Check your last two quarters of deals and accounts against this list:
- Win rate on qualified opportunities is high, and price almost never appears in closed-lost reasons
- Buyers sign without asking for a discount, or procurement approves without a second round
- List prices haven’t changed since launch, while the product has added major capabilities
- Your largest customers use many times more of the product than your smallest but pay only modestly more
- Direct competitors with a narrower product charge more
- Customers call you “a no-brainer” or “cheap” on calls and in reviews
- Support and infrastructure costs from heavy users are eating into gross margin
Three or more checked usually means price is lagging value. One caution: if churn is already high or activation is weak, fix that first. A price increase amplifies whatever retention problem you already have.
New customers vs existing customers: two different decisions
Changing price for new customers and changing price for existing customers look like one project. They aren’t. They carry different risks, produce evidence at different speeds and differ in how easily you can undo them.
| New customers | Existing customers | |
|---|---|---|
| Main risk | Lower conversion or win rate | Churn, downgrades, lost trust |
| Reversible? | Yes, you can adjust the pricing page next week | Mostly no; a rollback costs credibility |
| Evidence arrives | Within weeks, from trials and pipeline | At renewal, often months later |
| Who decides | Leadership, with sales input | Leadership, customer success and finance |
| Communication | Pricing page and sales collateral | Direct notice, emails, account calls |
Do them in sequence. Launch the new price for new customers first and watch conversion for four to eight weeks, longer if you close only a handful of deals a month. If new buyers accept it, you have evidence that the market supports it. That makes the existing-customer decision easier and gives your customer success team a credible answer when asked: “This is what new customers pay today.”
Grandfathering options and their trade-offs
Grandfathering is the rule for how long existing customers keep their old price. Pick one deliberately and write it down, because sales and success will be asked about it every day.
| Option | How it works | Upside | Downside |
|---|---|---|---|
| Permanent grandfathering | Existing customers keep the old price indefinitely | No churn from the change | Revenue gap grows; every future change gets harder |
| Grace period | Old price for a fixed window, such as 6 or 12 months | Time to adjust and budget | Needs a second communication when it ends |
| At next renewal | New price starts at each customer’s renewal date | Clean for annual contracts; respects commitments | Slow to roll through the base |
| Phased step-up | Increase applied in two or three steps | Smaller jump each time | More notices, more billing work |
| Legacy plan | Old plan keeps its price but gets no new features | Customers choose when to move | A plan you must support indefinitely |
| No grandfathering | Everyone moves on the same date | Fast and simple | Highest churn and trust risk |
For most B2B SaaS companies, I default to “at next renewal” for annual customers and a 60 to 90 day grace period for monthly customers, with a phased step-up for any account where the increase is large relative to what it pays now. Permanent grandfathering is almost always a way of postponing the decision, not making it.
Before you choose, read your contracts. Enterprise agreements often cap renewal increases or require specific notice periods, and those terms override your plan.
Pairing a price change with packaging or value changes
A price increase with no reason reads as a margin grab. A price increase tied to value reads as a product decision. The strongest reasons:
- You shipped meaningful capability. List it concretely: features, integrations, performance and support levels added since the current price was set.
- You’re moving to a better value metric. If price moves from a flat fee to seats, usage or another metric that tracks value, heavy users pay more and light users may pay the same or less. The mechanics are in SaaS packaging and value metrics.
- You’re adding a tier. A higher tier with features larger customers have asked for gives them a reason to move up rather than a bill to absorb.
Two rules. Don’t remove features from an existing plan in the same move, because customers will read it as a hidden increase. And don’t invent value you haven’t delivered. If the honest reason is “we’ve been underpriced and need to fund the roadmap,” say that plainly. Business buyers understand it better than a padded feature list.
Communicating the increase: timeline, emails and sales scripts
Most of the damage comes from surprise, not from the number. Work backward from the effective date.
| When | What happens |
|---|---|
| 120 days before | Final pricing, grandfathering rule and exception policy approved; billing changes tested |
| 100 days before | Customer success briefed; accounts segmented by revenue, health and renewal date |
| 90 days before | Personal calls or emails to top and at-risk accounts, before any mass email |
| 60 to 90 days before | Notice email to all affected customers (the full 90 for annual contracts) |
| 14 days before | Reminder email with the exact new amount and date |
| Effective date | Billing change goes live; in-app notice for anyone who missed the emails |
Shorten this for monthly-only businesses, but keep at least 30 days of notice and never go below what your terms require.
What the notice email should contain
- What’s changing, in plain numbers: old price, new price, which plan
- When it takes effect for this specific customer
- Why, in two or three sentences tied to value
- Their options: lock in the current price with an annual prepay, switch plans, or talk to someone
- A named contact, not a no-reply address
Put the number in the first paragraph. Burying it under a list of features makes people angrier when they find it.
A sales and success script
Give the team one short, consistent answer:
“Pricing for [plan] moves from $X to $Y on [date]. Since you signed, we’ve added [two or three specific things], and new customers already pay $Y. For you, the change starts at your renewal on [date]. If you’d like to keep the current rate for another year, renew annually before [date] and we’ll lock it in.”
Then stop talking and let the customer respond.
Handling pushback and at-risk accounts
Some customers will push back. Decide in advance what the team can offer, so every conversation doesn’t become a fresh negotiation.
Segment the base before notices go out:
- High value, healthy: personal outreach, standard terms
- High value, at risk (low usage, open escalations, champion left): call first, understand the risk, offer a phased step-up or a later start
- Low value, at risk: standard notice with a clear downgrade path
- Contract-capped: apply the maximum allowed increase at renewal
Acceptable concessions include a later effective date, a multi-year lock at a smaller increase, an annual prepay at the current rate, or a move to a lower plan. Keep one approval owner for exceptions and log every one with its reason. If more than a small share of accounts get exceptions, either the price or the reasoning is off, and the log will show which.
Some churn after an increase is existing churn arriving early: customers who were already disengaged and used the notice as a reason to leave. How to reduce SaaS churn covers how to separate accounts by churn cause, which keeps you from blaming the price for everything.
Measuring impact on conversion, churn and expansion
Measure new and existing customers separately. They react differently and on different timelines, and a blended number hides both.
New customers, from the week the new price launches:
- Visitor-to-trial and trial-to-paid conversion, or demo-to-close win rate
- Average contract value or average revenue per new account
- Sales cycle length and discount rate
- Plan mix, to see whether buyers now pick a lower tier
Compare against the prior four to eight weeks, adjusted for seasonality. A small drop in conversion with a larger rise in revenue per account is usually a win. New revenue per qualified opportunity captures both in one number.
Existing customers, over at least one full renewal cycle:
- Logo churn and gross revenue retention for affected cohorts vs comparable earlier cohorts
- Downgrade rate
- Net revenue retention, since a new tier can also unlock expansion
- Support tickets and cancellation reasons that mention price
The break-even math
To judge whether churn was acceptable, calculate how much affected revenue you could lose before the increase stops paying. For a price increase of p, the break-even loss is p ÷ (1 + p).
A hypothetical example: a 20% increase breaks even at about 17% of affected revenue lost (0.20 ÷ 1.20). A 10% increase breaks even at about 9%. If price-driven churn stays well below that line, the increase paid off. Lost customers also take future expansion and referrals with them, so treat break-even as a floor, not a target.
This sits inside the growth strategy work I do with SaaS teams: pricing, packaging and go-to-market decided together, with success metrics defined before the change, not after.
Get it built
If you suspect you’re underpriced but aren’t sure how far to move or how to roll it out, start with a Growth Audit: $1,500 fixed and credited if we continue. See pricing or get in touch.