Churn & Expansion Playbook Framework
A framework for splitting the retention motion from the expansion motion so post-sale revenue stops being an afterthought — with health scoring, trigger rules, and role ownership for each.
What's inside
- The core principle: why retention and expansion need different owners, triggers, and metrics
- Customer health-score rubric — the weighted inputs that predict churn risk
- Churn risk-trigger table mapped to specific save plays
- Expansion trigger table mapped to specific expansion plays
- Role split model: CSM vs. Account Manager vs. hybrid, with when each fits
- QBR cadence and agenda template split by retention-focused vs. expansion-focused accounts
- Comp model implications for splitting the two motions
- Metrics dashboard fields tracked separately for each motion
The Core Principle
Retention and expansion are opposite postures. Retention is defensive — protect revenue that's at risk. Expansion is offensive — grow revenue that's healthy. Blending them into one "post-sale" job with one set of metrics reliably produces a team that's reactive to churn and passive on expansion, because a rep under quota pressure will always chase the easier, more measurable motion (retention) at the expense of the harder, proactive one (expansion). Split them on purpose.
1. Customer Health-Score Rubric
Score every account 1-5 on each input, weight, and sum to a Health Score (max 100). Use this score to route accounts into the retention motion or the expansion motion below.
| Input | Weight | 1 (at-risk) | 3 (stable) | 5 (healthy) |
|---|---|---|---|---|
| Product usage trend | 30% | Declining usage 2+ consecutive periods | Flat usage | Growing usage/seats/features adopted |
| Executive sponsor engagement | 20% | No response to outreach, sponsor departed | Responsive but passive | Actively engaged, advocates internally |
| Support ticket volume/severity | 15% | Rising volume, unresolved critical tickets | Normal volume, resolved | Low volume or proactively resolved |
| NPS/CSAT (if collected) | 15% | Detractor (0-6) | Passive (7-8) | Promoter (9-10) |
| Renewal timeline proximity + payment history | 10% | Renewal <90 days out, prior late payment | Renewal 90-180 days out, on-time payment | Renewal 180+ days out, on-time/multi-year |
| Whitespace already penetrated | 10% | Single product/seat, no expansion history | Some expansion history | Multi-product, recurring expansion history |
Health Score bands:
- 70-100: Healthy → route to Expansion motion
- 40-69: Stable/Watch → default retention cadence, monitor for movement
- Below 40: At-Risk → route to Retention motion immediately
2. Retention Motion — Risk Triggers & Save Plays
| Trigger | Save play |
|---|---|
| Usage decline 2+ consecutive periods | Trigger a proactive check-in within 5 business days — do not wait for the renewal conversation to surface a usage problem |
| Executive sponsor departs | Immediately map the new stakeholder and re-establish champion relationship within 2 weeks; treat this as a re-onboarding event |
| Critical support ticket unresolved beyond SLA | Escalate cross-functionally (support + CS + product) with a named owner and a committed resolution date communicated to the customer |
| NPS/CSAT drops to detractor | Personal outreach from CS leadership (not just the CSM) within 1 week; document root cause, not just the symptom |
| Renewal inside 90 days with Health Score below 40 | Formal save-play kickoff: executive-to-executive call, documented risk register, and a retention offer only as a last resort — not the first move |
3. Expansion Motion — Growth Triggers & Expansion Plays
| Trigger | Expansion play |
|---|---|
| Usage approaching plan/seat limit | Proactive outreach before the customer hits the ceiling and feels friction — frame as "you're about to outgrow your current plan," not a hard sell |
| New department/team requesting access organically | Fast-track a pilot/expansion proposal for the new team — organic pull is the highest-propensity expansion signal available |
| High Health Score + low current product penetration | Structured whitespace review at the next QBR — map unused modules/features against the customer's stated goals |
| Renewal 180+ days out with strong usage trend | Multi-year or expanded-scope proposal conversation — the further from renewal pressure, the more this reads as partnership, not upsell |
| Customer champion gets promoted or moves to a new team internally | Follow the champion — this is one of the highest-conversion expansion triggers and is routinely missed without a deliberate tracking process |
4. Role Split Model
| Model | Structure | Best when |
|---|---|---|
| Fully split | Dedicated CSM (retention-focused, renewal-owning) + dedicated AM (expansion-focused, growth-quota-carrying) | Larger accounts, complex multi-product portfolio, enough account volume to justify two headcounts per book |
| Hybrid with clear metric split | One person owns the account but is measured and (ideally) compensated on GRR and expansion ARR as two separate numbers, not one blended "net retention" target | Mid-market, smaller teams where headcount doesn't justify a full split |
| Pooled specialist overlay | CSMs own the relationship day-to-day; a specialist expansion team is looped in only when the health-score/trigger tables above indicate a genuine expansion opportunity | Early-stage post-sale motion, limited headcount, want to avoid diluting focus while still capturing obvious expansion signals |
Rule regardless of model: never let one person's single quota number blend retention and expansion — even in the hybrid model, report and (where possible) compensate the two as separate line items, or the easier motion (retention) will always win the rep's attention under pressure.
5. QBR Cadence & Agenda by Motion
Retention-focused QBR (Health Score below 70):
- Usage review against the customer's original stated goals
- Open issues/support escalations — status and resolution owner
- Risk register review — what's changed since last QBR
- Renewal timeline and any commercial concerns surfaced directly
Expansion-focused QBR (Health Score 70+):
- Business outcomes achieved this period (ROI story, quantified)
- Whitespace review — modules/seats/departments not yet using the product
- Roadmap alignment — what's coming that unlocks further value for this account
- Explicit expansion proposal or next-step commitment
6. Comp Model Implications
- If roles are split (CSM/AM), comp should reflect it: CSM comp weighted toward GRR/renewal rate, AM comp weighted toward expansion bookings — mirroring them with the same plan defeats the purpose of splitting the roles
- If hybrid, avoid a single blended "NRR" comp trigger for an individual rep where possible — pay separately on the GRR component and the expansion component so an individual can't hit target purely by protecting the base and never expanding
- Any save-play discounting authority should sit with a manager/leader sign-off, not the individual rep, to prevent margin erosion becoming the default save tactic
7. Metrics Dashboard — Tracked Separately by Motion
| Retention motion metrics | Expansion motion metrics |
|---|---|
| Gross Revenue Retention (GRR) | Net expansion ARR (upsell + cross-sell) |
| Logo churn rate | Expansion Revenue Rate (Expansion ARR ÷ Starting ARR) |
| At-risk account count (Health Score <40) | % of accounts at Health Score 70+ engaged in active expansion motion |
| Save-play win rate (risk accounts successfully retained) | Whitespace penetration rate (products/seats sold vs. available) |
| Time-to-resolution on critical support triggers | Expansion deal cycle length |
Report these as two separate scorecards, even to the board — a single blended NRR number hides whether the business has a retention problem, an expansion problem, or both, and the fix for each is completely different.
How to use it
Score every post-sale account using the Health Score rubric, route accounts into the retention or expansion motion based on the resulting band, and report the two metrics dashboards separately in every internal and board review so a blended NRR number never masks which motion actually needs attention.