I'mBoardDocs
Board OntologyCustomers

Logo Churn Rate

Share of customer logos lost during the period — the inverse of logo retention. Numerator is logos that churned during the period; denominator is logos present at period start. Per the KBCM/Sapphire Private SaaS Company Survey definition (treated as the de-facto private-SaaS reporting convention). The board reads this as the simplest churn signal — independent of revenue-weighting. Common pitfall: confusing annualized vs. period-rate (monthly churn × 12 ≠ annualized churn for a compounding base) — be explicit about the time window and annualization method. — Customers KPI anchored to KBCM/Sapphire SaaS Survey 2024 (15th Annual).

Rogue ID: customers.logo_churn_rate Type: Percentage (%) Domain: Customers

Definition

Share of customer logos lost during the period — the inverse of logo retention. Numerator is logos that churned during the period; denominator is logos present at period start. Per the KBCM/Sapphire Private SaaS Company Survey definition (treated as the de-facto private-SaaS reporting convention). The board reads this as the simplest churn signal — independent of revenue-weighting. Common pitfall: confusing annualized vs. period-rate (monthly churn × 12 ≠ annualized churn for a compounding base) — be explicit about the time window and annualization method.

Formula

logo_churn_rate = customers_churned ÷ (customers active at period start). Mathematically: 1 − logo_retention_rate. Annualization for monthly/quarterly rates should be explicit (e.g. (1 − monthly_retention)^12, not monthly_churn × 12).

Why it matters

Direct read on whether customers are walking away. Independent of revenue-weighting, so it cannot be masked by a few large expansions.

How to interpret

Per KBCM/Sapphire Private SaaS Company Survey 2024 (§ "Customer Churn"), private SaaS logo churn typically sits in the high single digits annually, with top-quartile below 5% — but distributions are highly sensitive to ACV cohort (low-ACV SMB SaaS routinely sees 20%+ annual logo churn; six-figure enterprise contracts often see <3%). Pull the current vintage rather than citing a stale point estimate. Pair with customers_churned (absolute count) and gross_revenue_retention (revenue-weighted view).

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

  • Numerator: count of logos that churned (fully left) during the period.
  • Denominator: count of logos active at period start (the closed starting cohort).
  • Result is a percentage; the exact complement of customers.logo_retention_rate.

Exclusion rules

  • Net-new logos acquired in-period — not in the denominator.
  • Downgrades / contractions where the logo remains — this is a count-of-departures metric, not a revenue one.
  • Trials / pilots that never converted.

Required inputs

  • Count of churned logos in the period.
  • Count of logos active at period start.
  • Time window + annualization method (state explicitly).

Data-source priority

  • Customer-level subscription ledger with churn events.
  • CRM as a fallback.

Edge cases

  • Annualizing a monthly or quarterly rate: use 1 − (1 − periodic_churn)^periods (geometric), NOT periodic_churn × periods (arithmetic). The two diverge materially as churn rises.
  • Account merger: the absorbed logo is not churn — the relationship continued.
  • Reactivation within the period: if the logo is active at period end, it is retained, not churned. Disclose if reactivations are material.
  • ACV-cohort mixing: blended logo churn is misleading when SMB and enterprise are pooled — SMB routinely 20%+, enterprise <3%. Segment when material.

Validation checks

  • Logo Churn Rate + Logo Retention Rate = 100% exactly.
  • Bounded 0–100%.
  • Churned-logo count ≤ starting-cohort count.

Common miscomputations

  • Annualizing via monthly_churn × 12 instead of the geometric 1 − (1 − monthly_retention)^12 — overstates annual churn, badly so when churn is high.
  • Confusing logo churn with revenue churn — they diverge; logo churn cannot be masked by expansion, revenue churn can.
  • Using period-end logo count as the denominator — the cohort must be fixed at period start.
  • Counting account mergers or contractions as churn — only full departures count.
  • Reporting a blended rate across wildly different ACV cohorts without segmenting — the blend is not actionable.
  • customers.logo_retention_rate
  • customers.customers_churned
  • customers.gross_revenue_retention
  • customers.net_revenue_retention
  • customers.churn_risks

Source

KBCM/Sapphire SaaS Survey 2024 (15th Annual) · section: Logo Churn — published 2024-09-01.

Why does this cite KBCM/Sapphire SaaS Survey 2024 (15th Annual)? Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.

Industry benchmark

A reference distribution sourced from KBCM/Sapphire SaaS Survey 2024 (15th Annual) (2024):

PercentileValue
25th5%
Median13%
75th20%

Lower is better.

Stage relevance

Company stagePriority
Series ACore
Series BCore
Series C+Core
PublicCore

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

Default owning functions

  • Sales

Machine-readable

On this page