Churn Prevention

Churn Prevention

Production-grade SaaS churn reduction framework covering cancel flow architecture, dynamic save offer mapping, exit survey design, dunning sequence engineering, payment recovery optimization, win-back campaigns, and churn impact modeling. Addresses both voluntary churn (customers who decide to leave) and involuntary churn (customers who leave due to payment failure).

Table of Contents

• Initial Assessment
• Churn Taxonomy
• Cancel Flow Architecture
• Exit Survey Design
• Dynamic Save Offer System
• Dunning Sequence Engineering
• Win-Back Campaign Framework
• Churn Health Scoring
• Metrics and Benchmarks
• Churn Impact Calculator
• Output Artifacts
• Related Skills

Clarify First

Before designing the churn-prevention system, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• Voluntary vs involuntary churn split — which dominates (determines whether to build cancel flow/save offers or dunning/payment recovery)
• Existing cancel flow vs instant/support cancellation — sets build-from-scratch vs optimize mode
• Current MRR + ARPU + billing cycle — sizes the dollar impact and the save-offer budget
• Payment processor — Stripe / Braintree / Paddle / Recurly (determines card-updater and dunning retry implementation)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the deliverable.

Initial Assessment

Required Context

Churn Taxonomy

Voluntary Churn (Customer Decides to Leave)

Involuntary Churn (Payment Fails)

Cancel Flow Architecture

The 5-Stage Cancel Flow

[Cancel Button] → [Exit Survey] → [Dynamic Save Offer] → [Confirmation] → [Post-Cancel]

Stage 1: Cancel Trigger

• Cancel option is findable (Settings > Account > Cancel). Do not hide it.
• Clicking "Cancel" starts the flow -- it does not immediately cancel the account
• Works on both desktop and mobile

Stage 2: Exit Survey (Required, 1 Question)

Question: "What is the main reason you are cancelling?"

Present as radio buttons (not a dropdown). Maximum 8 options:

Rules:

• Survey is required before showing the save offer (the answer determines the offer)
• One question only. No multi-page surveys.
• Optional free-text field for "Other" and as a supplement to any selection
• Track response distribution monthly to identify systemic issues

Stage 3: Dynamic Save Offer

Map each exit reason to exactly one save offer:

Offer presentation rules:

• One clear offer per screen (not multiple choices)
• Quantify the value: "Save $120 over the next 3 months" not "Get a discount"
• CTA: "Accept Offer" vs "Continue Cancelling" (both clearly labeled)
• No countdown timers, no fake urgency
• No guilt-trip copy

Stage 4: Confirmation

If they decline the save offer or there is no offer to make:

┌────────────────────────────────────────┐
│  We're sorry to see you go             │
│                                        │
│  What happens when you cancel:         │
│  - Your data is saved for 90 days     │
│  - Access continues until [date]      │
│  - You can reactivate anytime         │
│                                        │
│  [Yes, Cancel My Account]             │
│  [Wait, I Changed My Mind]            │
│                                        │
│  No pre-checked boxes.                │
│  No confusing language.               │
└────────────────────────────────────────┘

Stage 5: Post-Cancel

Exit Survey Design

Data Analysis Framework

Track exit survey responses monthly and calculate:

Competitive Intelligence from Exit Surveys

When users select "Switching to a different product":

• Ask a follow-up: "Which product are you switching to?" (optional, free text or dropdown)
• Track the top 3 competitors winning your churners
• Feed this data into competitive-teardown skill for quarterly analysis

Dynamic Save Offer System

Offer Economics

Save Offer Decision Tree

User selects exit reason →
├── PRICE →
│   ├── Customer ARPU > median? → Offer 30% discount
│   └── Customer ARPU < median? → Offer downgrade to cheaper plan
├── LOW_USAGE →
│   ├── Last login > 30 days? → Offer pause
│   └── Last login < 30 days? → Offer usage tips + discount
├── MISSING_FEATURE →
│   ├── Feature on roadmap? → Share roadmap + workaround
│   └── Feature not planned? → Offer discount or acknowledge gap
├── COMPETITOR →
│   ├── Known competitor? → Show comparison + retention offer
│   └── Unknown competitor? → General retention offer
├── PROJECT_END →
│   └── Always → Offer pause
├── COMPLEXITY →
│   ├── Enterprise/high-value? → Offer dedicated onboarding session
│   └── SMB/low-value? → Offer guided tutorial link
└── TESTING →
    └── Always → No offer, let go gracefully

Dunning Sequence Engineering

Failed payments cause 20-40% of total churn. Most of it is recoverable with proper dunning.

Smart Retry Schedule

Do not retry immediately after failure. Cards often recover within 3-7 days.

Card Updater Services

Enable automatic card updating to prevent expired card churn:

Dunning Email Sequence

Email rules:

• Every email links directly to the payment update page (not the dashboard)
• No guilt, no shame. Card failures happen.
• Subject lines are specific (include product name)
• Include the amount owed and the card last 4 digits
• Offer a support channel for customers who need help

Win-Back Campaign Framework

Win-Back Timing

Win-Back Email Sequence

Day 7 Email:

• Subject: "Your [Product] account is waiting for you"
• Body: What they left behind (data, projects, team). One CTA: reactivate.
• No discount. Just value reminder.

Day 30 Email:

• Subject: "Here's what's new in [Product]"
• Body: 2-3 specific improvements since they left. One CTA: reactivate.
• Small incentive: "Come back with 1 month free"

Day 60 Email:

• Subject: "We'd love to have you back -- [offer]"
• Body: Strongest offer (50% off 3 months or extended free period). Clear deadline.
• Final significant outreach attempt.

Churn Health Scoring

Leading Indicators of Churn

Risk Score Calculation

Risk Score = Sum of (Signal Weight x Signal Present)

0-20: Low risk (monitor)
21-40: Moderate risk (proactive outreach)
41-60: High risk (intervention required)
61+: Critical risk (executive escalation)

Metrics and Benchmarks

Key Metrics

Red Flags

Churn Impact Calculator

Quick Estimate

Monthly MRR at risk = Total MRR x Monthly churn rate
Annual MRR saved by 1% churn reduction = Total MRR x 0.01 x 12
Annual MRR saved by 20% save rate = (Monthly MRR at risk x 0.20) x 12

Example:
  MRR: $500,000
  Monthly churn: 4% = $20,000/month lost
  Reduce to 3% = $5,000/month saved = $60,000/year
  Add 20% save rate on remaining = $3,000/month saved = $36,000/year
  Total annual impact: $96,000

Output Artifacts

Related Skills

• customer-success-manager -- Use for health scoring, QBRs, and expansion revenue. Not for cancel flow or dunning design.
• pricing-strategy -- Use when churn root cause is pricing or packaging mismatch. Not for save offer design.
• onboarding-cro -- Use when churn traces back to poor activation. If users never experienced value, fix onboarding first.
• referral-program -- Use for acquisition. Churn prevention handles the other end of the funnel.

Tool Reference

1. churn_impact_calculator.py

Purpose: Calculate the revenue impact of churn reduction at various improvement levels.

python scripts/churn_impact_calculator.py --mrr 500000 --churn-rate 4.0 --save-rate 20
python scripts/churn_impact_calculator.py --mrr 500000 --churn-rate 4.0 --save-rate 20 --json

2. dunning_sequence_analyzer.py

Purpose: Analyze dunning email sequence effectiveness and recommend retry timing optimizations.

python scripts/dunning_sequence_analyzer.py dunning_data.json
python scripts/dunning_sequence_analyzer.py dunning_data.json --json

Input JSON format:

{
  "failed_payments": [
    {
      "payment_id": "PAY-001",
      "amount": 99.00,
      "failure_reason": "expired_card",
      "retry_attempts": [
        {"day": 0, "recovered": false},
        {"day": 3, "recovered": false},
        {"day": 7, "recovered": true}
      ]
    }
  ]
}

3. exit_survey_analyzer.py

Purpose: Analyze exit survey responses to identify churn patterns, save offer effectiveness, and systemic issues.

python scripts/exit_survey_analyzer.py survey_data.json
python scripts/exit_survey_analyzer.py survey_data.json --json

Troubleshooting

Success Criteria

• Monthly voluntary churn rate below 2.5% (below 1.5% is excellent)
• Monthly involuntary churn rate below 1.0% (below 0.5% is excellent)
• Cancel flow save rate of 15-25% (above 20% is excellent)
• Payment recovery rate of 30%+ on failed payments
• Exit survey completion rate above 80%
• Win-back reactivation rate of 5-10% within 90 days post-cancel
• Save offer acceptance rate above 20% with retained customers staying 6+ months post-save

Scope & Limitations

• In scope: Cancel flow design, exit survey architecture, save offer mapping, dunning sequences, payment recovery, win-back campaigns, churn impact modeling
• Out of scope: Product-market fit analysis, pricing restructuring, ICP redefinition, customer acquisition
• Data dependency: Scripts analyze point-in-time snapshots from JSON input; no real-time CRM integration
• Not predictive ML: All scoring is deterministic and algorithmic -- no machine learning models
• Legal note: Cancel flows must comply with FTC guidelines (US) and consumer protection laws (EU) -- do not make cancellation unreasonably difficult
• Revenue estimates: Impact calculations are projections based on input assumptions, not guarantees

Integration Points

• customer-success-manager -- Feed health scores into churn risk assessment; use churn data to calibrate health score thresholds
• pricing-strategy -- When exit survey data shows PRICE as the dominant reason (>30%), escalate to pricing-strategy for structural pricing review
• onboarding-cro -- When exit survey data shows LOW_USAGE or COMPLEXITY as top reasons, the root cause is often poor activation; fix onboarding first
• revenue-operations -- Pipeline and forecast models should account for churn reduction impact on net revenue retention (NRR)
• referral-program -- Retained customers from save offers are candidates for referral program enrollment after 90 days of continued usage