-
1
Define the 180/120/90/60/30-day gates and name an owner at each one
A renewal playbook that is not anchored on fixed day counts drifts the moment calendars get busy. Lock the five gates at 180, 120, 90, 60, and 30 days before contract end, write the deliverable for each gate as a one-sentence output (not a vague activity), and name the CSM or AM as the single accountable owner of that gate even when both roles contribute. The CSM owns the 180-day health review, 120-day exec check-in, and 90-day value realization audit. The AM owns the 60-day pricing conversation, the 30-day renewal proposal, and legal routing. Writing the gates down and publishing the owner map removes the two biggest killers of renewal motion: silent assumptions about who moves next and quiet slippage of the start date.
- Pin the five gates to contract end date math, not to a quarterly cadence, so every account hits the same checkpoints at the same relative distance.
- Write each gate as a deliverable (health review doc, exec meeting notes, value audit, pricing proposal) not an activity (meeting, call, email).
- Assign a single accountable owner per gate; a co-owned gate is an unowned gate by week three of a busy quarter.
- Publish the owner map in the account record so the full team, including the exec sponsor on your side, can see who is driving which stage.
Tip: If your average deal cycle is under six months, keep the 180-day start anyway. Starting earlier never hurts, and compressed timelines are what let one surprise churn signal eat a whole quarter of net retention.
-
2
Run the 180-day account health review and classify risk honestly
At 180 days out, the CSM pulls the full health picture and classifies the account into one of four buckets: at-risk, flat renewal, expansion-ready, or strategic. Health inputs span product usage trends over the trailing 90 days, open support tickets and severity, executive engagement cadence, user NPS or CSAT scores, and any renewal risk flags like a champion departure or a competitor evaluation. The honesty of this classification is the single most important act in the whole playbook. Teams that mark every account green until 60 days out spend the back half of the motion scrambling, and leadership loses faith in the forecast. A fair at-risk flag at 180 days is a gift to the AM, not an admission of CSM failure.
- Pull trailing 90-day product usage trends by seat, module, and workflow depth; a flat seat count masking declining usage per seat is a classic silent churn signal.
- Review every open and recently closed support ticket for severity, sentiment, and whether a product fix was promised; broken product promises surface here or at legal.
- Confirm executive engagement in the last 90 days: an exec review that quietly slipped three months ago is a bigger risk signal than a loud ticket.
- Classify the account into at-risk, flat, expansion-ready, or strategic and write a two-paragraph read that justifies the bucket with evidence, not vibes.
Tip: Pre-populate the health review with Strkr AI drafts of usage summaries and ticket themes so the CSM spends their time on judgment calls, not data assembly. The classification itself always stays a human decision.
-
3
Book the 120-day executive check-in and preview the renewal motion
At 120 days out, the CSM books a 45-minute executive check-in with the economic buyer or their delegate. This is not a sales call; it is a status review tied to the business case the account signed on. Share the health classification in buyer-facing language, review the top two or three outcomes the customer said they wanted when they bought, name what has been delivered and what is still in flight, and close by previewing that a renewal conversation will begin in about 30 days with the AM. The point of the preview is to remove surprise from the pricing conversation that comes at 60 days. Executives who hear the renewal is coming at 120 days do not panic at 60; executives who first hear the word renewal at 45 days push the whole motion into procurement reflexively.
- Agenda the meeting around the original business case, not around your product roadmap; the roadmap belongs in a different conversation.
- Share two or three delivered outcomes with evidence (usage, workflow adoption, support resolution, named user quotes) rather than feature counts.
- Preview the renewal timeline explicitly: AM will be in touch in about 30 days for a value and commercial review, with the proposal landing around 60 days out.
- Capture any new business priority the exec raises; those priorities become the frame for the 90-day value audit, not an afterthought.
Tip: If the 120-day exec check-in cannot be booked within two weeks of the gate, treat that as a yellow flag on the account regardless of what the usage data says. Access decay is one of the earliest churn signals and the most ignored.
-
4
Complete the 90-day value realization audit against the original business case
At 90 days out, the CSM produces a written value realization audit that compares the outcomes the customer bought against what has actually been delivered. Pull the original mutual success plan or business case, line up each stated outcome with evidence from product usage, workflow adoption, operational metrics the customer shared, and user testimonials, and write a one-page summary that both the CSM and AM will reference for the rest of the motion. Where outcomes have been delivered, name the proof. Where they are in flight, name the realistic path and date. Where they will not be delivered, name that honestly and surface the alternative value the customer did get. A clear value audit shortens the pricing conversation at 60 days from a negotiation into a confirmation.
- Open the original mutual success plan or business case and list every stated outcome, in the customer's own words, as the audit scaffold.
- Attach proof per outcome: usage data, process metrics the customer provided, named user feedback, support resolution of blocking issues.
- Separate delivered, in-flight, and not-delivered outcomes clearly; obscuring the not-delivered bucket is how renewals blow up on legal review.
- Co-review the audit with the AM 10 days before the 60-day gate so pricing and legal come in with the same evidence base as adoption.
Tip: If the original business case does not exist, write a retroactive one with the exec sponsor as the opening act of the audit. You cannot renew on value you never defined, and the retroactive doc becomes the baseline for next year.
-
5
Transition from CSM to AM at the 60-day pricing conversation
At 60 days out, the AM takes operational lead and opens the pricing conversation with the account. The handoff is explicit, not implied: the CSM joins the first AM-led meeting, re-shares the value audit on the record, and formally introduces the AM as the renewal lead for commercial terms. The pricing conversation is a dialogue, not a quote. Walk through the health classification, the value audit, the usage trend, and any list price changes or packaging updates before any number lands on the table. If expansion is on the table, keep it as a separate conversation thread flagged for the expansion playbook; mixing renewal and expansion in the same conversation is a top cause of blown renewal cycles because procurement anchors on the combined number and demands concessions on both.
- Run a joint CSM plus AM transition call with the economic buyer at or just before the 60-day gate so the handoff is visible, not quiet.
- Walk the account through health, value, usage, and any list or packaging change before any price appears in writing.
- If expansion is live, hand it off to the expansion playbook thread with a separate owner and timeline; do not negotiate expansion as part of renewal uplift.
- Document every verbal concession or ask the moment it is raised; verbal commitments that go unlogged become legal arguments 20 days later.
Tip: If pricing is the first renewal conversation the economic buyer has heard, your 120-day exec check-in failed. Fix the playbook cadence, not the price, before you concede.
-
6
Send the 30-day renewal proposal and route it to legal in parallel
At 30 days out, the AM sends the formal renewal proposal with term, price, product mix, start date, and any negotiated terms clearly listed. The proposal references the value audit as the first attached document so the buyer sees the renewal grounded in delivered outcomes, not just a quote. In parallel, the AM routes the paper to legal on both sides immediately; waiting for a verbal yes before starting legal is a classic mistake that pushes closed dates past end-of-term and forces month-to-month bridges that leak revenue. Legal review in B2B SaaS routinely takes 10 to 20 business days, and renewal paper often has fewer novel terms than a new contract, so legal can run concurrently with final buyer approval without wasted work.
- Attach the value audit as the first appendix to the proposal so the first thing the buyer sees is outcomes, not price.
- List every negotiated term in writing (price, discount, true-up terms, service levels, data commitments) so legal has no ambiguity.
- Route redlines on both sides in a shared document with named reviewers and a clear two-business-day turnaround expectation.
- If the account is multi-year, write the pricing escalator and auto-renew language into the proposal explicitly; those are the terms procurement will fight over.
Tip: Keep a two-page renewal paper template that your legal team has already blessed. Teams that custom-draft every renewal from scratch add 10 to 15 days to average cycle time on paperwork that could have been standard.
-
7
Run weekly renewal forecast with CS and AM leadership
The playbook only holds if there is a standing surface where every account in the 180-day window gets reviewed every week. Run a 60-minute weekly renewal forecast call with CS leadership, AM leadership, and your revenue operations partner. Review every at-risk account, every account where a gate slipped by more than five days, and every account where new intel landed since the last meeting. The point of the call is pattern recognition and resource allocation, not individual deal rescue. If three accounts hit at-risk in the same week with the same product signal, that is a product issue that needs an exec escalation path, not three heroic CSM saves. Patterns across accounts drive the quarterly playbook iteration you do at step nine.
- Open the call with every account that hit a new red health classification or missed a gate in the past week.
- Review every account inside the 60-day window regardless of status; late-stage surprises are the most expensive kind.
- Flag any pattern of risk across accounts (same product, same segment, same vendor change) for exec escalation outside the renewal motion.
- Close the call with a one-slide snapshot of at-risk ARR, forecast net retention for the quarter, and any help the team needs from leadership.
Tip: If the weekly forecast turns into a status report where every account is green until it is suddenly red, the health inputs are too lagging. Add two leading indicators (executive engagement cadence, workflow depth trend) before you change the meeting.
-
8
Capture the renewal outcome and the save or expansion play in writing
The moment a renewal closes, the AM logs the outcome structurally: renewed, renewed with expansion, renewed with contraction, churned, or non-renewed by customer choice. For every outcome, write a short post-renewal read that captures what the health classification was at 180 days, what the final outcome was, which gates ran clean and which slipped, and what the deciding factor was. This post-renewal read is the raw material for both the quarterly playbook iteration and the next renewal cycle on the same account. Teams that renew without capturing why they renewed are starting the next 180-day cycle from scratch every year and will keep making the same mistakes on the same account tier.
- Log every outcome into the same account record so renewal history, not just the latest term, is visible to the next CSM or AM.
- Write a two-paragraph post-renewal read within five business days of close; the detail decays fast and the save or churn reason gets rewritten in team memory.
- Tag the deciding factor (value proof, exec access, pricing concession, product gap, legal friction) so patterns across accounts are queryable.
- Feed non-renewal reads directly into the product and support teams, not just revenue leadership; most non-renewals point at an operational fix that will save five more accounts.
Tip: Review the previous renewal read as the opening act of the next 180-day cycle. Last year's save play often maps directly to this year's playbook adjustment on the same account.
-
9
Iterate the playbook quarterly against renewal rate and net retention math
Freeze the five-gate structure for a full quarter, then open the playbook up for revision. Pull gross renewal rate, net revenue retention, average cycle time from 180-day gate to closed renewal, and the distribution of outcomes by starting health classification. If flat and at-risk accounts are closing at similar rates, your health model is lagging. If renewal cycle times are stretching past end-of-term, your 60-day pricing conversation is landing too late. If concessions are concentrating in the last 30 days, your value audit is not landing with enough proof at 90 days. Rewrite the gate deliverables, the owner map, and the forecast cadence based on what the data says, and publish the changelog so the CSM and AM teams see the playbook iterate on evidence, not on manager instinct.
- Pull the four core metrics per segment and per account tier so you can see where the playbook works and where it does not.
- Run a 60-minute quarterly retro with CS and AM leadership plus revenue operations; separate the retro from the forecast call.
- Rewrite only the gates where the data points at a specific break; wholesale rewrites every quarter signal panic, not iteration.
- Publish a changelog with the version, the change, and the business reason so field teams trust the playbook as a living document, not a moving target.
Tip: Give at least two quarters of data before you declare a gate broken. One bad quarter is often a product or market signal, not a playbook signal, and ripping out a working gate on noise is more expensive than leaving it in place.