churn-prevention

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

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill churn-prevention-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churn-prevention
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/churn-prevention
Command: npx skills add https://github.com/mintuz/.dotfiles --skill churn-prevention-mintuz

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 at-risk customers or recover lost revenue. This Skill provides a complete framework for building cancel flows, targeted save offers, churn prediction, and payment recovery. ## Core Features & Use Cases - Cancel Flow Design: Build multi-step cancellation flows with exit surveys, dynamic save offers matched to cancellation reasons, and compliant confirmation steps. - Dunning & Payment Recovery: Implement pre-dunning card expiry alerts, smart retry schedules, and escalating dunning email sequences to recover failed payments. - Churn Prediction: Create health scores from usage, engagement, and billing signals to trigger proactive retention interventions before customers cancel. - Use Case: A $49/month SaaS tool with 7% monthly churn uses this Skill to design an exit survey with reason-mapped offers (discounts, pauses, downgrades) and a 4-email dunning sequence, cutting both voluntary and involuntary churn. ## Quick Start Ask the AI to design a cancel flow with exit survey and save offers for your subscription product, including a dunning strategy 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, exit survey with 5-8 reason options, a dynamic save offer matched to the selected reason, a clear confirmation step, and a post-cancel reactivation path. Keep the continue-cancelling option visible to stay compliant with FTC click-to-cancel rules.

How do I recover failed subscription payments?

Use a dunning stack: pre-dunning card expiry alerts, smart retries timed to decline type and paydays, a four-email escalation sequence over 10 days, 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 offers to reasons: 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 discounts above 30%, which train cancel-for-discount behavior.

Does Stripe support smart retries and dunning emails?

Yes. Stripe Smart Retries uses machine learning to pick optimal retry timing and is enabled in Dashboard billing settings. Stripe also includes built-in dunning emails and automatic card updater services for expired or replaced cards.

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

Build a 0-100 health score from weighted signals: login frequency, feature usage, support sentiment, billing health, and engagement. Score drops below 60 trigger proactive interventions like check-in emails or personal outreach for high-value accounts.

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

Skip discounts when the reason is low usage, missing features, or business closure, since price is not the root cause. Also avoid re-offering discounts to repeat cancellers and never exceed 30%, as deeper discounts devalue the product.