Churn Prevention

---
name: Churn Prevention
description: Use when the user wants to reduce churn, build cancel flows or save offers, recover failed payments, or set up dunning and retention strategies.
category: Growth & Retention
version: 2.0.0
tools: []
---

# Churn Prevention

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.

## Before starting
Search the knowledge base for existing product-marketing context first; use whatever it already covers and only ask about what's missing.

Gather, if not already known:

**Current situation** — monthly churn rate (voluntary vs. involuntary if known); active subscriber count; average MRR per customer; whether a cancel flow exists today or cancellation is instant.

**Billing & platform** — billing provider (Stripe, Chargebee, Paddle, Recurly, Braintree); monthly, annual, or both billing intervals; support for pausing or downgrading; any existing retention tooling (Churnkey, ProsperStack, Raaft).

**Product & usage data** — per-user feature usage tracking; visibility into engagement drop-offs; historical cancellation-reason data; the activation metric that separates retained users from churned ones.

**Constraints** — B2B or B2C (affects flow design); whether self-serve cancellation is required by regulation; brand tone for offboarding (empathetic, direct, playful).

## Two churn types, two strategies

| Type | Cause | Solution |
|---|---|---|
| Voluntary | Customer chooses to cancel | Cancel flows, save offers, exit surveys |
| Involuntary | Payment fails | Dunning emails, smart retries, card updaters |

Voluntary churn is typically 50-70% of total churn; involuntary is 30-50% but usually easier to fix. Three modes of work: build a cancel flow from scratch; optimize an existing flow using cancel data; or set up dunning for failed-payment recovery.

## Cancel flow design

Sequence: **Trigger → Survey → Dynamic offer → Confirmation → Post-cancel.**

1. **Trigger** — customer clicks "Cancel subscription."
2. **Exit survey** — ask why; the answer determines which save offer to show.
3. **Dynamic save offer** — a targeted offer based on the stated reason.
4. **Confirmation** — if they still want out, confirm clearly with end-of-billing-period messaging.
5. **Post-cancel** — set expectations, offer an easy reactivation path, trigger a win-back sequence.

### Exit survey design
Single-select, 5-8 reason options max, optional free text, most common reasons listed first (review quarterly). Frame it as "help us improve," not "why are you leaving" — avoid guilt-trip framing.

| Reason | What it signals |
|---|---|
| Too expensive | Price sensitivity — may respond to discount or downgrade |
| Not using it enough | Low engagement — may respond to pause or onboarding help |
| Missing a feature | Product gap — show roadmap or a workaround |
| Switching to competitor | Competitive pressure — understand what they offer |
| Technical issues / bugs | Product quality — escalate to support |
| Temporary / seasonal need | Usage pattern — offer a pause |
| Business closed / changed | Unavoidable — let go gracefully |

### Dynamic save offers
Match the offer to the reason — a discount won't save someone who isn't using the product, and a roadmap won't save someone who can't afford it.

| Reason | Primary offer | Fallback |
|---|---|---|
| Too expensive | 20-30% discount for 2-3 months | Downgrade to a lower plan |
| Not using it enough | Pause (1-3 months) | Free onboarding session |
| Missing feature | Roadmap preview + timeline | Workaround guide |
| Switching to competitor | Competitive comparison + discount | Feedback session |
| Technical issues | Escalate to support immediately | Credit + priority fix |
| Temporary / seasonal | Pause subscription | Temporary downgrade |
| Business closed | Skip the offer — respect the situation | — |

**Discount** — 20-30% off for 2-3 months is the sweet spot; avoid 50%+ (trains customers to cancel for deals); time-limit it; show the dollar amount saved, not just the percentage.

**Pause** — 1-3 months maximum (longer pauses rarely reactivate); 60-80% of pausers eventually return to active; auto-reactivate with an advance-notice email; keep their data and settings intact.

**Downgrade** — offer a lower tier instead of full cancellation; show what they keep vs. lose; frame as "right-size your plan," not "downgrade"; make the path back up easy.

**Feature unlock / trial extension** — unlock a premium feature they haven't tried, or extend a trial of a higher tier; works best for "not enough value" reasons.

**Personal outreach** — for the top 10-20% of accounts by MRR, route to customer success for a call; for smaller companies, a personal email from the founder.

### Cancel-flow UI principles
Keep a visible "never mind, keep my subscription" exit at every step — no dark patterns. Show one primary offer plus one fallback, not a wall of options. Show specific dollar savings, not abstract percentages. Personalize with the customer's name and account data where possible. Design mobile-first — many cancellations happen on mobile.

## Churn prediction & proactive retention

The best save happens before the customer ever clicks "Cancel." Track leading indicators:

| Signal | Risk | Typical lead time |
|---|---|---|
| Login frequency drops 50%+ | High | 2-4 weeks before cancel |
| Key feature usage stops | High | 1-3 weeks before cancel |
| Support tickets spike then stop | High | 1-2 weeks before cancel |
| Email open rates decline | Medium | 2-6 weeks before cancel |
| Billing page visits increase | High | Days before cancel |
| Team seats removed | High | 1-2 weeks before cancel |
| Data export initiated | Critical | Days before cancel |
| NPS score drops below 6 | Medium | 1-3 months before cancel |

### Health score model
Build a 0-100 score from weighted signals:

`Health score = login frequency ×0.30 + feature usage ×0.25 + support sentiment ×0.15 + billing health ×0.15 + engagement ×0.15`

| Score | Status | Action |
|---|---|---|
| 80-100 | Healthy | Upsell opportunities |
| 60-79 | Needs attention | Proactive check-in |
| 40-59 | At risk | Intervention campaign |
| 0-39 | Critical | Personal outreach |

### Proactive interventions
Usage drop >50% for 2 weeks → "we noticed you haven't used [feature]" email. Approaching a plan limit → an upgrade nudge, not a hard wall. No login for 14 days → re-engagement email with recent product updates. NPS detractor (0-6) → personal follow-up within 24 hours. Support ticket unresolved >48h → escalate with a proactive status update. Annual renewal in 30 days → value-recap email plus renewal confirmation.

## Involuntary churn: payment recovery

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

Sequence: **Pre-dunning → smart retry → dunning emails → grace period → hard cancel.**

**Pre-dunning** — card-expiry alerts at 30/15/7 days out; prompt for a backup payment method at signup; use card-updater services (Visa/Mastercard auto-update programs cut hard declines 30-50%); send a pre-billing notice 3-5 days ahead for annual plans.

**Smart retry logic** — distinguish decline types: soft declines (insufficient funds, processor timeout) retry 3-5 times over 7-10 days; hard declines (stolen card, closed account) don't retry — ask for a new card; authentication-required declines (3D Secure, SCA) send the customer to update payment.

Retry cadence: 24 hours after failure, then 3 days, then 5 days, then 7 days (with dunning-email escalation); after 4 retries, hard-cancel with a reactivation path. Tip: retry on the day of month the payment originally succeeded — most billing providers' smart-retry features (e.g., Stripe Smart Retries) do this automatically.

### Dunning email sequence

| Email | Timing | Tone | Content |
|---|---|---|---|
| 1 | Day 0 | Friendly alert | "Your payment didn't go through. Update your card." |
| 2 | Day 3 | Helpful reminder | "Quick reminder — update your payment to keep access." |
| 3 | Day 7 | Urgency | "Your account will be paused in 3 days." |
| 4 | Day 10 | Final warning | "Last chance to keep your account active." |

Link directly to the payment-update page (no login if possible); show what they'll lose; don't blame ("your payment failed," not "you failed to pay"); include a support contact; plain text tends to outperform designed emails for dunning.

### Recovery benchmarks

| Metric | Poor | Average | Good |
|---|---|---|---|
| Soft decline recovery | <40% | 50-60% | 70%+ |
| Hard decline recovery | <10% | 20-30% | 40%+ |
| Overall payment recovery | <30% | 40-50% | 60%+ |
| Pre-dunning prevention | none | 10-15% | 20-30% |

## Metrics & measurement

| Metric | Formula | Target |
|---|---|---|
| Monthly churn rate | Churned customers ÷ start-of-month customers | <5% B2C, <2% B2B |
| Net revenue churn | (Lost MRR − expansion MRR) ÷ start MRR | Negative (net expansion) |
| Cancel-flow save rate | Saved ÷ total cancel sessions | 25-35% |
| Offer acceptance rate | Accepted ÷ shown offers | 15-25% |
| Pause reactivation rate | Reactivated ÷ total paused | 60-80% |
| Dunning recovery rate | Recovered ÷ total failed payments | 50-60% |

Segment churn by acquisition channel, plan type, tenure (when do most cancellations happen — 30/60/90 days?), cancel reason, and which save offer worked for which segment.

### Cancel-flow experiments
Test one variable at a time: discount size (20% vs 30%), pause duration (1 vs 3 months), survey placement (before vs after the offer), offer presentation (modal vs full page), copy tone (empathetic vs direct). Use the ab-testing skill to design these rigorously; a feature-flag/analytics platform (e.g., PostHog) can split users server-side and track each funnel step (survey → offer → accept/decline → confirm).

## Common mistakes
No cancel flow at all — even a simple survey plus one offer saves 10-15%. Hiding the cancel button — breeds resentment and bad reviews, and many jurisdictions require easy cancellation (the FTC's Click-to-Cancel rule). The same offer for every reason. Discounts deeper than 50% that train cancel-and-return behavior. Ignoring involuntary churn, which is often 30-50% of the total and the easiest to fix. No dunning emails at all. Guilt-trip copy that damages brand trust. Not tracking a "saved" customer's actual LTV — a save that churns 30 days later wasn't really a save. Pauses longer than 3 months, which rarely reactivate. No post-cancel path — make reactivation easy and trigger a win-back sequence.

## Platforms worth knowing
Retention platforms: Churnkey (full cancel flow + dunning, AI-adaptive offers, ~34% average save rate), ProsperStack (cancel flows with a rules engine, Stripe/Chargebee integration), Raaft (simple cancel-flow builder for early-stage teams), Chargebee Retention (native to Chargebee, formerly Brightback). Billing providers with built-in smart retries, dunning emails, and card-updater support: Stripe, Chargebee, Paddle, Recurly; Braintree requires manual configuration.

## Related skills
**emails** for win-back sequences after cancellation. **paywalls** for in-app upgrade moments and trial expiration. **pricing** for plan structure and annual-discount strategy. **onboarding** for activation that prevents early churn. **analytics** for churn-signal event tracking. **ab-testing** for statistically rigorous cancel-flow experiments.