churn-prevention

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill churn-prevention-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churn-prevention
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/marketing/skills/churn-prevention
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill churn-prevention-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Subscription businesses lose revenue to both voluntary churn (customers cancelling) and involuntary churn (failed payments), often without any system to intercept or recover 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 cancellation flows with exit surveys, reason-mapped save offers (discounts, pauses, downgrades), and compliant confirmation screens. - Churn Prediction: Construct a 0-100 customer health score from usage, engagement, and billing signals, with tiered intervention playbooks for at-risk accounts. - Dunning & Payment Recovery: Implement pre-dunning card expiry alerts, smart retry schedules by decline type, and a 4-email dunning sequence with recovery benchmarks. - Use Case: A SaaS product with 7% monthly churn uses this Skill to design an exit survey with 7 reason categories, map a 25% discount offer to "too expensive" cancellations, and set up Stripe Smart Retries with dunning emails to recover failed payments. ## Quick Start Ask the agent to design a cancel flow with exit survey and save offers for your subscription product, including 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 that reduces churn?

Structure the flow as trigger, exit survey, dynamic save offer, confirmation, then post-cancel. Use a single-question survey with 5-8 reason options, then show one primary offer matched to the selected reason plus one fallback, always keeping a visible continue-cancelling option.

What save offers work best for each cancellation reason?

Match offers to reasons: 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 recover failed subscription payments?

Use the dunning stack: pre-dunning card expiry alerts, smart retries timed to decline type and paydays, a 4-email sequence over 10 days with escalating urgency, then a grace period before pausing. Well-tuned dunning recovers 50-60% of failed payments.

Does Stripe support automatic payment retries and card updating?

Yes. Stripe Smart Retries uses machine learning to pick optimal retry timing, and its card updater automatically refreshes expired or replaced cards. Both are enabled in the Stripe Dashboard under Billing settings.

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

Build a health score from weighted signals: login frequency, feature usage, support sentiment, billing health, and engagement. Score 0-100, then trigger interventions by tier, such as personal outreach for scores below 40.

When should I not offer a discount to save a cancelling customer?

Skip discounts when the reason is not price-related, such as missing features or business closure, since discounts do not address the root cause. Also avoid re-offering discounts to repeat cancellers, which trains cancel-for-deal behavior.