Customers Churned
Count of customer logos that ended their subscription/contract during the period. Includes voluntary cancellations and non-renewals. Some companies separately track downgrade-to-zero as churn — be explicit about whether downgrades that drop ARR to $0 count as churn (typical: yes) vs. material contraction that keeps ARR > 0 (typical: tracked under contraction, not churn). The board reads this as the raw count behind `logo_churn_rate`; the percentage tells you the rate, the absolute count tells you the volume of CS pain. Common pitfall: counting customers that re-activate (sometimes called "boomerang" or resurrection) — settle the rule (typical: count each cancellation event, do not net resurrection). — Customers KPI, I'mBoard-authored (editorial tier).
I'mBoard-authored (editorial tier)
No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.
Rogue ID: customers.customers_churned
Type: Number
Domain: Customers
Definition
Count of customer logos that ended their subscription/contract during the period. Includes voluntary cancellations and non-renewals. Some companies separately track downgrade-to-zero as churn — be explicit about whether downgrades that drop ARR to $0 count as churn (typical: yes) vs. material contraction that keeps ARR > 0 (typical: tracked under contraction, not churn). The board reads this as the raw count behind logo_churn_rate; the percentage tells you the rate, the absolute count tells you the volume of CS pain. Common pitfall: counting customers that re-activate (sometimes called "boomerang" or resurrection) — settle the rule (typical: count each cancellation event, do not net resurrection).
Formula
customers_churned = count of customer logos that ended their paid subscription/contract during the period. Voluntary cancellations + non-renewals. Downgrade-to-$0 typically counts; document the rule and hold it constant.Why it matters
The absolute volume read on customer loss. The percentage (logo_churn_rate) tells you the rate; the count tells you the CS team load and the number of post-mortem conversations needed.
How to interpret
No citation-grade absolute benchmark exists — the right comparison is to the company's own trailing periods and to its starting logo count. Pair with logo_churn_rate for proportional context and with churn_risks for the qualitative narrative. A spike with stable rate means the install base grew; a spike with rising rate is a quality signal — both deserve a board comment.
Related KPIs
customers.logo_churn_ratecustomers.logo_retention_ratecustomers.total_customerscustomers.churn_risks
Source
I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.
Stage relevance
| Company stage | Priority |
|---|---|
| Series A | Recommended |
| Series B | Recommended |
| Series C+ | Recommended |
| Public | Recommended |
Suggested for stages: Series A, Series B, Series C+, Public.
Default owning functions
- Sales
Machine-readable
- This KPI as JSON:
/api/ontology/customers/customers_churned.json - All Customers KPIs:
/api/ontology/customers.json - Full catalog:
/api/ontology/index.json
Churn Risks
Named at-risk accounts, root-cause analysis of why they're at risk, and the mitigation plan in flight. Pairs with the quantitative `arr_at_risk` and `percent_arr_at_risk` and gives the board the names + the playbook. Common pitfall: listing the at-risk accounts without the diagnosis or the plan — the board reader needs to see what the team is doing about it, not just what the team is worried about. Also: avoid using this surface as a generic "things are bad" venting forum — keep it account-specific and action-specific. — Customers KPI, I'mBoard-authored (editorial tier).
Expansion Opportunities
Identified upsell, cross-sell, and seat-expansion opportunities inside the existing customer base, with deal size and timing where known. This is the qualitative narrative behind the expansion component of NRR — what the CS / Sales team sees in the pipeline that has not yet converted. The board reads this as forward-looking signal on whether NRR will trend up or down next quarter. Common pitfall: confusing "opportunities" (real conversations with named accounts) with "addressable upside" (theoretical TAM uplift) — keep this field anchored in actual pipeline. — Customers KPI, I'mBoard-authored (editorial tier).