churn-autopsy

Solid

Post-mortem analysis when a client churns. Takes client history, engagement data, support tickets, usage logs, and exit feedback to produce a comprehensive churn autopsy with root cause classification, timeline of decline, and preventive measures.

AI & Automation 288 stars 46 forks Updated 1 months ago MIT

Install

Quality Score: 84/100

Stars 20%

82

Recency 20%

75

Frontmatter 20%

70

Documentation 15%

82

Issue Health 10%

80

License 10%

100

Description 5%

100

Skill Content

# Churn Autopsy Dissect a client departure with forensic rigor and produce `churn-autopsy.md`: a historical record and retention playbook that turns a loss into organizational learning. ## Contents - `references/inputs.md` -- required and optional data to gather before analysis - `references/analysis-framework.md` -- the six-phase forensic method - `references/root-cause-taxonomy.md` -- root cause categories and subcategories - `references/output-template.md` -- full `churn-autopsy.md` report structure - `references/standards.md` -- objectivity, rigor, sensitivity, incomplete-data, and operating rules ## Workflow 1. **Collect.** Gather all available inputs per `references/inputs.md`. Read provided files directly; query connected CRM and analytics MCP tools for account, usage, and support data. Note any gaps. 2. **Organize.** Build the full chronological timeline from first touch to cancellation before attempting analysis. 3. **Analyze.** Apply the six phases in `references/analysis-framework.md` systematically, without skipping: baseline, timeline of decline, root cause classification, missed warning signs, counterfactual analysis, lessons learned. 4. **Classify.** Assign one primary root cause and any contributing causes using `references/root-cause-taxonomy.md`. 5. **Draft.** Write the report in the structure defined in `references/output-template.md`. 6. **Challenge.** Review every conclusion against `references/standards.md`; attempt to disprove each finding before k...

Details

Author: OneWave-AI
Repository: OneWave-AI/claude-skills
Created: 10 months ago
Last Updated: 1 months ago
Language: Python
License: MIT

Integrates with

Anthropic · AI Model Context Protocol · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

churn-postmortem

When a customer has churned, downgraded, or was nearly lost, and the user needs to know why it really happened, when it first became visible in data they already had, and what to change so the next one does not repeat. Also use when the user mentions 'what went wrong', 'accounts we lost', 'why did we lose', 'why did we lose them', 'churn post-mortem', 'loss review', 'post mortem on Acme', 'root cause analysis', 'we lost Northwind', 'they never renewed', 'churn reasons this quarter', 'could we have saved them', 'was it preventable', 'this account was green and churned', 'downgrade analysis', or 'quarterly churn review'. Use this whenever a loss has already happened and someone is trying to learn from it rather than relitigate it, even if they don't say 'post-mortem' — including a save that nearly failed. For live risk on an open account, see churn-risk. For feedback themes across the base, see voice-of-customer. For rebuilding the score this loss defeated, see health-score-designer.

1 Updated 2 weeks ago

AI & Automation Listed

churn-analyst

Finds churn patterns, scores account health from behavioural signals and designs retention interventions. Use when diagnosing why customers leave or building an at-risk model. Not for renewal outreach - use renewal-strategist.

0 Updated 5 days ago

Code & Development Listed

churn-postmortem

Works out why an account actually left, separating the reason the customer gave from the mechanism that caused it, and checks whether the loss was one of a correlated set. Trigger whenever the user says "churn postmortem", "why did we lose them", "post mortem", "churn analysis", "they did not renew", "we lost the account", "what went wrong with", "lessons learned", or names an account in the past tense. Also trigger when several accounts have been lost for the same stated reason, or before a churn review. It reconstructs the timeline, separates the date the account was lost from the date anyone noticed, identifies the earliest signal that was genuinely detectable at the time rather than obvious in hindsight, and asks whether the loss was winnable and when it stopped being so. Runs on whatever record survives and marks what could not be reconstructed.

1 Updated 5 days ago