Churn Prediction
Overview
Churn prediction shifts retention from reactive ("they cancelled — now what?")
to proactive ("this account shows 3 risk signals — intervene now"). Early
intervention reduces churn by 20-40% compared to waiting for cancellation.
This skill covers modeling leading indicators, building risk scores, and
designing intervention playbooks.
Authoritative Foundations
- Gainsight Churn Prediction Model — Named methodology governing recommendations in this skill's process.
- Retention Science Framework — Named methodology governing recommendations in this skill's process.
- Reforge — Lifecycle Marketing — Startup operating cadence — default alive, talk to users, launch fast.
When to Use
- "Build a churn prediction model"
- "Predict which accounts will churn"
- "Churn risk scoring"
- "Early warning system"
- "Retention analytics"
Lifecycle Stage
Retention (stage 6). Canonical index → references/gtm-lifecycle-stages.md.
Metrics → references/lifecycle-metrics-by-stage.md (Retention).
Scorecard → skills/analytics/gtm-metrics/templates/stage-health-scorecard.md (Retention panel).
Core Principle
The best churn signal is not "they stopped paying" — it's the behavior
pattern they exhibit 60-90 days before they stop paying. Your job is to
find those leading indicators and act on them while there's still time.
Step-by-Step Process
Phase 1: Identify Leading Indicators
Analyze churned customers looking back 90 days before cancellation:
Product Usage Signals:
- Login frequency declining (weekly → bi-weekly → monthly)
- Key feature usage dropping (>30% decline month-over-month)
- Time since last key action > 14 days
- Multiple users stopped logging in (if multi-seat)
- Failed imports/integrations (3+ failures = high frustration)
Engagement Signals:
- Stopped opening emails (unengaged for 30+ days)
- Support ticket sentiment turning negative
- No response to CSM outreach (2+ attempts)
- Missed QBR or success review meeting
- Stopped attending webinars/events they previously attended
Business Signals:
- Champion left the company (detected via LinkedIn)
- Company had layoffs or restructuring
- Budget cut or freeze in their department
- New competitor evaluation (detected via intent data)
- Contract renewal window approaching with no engagement
Phase 2: Build Risk Scoring Model
Weight each signal on a 0-100 risk score:
Critical (40 points max):
- Champion departure: 40 points
- Key feature usage down >50%: 35 points
- No login in 30+ days: 30 points
High (25 points max):
- Support ticket spike (3+ in 7 days): 20 points
- No response to CSM in 14+ days: 15 points
- Missed renewal meeting: 10 points
Medium (20 points max):
- Email engagement dropped to 0: 10 points
- Usage declining 20-30% MoM: 10 points
- New competitor intent signal: 5 points (cumulative)
Low (15 points max):
- Weather signal: minor usage dip, one missed meeting
Risk Tiers:
- Red (70+): Immediate executive intervention required. Cancel risk in <30 days.
- Yellow (40-69): CSM intervention this week. Cancel risk in 30-60 days.
- Green (<40): Standard monitoring.
Phase 3: Intervention Playbooks
Red Account Playbook:
- Day 0: CSM calls within 4 hours. "I noticed [specific signal]. Everything ok?"
- Day 0: Executive sponsor reaches out. "Your success is critical to us — let's
solve whatever is blocking you."
- Day 1: Root cause analysis. Is it product, support, business, or competition?
- Day 3: Action plan presented to customer. Specific timeline. Named owner.
- Day 7: Check-in. "Is the plan working? What else do you need?"
- Day 14: Success review. Have the signals reversed? If not, escalate to VP CS.
Yellow Account Playbook:
- Day 0: CSM email: "Noticed [signal] — quick check-in?"
- Day 2: If no reply, call.
- Day 5: Value reinforcement: usage stats, ROI summary, new features they should try
- Day 10: If signals persist, escalate to Red playbook
Phase 4: Automated Monitoring
- Daily scan: Run risk model on all accounts every 24 hours
- Alert routing: Red → CSM + VP CS + Account Executive. Yellow → CSM only.
- Slack/email alerts: "Account ABC moved to RED risk — champion departed,
usage down 60%."
- Dashboard: Real-time risk heatmap of all accounts. Sort by risk score.
- Trend tracking: Is risk score improving or worsening week-over-week?
Phase 5: Feedback Loop
- Churn post-mortem: For every churned account, review: what signals were
present 90 days before churn? Why weren't they acted on? What signal did we miss?
- Model refinement: Every quarter, update signal weights based on which
signals actually predicted churn vs false positives
- False positive analysis: Accounts flagged red that didn't churn — what
made them different? Refine model.
- Precision vs recall balance: High precision = fewer false alarms but
may miss churn. High recall = catch more churn but more false alarms.
Tune based on CSM capacity.
Output Format
Churn prediction model with: leading indicator catalog, risk scoring algorithm,
intervention playbooks, automated monitoring setup, and feedback loop.
Quality Check
Before delivering, verify:
Common Pitfalls
- Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
- Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
- Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
Execution Artifacts
references/framework-notes.md — Named frameworks and reference tables
templates/output-template.md — Deliverable shell for agent output
scripts/check-output.py — Lightweight deliverable validator
Canonical lifecycle (repo root): references/gtm-lifecycle-stages.md (Retention) · references/lifecycle-metrics-by-stage.md · skills/analytics/gtm-metrics/templates/stage-health-scorecard.md
Related Skills
- churn-prevention, cs-playbooks, onboarding-sequences, lifecycle-drips, expansion-selling
1---2name: churn-prediction3description: Build churn prediction models — leading indicators, risk scoring, early warning systems, intervention playbooks. Triggers on: "churn prediction", "predict churn", "churn model", "early warning", "risk scoring".4license: MIT5---67# Churn Prediction89## Overview10Churn prediction shifts retention from reactive ("they cancelled — now what?")11to proactive ("this account shows 3 risk signals — intervene now"). Early12intervention reduces churn by 20-40% compared to waiting for cancellation.13This skill covers modeling leading indicators, building risk scores, and14designing intervention playbooks.1516## Authoritative Foundations1718- **Gainsight Churn Prediction Model** — Named methodology governing recommendations in this skill's process.19- **Retention Science Framework** — Named methodology governing recommendations in this skill's process.20- **Reforge — Lifecycle Marketing** — Startup operating cadence — default alive, talk to users, launch fast.2122## When to Use23- "Build a churn prediction model"24- "Predict which accounts will churn"25- "Churn risk scoring"26- "Early warning system"27- "Retention analytics"2829## Lifecycle Stage3031**Retention** (stage 6). Canonical index → `references/gtm-lifecycle-stages.md`. 32Metrics → `references/lifecycle-metrics-by-stage.md` (Retention). 33Scorecard → `skills/analytics/gtm-metrics/templates/stage-health-scorecard.md` (Retention panel).3435## Core Principle36> The best churn signal is not "they stopped paying" — it's the behavior37> pattern they exhibit 60-90 days before they stop paying. Your job is to38> find those leading indicators and act on them while there's still time.3940## Step-by-Step Process4142### Phase 1: Identify Leading Indicators43Analyze churned customers looking back 90 days before cancellation:4445**Product Usage Signals:**46- Login frequency declining (weekly → bi-weekly → monthly)47- Key feature usage dropping (>30% decline month-over-month)48- Time since last key action > 14 days49- Multiple users stopped logging in (if multi-seat)50- Failed imports/integrations (3+ failures = high frustration)5152**Engagement Signals:**53- Stopped opening emails (unengaged for 30+ days)54- Support ticket sentiment turning negative55- No response to CSM outreach (2+ attempts)56- Missed QBR or success review meeting57- Stopped attending webinars/events they previously attended5859**Business Signals:**60- Champion left the company (detected via LinkedIn)61- Company had layoffs or restructuring62- Budget cut or freeze in their department63- New competitor evaluation (detected via intent data)64- Contract renewal window approaching with no engagement6566### Phase 2: Build Risk Scoring Model67Weight each signal on a 0-100 risk score:6869**Critical (40 points max):**70- Champion departure: 40 points71- Key feature usage down >50%: 35 points72- No login in 30+ days: 30 points7374**High (25 points max):**75- Support ticket spike (3+ in 7 days): 20 points76- No response to CSM in 14+ days: 15 points77- Missed renewal meeting: 10 points7879**Medium (20 points max):**80- Email engagement dropped to 0: 10 points81- Usage declining 20-30% MoM: 10 points82- New competitor intent signal: 5 points (cumulative)8384**Low (15 points max):**85- Weather signal: minor usage dip, one missed meeting8687**Risk Tiers:**88- Red (70+): Immediate executive intervention required. Cancel risk in <30 days.89- Yellow (40-69): CSM intervention this week. Cancel risk in 30-60 days.90- Green (<40): Standard monitoring.9192### Phase 3: Intervention Playbooks9394**Red Account Playbook:**95- Day 0: CSM calls within 4 hours. "I noticed [specific signal]. Everything ok?"96- Day 0: Executive sponsor reaches out. "Your success is critical to us — let's97 solve whatever is blocking you."98- Day 1: Root cause analysis. Is it product, support, business, or competition?99- Day 3: Action plan presented to customer. Specific timeline. Named owner.100- Day 7: Check-in. "Is the plan working? What else do you need?"101- Day 14: Success review. Have the signals reversed? If not, escalate to VP CS.102103**Yellow Account Playbook:**104- Day 0: CSM email: "Noticed [signal] — quick check-in?"105- Day 2: If no reply, call.106- Day 5: Value reinforcement: usage stats, ROI summary, new features they should try107- Day 10: If signals persist, escalate to Red playbook108109### Phase 4: Automated Monitoring110- **Daily scan:** Run risk model on all accounts every 24 hours111- **Alert routing:** Red → CSM + VP CS + Account Executive. Yellow → CSM only.112- **Slack/email alerts:** "Account ABC moved to RED risk — champion departed,113 usage down 60%."114- **Dashboard:** Real-time risk heatmap of all accounts. Sort by risk score.115- **Trend tracking:** Is risk score improving or worsening week-over-week?116117### Phase 5: Feedback Loop118- **Churn post-mortem:** For every churned account, review: what signals were119 present 90 days before churn? Why weren't they acted on? What signal did we miss?120- **Model refinement:** Every quarter, update signal weights based on which121 signals actually predicted churn vs false positives122- **False positive analysis:** Accounts flagged red that didn't churn — what123 made them different? Refine model.124- **Precision vs recall balance:** High precision = fewer false alarms but125 may miss churn. High recall = catch more churn but more false alarms.126 Tune based on CSM capacity.127128## Output Format129Churn prediction model with: leading indicator catalog, risk scoring algorithm,130intervention playbooks, automated monitoring setup, and feedback loop.131132133134## Quality Check135136Before delivering, verify:137- [ ] All required sections are complete138- [ ] Output matches the user's stated need139- [ ] Named frameworks are cited for key recommendations140- [ ] No vague claims — every recommendation has a specific action141- [ ] Deliverable is ready for operational use, not just conceptual142143## Common Pitfalls1441451. **Skipping research.** Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.1462. **Generic output.** "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.1473. **Missing framework citations.** Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.148149## Execution Artifacts150151- `references/framework-notes.md` — Named frameworks and reference tables152- `templates/output-template.md` — Deliverable shell for agent output153- `scripts/check-output.py` — Lightweight deliverable validator154**Canonical lifecycle (repo root):** `references/gtm-lifecycle-stages.md` (Retention) · `references/lifecycle-metrics-by-stage.md` · `skills/analytics/gtm-metrics/templates/stage-health-scorecard.md`155156## Related Skills157- churn-prevention, cs-playbooks, onboarding-sequences, lifecycle-drips, expansion-selling