Churned ARR

Rogue ID: sales.churn_arr Type: Currency Domain: Sales

Definition

Annualized recurring revenue lost during the period from customers who fully cancelled — terminating their contract or letting it lapse without renewal. The "leak" line of the ARR waterfall and a loss deducted in the numerator of Gross Revenue Retention. Distinct from Downgrade ARR (sales.downgrades) which captures contractions where the customer stays. Common pitfall: lumping mid-term cancellations with non-renewals masks two very different retention failures — surface them separately when material. The KpiVarianceTable widget tracks period forecast vs actual; a widening miss against forecast is the earliest signal of a retention problem.

Formula

Churned ARR = Sum of ARR from contracts that terminated during the period (cancelled mid-term or not renewed at the end of term) attributable to customers whose ARR with the company drops to zero. Store a non-negative loss magnitude: 5 means 5 lost, contributing a waterfall delta of −5. Excludes contractions where the customer remains (those land in Downgrade ARR).

Why it matters

Direct read on Gross Revenue Retention (GRR) — the floor of the retention math, since downgrades and churn cannot be offset by upsell in GRR. A board can tolerate slow new-logo growth if churn is low, but cannot tolerate high churn at any growth rate — it compounds against valuation.

How to interpret

Per KBCM/Sapphire SaaS Survey 2024 §Gross Revenue Retention, top-quartile SaaS companies hold GRR ≥ 90% (enterprise-segment) or ≥ 85% (SMB-segment); GRR below 80% in either segment usually means the product or onboarding has a structural problem, not a sales-execution one. Pair this line with the Customers domain to identify whether churn concentrates in a particular segment or cohort.

Calculation policy

How an AI agent should compute this KPI from messy company data. Free-text rules consumed at reasoning time — not a deterministic DSL. The most common ways to get this wrong are listed under Common miscomputations.

Inclusion rules

• Annualized ARR of contracts that terminated during the period such that the customer's total ARR with the company drops to zero.
• Both mid-term cancellations and non-renewals count.
• Use the customer's ARR at the most recent live period close as the churned amount (don't pro-rate the partial period of service).

Exclusion rules

• Contractions where the customer remains (seat reductions, tier downgrades) — those are sales.downgrades.
• New-logo failures (customer signed but never went live and was refunded) — these were never ARR and don't belong in churn.
• Pause / suspension if the contract is still open with a defined return SLA — flag separately as "paused ARR" rather than churned.

Required inputs

• Customer-level ARR snapshot at period start.
• Customer-level termination dates and cancellation reason codes if available.
• Distinction between mid-term cancellation and non-renewal (these are often surfaced separately on board packs).

Data-source priority

• Customer-level ARR ledger with churn events.
• CRM opportunity / renewal stages as a fallback.

Edge cases

• Customer terminates one product but keeps another: the per-customer ARR delta is negative but non-zero — that goes in sales.downgrades, NOT churn.
• Customer is acquired by another company and the contract is novated to the acquirer: typically count as retention, not churn (account identity transfers).
• Bankruptcy / non-payment write-offs: count as churn from the date the contract is voided.
• Mid-term cancellation with a non-cancellable balance still due: still count as churn from the cancellation effective date; the unpaid balance is an AR issue, not an ARR one.

Validation checks

• Churned ARR ≥ 0 always.
• GRR = (Starting ARR − Churned − Downgrades) / Starting ARR. Bounded at 100% — recompute if violated.
• Per-customer churned amount ≤ that customer's period-start ARR.

Common miscomputations

• Lumping downgrades and churn into a single "churn" number — masks the contraction-vs-cancellation signal that the waterfall exists to reveal.
• Counting customers who never went live (refunded new logos) as churn — they were never ARR.
• Using cancellation-request date instead of contract-end date for the period attribution — produces phantom churn in the request quarter and missing churn in the actual cancellation quarter.
• Treating "paused" customers as churned (or vice versa) — pick a convention and apply it; mid-stream policy changes corrupt the trend.
• Forgetting to remove the customer from the starting-cohort base for the next period — produces double-counting in the next quarter's retention math.

Related KPIs

• sales.arr
• sales.downgrades
• sales.expansion
• customers.gross_revenue_retention
• customers.net_revenue_retention
• customers.logo_retention_rate
• customers.logo_churn_rate

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

Suggested for stages: Pre-Seed, Seed, Series A, Series B, Series C+, Public.

Default owning functions

• Sales

Machine-readable

• This KPI as JSON: /api/ontology/sales/churn_arr.json
• All Sales KPIs: /api/ontology/sales.json
• Full catalog: /api/ontology/index.json