subscription-churn

Separate voluntary from involuntary subscription churn and prioritize retention interventions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill subscription-churn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subscription-churn
Source: https://github.com/ohsonerdy/openclaw-frontier-stack/tree/main/skills/subscription-churn
Command: npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill subscription-churn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps subscription-product operators reduce both voluntary churn and involuntary churn by diagnosing the dominant driver and prescribing retention actions that address it directly.

Core Features & Use Cases

  • Voluntary vs involuntary churn diagnostics: Separates cancellation intent from failed-payment churn and ranks fixes in the right priority order.
  • Data-driven retrieval (via MCP when connected): Pulls churn split, cancellation reason distribution, dunning recovery rates, and cohort survival curve shape to guide decisions.
  • Playbooks for action: Provides frameworks for dunning retry schedules, cancel-reason taxonomy responses, and save flow architecture (including skip-vs-cancel design and tenure-curve timing).
  • Use Case: If your churn is rising because customers fail to recover after payment issues and your save flow defaults to discounts, this Skill helps you restructure dunning and reason-routed save options to reduce churn without eroding price.

Quick Start

Use the subscription-churn skill when you need to lower churn and I will help you first separate voluntary from involuntary churn, then design the highest-leverage save and dunning changes.

Frequently Asked Questions about subscription-churn

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

FAQPage Schema
How do I diagnose whether subscription churn is voluntary or involuntary?

Diagnosing subscription churn involves separating voluntary cancellations from involuntary failed-payment churn by analyzing churn rate splits, cancellation reason distributions, and dunning recovery rates to identify the dominant driver and prioritize fixes.

What's the best way to design a save flow that reduces subscription cancellations?

Designing a save flow requires routing users based on cancel-reason taxonomy and tenure-curve timing, structuring skip-vs-cancel options to intercept voluntary churn without eroding price through default discounts.

How do I improve dunning recovery rates for failed payments?

Improving dunning recovery requires restructuring retry schedules and payment recovery flows to target involuntary churn, applying framework-based tactics to recover failed transactions before they result in permanent subscription loss.

Can I use cohort survival curves to guide my retention strategy?

Cohort survival curves help guide retention strategy by visualizing tenure-curve timing and drop-off patterns, allowing operators to time interventions and select the highest-leverage retention actions for specific subscriber cohorts.

Why does my churn rate keep rising even after offering discounts in the save flow?

Churn rates rise when save flows default to discounts instead of addressing the actual cancellation reason taxonomy or involuntary dunning failures, requiring a restructured approach that matches interventions to the diagnosed churn driver.

Do I need MCP-backed queries to analyze subscription churn drivers?

MCP-backed queries are required to pull churn rate splits, cancellation reasons, dunning recovery rates, and cohort survival data needed to produce an operator-ready action plan with testable retention changes.