A renewal forecast tells you how much revenue is at stake. A renewal playbook tells your team exactly what to do and when so that number actually lands.
A renewal playbook is the standard operating sequence a customer success manager runs in the ninety days before a contract ends. It is the motion, not the number. Typical steps include a usage and value check at ninety days out, an executive touch at seventy five days, a pricing and uplift letter at sixty days, a security and compliance refresh, a commercial conversation, and a signed renewal order form by thirty days before term end.
The six things every customer success leader should know before writing, running, or standardizing a renewal playbook.
A renewal playbook is the written, repeatable sequence a customer success team runs on every account before contract end. The forecast tells leadership what the number is. The playbook tells the owner what to do this week to protect it. One is a prediction, the other is an operating procedure.
Mature teams anchor the playbook on three dates. Ninety days before term end opens the motion with a usage review. Sixty days triggers the commercial conversation and pricing letter. Thirty days is the signature deadline. Each checkpoint has required artifacts, owners, and exit criteria before the account advances.
A complete playbook runs six core plays. A usage and value review proves the renewal case. An executive touch confirms the sponsor is still in seat. A pricing letter sets the uplift expectation in writing. A security and compliance refresh keeps procurement unblocked. A commercial negotiation resolves the final number. A signed renewal order form closes the loop.
The customer success manager owns the playbook and the relationship. On expansion or multi-year commercials, an account executive or renewals specialist joins at the pricing letter stage. The split keeps CSMs focused on value delivery while a commercially trained owner handles uplift and legal. Smaller teams run both roles from the CSM seat.
A playbook is only as good as its evidence. Each step produces a logged artifact in the account record. The usage review is a saved report. The executive touch is a meeting note with attendees. The pricing letter is an attached PDF. The order form is a signed document. Auditable artifacts turn renewals from a judgment call into a repeatable process.
The playbook forks by risk tier. Green accounts run the standard motion plus an expansion branch. Yellow accounts add a success plan refresh and a second executive touch. Red accounts trigger a save play with an executive sponsor on both sides, a defined turnaround target, and a weekly check-in cadence until the account is back to yellow or renewed.
A real renewal playbook has specific plays, specific owners, and specific exit criteria at each checkpoint. The sequence below is the shape most mid-market and enterprise B2B teams converge on. Smaller teams run a compressed version of the same motion.
The CSM pulls the last four quarters of product usage, support history, business reviews, and goal attainment into a single value brief. The brief answers one question. Is the customer getting what they paid for. The brief is shared internally first, then with the economic buyer before any commercial conversation starts.
The CSM books a thirty minute call with the executive sponsor. The agenda is the value brief, next period goals, and any organizational changes on the customer side. If the sponsor has moved on, the playbook branches into a new sponsor identification play before the pricing letter goes out. A missing sponsor is a leading churn signal.
A formal pricing letter goes out sixty days ahead of term end. It states the renewal amount, any contractual uplift, any proposed expansion, and the deadline for signature. The letter is a legal artifact, not a conversation. The commercial conversation happens separately. Sending the letter in writing anchors the negotiation and prevents last minute surprises.
Procurement teams at mid-market and enterprise buyers often require a refreshed security questionnaire, SOC 2 or ISO artifact, and updated data processing addendum before signature. The CSM proactively sends the current pack rather than waiting to be asked. This single play removes the most common last week renewal blocker.
The commercial call closes the gap between the pricing letter and the signed order form. Topics include seat changes, module adds, multi-year commitments, and any requested concessions. The AE or renewals specialist leads this call with the CSM in support. Everything agreed in the call is reflected in a revised order form within forty eight hours.
The target is a counter signed order form by fifteen days before term end. The buffer protects against legal review surprises on the customer side and keeps the renewal out of auto-renewal gray zones. Any renewal still open at fifteen days triggers an escalation to the CS leader and a joint push with sales leadership until it lands.
A renewal playbook is not a single rail. Green, yellow, and red accounts run different variants of the same motion. The branches are what turn a static checklist into an operating system. Here is what the fork looks like in practice.
Green accounts default to a flat or uplifted renewal plus an expansion branch. The CSM identifies two or three concrete expansion motions during the usage review, scopes them in the pricing letter, and lets the customer choose. The branch is additive. The base renewal is not held hostage to the expansion decision.
Yellow accounts add a success plan refresh at the ninety day mark. The CSM rewrites the mutual plan with new goals, new milestones, and new executive alignment. A second executive touch happens between the pricing letter and the commercial call. The branch is designed to walk a stalling account back to green before the pricing conversation starts.
Red accounts trigger a save play. An executive sponsor from the vendor side and the customer side both sign the play. A written turnaround target with a date and a measurable outcome is agreed. The CSM, the executive sponsor, and often an engineering or product leader meet weekly until the account is back to yellow or renewed on reduced terms.
If the economic buyer or executive sponsor has left the customer organization, the playbook pauses and a sponsor identification play opens. The CSM maps the current org, requests warm introductions, and does not send the pricing letter until a new sponsor is confirmed. Sending a pricing letter to a vacuum guarantees a stalled renewal.
A multi year renewal is a different legal document and a different commercial conversation. Procurement and legal join the thread at the pricing letter stage, not the commercial call. The playbook adds a redline round and a longer buffer at the end. Multi year motions skip the fifteen day target in favor of a thirty day target to account for the extra legal time.
Contracts with auto-renewal and a notice window change the math. The playbook anchors backward from the opt out date rather than the term end date. If the opt out notice is sixty days, the ninety day usage review becomes a one hundred fifty day usage review. Teams that forget to invert the timeline get surprised by churn notices before the pricing letter even goes out.
A renewal playbook on a slide deck is a document. A renewal playbook inside the CRM is an operating system. The difference is whether the plays are triggered, tracked, and reconciled automatically or by human memory. Here is what a systemized playbook includes.
Every renewal account carries a contract end date. The playbook triggers tasks at T minus ninety, seventy five, sixty, forty five, thirty, and fifteen days automatically. The CSM does not have to remember. The system opens the next play and routes it to the right owner on the right day. Missed triggers are visible on the manager rollup.
The usage review requires a saved report. The exec touch requires a meeting note. The pricing letter requires an attached document. The security refresh requires updated artifact dates. The order form requires a signed PDF. The playbook does not advance a step until the artifact is logged, which is what turns a motion into evidence.
When the health score drops an account from green to yellow or yellow to red mid motion, the playbook forks automatically. The branch opens the extra plays. The CSM gets notified. The manager rollup flags the account. The customer never sees the branch change, only the richer engagement that follows from it.
The CS manager opens one page and sees every account in their team's renewal book, which play each account is on, which artifacts are logged, which are overdue, and which forecasts are at risk. No pivot tables, no exported spreadsheets. The rollup is the operating surface for the weekly renewal meeting.
A systemized playbook produces an audit log. When the pricing letter was sent, when the exec touch was booked, when the security pack was shared, who touched what, and when the account advanced from stage to stage. The log is what makes renewal post mortems possible and what turns gut feel into coachable patterns.
At quarter end the system reconciles playbook completion against renewal outcomes. Which CSMs ran every play on every account. Which skipped the exec touch. Which renewal losses correlate to missing artifacts. The reconciliation turns renewal into a coachable craft rather than a mystery that gets diagnosed only after the churn email arrives.
Strkr ships scheduled renewal checkpoints, required artifacts logged to the account, health score branching, manager rollups, and quarter end playbook reconciliation out of the box. Fourteen day trial, no credit card, every customer success surface on every plan.
A renewal forecast is the committed number. It tells leadership how much revenue is projected to renew, churn, or expand in a period. A renewal playbook is the operating procedure that produces the number. The forecast is the output. The playbook is the input. A team can have a sophisticated forecasting model and still miss renewals if the playbook is not running on every account.
Most B2B subscription teams open the playbook ninety days before contract end. Enterprise accounts with auto-renewal notice windows or long procurement cycles start one hundred twenty to one hundred fifty days out. Shorter contracts and transactional subscriptions compress the sequence to forty five or sixty days. The anchor should always be the opt out date, not the term end date, when a notice window exists.
The customer success manager owns the playbook end to end. On expansion and multi year commercials, an account executive or dedicated renewals specialist joins at the pricing letter stage. Procurement and legal engage during the security refresh and the commercial conversation. The CSM remains the single accountable owner across the entire motion, including when other roles join the thread.
The six standard plays are a usage and value review, an executive touch, a pricing letter, a security and compliance refresh, a commercial negotiation, and a signed renewal order form. Mature teams add branches for expansion, success plan refreshes, save plays, sponsor identification, multi year legal cycles, and auto renewal notice windows. The core six are the baseline every team runs.
A success plan is the shared document between the vendor and the customer that defines the goals, milestones, and outcomes the customer is working toward. A renewal playbook is the internal vendor-side sequence for protecting a specific contract end date. The success plan runs continuously throughout the contract. The playbook fires in the final ninety days. A healthy renewal usually requires both.
A save play is triggered when an account crosses into the red risk tier at any point in the ninety day window, when the executive sponsor leaves the customer organization and cannot be replaced, when a competitive displacement is formally announced, or when the customer requests a termination for cause review. The play assigns executive sponsors on both sides, a written turnaround target, and a weekly cadence until resolution.
Smaller teams run the playbook in a spreadsheet with calendar reminders. Mid-market and enterprise teams move it into the CRM or a customer success platform. The must have features are automatic triggers off the contract end date, required artifacts logged to the account, health score branching, manager rollup, audit logging, and reconciliation at quarter end. Spreadsheets break at scale because they rely on human memory for every trigger.
The leading indicator is playbook completion rate. What percentage of accounts had every required play run with the required artifact logged by the required date. The lagging indicator is gross retention. Teams that keep playbook completion above ninety percent typically run three to five points of gross retention higher than teams that let plays slip. Reconcile both numbers quarterly and tie them to CSM coaching.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
