churn-prevention

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

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

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 either. This Skill provides structured frameworks for building cancel flows, mapping save offers to cancellation reasons, predicting at-risk customers, and recovering failed payments. ## Core Features & Use Cases - Cancel Flow Design: Build a multi-step flow (exit survey, dynamic save offer, confirmation, post-cancel) with reason-to-offer mapping and UI patterns. - Churn Prediction: Construct a 0-100 health score from usage, engagement, and billing signals, with tiered intervention playbooks. - Dunning & Payment Recovery: Implement pre-dunning card expiry alerts, smart retry schedules by decline type, and a 4-email escalating dunning sequence. - Use Case: A SaaS product with 7% monthly churn uses this Skill to launch an exit survey, offer 25% discounts to price-sensitive cancellers, enable Stripe Smart Retries, and cut involuntary churn in half. ## 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 that saves customers?

Structure the flow as trigger, exit survey, dynamic save offer, confirmation, then post-cancel. Map each cancellation reason to a matching offer, such as a 20-30% discount for price concerns or a pause for low usage, and always keep the continue-cancelling option visible.

How do I recover failed subscription payments?

Use the dunning stack: pre-dunning card expiry alerts, smart retries timed to decline type, a 4-email escalating sequence over 10 days, then a grace period before pausing the account. Stripe Smart Retries and card updater services handle much of this automatically.

What save offer should I show for each cancellation reason?

Match the offer to the reason: discounts for too expensive, pause for not using enough, roadmap preview for missing features, support escalation for technical issues, and no offer for business closures. Blanket discounts underperform reason-matched offers.

Does this work with Stripe, Chargebee, or Paddle?

Yes, the Skill includes provider-specific setup guidance for Stripe, Chargebee, Paddle, Recurly, and Braintree, covering smart retry configuration, dunning email settings, card updater availability, and relevant webhook events like invoice.payment_failed.

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 tier interventions from proactive check-ins at 60-79 down to personal outreach below 40.

What are common cancel flow mistakes to avoid?

Avoid instant cancellation with no save attempt, hidden cancel buttons, identical offers for every reason, discounts above 30-50%, and ignoring involuntary churn. Also track save offer LTV, since a saved customer who churns in 30 days was not truly saved.