plugins/growth/skills/churn-prevention/SKILL.md
Reduces voluntary churn (cancel flow design, exit surveys, dynamic save offers) and involuntary churn (dunning, smart retries, payment recovery) for SaaS products. Use when churn rate is too high, designing cancel flows, building retention systems, or recovering failed payments. Triggers include "reduce churn", "cancel flow", "dunning", "failed payments", "retention". NOT for user onboarding (use product-led-growth), growth experiments (use growth-hacking), pricing strategy (use pricing), or UX optimization (use ux-optimization).
npx skillsauth add petrogurcak/skills churn-preventionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill helps SaaS teams reduce both voluntary churn (customers actively cancelling) and involuntary churn (failed payments) through cancel flow design, proactive retention systems, and dunning strategies. Covers diagnostics, intervention design, and recovery with specific benchmarks.
Announce: "I'm using churn-prevention to design retention and recovery systems."
USE this skill:
DON'T use this skill:
product-led-growthgrowth-hackingpricingux-optimizationsaas-bootstrap| Situation | Go to | | --- | --- | | "I don't know why customers leave" | Churn Diagnostics | | "I need a cancel flow" | Cancel Flow Design | | "What offer for which reason?" | Dynamic Offer Matrix | | "I want to catch churn before it happens" | Proactive Retention | | "Failed payments are killing me" | Payment Recovery | | "What should I build first?" | Implementation Priority |
Before building anything, identify what type of churn you have and why.
Total Monthly Churn: ___%
Voluntary (active cancellations): ___% of total churn
Involuntary (failed payments): ___% of total churn
Industry baseline: failed payments account for 30-50% of total churn. If your involuntary churn is in that range, start with payment recovery -- it is the highest-ROI fix.
If you don't have exit survey data yet, deploy a simple survey first. Common reasons ranked by frequency:
| Reason | Typical Share | Recoverability | | --- | --- | --- | | Too expensive | 25-35% | High (discount/downgrade) | | Low engagement / not using | 20-30% | Medium (pause/onboarding) | | Missing features | 15-20% | Low-Medium (roadmap/workaround) | | Switching to competitor | 10-15% | Medium (comparison + discount) | | Business closed / no longer needed | 5-15% | Very low |
Break down churn by:
If churn concentrates in the first 90 days, fix onboarding before building cancel flows. Use product-led-growth for that.
A cancel flow is a multi-step funnel between the "Cancel" button and actual cancellation. Goal: understand the reason, present a matched intervention, and save 25-35% of cancellers.
[Cancel Button Clicked]
|
v
[Exit Survey: Why are you leaving?]
|
v
[Dynamic Offer based on reason]
|
Accept?
/ \
Yes No
| |
v v
[Saved] [Confirmation: Are you sure?]
|
Accept?
/ \
Yes No
| |
v v
[Cancelled] [Saved]
|
v
[Post-Cancel Email]
Keep it to ONE question with 5-6 options. Every option maps to an intervention.
"We're sorry to see you go. What's the main reason you're cancelling?"
[ ] It's too expensive
[ ] I'm not using it enough
[ ] It's missing features I need
[ ] I'm switching to another solution
[ ] My business/project ended
[ ] Other: ___________
Rules:
Each cancel reason maps to a specific intervention. Never show a generic "Are you sure?" -- match the offer to the pain.
| Cancel Reason | Primary Offer | Secondary Offer | Expected Save Rate | | --- | --- | --- | --- | | Too expensive | 20-30% discount for 3 months | Downgrade to cheaper plan | 30-40% | | Not using enough | Pause subscription (1-3 months) | Personal onboarding session | 20-30% | | Missing features | Roadmap preview + timeline | Workaround guide | 10-20% | | Switching competitor | Feature comparison + 25% discount | Concierge migration help | 15-25% | | Business ended | Pause option (up to 6 months) | Nothing (let them go gracefully) | 5-10% |
Don't wait for the cancel button. Build systems that identify at-risk customers early.
Score each customer 0-100 based on weighted engagement signals:
| Signal | Weight | Scoring | | --- | --- | --- | | Login frequency (vs. their baseline) | 25% | Dropping = risk | | Core feature usage | 30% | Not using key features = risk | | Support tickets (sentiment) | 15% | Angry tickets = risk | | Payment history | 15% | Failed payments, downgrades = risk | | NPS / survey responses | 15% | Detractors (0-6) = risk |
| Score | Tier | Action | | --- | --- | --- | | 80-100 | Healthy | Upsell opportunities, request referrals | | 50-79 | At Risk | Trigger re-engagement campaign | | 20-49 | High Risk | Personal outreach from CS team | | 0-19 | Critical | Executive escalation, save call |
Automate alerts when any of these occur:
For "At Risk" tier (score 50-79):
Failed payments are the easiest churn to fix. 50-70% recoverable with proper systems.
Not all declines are equal. Retry strategy should vary:
| Decline Type | Retry Strategy | Success Rate | | --- | --- | --- | | Soft decline (insufficient funds) | Retry in 24h, then 3 days, then 7 days | 60-70% | | Hard decline (card expired/stolen) | Don't retry. Email immediately for card update. | 30-40% (with email) | | Network/processing error | Retry in 1 hour, then 4 hours | 80-90% |
10-day sequence starting from first failed payment:
| Day | Email | Tone | | --- | --- | --- | | 0 | "Payment failed -- update your card" | Informational, helpful | | 3 | "Your subscription is at risk" | Urgent, clear deadline | | 7 | "Last chance before we pause your account" | Final warning | | 10 | "Your account has been paused" | Confirmation + easy reactivation link |
Email rules:
Stripe, Braintree, and others offer automatic card updater services that refresh expired card details before they fail. Enable this -- it silently prevents 10-20% of involuntary churn with zero customer friction.
| Metric | Poor | Acceptable | Good | Excellent | | --- | --- | --- | --- | --- | | Monthly churn (B2B) | >5% | 3-5% | 1-3% | <1% | | Monthly churn (B2C) | >10% | 5-10% | 3-5% | <3% | | Cancel flow save rate | <10% | 10-20% | 25-35% | >35% | | Payment recovery rate | <30% | 30-50% | 50-70% | >70% | | Net revenue retention | <90% | 90-100% | 100-110% | >110% |
Monthly Churn Dashboard:
Voluntary churn rate: ___%
Involuntary churn rate: ___%
Cancel flow save rate: ___%
Payment recovery rate: ___%
Net revenue retention: ___%
Top cancel reasons (this month):
1. _______________ (___%)
2. _______________ (___%)
3. _______________ (___%)
Save offer performance:
- Discount accepted: ___/___ (___%)
- Pause accepted: ___/___ (___%)
- Downgrade accepted: ___/___ (___%)
Build in this order. Each step delivers measurable ROI before moving to the next.
| Tool | What it does | Best for | | --- | --- | --- | | Churnkey | Full cancel flow + dunning | All-in-one, quick setup | | ProsperStack | Cancel flow + exit surveys | Deep survey analytics | | Chargebee Retention | Cancel flow + offer management | Chargebee users | | Stripe Smart Retries | ML-based retry optimization | Stripe users (enable in dashboard) | | Baremetrics | Churn analytics + dunning | Metrics-focused teams |
You don't need dedicated tools to start. A custom cancel flow + Stripe's built-in retries covers Phase 1-2. Add specialized tools when you need deeper analytics or A/B testing on save offers.
Skipping the exit survey: "Just show a discount to everyone" -- You waste discounts on people who would be saved by a pause, and miss product insights.
Discount addiction: Offering 50% off to every canceller trains customers to cancel-and-return for deals. Cap at 30%, time-limit to 3 months.
Ignoring involuntary churn: "It's only 3% from failed payments" -- That 3% is the easiest to recover. Start here.
Over-engineering health scores: Building an ML model before you have exit survey data. Start with login frequency + feature usage, iterate from there.
Aggressive retention dark patterns: Hiding the cancel button, requiring phone calls, 5-step flows. This generates chargebacks, bad reviews, and regulatory risk. Make it easy to leave gracefully -- and easy to come back.
Works with:
saas-bootstrap -- 3H/3L metrics (churn is a core LOW metric)product-led-growth -- Onboarding fixes for early churngrowth-hacking -- Retention experiments via ICE scoringpricing -- Plan structure affects churn (annual vs. monthly, tier design)Sequence for churn reduction project:
churn-prevention -- Diagnostics (identify churn type and reasons)churn-prevention -- Phase 1-2 implementation (dunning + cancel flow)product-led-growth -- Fix onboarding if early churn is highpricing -- Restructure plans if "too expensive" dominateschurn-prevention -- Phase 3 (proactive retention systems)development
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).