retention-playbook

Retention Playbook

Detect churn risks early, score customer engagement health, and deploy proven retention and win-back strategies for SaaS products.

First Run

When a user runs /retention-playbook diagnose, ALWAYS display this input summary before asking for any data:

""" 📊 Retention Playbook

What I'll ask you:

Product context: 1. SaaS vertical → e.g. "project management" 2. Pricing model → e.g. "per-seat" 3. Avg contract length → e.g. "monthly"

Churn metrics: 4. Monthly logo churn (%) → e.g. 5 5. Monthly revenue churn (%) → e.g. 3 6. Net Revenue Retention (%) → e.g. 102

Current tracking: 7. Which churn signals do you track? → e.g. "login frequency, support tickets"

Type "skip" for any you don't have. Type "demo" to see a sample diagnosis first.

What you'll get: → Churn categorization (preventable vs structural vs competitive) → Top 3 churn drivers identified → Prioritized retention action plan with timeline → Saved to RETENTION-DIAGNOSIS-REPORT.md

Ready? What's your SaaS vertical? """

Demo Mode

If the user types "demo", use this data to generate a full sample report:

{
  "vertical": "project management SaaS",
  "pricing_model": "per-seat",
  "avg_contract": "monthly",
  "monthly_logo_churn": 6.5,
  "monthly_revenue_churn": 4.2,
  "nrr": 97,
  "signals_tracked": ["login frequency", "support tickets"]
}

Save the demo report as RETENTION-DIAGNOSIS-REPORT-DEMO.md. After showing the summary, ask: "Want to run this with your own data now?"

Skip Handling

If the user types "skip" for any metric:

• Proceed with available data
• Provide general retention recommendations when specific data is missing
• Never block the report because one metric is unknown

Commands

/retention-playbook diagnose

Interactive churn diagnosis framework. Walk the user through identifying why customers are leaving and build a retention action plan.