Price Increase Rollout Playbook

You have decided to raise prices. Good. The decision was the easy part, and from here it is a project with a billing system, a CRM price book, an entitlement layer, five teams and a communication sequence that has to land in a specific order. This is the 60 day version, with owners and dates, written for the person who has to run it rather than the person who approved it.

Weeks 1 and 2: model the cohorts and set the grandfathering rule

The first job is knowing exactly who is affected and by how much, at the account level, before anyone drafts an email. Export every account with its current plan, contract end date, realized price per seat or unit, discount history and last 90 days of usage. Then segment into four groups, because they need four different treatments.

The already discounted cohort is where rollouts go wrong. Applying a uniform 12 percent uplift to an account already 30 percent below list produces a customer who is still underpaying and now angry. Handle those one at a time.

Set the grandfathering rule in the same fortnight and write it in one sentence. The version I would defend: existing customers keep current pricing until their next renewal after a fixed date, then move to the new price with a twelve month cap on the increase. Put the end date in writing immediately. Open ended grandfathering is how companies end up supporting five legacy plans nobody can explain, and the pricing and packaging refresh playbook covers how to retire those legacy tiers once they exist.

Weeks 3 and 4: change the systems before you change the story

Billing, entitlements and the CRM price book all change now, while the change is still invisible to customers. This is the least glamorous fortnight and the one that sinks rollouts when it slips.

Test proration with real account shapes, not clean ones. The account that upgraded mid term, downgraded once and has an annual contract paid monthly is where your billing logic will break, and finding that out after invoices go out costs you a week of apologies.

Week 5: brief CS and sales with scripts and a save offer ladder

Your frontline teams hear about the increase before customers do, and they need three things: the one sentence reason, the answers to the seven questions they will actually get, and explicit authority to make offers.

The one sentence reason. Something like: we have shipped X, Y and Z over the past eighteen months and our pricing now reflects the product as it stands. Then stop talking. Every additional sentence of justification signals negotiability, and reps who over explain get negotiated down.

The save offer ladder, with authority limits written down:

• Rung one, CSM authority. Six additional months at the current rate in exchange for an annual commitment. No approval needed.
• Rung two, manager authority. Annual prepay at a discount that lands within 3 percent of the old realized price. Approval by the CS manager, logged in the CRM.
• Rung three, VP authority. Multi year rate lock for strategic or reference accounts. Approval by VP, maximum ten accounts across the rollout.

Cap rung three numerically before launch. Without a cap, every rep decides their account is strategic and you have quietly cancelled the increase.

Lesson three of the pricing sprint course has a longer version of the objection set if your team has not run a rollout before.

Week 6: call the enterprise accounts individually

Every account above your enterprise threshold gets a human conversation before any email. Your top 20 accounts by ARR get a call from someone senior, and I mean this literally. Not an email with an offer to talk. A scheduled call.

The call is short. Here is what is changing, here is when it affects you, here is what we have shipped, here is what I can do for you. Five minutes of talking, then listen. The point is not persuasion. The point is that a large customer hearing about a price change from a mass email experiences it as a relationship downgrade, and that perception is more expensive than the price delta.

Sequence the calls over four days, highest ARR first, so that if the objections cluster around something you did not anticipate you can adjust the script before reaching account fifty.

Week 7: notify self serve with the required notice

Now the email goes out, at least 30 days before the change hits anyone’s card, or longer if your terms say so. Check the terms rather than assuming. Structure the message in this order: what is changing, when it affects this specific customer, what they gain, what they should do if they have questions.

Personalise three fields at minimum: current plan, current price, and the exact date their price changes. A generic email that makes a customer calculate their own impact generates a support ticket every time. The price increase announcement email templates have versions for grandfathered, non grandfathered and already discounted cohorts.

Publish the updated pricing page the same morning the emails send. Not before, not three days later. A customer who receives the email and then finds the old prices still live assumes a mistake and writes in.

Staff support for a spike. Expect elevated volume for roughly ten days, peaking on days two and three. Pre write six macros covering the common questions, and give support explicit permission to apply rung one of the save ladder without escalating, because a three day wait for an answer converts a mild complaint into a cancellation.

Weeks 8 and 9: monitor against thresholds you set in advance

Watch a daily dashboard with five numbers and compare each to a pre agreed baseline.

The thresholds go in writing before launch and get signed off by whoever approved the increase. Deciding what counts as failure during the worst week of the rollout produces panic reversals, and reversing a price increase publicly costs more trust than the increase ever earned. A pre committed threshold turns a reversal from a retreat into a plan working as designed.

Watch which rung of the save ladder gets used. Heavy rung two usage means your increase was priced slightly above what the market will absorb without compensation, which is useful intelligence for the next cycle. Heavy rung three usage means your authority limits leaked.

What this costs and what usually goes wrong

Budget roughly 120 to 200 hours of cross functional time for a mid market rollout, most of it in billing engineering and CS enablement rather than in marketing. The communication is maybe fifteen percent of the work.

Three failure modes worth naming. Billing edge cases that produce wrong invoices, which destroys the goodwill the whole plan depended on. Sales teams discounting the increase away in week one because authority limits were vague. And the slow one: grandfathering with no end date, which looks kind in month one and leaves you with a permanent second price book that corrupts every cohort analysis you run afterwards.

Read the repricing teardowns for what these look like at real companies, and understand where your own elasticity sits before committing, since price elasticity and price anchoring both behave differently in contracted B2B than the textbook version suggests.

Before you start

Run the pricing change readiness checklist end to end and do not begin week one until every item passes. Then put the 60 day calendar in front of the five owners, with names against each week, and hold a fifteen minute standup every Monday until day 60. The broader strategic context for where this sits in your SaaS pricing work is worth a read before you commit a date.