Agent skill · Business & Finance

churn-prevention

Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences. Use when designing or optimizing a cancel flow, building save offers, setting up dunning emails, or reducing failed-payment churn. Trigger keywords: cancel flow, churn reduction, save offers, dunning, exit survey, payment recovery, win-back, involuntary churn, failed payments, cancel page. NOT for customer health scoring or expansion revenue — use customer-success-manager for that.

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
claude-codecodexcursorships scriptsMIT
Install
npx skills add alirezarezvani/claude-skills --skill churn-prevention --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 11 KB
Bundled scripts: yes
Version: 1.0.0
Declared author: Alireza Rezvani
Path: marketing-skill/skills/churn-prevention/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 23,791 · +422 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Churn Prevention You are an expert in SaaS retention and churn prevention. Your goal is to reduce both voluntary churn (customers who decide to leave) and involuntary churn (customers who leave because their payment failed) through smart flow design, targeted save offers, and systematic payment recovery. Churn is a revenue leak you can plug. A 20% save rate on voluntary churners and a 30% recovery rate on involuntary churners can recover 5-8% of lost MRR monthly. That compounds. ## Before Starting **Check for context first:** If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for what's missing. Gather this context (ask if not provided): ### 1. Current State - Do you have a cancel flow today, or is cancellation instant/via support? - What's your current monthly churn rate? (voluntary vs. involuntary split if known) - What payment processor are you on? (Stripe, Braintree, Paddle, etc.) - Do you collect exit reasons today? ### 2. Business Context - SaaS model: self-serve or sales-assisted? - Price points and plan structure - Average contract length and billing cycle (monthly/annual) - Current MRR ### 3. Goals - Which pro

What's inside
Steps it walks through
  1. Before Starting
  2. 1. Current State
  3. 2. Business Context
  4. 3. Goals
  5. How This Skill Works
  6. Mode 1: Build Cancel Flow
  7. Mode 2: Optimize Existing Flow
  8. Mode 3: Set Up Dunning
  9. Cancel Flow Design
  10. The 5-Stage Flow
  11. Exit Survey Design
  12. Recommended Reason Categories
  13. Save Offer Playbook
  14. Involuntary Churn: Dunning Setup
Ships with 3 files
  • references/cancel-flow-playbook.md
  • references/dunning-guide.md
  • scripts/churn_impact_calculator.py
Commands it runs
python3 scripts/churn_impact_calculator.py
More from claude-skills
All skills →
About this skill
What does the churn-prevention skill do?

Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences. Use when designing or optimizing a cancel flow, building save offers, setting up dunning emails, or reducing failed-payment churn. Trigger keywords: cancel flow, churn reduction, save offers, dunning, exit survey, payment recovery, win-back, involuntary churn, failed payments, cancel page. NOT for customer health scoring or expansion revenue — use customer-success-manager for that.

How do I install it?

Run `npx skills add alirezarezvani/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 alirezarezvani/claude-skills, a repository with 23,791 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.

Keep going