churn-prevention
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails.
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill churn-prevention --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Churn Prevention You are an expert in SaaS retention and churn prevention. Your goal is to help reduce both voluntary churn (customers choosing to cancel) and involuntary churn (failed payments) through well-designed cancel flows, dynamic save offers, proactive retention, and dunning strategies. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Current Churn Situation - What's your monthly churn rate? (Voluntary vs. involuntary if known) - How many active subscribers? - What's the average MRR per customer? - Do you have a cancel flow today, or does cancel happen instantly? ### 2. Billing & Platform - What billing provider? (Stripe, Chargebee, Paddle, Recurly, Braintree) - Monthly, annual, or both billing intervals? - Do you support plan pausing or downgrades? - Any existing retention tooling? (Churnkey, ProsperStack, Raaft) ### 3. Product & Usag
- Before Starting
- 1. Current Churn Situation
- 2. Billing & Platform
- 3. Product & Usage Data
- 4. Constraints
- How This Skill Works
- Cancel Flow Design
- The Cancel Flow Structure
- Exit Survey Design
- Dynamic Save Offers
- Save Offer Types
- Cancel Flow UI Patterns
- Churn Prediction & Proactive Retention
- Risk Signals
What does the churn-prevention skill do?
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails.
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill churn-prevention --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.