All essays
May 20, 2026·6 min read

How we migrate pricing after a B2B SaaS acquisition without breaking NRR.

A four-quarter pricing playbook — instrument, repackage, fix contracts, then move list — designed to capture unrealized economics in an acquired SaaS business without spending the trust that made it acquirable.

A founder who has not raised list prices in three years is sitting on meaningful unrealized economics. So is a founder who has packaged the product as a single per-seat plan when the actual usage shape would support a value-based or hybrid model. So is a founder whose top accounts have rolled the same enterprise discount forward through four renewal cycles because nobody on either side wanted to reopen the conversation. We see all three patterns regularly, sometimes in the same business. The opportunity is real. So is the risk of squandering it.

The two failure modes we are trying to avoid

Pricing migrations after an acquisition fail in two recognizable ways. The first is the smash-and-grab — a new owner who reads the existing contracts, sees the gap to market, and pushes a sharp list-price increase in the first quarter. It works in the spreadsheet and breaks in the customer base. NRR drops, the CSAT line bends, and the team spends the next year defending a number rather than building the product. The second failure mode is the opposite — the new owner is so worried about disrupting the business that they touch nothing for two years, and the unrealized economics quietly compound against them. Both failures share a single cause, which is that the operator treated pricing as a one-decision event rather than a sequenced program.

Pricing is not a number you raise. It is a system you migrate.

The Cobalt Glacier sequencing

Our standard sequence runs across the first four quarters of ownership and is designed to put the pricing change at the end of the program, not the beginning. The first three quarters are about earning the right to move the number.

Quarter one — instrument and listen

In the first quarter we do nothing visible to the customer base on price. Internally, we stand up clean cohort reporting on net dollar retention, gross dollar retention, expansion, downgrade, and churn, broken out by plan, segment, and contract vintage. We also run structured win/loss and renewal interviews on the last twelve months of activity. The output is a real picture of where the existing pricing model is leaking value, where the customer base already perceives a value gap, and which packaging assumptions are being held together by sales accommodations rather than product design.

Quarter two — fix packaging before price

Packaging is almost always the first move, and the most under-rated. Renaming plans, adding a clearly differentiated higher tier, breaking out a usage-priced component, or moving a power feature into a paid module can move ARPU meaningfully without changing the price of any existing line item. Existing customers see continuity on their contracts; new customers buy into a cleaner ladder. Packaging changes ship in the second quarter, with the new structure introduced to the market through the website, the sales motion, and the renewal playbook simultaneously.

Quarter three — fix contract hygiene

The third quarter is the contract sweep. Every top-twenty customer contract is reviewed, and any of the following gaps are renegotiated on the next natural renewal — missing or undersized annual price escalators, missing assignment language, mis-priced overage terms, unfunded SLAs, and stale discount structures that no longer reflect the customer's actual size or commitment. None of these is a list-price increase. All of them prepare the book for the eventual list-price move and most of them produce measurable economics on their own.

Quarter four — the list-price move, if warranted

Only at the end of the first year, if the data still supports it, do we move list prices. By this point we have a clear picture of where the value gap is, the packaging change has been absorbed, the contracts are healthier, and any list-price increase lands against a product the customer base has spent a year watching improve. We grandfather existing customers for at least one full renewal cycle, telegraph the change at least ninety days in advance in writing, and tie the increase to a visible product or service improvement. The increase is almost always smaller than the gap-to-value analysis would suggest, because the goal is durable ARPU expansion across a permanent-capital holding period, not a single ratchet.

The mechanics of the actual increase

When the list-price change goes out, three rules govern it. They are not negotiable inside our playbook.

  • Grandfather existing customers for one renewal cycle. Customers who signed before the change keep their pricing until their next natural renewal date. This protects trust and gives the customer success team a clean, calendar-driven conversation rather than a surprise.
  • Telegraph in writing, at least ninety days out. The notice goes from the operator, not from billing operations, and it explains the reason — usually a combination of expanded product scope, improved support posture, and continued investment. The wording is direct and not defensive.
  • Tie the increase to a visible improvement. The change is paired with a product release, a new support tier, a measurable reliability commitment, or a substantive capability expansion. Pricing increases that arrive alongside something the customer can point to land cleanly. Increases that arrive in isolation do not.

What this does to NRR

Done correctly, a packaging refresh in quarter two and a list-price move in quarter four together produce a step-change in net revenue retention without a corresponding step in gross churn. The compounding effect is exactly the dynamic we wrote about in NRR is the only B2B SaaS metric that compounds. A two- or three-point lift in NRR is small in the first year and very large over a twenty-five-year hold. The patience in the sequencing is in service of that compounding, not in opposition to it.

What we do not do

We do not raise list prices in the first quarter. We do not change existing customers' contracts mid-term. We do not push existing customers off legacy plans onto new packaging unless the customer opts in. We do not introduce surprise overage charges or quietly change usage definitions. We do not use the acquisition as a pretext to reset commercial terms across the book in a way the customer experiences as a bait-and-switch. Each of those moves produces a one-time bump in revenue and a permanent loss of trust. The permanent loss of trust is the expensive part on our holding period, not the one-time bump that is the cheap part.

The connection to underwriting

The pricing program above is not separable from how we underwrite a deal. We underwrite to the steady-state pricing we believe the business should hold, not to the pricing it currently has, and we give ourselves a full year of operating runway to bridge the gap. That bridge is what gives us the discipline to pass on businesses where the pricing gap is too wide to close without breaking the customer relationship — a pattern that comes up most often in venture-backed targets, as we discussed in Why we pass on most venture-backed targets.

The bottom line

Pricing is the lever that most rewards patience and most punishes haste. The Cobalt Glacier pricing migration is a sequenced program — instrument, repackage, clean up contracts, then move list — designed to capture the unrealized economics in an acquired business without spending the trust that made it acquirable. The compounding shows up in NRR, in renewal rates, and in the relationship the company has with its top accounts a decade after close. The discipline is in waiting long enough to do it well.

If you are a founder weighing a permanent-capital home for a business you suspect is underpriced, start a conversation. If you are an operator who has run a pricing migration before and wants to embed with a portfolio brand, our Operating Partner program is the door.