Talk to an Expert

Staged change

Price changes on the installed base

5 min on the light depth

The frame

Raising prices on existing customers and moving them onto new pricing are one problem, the customer transition. That is the sequence by which an installed base moves from the terms it bought on to the terms you sell on now. While the sequence runs, the old terms become a legacy carry-forward: existing customers keep the price and unit they signed for while new customers buy on the new ones. A rupture moment is a repricing that moves the unit, the editions and the price in one event. The customer meets every change at once and accepts or refuses the whole of it.

The first request will be an increase. Most installed-base increases are applied to the list price and absorbed by the discount waterfall, the sequence of discounts between list and the invoice. The measure is realized price, what a customer pays per unit after every discount and old term, read on the same cohort before and after. An increase on list that the discounts absorb changed nothing. Transitions fail on the existing base, so plan the move for the customers you already have before you plan the launch.

The piece on raising prices argues that the test comes first and the percentage last, and that undercharging usually begins in the value metric, the unit your price attaches to. The piece on legacy carry-forward argues that a hold which never ends locks in a price-value gap, so the hold needs a boundary. The per-seat piece argues that a move from seats to usage is a metric transition: the unit changes while the pricing rulebook may stay. The wrong unit becomes a tax customers learn to avoid.

On the customers you raised prices for last time, did realized price move, or did the discounts absorb the increase?

Three things to say in the room this week

  • Before we pick a percentage, show me what that cohort paid per unit before the last increase and after it.
  • Our existing customers are the design constraint on any new pricing, so the transition plan comes before the launch date.
  • If we keep some customers on the old terms, the hold needs a boundary and an owner.

Core reading

Go deeper: the heavy depth

Read the core in this order.

  • How to raise prices on existing customers: why an increase on list is absorbed before the invoice, and the tests before the percentage.
  • Transitioning existing customers to new pricing: what an open-ended legacy carry-forward does to the price-value gap, and the upgrades that end it.
  • Per-seat to usage pricing transition: the seat as a proxy that stopped tracking value, and usage as a unit that must pass the same test.

Then the shelf.

  • AI agents seat count repricing: the exposure is in contract language written before agents existed.
  • Repricing freemium: the transition owed to free users when a free edition is withdrawn.
  • Repricing legacy portcos for the AI era: a price increase will not close an architecture gap.
  • Managing risk in software pricing: licensing changes hold the most risk, and moving legacy customers all at once is a deployment failure.
  • How software pricing facilitates value-based selling: legacy migrations as part of equipping sales at go-live.
  • Software pricing in a continuation vehicle hold period: legacy carry-forward grants stay with the owner through a longer hold.
  • Why land and expand strategies fail to expand: expansion pricing that stops scaling with value.

Glossary pages to open: customer transition and rupture moment. The research hub on customer retention and churn holds the peer-reviewed work on price changes and whether subscribers stay.

Where this leads: the Pricing Model Transition page says transitions fail on the existing customer base, and a blanket cutover date is a churn plan. It covers perpetual to SaaS, open source to commercial, services to platform, and seats to consumption, designed customer by customer with the existing customers as the design constraint.

The next module is The admired company: reading the market without copying it.

The shelf

Terms

Where this leads

Which depth did you take?