Guide

Revenue Churn vs Customer Churn: Logo and MRR Metrics Explained

Your billing export shows forty customers canceled this month. Your finance lead reports 3.3% customer churn. Someone else says lost MRR was $9,900. Those statements are not contradictory — they are measuring different things. Customer churn (logo churn) counts accounts. Revenue churn weights exits by how much those accounts paid.

This guide defines both metrics for subscription SaaS, gives standard formulas with the caveats that actually change the number, and explains when logo and revenue churn move in opposite directions. It stays at the company-metrics layer: what you compute from billing or CRM exports before you optimize a cancel flow.

If you already run a voluntary cancellation flow and want to rank reasons by revenue impact from session data, that workflow lives in customer churn analysis. If you are still mixing voluntary cancels with failed payments in one churn figure, start with voluntary vs involuntary churn before interpreting either metric.

Last updated October 13, 2026

Customer churn vs revenue churn — definitions

Annual or multi-year contracts can use ARR instead of MRR in the same formulas — keep one revenue unit consistent within a report.

TermAlso calledWhat it measures
Customer churnLogo churn, account churnHow many customer accounts left in a period (each account counts equally)
Revenue churnMRR churn (when you bill monthly)How much recurring revenue left in a period (each dollar counts equally)
Lost MRRChurned MRRSum of recurring revenue from subscriptions that ended in the period

Formulas (and what trips teams up)

Customer churn rate (logo churn rate)

For a calendar month with monthly subscriptions, a common form is:

  • Define “lost” consistently — usually canceled or not renewed, not merely past-due unless that is your policy
  • Pick a single population: active paying customers at period start, not trials unless you report trial churn separately
  • Annualizing a monthly rate (for example compounding twelve months) is a separate choice — label it clearly on board slides
Customer churn rate = Customers lost in period ÷ Customers at start of period

Revenue churn and gross MRR churn rate

Lost MRR is the sum of recurring revenue from accounts that churned in the period. Gross MRR churn rate compares that loss to the revenue base at period start:

Net MRR churn and net revenue retention subtract expansion from existing customers. See gross vs net revenue churn and net revenue retention (NRR). They are not the same as logo churn.

Gross MRR churn rate = Lost MRR in period ÷ MRR at start of period

When logo churn and revenue churn diverge

The gap between the two metrics is diagnostic. Below are illustrative patterns — not ChurnIntel customer data.

PatternLogo churnRevenue churnTypical interpretation
Many small accounts leaveHighModerate or lowOnboarding, fit, or self-serve pricing — volume problem more than whale loss
Few large accounts leaveLowHighRelationship, enterprise gap, or concentration risk — few logos dominate MRR
Price increase monthCan spikeMay look healthierSmaller accounts churn; remaining base pays more — read both metrics together

Which metric for which audience

  • Product and CS weekly reviews — logo churn by segment surfaces activation and fit issues quickly
  • Finance and board — gross MRR churn and lost MRR anchor revenue planning
  • Retention prioritization — use MRR when deciding what to fix first; use logo count when the issue is clearly volume at an entry tier

Do not blend churn types in one number

Customer churn and revenue churn describe how much you lost, not why. Voluntary cancels, failed payments, and deliberate downgrades belong in different operational buckets. Reporting one blended churn rate hides whether you have a product problem, a payments problem, or a pricing problem.

Classify exits first, then compute logo and revenue churn within each type where sample size allows. See voluntary vs involuntary churn for Stripe-oriented classification patterns.

From company metrics to cancel-flow analysis

Company-level logo and MRR churn tell you how much left. They do not tell you which stated reasons or save offers drove the loss. Once you capture reasons in a voluntary cancel flow, you need a second layer: reason share by count versus reason share by lost MRR, offer acceptance, and segmentation by plan.

That session-level methodology — including how priorities change when count rank and MRR rank disagree — is documented in customer churn analysis. ChurnIntel’s churn analytics product focuses on MRR-ranked reasons from voluntary cancellation sessions, not on computing company-wide NRR for you.

See which cancellation reasons cost the most MRR

ChurnIntel ranks voluntary cancel reasons by revenue impact from your in-app flow — so product decisions follow MRR, not just logo count.