---
title: "Churn reason codes: definition and how to analyze churn"
url: https://renewalfix.com/glossary/churn-reason-codes/
description: "What churn reason codes are, a reason list with owning teams, a worked example of churn analysis by reason, and the mistakes that make the data useless."
updated: 2026-11-03
---

Glossary

# Churn reason codes

Churn reason codes are a fixed list of categories used to record why each customer left or downgraded, so lost revenue can be added up by cause and given to an owning team.

## Formula

```
Share of lost ARR for a reason = lost ARR with that reason ÷ total lost ARR
```

Count churned and downgraded [ARR](https://renewalfix.com/glossary/annual-recurring-revenue/) 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](https://renewalfix.com/glossary/gross-revenue-retention/) 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](https://renewalfix.com/guides/board-retention-report/) 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](https://renewalfix.com/product/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](https://renewalfix.com/topics/churn/).

---

Horizon is renewal risk software for Customer Success teams. Book a call: https://calendar.chilipiper.com/book/me/serban-goanta
