Source: https://www.revvly.ai/blog/saas-price-increase-how-to-raise-prices-without-churn Pricing 8 min read Jul 21, 2026 # SaaS price increases: how to raise prices without spiking *churn*. The strategic case for a price increase is easy to make in the boardroom. The operational case, how to do it without support tickets piling up and renewals dropping, is where most companies *improvise*. SA Samuel Adeyemo Revenue Systems, Revvly Every subscription business eventually has the same conversation. Costs have gone up, the product has grown well past what it was when pricing was first set, and the number everyone agreed on two years ago no longer reflects the value being delivered. The strategic case for a price increase is usually easy to make in the boardroom. The operational case, how to actually do it without support tickets piling up and renewal rates dropping, is where most companies improvise. ## Quick answer > A SaaS price increase works best when it is segmented, not blanket: model which accounts are churn-sensitive before you announce anything, give existing customers real advance notice (Chargebee's own pricing playbook recommends at least a month, with grandfathering held for a minimum of two years if used at all), and measure net revenue retention before and after so you know whether the increase actually grew revenue or just reshuffled it. Companies that skip the segmentation step and raise prices uniformly tend to find out which customers were price-sensitive only after they've already left. ## What counts as a reasonable SaaS price increase There is no single industry-standard number, but there is a real range worth anchoring to. Vertice's purchasing data across roughly 16,000 vendors found that 73% of SaaS providers raised prices in the twelve months to August 2023, with prices increasing 12% on average, more than double the 6% average increase Vertice tracked in 2019. SaaStr founder Jason Lemkin points to Salesforce as the reference case at the high end of predictability: Salesforce's standard Master Services Agreement bakes in a 7% annual increase every year, disclosed upfront in the contract. 12% Average SaaS price increase across roughly 16,000 vendors in the twelve months to August 2023, more than double the 6% average Vertice tracked in 2019. Lemkin's broader guidance is useful precisely because it is stage-dependent rather than a flat rule: guarantee pricing for three years while a company is still small and use that certainty as a sales lever, grandfather the earliest customers' pricing through roughly $1 million to $2 million in ARR and consider leaving it alone entirely, and only revisit pricing more aggressively once a company is well past $30 million to $40 million in ARR, at which point the calculus shifts from winning every logo to maximizing revenue per account. The pattern shows up in how frequently the market actually moves. Pricing intelligence firm PricingSaaS tracked 3,500 of the top SaaS companies through 2024 and counted 339 total pricing and packaging changes, 126 of them straight pricing updates and 213 packaging changes, with 29 companies changing prices more than once in the year. Price increases are not a rare, once-a-decade event for most of this cohort. They are a recurring lever, which is exactly why they need a repeatable process rather than a one-off scramble. ## How to raise prices without spiking churn ### Segment your base before you touch a single price The biggest mistake in a blanket price increase is treating every account the same. A customer who has expanded seats twice in the last year and uses the product daily will absorb a 10% increase without blinking. A customer already flagged as at-risk, with declining usage, a recent support escalation, or a payment that failed last cycle, is a very different conversation. Running an [AI-powered churn prediction](https://www.revvly.ai/blog/churn-product-signals) pass across the base before you finalize the increase turns this from a guess into a segmentation exercise: you can identify which accounts are genuinely price-elastic and which ones need a different approach (a longer grace period, a call from customer success, or exclusion from this round entirely) before a single email goes out. ### Choose your mechanism: blanket, new-customer-only, or grandfathered There are three broad paths, and they are not mutually exclusive: - **New-customer-only pricing.** The new price applies to net-new signups; existing customers stay on their current terms indefinitely. Lowest churn risk, slowest revenue impact. - **Time-limited grandfathering.** Existing customers keep their current price for a defined grace period, commonly a year or two, before moving to the new price. Chargebee's own pricing guidance recommends grandfathering for a minimum of two years if you use it at all, on the reasoning that the churn a sudden increase avoids is worth more than the revenue grandfathering defers. - **Across-the-board increase with notice.** Every account moves to the new price on a set date, typically with advance notice built in. Fastest revenue impact, highest churn exposure, and the option that most needs the segmentation step above. Which one fits depends on company stage, contract structure, and how concentrated revenue is in a small number of accounts. A modular pricing engine that can run more than one active price book at once, rather than forcing every customer onto a single global price list, is what makes options one and two operationally realistic instead of a manual spreadsheet exercise. ### Set the notice window deliberately A month of advance notice is the baseline most billing platforms and pricing playbooks converge on, not because it is a regulatory requirement but because it gives customers time to either accept the new terms, lock in a longer contract at the old rate, or make an informed decision to leave on their own timeline rather than being surprised by a charge. Enterprise and annual-contract customers typically need more, often tied to their renewal date rather than a fixed calendar date across the whole base. ### Get the communication sequence right The mechanics matter less than most teams assume; the sequencing is what causes problems. Internal teams, sales, support, and customer success, need to know the change and the reasoning before customers do, not find out from an inbound support ticket. Chargebee's own pricing-change guidance cites Appcues as an example of turning a required pricing announcement into a sales moment: a clear, transparent email explaining what changed and why reportedly grew sales 263% for that cohort, largely by giving prospects a reason to lock in before the new price took effect. The common failure mode is the opposite: a terse billing notice with no context, which reads as a fee grab even when the underlying pricing logic is sound. ### Execute without breaking billing This is where a fragmented stack usually shows its limits. A price change that touches active subscriptions needs correct proration for customers mid-cycle, the ability to run the old and new price books concurrently for however long grandfathering lasts, and invoices that reflect the right price for the right cohort without manual intervention in a spreadsheet. Automated proration and a pricing engine built to hold multiple concurrent price books are what keep this from becoming a manual reconciliation project every time finance wants to run a pricing change. ## What the last round of pricing moves actually looked like Real examples from 2024's pricing cycle, compiled by PricingSaaS, illustrate the spread between a well-executed increase and a rushed one. Docker raised its Pro and Team plan prices by 80% and 67% respectively while leaving its Business plan untouched, a move PricingSaaS flagged as leaving revenue on the table by not adjusting the least price-sensitive tier at all. Ahrefs took a subtler approach, restructuring how its Enterprise plan price was displayed while increasing the actual annual price by 20%, a change PricingSaaS characterized as overdue and well-executed because it also made the pricing page easier to compare across tiers. Pipedrive combined a new top-tier Enterprise plan with a price increase on its Advanced plan, using the new tier as an anchor that made the tier it wanted to sell look more reasonably priced by comparison. None of these are Revvly customers or case studies; they are documented, publicly reported examples used here only to show the range of outcomes a single pricing decision can produce. ## A short checklist before you announce anything - Have you segmented the base by churn risk, not just by plan or contract size? - Does the increase apply to new customers only, existing customers with grandfathering, or everyone at once, and does that match your actual revenue-concentration risk? - Is the notice window long enough for your longest sales cycle or your largest annual contracts, not just your smallest self-serve accounts? - Do sales, support, and customer success know the change and the reasoning before customers receive it? - Can your billing system run the old and new price books concurrently without manual invoice edits? - Do you have a plan to measure net revenue retention, expansion, and contraction in the weeks after the change, not just gross revenue booked? ## Why this breaks down in a fragmented stack The steps above sound sequential, but in practice they are simultaneous: segmentation depends on usage and support data, execution depends on billing logic, and measurement depends on revenue reporting. When those three things live in Stripe, a support tool, and a spreadsheet respectively, a pricing change becomes a cross-functional project with its own timeline. A [unified view of subscription, usage, and revenue data](https://www.revvly.ai/blog/revenue-stack) is what turns "raise prices carefully" from a quarter-long initiative into a repeatable motion finance can run more than once a year, which the PricingSaaS data suggests is increasingly normal rather than exceptional. It's also what makes the aftermath measurable: watching [net revenue retention](https://www.revvly.ai/blog/nrr-compounds) move in the weeks after a price change tells you whether the increase actually expanded revenue per account or simply pushed marginal customers out the door, a distinction a single end-of-quarter revenue report will not show you in time to correct course. Real-time ARR and NRR dashboards, rather than a monthly export, are what let a RevOps or finance lead catch an unexpected churn spike within days of a price change instead of a quarter later, and pair naturally with the same [pricing experimentation](https://www.revvly.ai/blog/pricing-experiment) discipline used for tier design more broadly. ## Frequently asked questions ### What is a reasonable SaaS price increase percentage? There is no fixed industry standard, but recent market data points to roughly 12% as an average annual increase across a broad sample of SaaS vendors, up from about 6% a few years earlier. Salesforce, as a reference case, bakes in a fixed 7% annual increase in its standard contract. The right number depends more on cost structure and product value growth than on matching a market average. ### How often should a SaaS company raise prices? There is no single cadence, but pricing intelligence data shows it happens more often than founders expect: one 2024 study of 3,500 SaaS companies found 126 pricing changes and 213 packaging changes across the year, with dozens of companies changing prices more than once. An annual review, with an actual increase only when the case is clear, is a reasonable default for most early to growth-stage companies. ### Will raising prices cause customers to churn? Some churn is close to inevitable with any price increase, but the goal is to keep it limited to genuinely price-sensitive accounts rather than surprising customers who would have stayed. Segmenting the base by usage and risk signals before the increase, giving adequate notice, and grandfathering at-risk customers are the levers that keep churn proportional rather than a surprise. ### What is price grandfathering and should we use it? Grandfathering means existing customers keep their current price while new customers pay the new rate, either indefinitely or for a defined grace period. A minimum two-year grace period is a common recommendation if grandfathering is used at all, since the retained revenue from avoided churn typically outweighs the revenue given up by not moving existing accounts to the new price immediately. ### How much notice should you give customers before a price increase? A month is the common baseline cited in SaaS pricing guidance, enough time for customers to plan around the change or lock in a longer contract at the current rate. Enterprise and annual-contract customers generally warrant more notice, often aligned to their individual renewal date rather than a single calendar date applied to the whole base. ### Can Stripe alone tell you which customers are at risk before a price increase? Stripe and similar billing tools record what was charged and paid, but they were not built to model which customers are likely to churn in response to a change. That requires combining billing history with usage patterns, support signals, and payment health, which is why churn-risk modeling is typically a separate layer rather than a built-in billing feature. ### What is the difference between a price increase and a value-metric pricing change? A price increase raises the number a customer pays for the same plan and the same value metric. A value-metric change alters what is actually being measured and billed against, such as moving from per-seat to usage-based billing, which can increase or decrease what any individual customer pays depending on usage, independent of whether list prices moved at all. SA Samuel Adeyemo Revenue Systems, Revvly Samuel builds the systems that turn billing events into trustworthy revenue numbers. He writes about retention, pricing, and the operational details that decide whether the metrics hold up. Revvly Orchestrate the flow of revenue. © 2026 AcceleratorApp Limited. All rights reserved.