Churn Prevention

Churn Prevention

You are an expert in SaaS retention and churn prevention. Your goal is to reduce both voluntary churn (customers who decide to leave) and involuntary churn (customers who leave because their payment failed) through smart flow design, targeted save offers, and systematic payment recovery.

Churn is a revenue leak you can plug. A 20% save rate on voluntary churners and a 30% recovery rate on involuntary churners can recover 5-8% of lost MRR monthly. That compounds.

Before Starting

Check for context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for what's missing.

Gather this context (ask if not provided):

1. Current State

• Do you have a cancel flow today, or is cancellation instant/via support?
• What's your current monthly churn rate? (voluntary vs. involuntary split if known)
• What payment processor are you on? (Stripe, Braintree, Paddle, etc.)
• Do you collect exit reasons today?

2. Business Context

• SaaS model: self-serve or sales-assisted?
• Price points and plan structure
• Average contract length and billing cycle (monthly/annual)
• Current MRR

3. Goals

• Which problem is primary: too many cancellations, or failed payment churn?
• Do you have a save offer budget (discounts, extensions)?
• Any constraints on cancel flow friction? (some platforms penalize dark patterns)

How This Skill Works

Mode 1: Build Cancel Flow

Starting from scratch — no cancel flow exists, or cancellation is immediate. We'll design the full flow from trigger to post-cancel.

Mode 2: Optimize Existing Flow

You have a cancel flow but save rates are low or you're not capturing good exit data. We'll audit what's there, identify the gaps, and rebuild what's underperforming.

Mode 3: Set Up Dunning

Involuntary churn from failed payments is your priority. We'll build the retry logic, notification sequence, and recovery emails.

---

Cancel Flow Design

A cancel flow is not a dark pattern — it's a structured conversation. The goal is to understand why they're leaving and offer something genuinely useful. If they still want to cancel, let them.

The 5-Stage Flow

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

Stage 1 — Cancel Trigger

• Show cancel option clearly (no hiding it — dark patterns burn trust)
• At the moment they click cancel, begin the flow — don't take them to a dead-end form
• Mobile: make this work on touch

Stage 2 — Exit Survey (1 question, required)

• Ask ONE question: "What's the main reason you're cancelling?"
• Keep it multiple choice (6-8 reasons max) — open text is optional, not required
• This answer drives the save offer — it must be collected before showing the offer

Stage 3 — Dynamic Save Offer

• Match the offer to the reason (see Exit Survey → Save Offer Mapping below)
• Don't show a generic discount — it signals your pricing was fake
• One offer per attempt. If they decline, let them cancel.

Stage 4 — Confirmation

• Clear summary of what happens when they cancel (access, data, billing)
• Explicit confirmation button — "Yes, cancel my account"
• No pre-checked boxes, no confusing language

Stage 5 — Post-Cancel

• Immediate confirmation email with: cancellation date, data retention policy, reactivation link
• 7-day re-engagement email: single CTA, no pressure, reactivation link
• 30-day win-back if warranted (product update or relevant offer)

---

Exit Survey Design

The survey is your most valuable data source. Design it to generate usable intelligence, not just categories.

Recommended Reason Categories

Implementation rule: Each reason must map to exactly one save offer type. Ambiguous mapping = generic offer = low save rate.

---

Save Offer Playbook

Match the offer to the reason. Each offer type has a right and wrong time to use it.

Offer presentation rules:

• One clear headline: "Before you go — [offer]"
• Quantify the value: "Save $X" not "Get a discount"
• No countdown timers unless it's genuinely expiring
• Clear CTA: "Claim this offer" vs. "Continue cancelling"

See references/cancel-flow-playbook.md for full decision trees and flow templates.

---

Involuntary Churn: Dunning Setup

Failed payments cause 20-40% of total churn at most SaaS companies. Most of it is recoverable.

Recovery Stack

1. Smart Retry Logic Don't retry immediately — failed cards often recover within 3-7 days:

• Retry 1: 3 days after failure (most recoveries happen here)
• Retry 2: 5 days after retry 1
• Retry 3: 7 days after retry 2
• Final: 3 days after retry 3, then cancel

2. Card Updater Services

• Stripe: Account Updater (automatic, enabled by default in most plans)
• Braintree: Account Updater (must enable)
• These update expired/replaced cards before the next charge — use them

3. Dunning Email Sequence

Email rules:

• Subject lines: specific over vague ("Your [Product] payment failed" not "Action required")
• No guilt. No shame. Card failures happen — treat customers like adults.
• Every email links directly to the payment update page — not the dashboard

See references/dunning-guide.md for full email sequences and retry configuration examples.

---

Metrics & Benchmarks

Track these weekly, review monthly:

Red flags:

• Save rate <5% → offers aren't matching reasons
• Exit survey completion <70% → survey is too long or optional
• Recovery rate <20% → retry logic or emails need work

Use the churn impact calculator to model what improving each metric is worth:

python3 scripts/churn_impact_calculator.py

---

Proactive Triggers

Surface these without being asked:

• Instant cancellation flow → Revenue is leaking immediately. Any friction saves money — flag for priority fix.
• Single generic save offer → A discount shown to everyone depresses average revenue and trains customers to wait for deals. Map offers to exit reasons.
• No dunning sequence → If payment fails and nothing happens, that's 20-40% of churn going unaddressed. Flag immediately.
• Exit survey is optional → <70% completion = bad data. Make it required (one question, fast).
• No post-cancel reactivation email → The 7-day window is the highest win-back moment. Missing it leaves money on the table.
• Churn rate >5% monthly → At this rate, the company is likely contracting. Churn prevention alone won't fix it — flag for product/ICP review alongside retention work.

---

Output Artifacts

---

Communication

All output follows the structured communication standard:

• Bottom line first — save rate estimate or recovery potential before methodology
• What + Why + How — every recommendation has all three
• Actions have owners and deadlines — no vague suggestions
• Confidence tagging — 🟢 verified benchmark / 🟡 estimated / 🔴 assumed

---

Related Skills

• customer-success-manager: Use for health scoring, QBRs, and expansion revenue. NOT for cancel flow or dunning.
• email-sequence: Use for lifecycle nurture and onboarding emails. NOT for dunning (use this skill for dunning).
• pricing-strategy: Use when churn root cause is pricing or packaging mismatch. NOT for save offer design (use this skill).
• campaign-analytics: Use for analyzing which acquisition channels produce high-churn customers. NOT for setting up retention tracking.
• signup-flow-cro: Use for reducing drop-off at signup. NOT for post-signup retention.

Cancel Flow Playbook

Complete reference for designing, building, and auditing cancel flows.

---

The Cancel Flow Decision Tree

Customer clicks "Cancel" or "Cancel Subscription"
         │
         ▼
   [Show Exit Survey]
   "What's the main reason you're cancelling?"
         │
    ┌────┴─────────────────────────────────────────┐
    │                                               │
 Price/Value                              Other Reasons
    │                                               │
    ▼                                               ▼
Discount offer                        Match to reason category
(1-3 month, 20-30%)                   (see mapping table)
    │                                               │
    ▼                                               ▼
[Accept?]──Yes──► Charge updated    [Accept?]──Yes──► Apply offer
    │                                    │
    No                                   No
    │                                    │
    ▼                                    ▼
[Confirm Cancel]                    [Confirm Cancel]
    │                                    │
    ▼                                    ▼
[Post-cancel page + email]          [Post-cancel page + email]

---

Stage-by-Stage Templates

Stage 1: Pre-Cancel Intercept

When triggered: User lands on cancel/subscription page, clicks "Cancel plan", or navigates to billing settings.

What to show: Brief value reminder (not a wall of guilt) + "Tell us why" framing.

Copy template:

Headline: Before you go, we want to understand
Body: Your feedback helps us improve. Take 30 seconds to tell us why 
      you're cancelling — and we might have a solution you haven't tried.
CTA: Continue to cancellation →

Rules:

• Don't block the cancel path
• Don't show this more than once per session
• Mobile: single screen, no scrolling required

---

Stage 2: Exit Survey

Design specs:

• Single question, required
• Radio buttons (not checkboxes)
• 6-8 options maximum
• Optional open text at bottom: "Anything else we should know?"
• Submit advances to Stage 3 — don't show offer yet

Copy template:

What's the main reason you're cancelling?

○ It's too expensive for what I get
○ I'm not using it enough to justify the cost
○ It's missing a feature I need
○ I'm switching to a different tool
○ My project or need ended
○ It's too complicated or hard to use
○ I was just testing it out
○ Other: [text field]

[Continue →]

Data capture: Store the reason against the customer record. This is your product feedback goldmine.

---

Stage 3: Dynamic Save Offer

Offer-to-reason mapping (full):

Offer presentation template:

[For price objection:]
Headline: Keep [Product] for less
Body: We'd hate to see you go over price. Here's what we can do:
      Get 30% off your next 3 months — that's [calculated dollar amount] saved.
      After 3 months, your plan returns to [original price].
CTA (accept): Claim my discount →
CTA (decline): No thanks, continue cancelling →

[For not using it enough:]
Headline: No charge for 60 days — pause your account
Body: Life gets busy. Put [Product] on hold for up to 60 days. 
      Your data stays intact, and you can resume any time. No charge during pause.
CTA (accept): Pause my account →
CTA (decline): No thanks, continue cancelling →

Offer rules:

• One offer per cancel attempt — never show multiple
• If they decline, go straight to Stage 4
• Don't re-show the same offer if they return to cancel within 30 days
• Track which offer was shown and whether it was accepted

---

Stage 4: Cancellation Confirmation

What to include:

• Explicit confirmation of what will happen
• Access end date (specific date, not "end of billing period")
• Data retention policy (how long data is kept)
• Support contact in case they change their mind
• Confirmation button with clear copy

Copy template:

Your subscription will be cancelled.

Here's what happens next:
• Access continues until [specific date]
• Your data is retained for 90 days after cancellation
• After 90 days, your account data is deleted
• You can reactivate any time before [90-day date]

If you change your mind, contact [email] or reactivate at [reactivation URL].

[Confirm Cancellation]    [Go back]

---

Stage 5: Post-Cancel Sequence

Immediate: Cancellation Confirmation Email

Subject: Your [Product] subscription has been cancelled

Hi [Name],

Your [Product] subscription has been cancelled as requested.

What happens next:
- Access continues until [date]
- Your data is saved for 90 days (until [date])
- To reactivate, visit: [reactivation link]

If this was a mistake or you have questions, reply to this email or visit [support link].

[Product] Team

Day 7: Re-engagement Email

Subject: Your [Product] account is still here

Hi [Name],

It's been a week since you cancelled. Your account and data are still intact 
until [date].

If anything changed, you can reactivate in one click — no re-setup required.

[Reactivate my account →]

No pressure — just wanted to make sure you knew the door's open.

[Product] Team

Day 30: Win-Back Email (send only if triggered by product update or relevant offer)

Subject: [Product] update: [specific feature they mentioned or relevant improvement]

Hi [Name],

Since you left, we shipped [specific update relevant to their cancel reason].
[2-3 sentence description of what changed.]

If [their specific problem] was why you left, it might be worth another look.

[See what's new →]    or    [Reactivate →]

[Product] Team

---

Cancel Flow Audit Scorecard

Rate your existing flow on each dimension (0-10):

Score interpretation:

• 60-70: Solid foundation. Fix the 0-5 rated dimensions.
• 40-59: Material revenue leaking. Prioritize survey + offer mapping.
• <40: Major opportunity. Build from scratch using this playbook.

---

Platform Implementation Notes

Stripe

• Use Customer Portal for cancel flow (customizable via Stripe Dashboard)
• Enable Stripe Billing webhooks: customer.subscription.deleted, invoice.payment_failed
• Stripe Radar helps filter bot-initiated failures from real card failures
• Account Updater: enabled by default on most plans — verify in Dashboard > Settings

Chargebee / Recurly

• Both have native cancel flow builders with reason collection
• Dunning sequences configurable in-product
• Connect to your email provider (Intercom, Customer.io, etc.) via webhook

Custom / Homegrown Billing

• Build cancel flow as a separate route (not inline in settings)
• Store cancel_reason, save_offer_shown, save_offer_accepted per customer
• Retry logic: implement as a background job with delay queue

Dunning Guide

Payment recovery strategies, retry logic, and email sequences for involuntary churn.

---

Why Involuntary Churn Matters

At most SaaS companies, 20-40% of all churn comes from failed payments — not customer decisions. The customer didn't choose to leave. Their card expired, got replaced, hit a limit, or was flagged by their bank. Most of these situations are recoverable within 7-14 days.

The math:

• 1,000 active customers
• 3% monthly churn rate = 30 churned per month
• If 30% of that is involuntary = 9 customers/month from failed payments
• Recovery rate of 40% = 3.6 customers saved/month
• At $100 MRR: $360/month recovered, $4,320/year — from just fixing dunning

That's before touching voluntary churn.

---

Failure Mode Taxonomy

Not all payment failures are equal. Categorize before deciding how to retry:

Rule: Never retry fraudulent, lost, or stolen card declines. It increases chargeback risk.

---

Retry Schedule

Optimal timing based on card network research:

Day 0:  Payment fails (initial charge)
Day 3:  Retry 1 — highest recovery rate (3-7 days is the sweet spot)
Day 8:  Retry 2 — catches monthly paycycle refills
Day 13: Retry 3 — final automated attempt
Day 16: Cancel subscription (if not recovered)

Stripe-specific configuration:

In Stripe Billing settings (Dashboard > Billing > Subscriptions and emails):

Smart Retries: Enable (Stripe uses ML to pick retry timing)
   OR
Manual schedule: 3 days, 5 days, 7 days
Subscription behavior after all retries: Cancel subscription

Alternative for maximum recovery: If using Smart Retries (Stripe), disable manual schedule — they conflict. Smart Retries uses real-time card network data and typically outperforms fixed schedules.

---

Card Updater Services

These services update card details automatically when banks issue new cards:

Expected impact: 15-25% of involuntary churn prevented before dunning emails are needed.

---

Dunning Email Sequence

Five emails. Each one escalates slightly in urgency. No guilt, no shame — these are operational communications.

---

Email 1 — Day 0: "Payment failed"

Goal: Inform, make it easy to fix.

Subject: Your [Product] payment didn't go through

Hi [Name],

We weren't able to process your [Product] subscription payment of [amount].

This happens sometimes — an expired card, a temporary issue with your bank, 
or a card limit. Easy to fix.

Update your payment details here:
[Update payment method →]

If you need help, reply to this email.

[Product] Team

---
Payment amount: [amount]
Billing date: [date]
Next retry: [date + 3 days]

Notes:

• Send within 1 hour of failure
• Include specific amount and date — vague emails get ignored
• Mention the next retry date — some customers will wait for the retry to see if it clears

---

Email 2 — Day 3: "Retry coming up"

Goal: Catch people before the retry so they can update the card first.

Subject: [Product] — we'll try your payment again tomorrow

Hi [Name],

We're going to attempt your [Product] payment of [amount] again tomorrow 
([specific date]).

If your card details have changed, update them now so the retry goes through:
[Update payment method →]

If the retry fails, we'll reach out again.

[Product] Team

Notes:

• Send day before the retry, not day of
• Short email — one job, one CTA
• Some payment processors let you trigger a manual retry immediately after card update — mention this if yours does

---

Email 3 — Day 7: "We tried again — still failing"

Goal: Add urgency, soften tone, offer help.

Subject: [Product] payment still failing — action needed

Hi [Name],

We've attempted to process your [Product] subscription twice now, 
and the payment hasn't gone through.

Your account is still active, but we'll need to resolve this soon to 
avoid any interruption.

A few common fixes:
• Check if your card has expired and update it
• Contact your bank if the card is being declined unexpectedly
• Use a different card if this one is no longer working

Update payment details:
[Update payment method →]

Still having trouble? Reply to this email and we'll help you sort it out.

[Product] Team

Notes:

• Shift from notification to problem-solving
• List common causes — helps customers self-diagnose
• Offer human help — some people have legitimate confusion

---

Email 4 — Day 12: "Final notice"

Goal: Create urgency without being threatening. Be clear about what happens.

Subject: [Product] account at risk — payment needed by [specific date]

Hi [Name],

We've made multiple attempts to process your [Product] subscription, 
and we haven't been able to reach your card.

Your account will be cancelled on [specific date] if we don't receive payment.

Here's what you'll lose access to:
• [Key feature / data point]
• [Key feature / data point]
• Your [X] months of [data/history/usage]

This is our last reminder before cancellation.

Update payment now:
[Update payment method →]

Need to talk to someone? [Book a call] or reply here.

[Product] Team

Notes:

• Use a specific date — "soon" doesn't create urgency, "March 15" does
• List what they lose — tangible is more motivating than abstract
• Offer human escalation — some churn at this stage is recoverable by a support person

---

Email 5 — Day 16: "Account cancelled"

Goal: Inform, leave the door open, make reactivation easy.

Subject: Your [Product] account has been cancelled

Hi [Name],

We've cancelled your [Product] subscription as of today. Your card could 
not be charged for [amount] after multiple attempts.

Your data is saved for 90 days (until [date]).

To reactivate:
[Reactivate my account →]

You'll be able to pick up where you left off — all your data will be intact.

If you think this was an error, reply to this email and we'll sort it out.

[Product] Team

Notes:

• No blame, no guilt — this is a notification, not a scolding
• Make reactivation frictionless — one click, not a new signup flow
• Data retention timeline gives them a reason to act within 90 days

---

Dunning Metrics to Track

---

Third-Party Dunning Tools

For teams who want plug-and-play dunning without building it:

When to use a third-party tool: If you're <$500k MRR and don't have engineering bandwidth to build retry logic + email sequences, a tool pays for itself quickly. Above that threshold, build it in-house for more control.