Downgrade ARR

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

Definition

Annualized recurring revenue lost from existing customers who reduced spend mid-term or at renewal (seat reductions, tier downgrades, removed modules) — without leaving entirely. The "contraction" line of the ARR waterfall, distinct from full churn. Often a more sensitive leading indicator than churn because customers tend to contract before they cancel. Common pitfall: lumping downgrades into churn obscures the early-warning signal — boards looking only at logo churn miss the slow-bleed pattern. Surfaces in the KpiVarianceTable widget alongside expansion and churn so the net-retention math is auditable.

Formula

Downgrade ARR = Sum across existing customers of (ARR at period start − ARR at period close) for the subset where the delta is positive AND the customer's ARR did not drop to zero. Customers whose ARR drops to zero count in Churned ARR instead.

Why it matters

Earliest leading indicator of retention risk — customers usually contract before they cancel, so a rising downgrade line predicts churn 1–2 quarters out. Inputs NRR (subtracts from expansion) and CCO/CS comp models that gate on Net Retention.

How to interpret

Downgrade ARR rising as a share of expansion ARR over 2+ quarters is the canonical leading signal of a renewal-cycle problem. There is no widely-published cross-company benchmark for downgrade rates as a standalone — read it in context of NRR (industry folk-wisdom: a healthy SaaS company with NRR ≥ 110% typically has downgrade ARR ≤ 3% of starting ARR per period).

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

• Sum across existing customers of (period-start ARR − period-end ARR) where the delta is positive AND the customer's ARR did not drop to zero.
• Includes seat reductions, tier downgrades, removed modules/products, and renewal-time contractions.

Exclusion rules

• Customers whose ARR dropped to zero — those are full churn (sales.churn_arr), not downgrades.
• New-logo deals and expansions — positive-delta customers do not appear here.
• Contractual price decreases that were pre-agreed in the original contract (rare, but disclose if present).

Required inputs

• Customer-level ARR snapshot at period start.
• Customer-level ARR snapshot at period end.
• Per-customer churn flag (to separate full churn from contraction).

Data-source priority

• Customer-level ARR ledger (same source as expansion / churn / NRR).
• CRM contract changelog as a fallback.

Edge cases

• Customer downgrades one product and expands another in the same period: net the per-customer delta; if negative, it counts here; if positive, it counts in expansion.
• Renewal at a lower price after a discount expires: count the reduction as a downgrade.
• Customer contracts to zero: that is churn, not a downgrade — even though it "feels" like the extreme downgrade.

Validation checks

• Downgrade ARR ≥ 0 always.
• NRR = (Starting ARR + Expansion − Downgrades − Churn) / Starting ARR — downgrades and churn together must reconcile the waterfall.
• Per-customer downgrade ≤ that customer's period-start ARR.

Common miscomputations

• Lumping downgrades into churn — destroys the leading-indicator signal; customers usually contract 1-2 quarters before they cancel.
• Counting a contract-to-zero as a downgrade — it is churn; mixing the two corrupts both GRR and the churn line.
• Netting downgrades against same-customer expansion and reporting only the net — both gross lines are needed for the waterfall.
• Missing renewal-time downgrades because the system only captures mid-term amendments — renewal contractions are the larger share for most SaaS.

Related KPIs

• sales.expansion
• sales.churn_arr
• sales.arr
• customers.net_revenue_retention
• customers.gross_revenue_retention

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: Series A, Series B, Series C+, Public.

Default owning functions

• Sales

Machine-readable

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