A renewal playbook is not a list of email templates. It's a decision system — a set of documented rules that determine what happens, when, for which accounts, and who owns it. Done right, it takes the institutional knowledge that lives in your best CSM's head and turns it into something the whole team can execute consistently.
This guide covers the five components of a functional renewal playbook, in the order you should build them. Each section includes the specific questions you need to answer before moving to the next.
Step 1: Define your renewal segments
Segment before you sequence
The most common mistake in renewal playbook design is building a single sequence and applying it to all accounts. Segmentation — deciding which accounts get which treatment — has to come first, because every subsequent decision (timing, touch frequency, escalation path) depends on which segment an account is in.
At minimum, build two dimensions: ARR tier and risk level. ARR tier determines the commercial weight of the renewal (how much attention it deserves). Risk level determines the urgency and track (healthy, at-risk, or escalated).
| Segment | ARR Range | Outreach Start | Touch Frequency | Escalation Owner |
|---|---|---|---|---|
| Enterprise | $100K+ | 120 days | Weekly touchpoints | VP CS + AE |
| Mid-market | $20K–$100K | 90 days | Bi-weekly | Senior CSM |
| SMB | Under $20K | 60 days | Automated + CSM review | CSM queue |
Add a risk modifier: any account regardless of ARR tier that crosses a health score threshold drops into the escalation track immediately, overriding the standard timing. A $15K account showing three concurrent churn signals at T-100 gets treated like a mid-market account, not left on the standard SMB track.
Step 2: Define your health scoring signals
Pick 4–5 signals, weight them, set your threshold
Health scoring collapses to a single question: what behaviours in the 60–90 days before renewal are predictive of churn at your specific company? The signals vary by product, but the categories that matter most for most SaaS products are consistent.
Assign each signal a weight based on its historical correlation with churn at your company. Score each account 0–100. Set a threshold — typically 65 — below which an account enters the at-risk track. Set a secondary threshold — typically 45 — below which an account enters the escalation track. Revisit the weights quarterly as you accumulate more outcome data.
Step 3: Map your sequence timing and branching logic
Build sequences that adapt — not timers that fire regardless
A renewal sequence is not a drip. A drip fires on a fixed schedule. A sequence fires on a schedule, then adapts based on what actually happens — a reply, a health score change, a click, an escalation. That distinction is the difference between automation that helps and automation that damages the relationship.
For each segment, map the sequence as a decision tree, not a list. The nodes are: touchpoint fired → response detected? → if yes: pause and route to CSM. If no: is health score still above threshold? → if yes: next scheduled touchpoint. If no: escalate and move to escalation track. This logic should be written down before it's built into any tool.
The three non-negotiable sequence rules
1. Every sequence pauses immediately when the customer replies — no exceptions.
2. Every email passes through CSM approval before sending — AI-drafted or template-based.
3. Health score changes override the sequence timeline — a score drop overrides "next email at T-60."
Step 4: Build your escalation tracks before you need them
The escalation protocol has to exist before an account enters it
Escalation track design is the part most playbooks get wrong — because it gets built reactively. An account hits a crisis point, and the team improvises an escalation response. By the time the executive sponsor is looped in, the optimal response window has already closed. The escalation protocol has to be documented before any account needs it.
The escalation track needs four things defined in advance:
- Trigger conditions — the specific signal combinations that move an account into escalation (health score below threshold, or specific manual override)
- Owner assignment — who owns the escalated account immediately and who is looped in at what stage
- Response SLA — maximum time between escalation trigger and first owner action (24 hours is a reasonable standard)
- Resolution criteria — what outcome closes the escalation (renewal committed, account moved to active risk, or specific decision date set)
Step 5: Build your leadership visibility layer
The playbook is only complete when leadership can act on it in real time
A renewal playbook that produces good CSM-level execution but no leadership visibility isn't a system — it's a better version of the old manual process. The final layer of the playbook defines what leadership can see, how current it is, and what decisions they can make from it without asking the CS team.
At minimum, leadership needs three views: total ARR renewing by month over the next 90 days, ARR by risk tier (healthy / at-risk / escalated), and per-CSM renewal pipeline health. These aren't reporting views — they're intervention triggers. When the VP of CS sees that 30% of next quarter's renewal ARR is in the at-risk tier in January, they can reallocate CSM bandwidth in February. That's the value of the visibility layer: it turns lagging indicators into leading actions.
What a complete playbook looks like on one page
| Component | What it defines | Who owns it |
|---|---|---|
| Segmentation rules | Which tier each account belongs to and why | VP CS |
| Health scoring model | 5 signals, weights, and risk thresholds | CS Ops / RevOps |
| Sequence map | Timing, content, branching logic per tier | CS Team |
| Escalation protocol | Triggers, owners, SLAs, resolution criteria | VP CS + AE |
| Leadership dashboard | ARR at risk by tier, per-CSM pipeline, 90-day forecast | CS Ops |
A playbook that covers all five components converts the renewal motion from something that depends on individual CSM quality to something that runs consistently at the system level. New CSMs onboard faster. Coverage during absence doesn't degrade. Leadership can resource proactively. The process itself becomes a competitive advantage. To see how Renewal360 executes each of these five components automatically, visit How It Works or review the full feature set.
Ready to run this playbook in a system that executes it automatically?
Renewal360 implements the segmentation, health scoring, sequences, escalation tracks, and leadership dashboard from this playbook — configured to your accounts in 7 days. No credit card required.
Start Free Pilot →