suede-churn-prevention

Designs cancel flows, save offers, and dunning sequences to reduce subscription churn.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-churn-prevention-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-churn-prevention
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-churn-prevention
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-churn-prevention-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Subscription businesses lose revenue to both voluntary churn (customers choosing to cancel) and involuntary churn (failed payments), often without any structured retention process. This Skill provides a complete retention playbook covering cancel flow design, reason-matched save offers, churn prediction signals, and failed-payment recovery. ## Core Features & Use Cases - Cancel Flow Design: Builds the full trigger → exit survey → dynamic save offer → confirmation → post-cancel sequence, with offer-to-reason mapping (discount, pause, downgrade, feature unlock) and UI patterns that avoid dark patterns. - Involuntary Churn Recovery: Implements the dunning stack — pre-dunning card expiry alerts, smart retry schedules by decline type, a four-email dunning sequence, and grace period management for Stripe, Chargebee, Paddle, and Recurly. - Proactive Retention: Defines churn risk signals, a weighted 0-100 health score model, risk tiers, and intervention triggers before customers reach the cancel button. - Use Case: A SaaS product with 7% monthly churn asks for a retention strategy; the Skill designs the cancel flow with exit survey categories, maps save offers per reason, sets up dunning for failed payments, and delivers a phased implementation checklist. ## Quick Start Ask the agent to design a cancel flow and dunning strategy for your subscription product, providing your churn rate, billing provider, and plan structure.

Frequently Asked Questions about suede-churn-prevention

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a cancel flow that saves subscribers?

Structure the flow as trigger, exit survey, dynamic save offer, confirmation, and post-cancel steps. Map each cancel reason to a matching offer — discounts for price concerns, pauses for low usage, downgrades for value mismatch — while keeping the continue-cancelling option clearly visible.

How do I recover failed subscription payments?

Use the dunning stack: pre-dunning card expiry alerts, smart retries on a Day 1/3/5/7/10 schedule matched to decline type, a four-email sequence with escalating urgency, then a grace period before pausing. Card updater services reduce hard declines by 30-50%.

What save offer works best for each cancellation reason?

Match the offer to the stated reason: 20-30% discounts for price sensitivity, 1-3 month pauses for low usage, roadmap previews for missing features, and support escalation for technical issues. Discounts fail when the real problem is engagement, not price.

Does this skill work with Stripe, Chargebee, or Paddle?

Yes, the dunning playbook includes provider-specific setup for Stripe Smart Retries, Chargebee retry settings, Paddle managed dunning, and Recurly revenue recovery. It ships no connectors itself, so you configure your authorized billing system directly.

Can the skill change my billing settings automatically?

No. Before any change to live billing objects — retry rules, discounts, pauses, or cancellations — it halts and requires explicit authorization with a defined rollback path. Inferred consent from a general request is not treated as authorization.

When should I not use this churn prevention skill?

It is out of scope for lifecycle email writing (use suede-emails), pricing architecture (suede-pricing), paywall design (suede-paywalls), and event instrumentation (suede-analytics). It also covers only the merchant side, not consumers disputing their own charges.