Retention & Unit Economics

Logo Churn vs Revenue Churn in SaaS

Compare customer-count churn with revenue churn so a SaaS business can distinguish lost logos from the economic weight of the customers that leave.

Last reviewed Oct 7, 2026 Source set reviewed Oct 7, 2026 Next review Apr 7, 2027

Editorial attribution: BizCalcAtlas editorial team. Formula and source provenance follow the published methodology.

Logo Churn vs Revenue Churn in SaaS explains logo churn vs revenue churn with the same definitions and calculation method used by the linked tools. Use the method for a consistent scenario, then verify any current rate, legal rule, or platform policy against the cited source.

Answer in brief

logo churn rate = customers lost during period / customers at start of period gross revenue churn rate = recurring revenue lost from churn and contraction / beginning recurring revenue

Scope and definitions

This guide owns the informational intent; linked calculator pages continue to own interactive calculator intent.

The guide supports Churn Rate Calculator; Net Revenue Retention Calculator; Monthly Recurring Revenue Calculator. Keep the numerator, denominator, cost categories, fee base, and time period consistent from the first input through the final comparison.

Calculation method

Step Calculation or rule
1 logo churn rate = customers lost during period / customers at start of period gross revenue churn rate = recurring revenue lost from churn and contraction / beginning recurring revenue

Formula / rule

logo churn rate = customers lost during period / customers at start of period
gross revenue churn rate = recurring revenue lost from churn and contraction / beginning recurring revenue

Worked example

A company starts with 100 customers and $500,000 MRR. Five customers churn, so logo churn is 5%. Those customers represented $60,000 MRR, producing 12% revenue churn before considering contraction. The lost logos were larger than average.

Practical reference

Record the relevant scenario fields together before calculating. The implementation brief calls for these comparison fields: Metric, Example. Using one record prevents values from different periods or scopes from being mixed.

Common mistakes

  • Using a different definition or time period from the one specified by the logo churn vs revenue churn method.
  • Comparing outputs from Churn Rate Calculator; Net Revenue Retention Calculator; Monthly Recurring Revenue Calculator without holding the shared assumptions constant.
  • Treating a worked scenario as a universal target instead of testing the inputs that apply to the business.
  • Relying on an undated secondary claim when the listed first-party or official source governs a current rate or rule.

Frequently asked questions

Which churn metric should SaaS teams use?

The answer depends on the scenario and assumptions. Use the stated method for logo churn vs revenue churn, then test the result with the linked calculators and verify any current rate or rule against the listed sources.

Can logo churn improve while revenue churn worsens?

The answer depends on the scenario and assumptions. Use the stated method for logo churn vs revenue churn, then test the result with the linked calculators and verify any current rate or rule against the listed sources.

Should downgrades count as logo churn?

The answer depends on the scenario and assumptions. Use the stated method for logo churn vs revenue churn, then test the result with the linked calculators and verify any current rate or rule against the listed sources.

How this guide was created and tested

  • Method basis: the guide uses the same definitions and method boundaries as the linked calculator family and the audited implementation package.
  • Validation coverage: the linked calculators currently contribute 6 audited release test vectors to the underlying calculation methods used by this guide.
  • Source hierarchy: current rates, fees, laws, or platform rules prefer government and first-party sources; educational and industry references are supporting evidence rather than silent overrides.
  • Automation and AI: automation or AI may assist drafting, organization, source grouping, and regression work, but it is not treated as an authoritative source and cannot replace the cited evidence or audited formula.
  • Editorial responsibility: MIASIN S.R.O. controls publication, source policy, corrections, and release decisions. No named individual expert review is claimed unless a page explicitly identifies one.

Read the full Methodology, Editorial Standards, and Corrections Policy.

Sources and review

Sources are ordered by authority: government or official sources first, then first-party platform sources, educational references, and finally supporting industry references.

  • First-party / platform source: Stripe
  • First-party / platform source: Stripe
  • First-party / platform source: Stripe
  • Supporting industry reference: chartmogul.com

Last reviewed: October 7, 2026
Source set reviewed: October 7, 2026
Next scheduled review: April 7, 2027
Review guidance: Recheck cohort definitions, contraction treatment and customer segmentation.