churn-analysis

Solid

Analyse customer churn for a product or cohort and produce a structured churn report. Use when asked to analyse churn, understand why customers are leaving, identify churn patterns, calculate churn rate, or build a churn reduction plan. Produces a churn analysis with rate calculations, categorised reasons, early warning signals, and prioritised interventions.

Data & Documents 915 stars 165 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Churn Analysis Skill Produce a structured churn analysis that goes beyond the headline rate — identifying why customers leave, which segments are most at risk, and what interventions will have the highest impact on retention. ## Required Inputs Ask for these if not already provided: - **Time period** being analysed (e.g. Q1, last 12 months) - **Total customers at start of period** and **customers churned** - **ARR or revenue lost** to churn - **Churn reasons data** — exit survey results, CSM notes, support data, or sales loss reasons - **Customer segments** — by tier, industry, cohort, or product line - **Current retention rate** if known - **Any recent changes** — pricing, product, support model — that may have affected churn ## Churn Categories Always classify churn before analysing it: | Category | Definition | |---|---| | **Voluntary — avoidable** | Customer left due to a problem we could have addressed (product gaps, poor onboarding, relationship failures) | | **Voluntary — unavoidable** | Customer left for reasons outside our control (budget cuts, acquisition, company shutdown) | | **Involuntary** | Payment failure, contract non-renewal by mistake, admin error | The interventions for each category are different. Conflating them leads to wrong conclusions. ## Output Format --- # Churn Analysis: [Product / Segment / Company] **Period:** [Start date] — [End date] **Prepared by:** [Name] | **Date:** [Date] --- ## Headline Numbers | Metric | Value | |---|---| ...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
4 months ago
Last Updated
3 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

churn-analysis-pdca

Guides monthly SaaS customer churn analysis — AI handles data wrangling, SQL execution, and pattern surfacing; human owns interpretation of patterns and all recommendations to leadership. Use this skill whenever working on churn analysis, cohort analysis, retention reporting, or any monthly data analysis cycle that produces leadership-facing recommendations. Triggers on phrases like "churn analysis", "monthly retention report", "cohort data", "churn report for leadership", or "let's do the monthly analysis".

41 Updated 2 days ago
kenjudy
AI & Automation Solid

retention-analysis

Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.

915 Updated 3 days ago
mohitagw15856
DevOps & Infrastructure Listed

churn-risk

Use when the user wants to assess customer churn risk — score segments by churn probability, identify at-risk customers, and generate intervention playbooks with recommended actions and timing.

2 Updated today
Faiz07yo
AI & Automation Featured

churn-prevention

Reduce voluntary and involuntary churn with cancel flows, save offers, dunning, win-back tactics, and retention strategy. Use when users are cancelling, failed payments are rising, or subscription retention needs improvement.

39,227 Updated today
sickn33
Web & Frontend Listed

churn-risk-detector

Scan support tickets, Slack channels, NPS scores, and usage patterns to flag accounts showing early churn indicators. Produces a weekly risk scorecard with severity tiers, root cause hypotheses, and suggested save plays per account. Designed for seed/Series A teams where the founder or a single CSM manages all accounts manually.

711 Updated 3 weeks ago
gooseworks-ai