churn-prevention

Design cancel flows, save offers, and dunning for SaaS subscriptions.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/cristian473/ps-landing-2 --skill churn-prevention-cristian473
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churn-prevention
Source: https://github.com/cristian473/ps-landing-2/tree/main/.agents/skills/churn-prevention
Command: npx skills add https://github.com/cristian473/ps-landing-2 --skill churn-prevention-cristian473

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Churn-prevention helps reduce both voluntary churn (cancellations) and involuntary churn (failed payments) by designing effective cancel flows, dynamic save offers, proactive retention, and dunning strategies. It guides teams on how to collect meaningful cancellation feedback, tailor offers to reasons, and orchestrate post-cancel win-back.

Core Features & Use Cases

  • Cancel flow design: trigger, survey, dynamic offer, confirmation, and post-cancel steps to recover value
  • Dynamic save offers matched to cancellation reasons (discounts, pauses, downgrades, roadmap communication, etc.)
  • Dunning and payment-recovery workflows with smart retries and automated emails
  • Proactive health scoring and segmentation to identify at-risk users early
  • Post-cancel win-back sequencing to re-engage former customers

Quick Start

Identify your churn drivers and implement a baseline cancel flow with one save offer and a four-step dunning sequence

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 recovers users before they churn?

A SaaS cancel flow reduces churn by following a Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel sequence. It collects cancellation feedback and tailors save offers to the user's specific reason for leaving.

What is the difference between voluntary and involuntary churn in SaaS subscriptions?

Involuntary churn happens when recurring billing fails due to expired cards or payment errors, while voluntary churn occurs when users actively cancel. This skill addresses both by implementing automated dunning workflows and dynamic save offers.

How do I set up dunning workflows to recover failed subscription payments?

Dunning workflows recover failed payments by automating smart retry schedules and targeted email sequences. This skill guides you in configuring payment-recovery automation with provider integrations to reduce involuntary churn.

Can I use this approach for both self-serve and enterprise SaaS billing models?

Yes, this approach applies to both self-serve and enterprise SaaS environments. It supports monthly and annual billing cycles, handling proactive retention, segmentation, and dunning across different subscription structures.

What are the best save offers to match different cancellation reasons?

Effective save offers match the cancellation reason, including targeted discounts, account pauses, plan downgrades, or roadmap communication. This skill helps you tailor these dynamic offers to address specific user concerns during the cancel flow.

How does proactive health scoring identify at-risk SaaS users before they cancel?

Proactive health scoring identifies at-risk users early by analyzing engagement and usage patterns to segment accounts. This allows you to trigger retention flows and win-back sequencing before voluntary churn occurs.