churn-prevention

Designs cancel flows, save offers, and dunning sequences to reduce SaaS churn.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/yo16/cc_dev_team --skill churn-prevention-yo16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: churn-prevention
Source: https://github.com/yo16/cc_dev_team/tree/main/specific_set/seo/skills/churn-prevention
Command: npx skills add https://github.com/yo16/cc_dev_team --skill churn-prevention-yo16

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? SaaS businesses lose subscribers through voluntary cancellations and failed payments, often without any system to save them. This Skill provides a complete retention framework covering cancel flow design, dynamic save offers, churn prediction, and payment recovery. ## Core Features & Use Cases - Cancel Flow Design: Build multi-step cancel flows with exit surveys, reason-mapped save offers (discounts, pauses, downgrades), and compliant confirmation screens. - Involuntary Churn Recovery: Implement the full dunning stack including pre-dunning card expiry alerts, smart retry schedules, and a 4-email recovery sequence for Stripe, Chargebee, Paddle, and Recurly. - Churn Prediction: Create a weighted health score from usage, support, and billing signals, with tiered interventions for at-risk accounts. - Use Case: A $49/month SaaS with 7% monthly churn uses this Skill to build a cancel flow with exit survey and dynamic offers, set up Stripe Smart Retries with dunning emails, and deploy a health score to catch at-risk customers before they cancel. ## Quick Start Ask the AI to design a churn prevention strategy for your SaaS, including a cancel flow with exit survey and save offers plus a dunning sequence for failed payments.

Frequently Asked Questions about churn-prevention

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a cancel flow to reduce SaaS churn?▼

Build a five-step flow: cancel trigger, one-question exit survey, dynamic save offer matched to the cancellation reason, clear confirmation, and post-cancel follow-up. Keep the continue-cancelling option visible at every step to stay compliant with FTC click-to-cancel rules.

How do I recover failed subscription payments?▼

Use the dunning stack: pre-dunning card expiry alerts, smart retries timed to decline type and paydays, a four-email sequence over 10 days with escalating urgency, then a grace period before pausing the account. Stripe Smart Retries automates optimal retry timing.

What save offers work best for each cancellation reason?▼

Match the offer to the reason: 20-30% discounts for price concerns, 1-3 month pauses for low usage, roadmap previews for missing features, and support escalation for technical issues. Avoid discounts above 30%, which train customers to cancel for deals.

How do I predict which customers will churn before they cancel?▼

Build a 0-100 health score from weighted signals: login frequency (30%), feature usage (25%), support sentiment (15%), billing health (15%), and engagement (15%). Accounts scoring below 40 get personal outreach, while 40-59 triggers intervention campaigns.

Does this work with Stripe, Chargebee, and other billing providers?▼

Yes, the Skill includes provider-specific setup for Stripe, Chargebee, Paddle, Recurly, and Braintree, covering smart retry configuration, dunning email settings, card updater services, and relevant webhook events like invoice.payment_failed.

What are common mistakes when building cancellation flows?▼

Common mistakes include having no cancel flow at all, hiding the cancel button, offering the same discount for every reason, ignoring involuntary churn, and using guilt-trip copy. Even a simple survey plus one offer typically saves 10-15% of cancellations.