Churn Prevention

Reduces voluntary and involuntary churn by designing cancel flows, building targeted save offers, setting up dunning sequences for failed payments, and collecting exit data. Use when optimizing cancellation experiences, creating payment recovery strategies, or building save offer logic.

skills.sh installs: 604
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill churn-prevention --agent claude-code

Installs into .claude/skills of the current project.

Files

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?