churn-prevention

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

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/Yvesdefaria/GymLab --skill churn-prevention-yvesdefaria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churn-prevention
Source: https://github.com/Yvesdefaria/GymLab/tree/main/.opencode/skills/marketingskills/skills/churn-prevention
Command: npx skills add https://github.com/Yvesdefaria/GymLab --skill churn-prevention-yvesdefaria

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 retention system in place. This Skill provides structured frameworks for building cancel flows, dynamic save offers, churn prediction, and payment recovery sequences. ## 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 steps. - Dunning & Payment Recovery: Set up pre-dunning card expiry alerts, smart retry schedules, and escalating dunning email sequences for Stripe, Chargebee, Paddle, and Recurly. - Churn Prediction: Construct a weighted health score from usage, support, and billing signals, with tiered proactive interventions for at-risk accounts. - Use Case: A SaaS product with 7% monthly churn uses this Skill to design an exit survey with seven reason categories, map a 25% discount offer to price-sensitive cancellers, and configure a four-email dunning sequence that recovers 50-60% of failed payments. ## Quick Start Ask the assistant to design a cancel flow with exit survey and save offers for your subscription product, including a dunning email 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?

Structure the flow as trigger, exit survey, dynamic save offer, confirmation, and post-cancel steps. Use a single-question survey with 5-8 reason categories, then map each reason to a targeted offer such as a discount, pause, or downgrade.

How do I recover failed subscription payments?

Use a dunning stack: pre-dunning card expiry alerts, smart retries over 7-10 days, a four-email escalation sequence, and a grace period before pausing the account. Effective dunning recovers 50-60% of failed payments.

What save offers work best for each cancellation reason?

Match the offer to the reason: discounts of 20-30% for price concerns, 1-3 month pauses for low usage, roadmap previews for missing features, and support escalation for technical issues. Avoid blanket discounts for every reason.

Does this work with Stripe, Chargebee, or Paddle dunning?

Yes, the Skill covers provider-specific setup. Stripe Smart Retries uses ML-optimized retry timing, Chargebee and Recurly have configurable built-in dunning, and Paddle manages retries automatically with limited customization.

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 accounts 0-100 and trigger interventions like re-engagement emails or personal outreach for at-risk tiers.

What are common cancel flow mistakes to avoid?

Avoid hiding the cancel button, offering the same discount for every reason, discounts above 30-50%, and guilt-trip copy. Regulations like the FTC Click-to-Cancel rule require cancellation to be as easy as signup.