Churn Prevention#

You are an expert in SaaS retention and churn prevention. Your goal is to help reduce both voluntary churn (customers choosing to cancel) and involuntary churn (failed payments) through well-designed cancel flows, dynamic save offers, proactive retention, and dunning strategies.

Before Starting#

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Current Churn Situation#

• What's your monthly churn rate? (Voluntary vs. involuntary if known)
• How many active subscribers?
• What's the average MRR per customer?
• Do you have a cancel flow today, or does cancel happen instantly?

2. Billing & Platform#

• What billing provider? (Stripe, Chargebee, Paddle, Recurly, Braintree)
• Monthly, annual, or both billing intervals?
• Do you support plan pausing or downgrades?
• Any existing retention tooling? (Churnkey, ProsperStack, Raaft)

3. Product & Usage Data#

• Do you track feature usage per user?
• Can you identify engagement drop-offs?
• Do you have cancellation reason data from past churns?
• What's your activation metric? (What do retained users do that churned users don't?)

4. Constraints#

• B2B or B2C? (Affects flow design)
• Self-serve cancellation required? (Some regulations mandate easy cancel)
• Brand tone for offboarding? (Empathetic, direct, playful)

---

How This Skill Works#

Churn has two types requiring different strategies:

TypeCauseSolutionVoluntaryCustomer chooses to cancelCancel flows, save offers, exit surveysInvoluntaryPayment failsDunning emails, smart retries, card updaters

Voluntary churn is typically 50-70% of total churn. Involuntary churn is 30-50% but is often easier to fix.

This skill supports three modes:

1. Build a cancel flow — Design from scratch with survey, save offers, and confirmation
2. Optimize an existing flow — Analyze cancel data and improve save rates
3. Set up dunning — Failed payment recovery with retries and email sequences

---

Cancel Flow Design#

The Cancel Flow Structure#

Every cancel flow follows this sequence:

text

Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel

Step 1: Trigger Customer clicks "Cancel subscription" in account settings.

Step 2: Exit Survey Ask why they're cancelling. This determines which save offer to show.

Step 3: Dynamic Save Offer Present a targeted offer based on their reason (discount, pause, downgrade, etc.)

Step 4: Confirmation If they still want to cancel, confirm clearly with end-of-billing-period messaging.

Step 5: Post-Cancel Set expectations, offer easy reactivation path, trigger win-back sequence.

Exit Survey Design#

The exit survey is the foundation. Good reason categories:

ReasonWhat It Tells YouToo expensivePrice sensitivity, may respond to discount or downgradeNot using it enoughLow engagement, may respond to pause or onboarding helpMissing a featureProduct gap, show roadmap or workaroundSwitching to competitorCompetitive pressure, understand what they offerTechnical issues / bugsProduct quality, escalate to supportTemporary / seasonal needUsage pattern, offer pauseBusiness closed / changedUnavoidable, learn and let go gracefullyOtherCatch-all, include free text field

Survey best practices:

• 1 question, single-select with optional free text
• 5-8 reason options max (avoid decision fatigue)
• Put most common reasons first (review data quarterly)
• Don't make it feel like a guilt trip
• "Help us improve" framing works better than "Why are you leaving?"

Dynamic Save Offers#

The key insight: match the offer to the reason. A discount won't save someone who isn't using the product. A feature roadmap won't save someone who can't afford it.

Offer-to-reason mapping:

Cancel ReasonPrimary OfferFallback OfferToo expensiveDiscount (20-30% for 2-3 months)Downgrade to lower planNot using it enoughPause (1-3 months)Free onboarding sessionMissing featureRoadmap preview + timelineWorkaround guideSwitching to competitorCompetitive comparison + discountFeedback sessionTechnical issuesEscalate to support immediatelyCredit + priority fixTemporary / seasonalPause subscriptionDowngrade temporarilyBusiness closedSkip offer (respect the situation)—

Save Offer Types#

Discount

• 20-30% off for 2-3 months is the sweet spot
• Avoid 50%+ discounts (trains customers to cancel for deals)
• Time-limit the offer ("This offer expires when you leave this page")
• Show the dollar amount saved, not just the percentage

Pause subscription

• 1-3 month pause maximum (longer pauses rarely reactivate)
• 60-80% of pausers eventually return to active
• Auto-reactivation with advance notice email
• Keep their data and settings intact

Plan downgrade

• Offer a lower tier instead of full cancellation
• Show what they keep vs. what they lose
• Position as "right-size your plan" not "downgrade"
• Easy path back up when ready

Feature unlock / extension

• Unlock a premium feature they haven't tried
• Extend trial of a higher tier
• Works best for "not getting enough value" reasons

Personal outreach

• For high-value accounts (top 10-20% by MRR)
• Route to customer success for a call
• Personal email from founder for smaller companies

Cancel Flow UI Patterns#

text

┌─────────────────────────────────────┐
│  We're sorry to see you go          │
│                                     │
│  What's the main reason you're      │
│  cancelling?                        │
│                                     │
│  ○ Too expensive                    │
│  ○ Not using it enough              │
│  ○ Missing a feature I need         │
│  ○ Switching to another tool        │
│  ○ Technical issues                 │
│  ○ Temporary / don't need right now │
│  ○ Other: [____________]            │
│                                     │
│  [Continue]                         │
│  [Never mind, keep my subscription] │
└─────────────────────────────────────┘
         ↓ (selects "Too expensive")
┌─────────────────────────────────────┐
│  What if we could help?             │
│                                     │
│  We'd love to keep you. Here's a    │
│  special offer:                     │
│                                     │
│  ┌───────────────────────────────┐  │
│  │  25% off for the next 3 months│  │
│  │  Save $XX/month               │  │
│  │                               │  │
│  │  [Accept Offer]               │  │
│  └───────────────────────────────┘  │
│                                     │
│  Or switch to [Basic Plan] at       │
│  $X/month →                         │
│                                     │
│  [No thanks, continue cancelling]   │
└─────────────────────────────────────┘

UI principles:

• Keep the "continue cancelling" option visible (no dark patterns)
• One primary offer + one fallback, not a wall of options
• Show specific dollar savings, not abstract percentages
• Use the customer's name and account data when possible
• Mobile-friendly (many cancellations happen on mobile)

For detailed cancel flow patterns by industry and billing provider, see references/cancel-flow-patterns.md.

---

Churn Prediction & Proactive Retention#

The best save happens before the customer ever clicks "Cancel."

Risk Signals#

Track these leading indicators of churn:

SignalRisk LevelTimeframeLogin frequency drops 50%+High2-4 weeks before cancelKey feature usage stopsHigh1-3 weeks before cancelSupport tickets spike then stopHigh1-2 weeks before cancelEmail open rates declineMedium2-6 weeks before cancelBilling page visits increaseHighDays before cancelTeam seats removedHigh1-2 weeks before cancelData export initiatedCriticalDays before cancelNPS score drops below 6Medium1-3 months before cancel

Health Score Model#

Build a simple health score (0-100) from weighted signals:

text

Health Score = (
  Login frequency score × 0.30 +
  Feature usage score   × 0.25 +
  Support sentiment     × 0.15 +
  Billing health        × 0.15 +
  Engagement score      × 0.15
)

ScoreStatusAction80-100HealthyUpsell opportunities60-79Needs attentionProactive check-in40-59At riskIntervention campaign0-39CriticalPersonal outreach

Proactive Interventions#

Before they think about cancelling:

TriggerInterventionUsage drop >50% for 2 weeks"We noticed you haven't used [feature]. Need help?" emailApproaching plan limitUpgrade nudge (not a wall — paywall-upgrade-cro handles this)No login for 14 daysRe-engagement email with recent product updatesNPS detractor (0-6)Personal follow-up within 24 hoursSupport ticket unresolved >48hEscalation + proactive status updateAnnual renewal in 30 daysValue recap email + renewal confirmation

---

Involuntary Churn: Payment Recovery#

Failed payments cause 30-50% of all churn but are the most recoverable.

The Dunning Stack#

text

Pre-dunning → Smart retry → Dunning emails → Grace period → Hard cancel

Pre-Dunning (Prevent Failures)#

• Card expiry alerts: Email 30, 15, and 7 days before card expires
• Backup payment method: Prompt for a second payment method at signup
• Card updater services: Visa/Mastercard auto-update programs (reduces hard declines 30-50%)
• Pre-billing notification: Email 3-5 days before charge for annual plans

Smart Retry Logic#

Not all failures are the same. Retry strategy by decline type:

Decline TypeExamplesRetry StrategySoft decline (temporary)Insufficient funds, processor timeoutRetry 3-5 times over 7-10 daysHard decline (permanent)Card stolen, account closedDon't retry — ask for new cardAuthentication required3D Secure, SCASend customer to update payment

Retry timing best practices:

• Retry 1: 24 hours after failure
• Retry 2: 3 days after failure
• Retry 3: 5 days after failure
• Retry 4: 7 days after failure (with dunning email escalation)
• After 4 retries: Hard cancel with reactivation path

Smart retry tip: Retry on the day of the month the payment originally succeeded (if Day 1 worked before, retry on Day 1). Stripe Smart Retries handles this automatically.

Dunning Email Sequence#

EmailTimingToneContent1Day 0 (failure)Friendly alert"Your payment didn't go through. Update your card."2Day 3Helpful reminder"Quick reminder — update your payment to keep access."3Day 7Urgency"Your account will be paused in 3 days. Update now."4Day 10Final warning"Last chance to keep your account active."

Dunning email best practices:

• Direct link to payment update page (no login required if possible)
• Show what they'll lose (their data, their team's access)
• Don't blame ("your payment failed" not "you failed to pay")
• Include support contact for help
• Plain text performs better than designed emails for dunning

Recovery Benchmarks#

MetricPoorAverageGoodSoft decline recovery<40%50-60%70%+Hard decline recovery<10%20-30%40%+Overall payment recovery<30%40-50%60%+Pre-dunning preventionNone10-15%20-30%

For the complete dunning playbook with provider-specific setup, see references/dunning-playbook.md.

---

Metrics & Measurement#

Key Churn Metrics#

MetricFormulaTargetMonthly churn rateChurned customers / Start-of-month customers<5% B2C, <2% B2BRevenue churn (net)(Lost MRR - Expansion MRR) / Start MRRNegative (net expansion)Cancel flow save rateSaved / Total cancel sessions25-35%Offer acceptance rateAccepted offers / Shown offers15-25%Pause reactivation rateReactivated / Total paused60-80%Dunning recovery rateRecovered / Total failed payments50-60%Time to cancelDays from first churn signal to cancelTrack trend

Cohort Analysis#

Segment churn by:

• Acquisition channel — Which channels bring stickier customers?
• Plan type — Which plans churn most?
• Tenure — When do most cancellations happen? (30, 60, 90 days?)
• Cancel reason — Which reasons are growing?
• Save offer type — Which offers work best for which segments?

Cancel Flow A/B Tests#

Test one variable at a time:

TestHypothesisMetricDiscount % (20% vs 30%)Higher discount saves moreSave rate, LTV impactPause duration (1 vs 3 months)Longer pause increases return rateReactivation rateSurvey placement (before vs after offer)Survey-first personalizes offersSave rateOffer presentation (modal vs full page)Full page gets more attentionSave rateCopy tone (empathetic vs direct)Empathetic reduces frictionSave rate

How to run cancel flow experiments: Use the ab-test-setup skill to design statistically rigorous tests. PostHog is a good fit for cancel flow experiments — its feature flags can split users into different flows server-side, and its funnel analytics track each step of the cancel flow (survey → offer → accept/decline → confirm). See the PostHog integration guide for setup.

---

Common Mistakes#

• No cancel flow at all — Instant cancel leaves money on the table. Even a simple survey + one offer saves 10-15%
• Making cancellation hard to find — Hidden cancel buttons breed resentment and bad reviews. Many jurisdictions require easy cancellation (FTC Click-to-Cancel rule)
• Same offer for every reason — A blanket discount doesn't address "missing feature" or "not using it"
• Discounts too deep — 50%+ discounts train customers to cancel-and-return for deals
• Ignoring involuntary churn — Often 30-50% of total churn and the easiest to fix
• No dunning emails — Letting payment failures silently cancel accounts
• Guilt-trip copy — "Are you sure you want to abandon us?" damages brand trust
• Not tracking save offer LTV — A "saved" customer who churns 30 days later wasn't really saved
• Pausing too long — Pauses beyond 3 months rarely reactivate. Set limits.
• No post-cancel path — Make reactivation easy and trigger win-back emails, because some churned users will want to come back

---

Tool Integrations#

For implementation, see the tools registry.

Retention Platforms#

ToolBest ForKey FeatureChurnkeyFull cancel flow + dunningAI-powered adaptive offers, 34% avg save rateProsperStackCancel flows with analyticsAdvanced rules engine, Stripe/Chargebee integrationRaaftSimple cancel flow builderEasy setup, good for early-stageChargebee RetentionChargebee customersNative integration, was Brightback

Billing Providers (Dunning)#

ProviderSmart RetriesDunning EmailsCard UpdaterStripeBuilt-in (Smart Retries)Built-inAutomaticChargebeeBuilt-inBuilt-inVia gatewayPaddleBuilt-inBuilt-inManagedRecurlyBuilt-inBuilt-inBuilt-inBraintreeManual configManualVia gateway

Related CLI Tools#

ToolUse ForstripeSubscription management, dunning config, payment retriescustomer-ioDunning email sequences, retention campaignsposthogCancel flow A/B tests via feature flags, funnel analyticsmixpanel / ga4Usage tracking, churn signal analysissegmentEvent routing for health scoring

---

Related Skills#

• email-sequence: For win-back email sequences after cancellation
• paywall-upgrade-cro: For in-app upgrade moments and trial expiration
• pricing-strategy: For plan structure and annual discount strategy
• onboarding-cro: For activation to prevent early churn
• analytics-tracking: For setting up churn signal events
• ab-test-setup: For testing cancel flow variations with statistical rigor