churn-analysis

Reconstruct churn signal timelines and derive evidence-based root causes.

58|21|Updated May 15, 2026
One-click install
npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill churn-analysis-t0ddc3by
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churn-analysis
Source: https://github.com/t0ddc3by/claude-for-customer-success/tree/main/renewals/skills/churn-analysis
Command: npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill churn-analysis-t0ddc3by

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It performs root-cause analysis for a closed churn or contraction event by reconstructing the signal timeline, categorizing why the churn occurred, and capturing lessons for preventing similar losses.

Core Features & Use Cases

  • Post-loss timeline reconstruction: Builds a chronological table of signals, when they first appeared, when they were noticed, and what actions were taken.
  • Evidence-based root cause categorization: Assigns a primary root cause and up to two contributing factors using a configured taxonomy and specific timeline evidence, with explicit confidence labeling.
  • Response adequacy diagnostics: Evaluates whether monitoring, escalation timing, and save strategy were appropriate based on what was visible at the time.
  • Portfolio pattern scan (optional mode): Searches active accounts for matching signal patterns to identify where similar churn drivers may be present.

Quick Start

Run /renewals:churn-analysis Acme Corp --quick to get an abbreviated root cause, key lessons, and whether a portfolio scan should be performed.

Frequently Asked Questions about churn-analysis

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

FAQPage Schema
How do I find the root cause of customer churn after losing an account?

To find the root cause of customer churn, reconstruct the signal timeline to derive an evidence-based explanation for the closed contraction event. This categorizes the primary driver and contributing factors using specific timeline evidence.

How does a post-mortem churn analysis evaluate if our response was adequate?

A post-mortem churn analysis evaluates response adequacy by assessing whether monitoring, escalation timing, and save strategy were appropriate based on what signals were visible at the time. This diagnostic identifies gaps in your customer success workflow.

Can I scan my active renewal portfolio for accounts showing similar churn risks?

Yes, you can scan your active renewal portfolio for matching signal patterns to identify where similar churn drivers may be present. This optional portfolio scan mode searches active accounts to prevent similar losses across your book.

What pre-flight configuration is required for root cause churn analysis?

Root cause churn analysis requires pre-flight configuration from churn-signal and escalation fields before processing. This setup ensures timing and confidence guardrails are enforced and structured lessons are accurately generated.

What is the time limit for running a post-mortem analysis on a closed churn event?

Post-mortem analysis applies to closed churn or contraction events within about 30 days of churn confirmation. Analyzing events outside this window limits the accuracy of the reconstructed signal timeline and evidence-based categorization.

Can I run a quick batch churn analysis on multiple lost accounts?

Yes, you can run a quick batch churn analysis on multiple lost accounts using the abbreviated mode. This provides a rapid root cause, key lessons, and a recommendation on whether a full portfolio scan should be performed.