-
1
Lock the pricing change and effective date in writing
The rollout starts the moment the pricing decision is captured in a single memo and circulated to every function that will touch the change. The memo names the new list prices, the new packaging, the value-metric treatment, the effective date, the grandfathering policy, the discount envelope, and the kill criteria that would reverse the change. Verbal exec sign-off that lives in a Slack thread evaporates the first time a regional sales leader needs to invoke it against a complaining VP. Pick an effective date that gives the team at least thirty days of public notice before the price moves, that avoids the quarter-end rush where field discounting is highest, and that lands on a Monday so the first week of the new pricing gets a full operating cycle before anyone looks at the numbers.
- Write a one-page decision memo that names list prices, packaging, value-metric treatment, effective date, grandfathering, discount envelope, and kill criteria
- Collect written sign-off from the CEO, CFO, CRO, and head of CS on the memo itself, not on a separate thread
- Pick an effective date at least thirty days out, away from quarter-end, and on a Monday so the first week runs clean
- Store the memo in the single location sales, CS, finance, and legal already use so nobody is working from a stale copy
Tip: Pricing changes that ship without named kill criteria are extremely hard to reverse later. Decide the rollback trigger before the change goes live, not during the first bad quarter.
-
2
Grandfather existing customers with a defined scope and duration
Grandfathering is not a courtesy. It is the single biggest lever the rollout has for turning a pricing change into a retention event instead of a churn event. The policy has to answer four questions in writing before any customer sees the announcement. Which customer cohorts are covered: everyone on the old plan, only accounts above a certain size, only accounts in good standing. How long the grandfathering lasts: through the next renewal, for a fixed window such as twelve months, or indefinitely until a packaging trigger. What ends it: a renewal, a plan upgrade, an expansion seat purchase, a contract amendment. And what the renewal converts on: the new list price, a blended price, a negotiated bridge. Document the answers in the decision memo and in the account-owner playbook so there is one source of truth when a customer pushes back.
- Name the covered cohorts explicitly: all customers on the old plan as of the effective date is the clean default
- Pick a duration anchored to a trigger customers already understand, such as through the next contract renewal
- Decide what happens on expansion inside a grandfathered account so a seat add does not accidentally end grandfathering
- Write the renewal conversion terms so account owners know exactly what the new contract will quote
Tip: A packaging change that moves a popular feature into a higher tier is a hidden price increase on existing customers. Flag those moves in the grandfathering policy so the plan covers them, not just the headline list price.
-
3
Draft the customer announcement with why, what, when, and grandfather
The announcement is the single most-read artifact of the entire rollout, and buyers forgive almost any pricing change if the note is honest, specific, and lands well before the effective date. Lead with why the pricing is changing: invested capability, expanded value, inflationary cost structure, platform maturity. Follow with what is changing in concrete terms, including the new prices and the new packaging. State when the change takes effect and name the exact date, not a vague window. Close with the grandfathering treatment so existing customers see their protection before they see the new price. Give the note a named point of contact and a clear link to a longer FAQ for buyers who want detail. Keep the top of the message under two hundred words so it survives a quick skim.
- Open with a two-sentence why anchored in product value, not internal cost pressure
- List the concrete what in a short table or bulleted comparison so the delta is unambiguous
- State the exact effective date and the public notice window in the first paragraph
- Close with the grandfathering treatment, the renewal timeline, and a named account contact or team alias
-
4
Train sales and customer success on the new comms
The announcement is only half the comms plan. The other half is every live conversation the field has in the thirty days before and the ninety days after launch. Sales and customer success need the same objection-handling doc, the same grandfathering decision tree, and the same escalation path for exceptions, or the rollout dies by inconsistency. Run live training sessions, not just a doc drop. Roleplay the top ten objections the team has already predicted: the loyal customer who feels punished, the pilot that signed last month, the expansion that was about to close, the multi-year that is mid-term. Record the training so new hires onboarding in the first ninety days get the same answers. Freeze outbound discounts outside the new envelope for the first thirty days so field pressure does not immediately re-break the model.
- Build a single objection-handling doc covering the top ten questions sales and CS have already predicted
- Run a live training session for every revenue team with roleplay on the hardest objections, not a slide read
- Publish a grandfathering decision tree so account owners can answer the common edge cases without escalating
- Freeze discounts outside the new envelope for the first thirty days and name the exceptions path for everything else
Tip: Train customer success before sales, not after. Existing customers hear about the change from their account owner first, and a CS team that is confident on day one prevents half the inbound questions sales would otherwise field.
-
5
Publish the change at least 30 days before the effective date
The thirty-day minimum notice window is both a courtesy and a legal baseline in many jurisdictions, and shorter windows are the single most common unforced error in a pricing rollout. Publish the announcement to every audience on the same day: the public pricing page updates to show the new prices with an effective-date callout, every existing customer gets a direct note from their account owner with the grandfathering terms, every partner or reseller with a quote outstanding gets the transition rules in writing, and the sales enablement portal flips to the new collateral. Hold the public pricing page in a staging state until the announcement goes out so nobody reads the new price before they read the explanation. Expect a spike of inbound questions in the first forty-eight hours and staff the response channel accordingly.
- Publish the pricing page, the customer email, the partner note, and the sales collateral on the same day
- Keep the thirty-day window as a floor, not a target, and extend it for enterprise cohorts with longer procurement cycles
- Staff the inbound response channel for the first forty-eight hours with named owners from sales, CS, and finance
- Monitor the pricing page and the announcement thread for errors and ship corrections inside two hours, not two days
-
6
Honor every existing contract through its current term
No existing contract gets repriced mid-term, period. The signed agreement is the signed agreement, and any attempt to pull revenue forward by invoking a vague price-change clause will cost more in trust and churn than it will ever recover in uplift. Build a contract register before launch that lists every active agreement, its current price, its renewal date, and whether it falls inside or outside the grandfathering policy at renewal. Flag the agreements with explicit price-lock clauses so legal and the account owner know the terms before the renewal conversation starts. For multi-year deals, the new pricing applies at the next renewal under the grandfathering rules, not at an arbitrary anniversary. Expansion inside a mid-term contract should follow the grandfathering policy on expansion, which was decided in step two, not improvised in the moment.
- Build a contract register before launch with price, renewal date, and grandfathering status for every active agreement
- Flag agreements with explicit price-lock or price-cap clauses so legal and the account owner have the terms in hand
- Route any proposed mid-term price change through legal and the exec sponsor, with written customer consent as a hard gate
- Apply the expansion grandfathering rule decided in step two to every mid-term seat add or module add, consistently
Tip: A customer who discovers a mid-term reprice they did not consent to will tell every peer in their category. The reputational cost of a single mishandled contract is higher than the ARR uplift from the whole rollout.
-
7
Monitor churn, win rate, and ARR impact daily for 90 days
Pricing changes are won or lost in the first ninety days after the effective date, and the measurement discipline has to be locked before launch, not retrofitted after the first bad week. Track five numbers every day on the same dashboard: gross churn and downgrade rate on existing accounts split by grandfathered and ungrandfathered cohorts, new-logo win rate against the pre-change baseline on comparable deals, average contract value on new business, net ARR impact including expansion and contraction, and discount depth against the new envelope. Pair the numbers with a running feedback log from sales and CS so qualitative signal does not get buried under dashboards. If the kill criteria defined in step one trigger, invoke them. If the numbers come in ahead of plan, document what worked so the next change starts from evidence.
- Lock a daily reporting cadence for ninety days covering churn, win rate, ACV, net ARR impact, and discount depth
- Split every metric by grandfathered and ungrandfathered cohorts so the real impact on the installed base is visible
- Keep a running sales-and-CS feedback log and tag every entry to the pricing or packaging decision it touches
- Review the dashboard with the exec sponsor on a weekly cadence and invoke kill criteria the day a threshold breaks, not the week after
Tip: The first fourteen days of post-launch win-rate data are noisy because pipeline that was already in flight closes on a mix of old and new pricing. Hold the kill criteria to the thirty-to-ninety-day window unless churn moves hard early.
-
8
Run a formal retro after 90 days and feed it into the next review
The retro is where the rollout turns into institutional memory instead of folklore. Pull the ninety-day numbers against the modeled base case, read the sales-and-CS feedback log end to end, interview five to ten customers who stayed and three to five who downgraded or churned, and write a single memo that answers four questions. What landed better than expected and why. What landed worse and why. Which decisions in the rollout would be made differently next time. What the next pricing review should start from in terms of evidence, open questions, and policy. Circulate the retro to every function that touched the rollout, store it where the next review will find it, and name an owner for the follow-up actions so the lessons do not sit in a doc until the next change is already overdue.
- Compare the ninety-day actuals to the modeled base case for every metric that was on the pre-launch dashboard
- Interview five to ten customers who stayed and three to five who churned or downgraded during the window
- Write a four-question memo covering what worked, what did not, what to change, and what the next review inherits
- Name a single owner for the follow-up actions and store the memo where the next annual pricing review will start from
