churn-prevention

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

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/marketing-skills --skill churn-prevention-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churn-prevention
Source: https://github.com/imMamdouhaboammar/marketing-skills/tree/main/skills/churn-prevention
Command: npx skills add https://github.com/imMamdouhaboammar/marketing-skills --skill churn-prevention-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? SaaS businesses lose revenue to both voluntary churn (customers cancelling) and involuntary churn (failed payments), often without any system to intercept or recover those customers. ## Core Features & Use Cases - Cancel Flow Design: Builds multi-step cancellation flows with exit surveys, dynamic save offers matched to cancellation reasons, and compliant confirmation steps. - Dunning & Payment Recovery: Implements pre-dunning card expiry alerts, smart retry schedules, and escalating dunning email sequences for failed payments. - Churn Prediction: Defines health score models from usage, engagement, and billing signals with tiered proactive interventions. - Use Case: A $49/month SaaS with 7% monthly churn uses this Skill to build a cancel flow with reason-mapped save offers, set up Stripe Smart Retries with a 4-email dunning sequence, and establish a customer health score for proactive outreach. ## Quick Start Ask the agent 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 that saves customers?

A cancel flow follows the sequence: trigger, exit survey, dynamic save offer, confirmation, and post-cancel. The exit survey captures the cancellation reason, which determines which save offer to show, such as a discount for price concerns or a pause for low usage.

How do I recover failed subscription payments?

Failed payment recovery uses a dunning stack: pre-dunning card expiry alerts, smart retries timed to decline type, a 4-email escalating sequence over 10 days, and a grace period before pausing the account. Effective dunning recovers 50-60% of failed payments.

What save offer should I show for each cancellation reason?

Match the offer to the reason: discounts of 20-30% for price concerns, subscription pauses for low usage, roadmap previews for missing features, and support escalation for technical issues. A blanket discount fails to address non-price reasons.

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

Yes, the dunning guidance covers Stripe Smart Retries, Chargebee retry settings, Paddle's managed dunning, Recurly, and Braintree. It includes provider-specific setup steps, webhook events to handle, and card updater service configuration.

How do I identify customers at risk of churning before they cancel?

Build a health score from weighted signals: login frequency, feature usage, support sentiment, billing health, and engagement. Customers scoring below 40 are critical and warrant personal outreach, while scores of 40-59 trigger intervention campaigns.

What are common cancel flow mistakes to avoid?

Common mistakes include having no cancel flow, hiding the cancel button, offering the same discount for every reason, discounts deeper than 50%, ignoring involuntary churn, and guilt-trip copy. Regulations like the FTC Click-to-Cancel rule require cancellation to be as easy as signup.