churn-prevention

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

Updated Dec 22, 2025
One-click install
npx skills add https://github.com/Endsi3g/prospecting-app --skill churn-prevention-endsi3g
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churn-prevention
Source: https://github.com/Endsi3g/prospecting-app/tree/main/.agents/skills/churn-prevention
Command: npx skills add https://github.com/Endsi3g/prospecting-app --skill churn-prevention-endsi3g

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? SaaS businesses lose revenue to both voluntary churn (customers choosing to cancel) and involuntary churn (failed payments), often without any system to intercept or recover those customers. This Skill provides structured frameworks for building cancel flows, matching save offers to cancellation reasons, predicting at-risk accounts, and recovering failed payments. ## Core Features & Use Cases - Cancel Flow Design: Build multi-step cancellation flows with exit surveys, dynamic save offers mapped to each cancel reason, and compliant confirmation steps. - Dunning & Payment Recovery: Set up pre-dunning card expiry alerts, smart retry schedules by decline type, and escalating dunning email sequences for Stripe, Chargebee, Paddle, and Recurly. - Churn Prediction: Construct a weighted health score from usage, engagement, and billing signals, with tiered interventions for at-risk accounts. - Use Case: A $49/month SaaS with 7% monthly churn uses this Skill to design an exit survey with seven reason categories, map discounts and pause offers to each reason, and configure Stripe Smart Retries with a four-email dunning sequence. ## Quick Start Ask the assistant to design a cancel flow with exit survey and save offers for your subscription product, including a dunning plan 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, a dynamic save offer matched to the cancellation 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.

What save offers work best for each cancellation reason?

Match the offer to the reason: 20-30% discounts for price-sensitive users, 1-3 month pauses for low-usage customers, roadmap previews for missing features, and support escalation for technical issues. Blanket discounts for every reason underperform reason-matched offers.

How do I recover failed subscription payments with dunning?

Use a dunning stack: pre-dunning card expiry alerts, smart retries timed to decline type (soft declines retry 3-5 times over 7-10 days, hard declines need a new card), and a four-email sequence over 10 days with escalating urgency. Good programs recover 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 is enabled in Dashboard billing settings. Stripe also includes automatic card updater services and built-in dunning emails, recovering roughly 15% more than fixed retry schedules.

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%). Scores below 40 indicate critical risk and warrant personal outreach.

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

Avoid discounts when the reason is low usage, missing features, or business closure, since price is not the cause. Also avoid discounts above 30% or repeated discounts to the same customer, which trains cancel-for-deal behavior.