Every price-increase conversation lands on the same two numbers. How much (4%? 10%?), and how many customers will churn. Both are the wrong place to start.

The decisive questions sit one level up. Do you have the pricing power to raise prices in the first place? And do you have the structure to reprice your existing book without a year of renegotiation?

"If you keep adding functionality without diversifying your core product's packaging or raising prices, you will be delivering more and more value for less and less money."

‍- Ulrik Lehrskov-Schmidt, author of The Pricing Roadmap

Get those two right and a price increase becomes a repeatable capability rather than an annual act of nerve. In practice, B2B SaaS pricing tends to sit meaningfully behind the value the product delivers - prices get set once, when the product is less mature, and rarely revisited as value grows. The opportunity is large, and the risk is usually smaller than it feels.

Repricing is a large part of what we do at WillingnessToPay - and the framework below is how we approach it in practice, across companies at every stage of scale. (see also: our case studies)

What is a SaaS price increase?

A price increase is any upward change to what customers pay - but the label covers two very different moves, and getting them mixed up is the first step to underpricing a business for another five years.

Indexation is the small annual adjustment most contracts have a clause for - typically 2-7%, with 4-5% as the norm. It's meant to keep pace with inflation, though in practice it often doesn't even manage that - the real cost of serving a customer (salaries, infrastructure, the AI and tooling stack) tends to climb faster than the CPI figure the clause is indexed to. Useful as a floor, but this isn't where the interesting money is.

Structural repricing is a different exercise. It's realigning what customers pay to the value the product now delivers, and for a company that's been underpriced for years it's often a 50%, 100%, or larger move. This is where the interesting money is, and it's what the rest of this page is about.

There's also the question of who the increase applies to. New customers only is the simplest case - you just charge more from the next deal onwards, and existing revenue keeps flowing on the old terms.

Repricing the existing book, your installed customer base, is a different sport. That's where both the value and the operational difficulty concentrate, and it's the version everyone underestimates the difficulty of. The framework that follows is designed to make it survivable.

‍Can you raise prices? The four signals of pricing power

Before deciding how much, decide whether you have the room in the first place. Pricing power isn't a mood - it's a set of conditions in the market. We look for four signals when we sit down with a client, and we look for them in the order below - because each earlier one matters more than the next.

1. Churn is the strongest signal. If nothing else were available, churn is the number to look at. The rough rule is that annual churn below ~8% means you have pricing power, with room for a 20-30% increase you can easily offset. Below 4%, moves of 50-100% are often on the table, even in enterprise. Churn also reads by segment: if your large accounts churn at 4% while your small ones churn at 12%, the pricing power lives in the large accounts, and treating the whole book - every account - as one number will lead you astray.

2. Conversion is the second signal. When well-qualified leads convert above ~30% - especially through your stronger sales performers - you're most likely under-priced. High win rates read like a trophy on the board deck, but in practice they're a sign you're leaving money on the table with every deal you close cleanly.

3. Competition sets the reference point. Benchmark against what the market really charges, not what you think it charges. If you're at 100 and comparable vendors are pricing at 400, the conversation isn't about whether to raise prices - it's about how quickly to catch up.

4. Value calculation is the fallback. When you don't have enough churn or conversion data to read from (because the product, market, or sales motion is still new), fall back to a simpler question: what is the outcome actually worth to the customer, in hard numbers? If your product saves an insurer $10M a year, charging them $100K a year isn't really a price. It's a discount.

The churn signal is hard to overstate. In one private-equity due-diligence engagement we ran, a vertical B2B SaaS company sitting at ~$15M ARR and a 10% margin had almost no churn on a business-critical product - the kind of product no procurement team wanted to be seen swapping out.

That was the tell. We doubled prices, took the top line to ~$32M and the margin to ~55%, and most of the incremental revenue landed straight in profit. The pricing power had been there for years; nobody had used it.

‍

‍

The real blocker: commercial debt

So you have the pricing power, and you know the size of the move. The next question is what stops most companies from making it - and, in our experience, the answer is rarely the customer.

Two things hold teams back: internal fear of the conversation, and, underneath it, their own contracts.

Fear is the one everyone talks about, but contracts are the one that makes the move almost impossible.

Commercial debt (full guide at [add spoke link]) is the commercial cousin of technical debt - the operational load that builds up when a book of business fills with bespoke contracts one exception at a time.

A discount here, a bespoke term there, a custom configuration to close a deal. A few years in, the book is a hodgepodge of hundreds of different agreements, and repricing means reopening every one of them individually.

The value is there. You just can't act on it. The fix isn't a better negotiating script, it's structural: standardize onto one contract template, one price list, and one discount policy, so every future concession is a temporary, tracked discount inside that structure rather than a permanent, bespoke exception bolted onto it.

Repricing existing customers: pricing cohorts

With the contract structure in place, the next question is how to roll a new price through the existing book in practice. Broadly, there are two routes.

You can raise prices for new customers only, and let the existing base carry on at the old rate. Or you can raise prices for new and existing customers together. Doing everyone at once is operationally simpler and gets you to the new ARR faster, but it concentrates churn risk across the whole base on day one, which is why we rarely recommend it at meaningful ACV.

The safer pattern, and the one we default to at medium-to-large ACVs, is to test on new customers first. Prove that the new price works in the market for six months. Then go back to existing customers armed with the strongest possible argument, which is that this is what every new customer has been paying for the last half-year. Fair, market-tested, and very hard to argue with in a renewal conversation.

To manage who is on what pricing, we use pricing cohorts. Each cohort is a group of customers who were closed on a specific pricing and product scheme, and each is tracked so you know exactly which customer had which pricing at which time.

Every year or two, you run a rollback that lifts older cohorts up to current pricing. In practice, 90-95% of customers can be managed inside the cohort scheme, and only a handful of the very largest accounts need to be handled individually - each of them effectively its own cohort of one.

Repricing the existing book is also where repackaging starts to pay for itself.

Take one claims-management platform we worked with, where the primary buyer had already maxed out on the per-claim metric and simply couldn't take another dollar on that line. The redesign moved storage, API, test-environment, and services into their own line items, each mapped onto a different budget owner in the customer organisation.

The new structure was tested on two new customers at a ~90% gross margin, then rolled onto the legacy accounts without losing a single enterprise customer.

De-risking the rollout

Cohorts give you the mechanism. Getting the actual increase into the market without a bad quarter is a separate question, and there are three tools we lean on to do it - each one a way of turning a single frightening moment into a series of smaller, recoverable ones.

The first is to slice the pain. Nothing says you have to raise prices for everyone on the same day. Roll the increase out cohort by cohort, watch the churn, and only extend it once you're confident. If it works you keep going, and if it doesn't you've only exposed a small slice of the book to the downside.

The second is to stage the rollout across revenue quartiles. Sequence the increase by customer size, proving it on smaller quartiles before touching the largest, most sensitive accounts. The economics work in your favour here - the smaller accounts are where you learn cheaply, and the larger ones are where the money is.

The third is time-limited grandfathering, and it works best when the move is large. Netflix raised new-customer prices in 2017 but told existing customers it wouldn't take effect until January 2018 - a full sixteen months of runway. That's a negative call to action: customers have so much time to react that they end up doing nothing, and by the time the date arrives they've implicitly accepted the new price.

We did the same thing for Proper (Helloproper) when we doubled unit pricing from €7 to €15, announcing it to existing customers nine months ahead. The upside was twofold - customers had time to absorb it, and the company was able to book the full €15 as run-rate ARR in its next funding round. The wider redesign drove 300% ARR growth, an 80% price lift, and a 146% increase in the SMB unit fee. (Proper case study: willingnesstopay.com/case-studies/b2b-saas-packaging-and-pricing-redesign-proper)

One caveat on grandfathering as a default, though. In most cases the squeeze isn't worth the juice. If you've raised new-customer prices 40% after proper testing, not grandfathering the existing base would have to trigger 30%+ churn before grandfathering everyone comes out ahead - and teams nearly always overestimate that number.

Multiple permanent cohorts also carry a real operational cost that lasts forever, and every year of grandfathering makes the next repricing harder. The pragmatic move is to cherry-pick only the largest and most sensitive accounts for (time-limited) grandfathering, and to roll everyone else onto current pricing. The loyalty argument - that we owe our early customers - is, in our experience, one that sounds better in the room than it holds up in the numbers.

Communicating a price increase

With the cohorts identified and the rollout de-risked, the last piece of the machinery is how you tell the customer. For smaller and self-serve customers, the honest answer is that the announcement can be short - and teams routinely make far too big a deal of it. If you've done the upstream work of a tested price, a dynamic contract framework, a clean cohort overview, and packaging that maps to real jobs, a plain template does the job:

Dear [name],

The price of your [subscription] will change to [new price] from [date].
We keep developing the best possible product to [do the job they bought it for]. Last [period] we shipped [feature] and [feature]; next [period] we're releasing [feature] and [feature].

Best regards,

That template takes ten minutes to write, but it's a floor, not the whole job. A larger B2B customer needs more.

Enterprise buyers compare notes with peers and are under their own cost pressure, so the increase has to arrive wrapped in a clear value narrative, not just a date and a number. For very large accounts (ACV above ~$100K), the announcement should happen in a meeting - a friendly FYI and a chance to ask questions, not an invitation to negotiate. We use a dedicated narrative framework for that meeting, and its purpose is to let the increase land without straining the underlying relationship.

Two moves lift the message from defensive to offensive:

The first is to lead with value, not apology. Customers don't pay for your product; they pay for the outcomes it delivers, and framing the increase around why the product is worth more today than when they signed is far stronger than apologising or burying the news in fine print. Continuous product development, the recent roadmap, time elapsed since the last change, the virtuous cycle of reinvestment, market alignment ("your peers already pay this"), and simple catch-up logic are all narratives we've watched work in practice.

The second move is to use the email itself to sell. Everyone reads the price-increase email, which makes it the single best upsell surface most SaaS companies ever have. If the increase coincides with new tiers or a repackaging, this is the moment to show customers the value they've been missing and migrate them up rather than back down. Split-test the message across cohorts. Done well, the increase generates expansion revenue rather than leaving you standing there like a victim of your own value.

Repricing through repackaging: more for more

The cleanest way to take a large increase is to make the new offer hard to compare to the old one in the first place.

When you reprice substantially, change the packaging at the same time - add value alongside the higher number - so the customer can't hold the two prices side by side and start subtracting. A steak isn't an expensive sandwich; it's a different thing, judged on its own terms, and the customer conversation lands very differently as a result.

This more-for-more move does two things at once:

1. It lets you close the gap on the pricing power you were leaving unused
2. It lets you capture some of the additional value you're now delivering.

A product reconfiguration therefore becomes the natural occasion for an increase - you're not asking existing customers to pay more for the same thing, you're moving them onto something better.

BizBrains is the case we point to here. Their redesign lifted recurring revenue 62%, and the number held because the new structure shipped with full leadership alignment behind it, rather than as a pricing change trying to sell itself in isolation. (BizBrains case study: willingnesstopay.com/case-studies/bizbrains)

Why the churn you fear rarely arrives

At this point in a project we usually get the same question from the team about to press send: what if a huge chunk of the base churns?

The dread is real - the fear of the email going out and half the customer base cancelling by lunch is what keeps most companies from raising prices in the first place. It's also, in practice, wrong most of the time. After a tested and validated increase, the typical churn outcome is modest, and most of the churn that does arrive isn't really new churn at all.

Accelerated churn.

‍The customers who leave after a price increase are usually the ones who were going to leave within the next year or so anyway - just brought forward by a few months. They also tend to be the worst-fit accounts in the book, the ones already placing the heaviest load on customer success and support relative to what they pay.

This is why grandfathering out of fear tends to be the wrong call, and why we recommend restraint on it. The fear is real. The loss usually isn't.

Envidan is a useful illustration at the far end of the range - a water-management leader moving from perpetual and on-prem licensing into SaaS, where the redesign supported a 600%+ price increase with zero churn and stood up a self-sustaining SaaS division inside the company.

Not every case sees that kind of headroom, but the general pattern - that the churn coming out of a well-designed repricing is smaller than the churn you fear going in - holds up across engagements. (Envidan case study: willingnesstopay.com/case-studies/saas-packaging-pricing-redesign-for-a-water-management-leader)

How not to grow into a higher price: hydras and monoliths

Repricing well is only half the discipline. The other half is not backing yourself into a corner between repricings, and there are two patterns we see companies drift into when they try to grow into a higher price the wrong way.

The first is the hydra. You keep bolting on new modules and add-ons to justify charging more, and after enough years the cost of building and maintaining all those heads starts to outweigh the incremental revenue they bring in. The catalogue looks impressive on paper, but the margins and the sales complexity tell a different story.

The second is the monolith. You keep piling new functionality into the core product without charging for any of it, so the price stays flat while the value the customer gets keeps climbing. This is the more polite failure mode - the customer is well served - but the company ends up giving away years of product investment for free, and the eventual repricing has to make up for all of it at once.

The cure for both is packaging integrity, tied back to jobs-to-be-done. When new functionality solves a distinctly new job for a distinctly different customer, it earns its own offering - which keeps the monolith in check. When new functionality just makes an existing job better, it belongs inside the offering already built around that job - which keeps the hydra in check. In either case, the packaging structure is what makes a future price increase legible to the customer in the first place, and it's why repricing and repackaging are usually done together in practice (see SaaS Packaging: willingnesstopay.com/saas-packaging).

How often to raise prices

Everything above assumes that a price increase is something you do occasionally, in a big moment, with a lot of internal buildup.

In our experience, that's the wrong frame. Price rises should happen regularly - at least annually, and often quarterly for the fastest-growing companies - because the product keeps developing, the value to the customer keeps rising, and pricing that stays frozen falls further behind that value every quarter.

For a company growing 300% a year, most customers have been on the book less than a year anyway, and frequent increases barely register in the base.

The enabler for all of this is, again, structural rather than tactical.

A dynamic contract framework, a single unified structure for pricing and discounting, and a book that is managed as cohorts rather than as individual contracts. Build those once and repricing becomes a routine, low-drama cadence rather than a wrenching event you brace for every few years.

Companies that treat pricing as static accumulate commercial debt in the meantime, and companies that treat pricing as an evolving system end up repricing as easily as they ship features - which is where every SaaS business should want to end up.