Formula
Count churned and downgraded ARR together, and give each loss one primary reason so the shares add up to 100%.
Worked example
A company lost $1,200,000 ARR to churn and downgrades in a year. (Example numbers.)
| Reason | Owning team | Lost ARR | Share |
|---|---|---|---|
| Went dark | Customer Success | $360k | 30% |
| Low adoption | Customer Success | $300k | 25% |
| Competitors and product gaps | Product | $240k | 20% |
| Commercial pressure | Account management | $180k | 15% |
| Outside our control (M&A, shutdowns) | Leadership | $120k | 10% |
| Total | $1.2M | 100% |
Here 55% of lost ARR (30% + 25%) sits with reasons Customer Success owns, which tells the VP where the next quarter's plan should start.
How CS leaders use it
Churn analysis by reason turns a GRR number into a plan. Bring the table to the board with an owner per reason, then add how much of each reason was preventable and how early the first warning appeared. The board retention report guide has a slide outline. Horizon splits lost revenue into nine reasons, each with an owning team, and a second model checks the AI loss reviews; see retention reporting.
Common mistakes
- A long list nobody uses the same way. Keep it short and define each code.
- Taking the stated reason at face value. "Price" can be the reason a customer gives when the cause is low adoption or a lost champion, so check the evidence.
- No "Unknown" code. Track it and keep it small, so missing data shows instead of being guessed.
- Coding losses months later from memory. Record the reason, with evidence, when the loss happens.
More on this topic: churn, definitions, guides and tools.
Updated November 3, 2026