churn-prevention

Design cancel flows and dunning systems for subscription SaaS businesses.

5|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/barkleesanders/claude-code-starter --skill churn-prevention-barkleesanders
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churn-prevention
Source: https://github.com/barkleesanders/claude-code-starter/tree/main/skills/churn-prevention
Command: npx skills add https://github.com/barkleesanders/claude-code-starter --skill churn-prevention-barkleesanders

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the critical revenue loss SaaS businesses face from both voluntary churn (customers choosing to cancel subscriptions) and involuntary churn (failed payments), eliminating guesswork with proven, data-backed retention frameworks.

Core Features & Use Cases

  • Voluntary Churn Reduction: Design multi-step cancel flows with exit surveys and dynamic save offers matched to cancellation reasons, plus proactive health scoring to identify at-risk users before they cancel.
  • Involuntary Churn Recovery: Implement full dunning stacks with pre-dunning alerts, smart payment retries, and escalating email sequences to recover 50-60% of failed payments.
  • Retention Strategy Optimization: Access industry-specific cancel flow patterns, A/B testing frameworks, and compliance guidance for regulations like the FTC Click-to-Cancel rule. For example, a 2,000-customer SaaS with 7% monthly churn can use this Skill to build a cancel flow that saves 25-35% of at-risk subscribers and cut involuntary churn from 15% to under 2%.

Quick Start

Use the churn-prevention skill to design a cancel flow for our $49/month project management tool that reduces voluntary churn and sets up dunning emails to recover 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 SaaS cancel flow that reduces voluntary churn?

Design a SaaS cancel flow to reduce voluntary churn by implementing multi-step exit surveys and dynamic save offers matched to cancellation reasons. This framework also incorporates proactive health scoring to identify at-risk users before they initiate cancellation.

What is the best way to recover failed payments and reduce involuntary churn?

Recover failed payments and reduce involuntary churn by implementing a full dunning stack. This includes smart payment retry logic, pre-dunning alerts, and escalating email sequences to recover 50-60% of failed transactions.

Can I use health score modeling for B2B and B2C SaaS retention?

Yes, you can use health score modeling for both B2B and B2C SaaS retention. The framework applies proactive churn prediction models to identify at-risk users across different use cases before they decide to cancel.

How do I map save offers to specific cancellation reasons?

Map save offers to cancellation reasons using dynamic offer matching within a multi-step cancel flow. This strategy targets the specific feedback provided in exit surveys to present the most relevant retention incentive.

Does this approach support compliance with FTC Click-to-Cancel regulations?

Yes, this approach supports compliance with cancellation regulations like the FTC Click-to-Cancel rule. The framework provides specific guidance to ensure your cancel flow meets regulatory requirements while optimizing retention.

What dunning email sequence strategy recovers the most failed subscriptions?

An escalating dunning email sequence strategy recovers failed subscriptions by combining pre-dunning alerts with smart payment retries. This structured approach can cut involuntary churn from 15% to under 2%.