Logo churn vs. revenue churn: why SaaS teams need to track both.

Your customer success dashboard says churn is fine this month. Two customers canceled out of a base of 200, a 1% logo churn rate that would make most SaaS boards happy. Meanwhile finance is asking hard questions, because one of those two customers was your fourth-largest account, and revenue churn for the same month just hit 4%. Nobody on either team is lying. They're both reading the same event through a different lens, and if only one of those lenses reaches leadership, someone is going to make a decision on incomplete information.

Quick answer

Logo churn measures the percentage of customers who cancel in a period, treating a $50/month account and a $50,000/month account as the same one customer. Revenue churn measures the percentage of recurring revenue lost in that same period, weighted by contract value. They diverge whenever the customers who leave aren't the same size as the customers who stay or expand, which in B2B SaaS is most of the time. A business needs both numbers, tracked together and reconciled against the same billing data, to know whether it's actually losing accounts, losing dollars, or both.

What logo churn and revenue churn actually measure

Logo churn, sometimes just called customer churn, counts accounts. The formula is the number of customers lost in a period divided by the number of customers at the start of that period. A company with 100 customers at the start of the year that lost 5 over twelve months has 5% annual logo churn. Every customer counts as one unit regardless of what they pay, which is exactly why the metric is easy to calculate and easy to misread.

Revenue churn counts dollars. Gross revenue churn takes the starting monthly recurring revenue (MRR) of every account that canceled or downgraded during the period and divides it by total starting MRR. It answers a different question: not how many relationships ended, but how much recurring revenue those endings represent. Net revenue churn goes a step further and nets out expansion revenue from existing accounts, which is why a business can post negative net revenue churn (in other words, revenue growth from the existing customer base) even while losing customers.

The two metrics tell the same story only when every customer pays roughly the same amount. In practice, B2B SaaS customer bases are rarely that even. A 10-person startup and a 500-person enterprise account might pay 40 times as much per month for the same product, so a canceled enterprise account can single-handedly wipe out a month of otherwise healthy logo retention.

Why the two numbers pull apart

Three patterns explain most of the divergence between logo churn and revenue churn:

Concentration in the customer base. If the top 10% of accounts by contract value generate half of total MRR, then losing even one of those accounts moves revenue churn far more than it moves logo churn. This is normal in usage-based and tiered pricing models, where a handful of large accounts can represent a disproportionate share of revenue.

Segment-specific churn behavior. Self-serve or SMB segments typically churn more accounts, but at a lower dollar value per loss, while enterprise segments churn fewer accounts at a much higher dollar cost per loss. A business selling into both segments needs to break out churn by segment, not just report a single blended number, or it will consistently misjudge where the actual risk sits.

Expansion offsetting logo losses. A company can lose accounts and still show flat or improving revenue churn if the accounts that stay are expanding fast enough to cover the gap. This is common in product-led or seat-based pricing, where existing customers grow their usage even as some smaller accounts churn out. It's also exactly the scenario that makes a single "churn rate" headline dangerous: it can hide a shrinking customer base behind a growing revenue line, which eventually catches up once expansion slows.

Why tracking only one number creates blind spots

A team that only watches logo churn misses revenue risk concentrated in its biggest accounts. Everything can look calm on the customer-count dashboard while a handful of large renewals quietly wobble, and by the time revenue churn spikes, there's no early warning left to act on.

A team that only watches revenue churn misses the erosion happening across the smaller end of the base. Revenue churn can look fine for months while logo churn creeps upward, because expansion from a few large accounts is masking a steadily shrinking customer count. That's a warning sign that tends to show up in usage and engagement data well before it shows up in the revenue number, which is one reason churn analysis works better when it pulls from billing, usage, and account data together rather than one system in isolation.

This is also where the reactive-versus-predictive gap tends to show up. Most teams review churn once a month, after invoices have already run and cancellations have already happened. By the time the monthly report flags a problem, the accounts involved have usually already made their decision. Reviewing logo churn and revenue churn side by side, continuously, against live billing and usage data rather than a lagging monthly export, is what turns churn reporting from a postmortem into an early-warning system. This is the specific gap Revvly's real-time MRR, ARR, and NRR dashboards are built to close: both metrics pulled from the same subscription and billing records, broken out by segment, updated as accounts change rather than reconstructed at month-end, with AI-powered churn prediction flagging accounts where usage or payment behavior suggests risk before a cancellation shows up in either number.

A practical way to reconcile the two metrics

Segment before you average. Break both logo churn and revenue churn out by customer size, plan tier, or region before looking at the blended company-wide number. A blended average can look acceptable while a specific segment is bleeding.

Look at both on the same time axis. Logo churn and revenue churn should be reviewed for the same period, on the same cadence, ideally monthly for month-to-month subscriptions and by contract term for annual ones. Comparing a monthly logo churn figure against a trailing-twelve-month revenue churn figure will produce numbers that look disconnected because they're measuring different windows, not different problems.

Separate voluntary from involuntary churn in both metrics. A cancellation from a customer choosing to leave is a different problem than a failed payment causing an involuntary cancellation. Recurly's research puts the overall churn rate across subscription businesses at 3.27%, split roughly into 2.41% voluntary and 0.86% involuntary, with B2B software and professional services businesses averaging around 3.8% churn compared to roughly 6.5% for more consumer-oriented subscription categories. Involuntary churn is a billing and dunning problem with a fairly mechanical fix; voluntary churn is a product and retention problem that needs a different response.

Benchmark revenue retention, not just churn. Gross revenue retention (GRR) measures the revenue kept from existing customers before counting any expansion, while net revenue retention (NRR) adds expansion back in.

SaaS Capital's 2026 survey of more than 1,000 private B2B SaaS companies found bootstrapped companies with $3M to $20M in ARR posting median GRR of 91% and median NRR of 103%, with the top decile reaching 100% GRR and 117.9% NRR. A company sitting well below its peer GRR benchmark, even with strong logo retention, usually has a revenue-concentration problem worth investigating before it shows up as a headline churn number.

Connect churn analysis to the same source of truth as billing. When customer success tracks logo churn in one tool, finance tracks revenue churn in a spreadsheet built from a billing export, and neither reconciles against the other on a regular basis, the two numbers drift and nobody notices until a board meeting forces the question. Keeping the full subscription lifecycle, from signup through cancellation, in one system where both metrics are calculated from the same underlying data removes that drift entirely.

Managing both metrics without two disconnected dashboards

Most subscription businesses end up here by accident rather than design: a CS platform reports customer-level churn, a billing tool or spreadsheet reports revenue churn, and someone manually reconciles the two before a leadership review. That works at a small scale. It breaks down once contract sizes diverge or the customer base spans self-serve and enterprise segments, because reconciling two exports by hand is exactly the kind of process that quietly falls out of date.

A subscription intelligence platform that unifies billing, revenue analytics, and customer engagement data removes the reconciliation step by calculating both metrics from the same subscription records in the first place. Revvly's real-time MRR/ARR/NRR dashboards break out revenue churn and logo churn by segment, plan, and region from live billing data, while its AI-powered churn prediction layer flags accounts showing early risk signals, whether that risk is concentrated in high-value accounts or spread across the smaller end of the base, before it shows up as a cancellation in either metric.

Frequently asked questions