Tag: churn

  • What Is Net Revenue Retention? How to Calculate and Improve It.

    Net revenue retention (NRR) is the percentage of recurring revenue you keep from your existing customers over a period, usually 12 months, after counting upgrades, downgrades, and cancellations. It excludes revenue from new customers. An NRR above 100% means your existing base is growing on its own, and below 100% means it is shrinking.

    If your revenue grew 15% last year, a fair next question is how much of that came from customers you already had. NRR answers it. Two companies can post identical growth, but one is adding customers faster than it loses them, while the other is quietly compounding what it already has. Investors, boards, and RevOps teams care about the difference.

    This guide explains what NRR measures, how to calculate it, what a good number looks like, how to diagnose a weak one, and what actually improves it.

    How to calculate net revenue retention

    The formula is:

    NRR = (starting recurring revenue + expansion − contraction − churn) ÷ starting recurring revenue × 100

    Take the customers you had on day one of the period. Add what they expanded, subtract what they downgraded and what churned, and divide by what they paid on day one. Customers who signed during the period are not included.

    Here’s an illustrative example for a SaaS company with $2,000,000 in ARR at the start of the year.

    Line Amount
    Starting ARR from existing customers $2,000,000
    + Expansion (upgrades, extra seats, cross-sell) $300,000
    − Contraction (downgrades) $80,000
    − Churn (cancellations) $120,000
    Ending ARR from the same customers $2,100,000
    NRR $2,100,000 ÷ $2,000,000 = 105%

    These buckets are the same ones in a revenue waterfall, which is why a clean waterfall makes NRR easy to calculate and explain. New-logo revenue sits in a separate line and never enters the NRR math.

    NRR, GRR, and logo retention: what each tells you

    Metric What it counts Can it exceed 100%? What it tells you
    Net revenue retention Revenue kept plus expansion, minus contraction and churn Yes Whether the existing base is growing or shrinking
    Gross revenue retention Revenue kept after contraction and churn, with expansion excluded No, capped at 100% How leaky the bucket is
    Logo retention Share of customers kept, regardless of size No Whether you’re losing many small accounts or a few big ones

    In the example above, gross revenue retention is ($2,000,000 − $80,000 − $120,000) ÷ $2,000,000 = 90%. Look at NRR and GRR together. A 105% NRR sitting on a 90% GRR means you’re losing a tenth of your base every year and relying on expansion to cover it. That’s a different company from one with 105% NRR and 97% GRR.

    What is a good NRR?

    Benchmarks vary by source, company size, pricing model, and customer segment, so treat any single number carefully. Two recent datasets give a sense of the range:

    Source Sample Median NRR Higher performers Median GRR
    SaaS Capital, 2026 survey Bootstrapped B2B SaaS, $3M to $20M ARR 103% 117.9% at the 90th percentile 91%
    Aleph and Benchmarkit, calendar 2025 B2B SaaS panel 102% About 108% in the top quartile 84%, down from 88%

    The Benchmarkit data also found that usage-based companies had a median NRR near 108%, compared with about 98% for seat-based ones. So pricing model matters. The practical takeaway is that a median private SaaS company sits a little above 100%, and anything well above that is strong. Compare yourself with companies at a similar size, price point, and segment, not with the best public software companies.

    Why NRR matters

    Expansion revenue is cheaper than new-customer revenue, because you already have the relationship, the implementation, and the trust. High NRR lets a company grow with less acquisition spend, and it shows up in valuations. It’s also the measure that a land and expand strategy is built to move: land small, prove value, then grow the account.

    A blended number can hide the problem

    Here’s the same $2,000,000 base split by segment, with illustrative numbers:

    Segment Starting ARR NRR GRR
    Small business $600,000 92% 82%
    Mid-market $900,000 108% 93%
    Enterprise $500,000 115% 96%
    Blended $2,000,000 About 105% About 90%

    The blended 105% looks healthy. Underneath, the small business segment shrinks every year, while enterprise carries the average. Always break NRR down by segment, plan, and customer age. It also helps to cut it by acquisition source, which is where closed-loop reporting comes in: if you can trace each customer back to the channel that brought them in, you can see which sources produce customers who stay and grow, and which ones produce customers who churn in a year.

    Diagnose before you fix

    A weak NRR has three possible causes, and each needs a different response. Use your waterfall to see which component is the problem.

    What you see Likely cause First move
    Low GRR, with high churn Poor onboarding, weak fit, or unnoticed risk Study churned accounts; build early-warning signals
    Contraction is large Over-sold seats, unused licenses, or poor packaging Review seat utilization; right-size plans at renewal
    GRR is fine, expansion is small No upgrade path, or nobody owns growth Add packaging steps and name an expansion owner
    Strong in one segment, weak in another Ideal customer mismatch Tighten targeting and change how you serve the weak segment

    How to improve net revenue retention

    Reduce churn. Since expansion can’t outrun a leaky base for long, start here. Make the first 90 days count with a clear onboarding path and a defined first-value milestone. Build a customer health score so you can spot at-risk accounts early, and attach a playbook to each risk band. Track champion changes, since a departed sponsor is a common warning sign.

    Reduce contraction. Watch seat utilization and flag accounts using far fewer licenses than they pay for. Offer right-sizing before renewal, so a downgrade is a planned conversation and not a surprise. Review packaging to make sure the plans fit how customers actually use the product.

    Grow expansion. Design pricing with natural upgrade steps tied to value, such as seats, usage, or advanced features. Have usage thresholds trigger alerts for the account owner. Pursue cross-sell where a second team or product genuinely fits, and name one owner for expansion, whether in sales or customer success. Our guide to land and expand covers expansion levers in more detail.

    Be careful with price increases. A list price rise can lift NRR in the short term, but if churn follows, GRR drops and the gain disappears. Watch both numbers together.

    What your data needs to track NRR reliably

    • A matching account ID between your CRM and billing system, so revenue lines up with the right customer.
    • Recurring revenue per account at the start of each period, stored as a snapshot, so you aren’t recalculating history.
    • Agreed definitions for expansion, contraction, churn, and reactivation. Decide how to treat a customer who cancels and returns, and a plan change that lowers revenue but keeps the customer.
    • Consistent currency handling if you sell in several currencies.
    • A monthly review. NRR is a good fit for the monthly commercial review in a RevOps meeting cadence.

    Mistakes to avoid

    • Including revenue from customers who joined during the period
    • Mixing recurring revenue with one-time fees and services
    • Letting teams define churn and contraction differently
    • Reporting a blended number without segment breakdowns
    • Celebrating NRR while GRR falls
    • Comparing yourself with companies at a very different size or pricing model

    Summary

    Net revenue retention measures how much recurring revenue you keep and grow from existing customers: (starting revenue + expansion − contraction − churn) ÷ starting revenue. It excludes new customers and can exceed 100%. Read it alongside gross revenue retention, which excludes expansion and shows how leaky the base is. Recent benchmarks put the median around 102% to 103%, with usage-based companies higher than seat-based ones, though samples differ.

    Break NRR down by segment and acquisition source, because a healthy blended number can hide a shrinking segment. Use your revenue waterfall to see whether churn, contraction, or weak expansion is the problem. Fix churn first, then contraction, then grow expansion with clear upgrade paths and a named owner, and make sure your CRM and billing share account IDs and definitions.

    FAQ

    What is net revenue retention?

    It’s the percentage of recurring revenue retained from existing customers over a period, including expansion and subtracting contraction and churn. It excludes new customers.

    How do you calculate NRR?

    Add expansion to starting recurring revenue, subtract contraction and churn, divide by starting recurring revenue, and multiply by 100. Use only the customers who existed at the start of the period.

    What’s the difference between NRR and GRR?

    NRR includes expansion and can exceed 100%. GRR excludes expansion, counts only contraction and churn, and can’t exceed 100%. GRR shows how much you lose, and NRR shows the net result.

    What is a good NRR for B2B SaaS?

    Medians in recent benchmarks sit around 102% to 103%, with stronger performers at 108% or more, and some top-decile figures near 118%. Compare yourself with companies of a similar size, price point, and pricing model.

    Can NRR be too high?

    High NRR is rarely a problem, but it can hide weaknesses. If it relies on a few large expanding accounts while many small ones churn, GRR and logo retention will show the problem.

    Should NRR be calculated monthly or annually?

    The headline figure is usually annual, using a 12-month cohort. Many teams track it monthly on a trailing 12-month basis, which smooths seasonality. Whichever you use, keep the definition consistent.

    How do we improve NRR fastest?

    Diagnose first. If churn is the main drag, fix onboarding and early warning signals. If contraction is large, review seat utilization and packaging. If expansion is the gap, add upgrade paths and name an owner for growth.

  • What Is a Revenue Waterfall? A RevOps Beginner’s Guide

    A revenue waterfall is a chart that bridges your starting revenue to your ending revenue for a period, breaking out every gain and loss along the way: new business, expansion, contraction, and churn. It shows exactly where growth or decline came from, not just the final total.

    If you’ve ever stared at a quarterly revenue number and had no idea whether it grew because of new customers or just a couple of big upsells, you’ve felt the problem a revenue waterfall solves. A single top-line number hides the whole story. A waterfall forces that story into the open.

    This matters more the bigger your business gets. Once you have renewals, upgrades, downgrades, and churn all happening in the same month, you need a structured way to see what’s actually driving the change, not just the net result.

    What Is a Revenue Waterfall, Exactly?

    A revenue waterfall (sometimes called an ARR waterfall, ARR bridge, or revenue bridge) is a visual model that shows how your recurring revenue moved from one period to the next. It starts with your beginning revenue, adds everything that pushed it up, subtracts everything that pulled it down, and lands on your ending revenue.

    Think of it as a step-by-step accounting of change, not a snapshot. One finance-focused description puts it well: a revenue waterfall chart shows how a starting revenue figure changes through a series of gains and losses to reach an ending figure, and by the time you reach the final bar, you can see exactly what happened between point A and point B.

    If you’re still getting familiar with RevOps as a discipline, it helps to back up a step first. Our guide on what RevOps actually is covers the basics of how revenue operations connects marketing, sales, and customer success data into one system, which is exactly the kind of system a revenue waterfall depends on.

    How Does a Revenue Waterfall Work?

    The mechanics are simpler than the name suggests. Every dollar of revenue change during a period gets sorted into one bucket, and those buckets get stacked (or “waterfalled”) between your starting and ending numbers.

    A typical waterfall follows this flow:

    1. Start with beginning ARR or MRR. This is your recurring revenue total at the start of the period.
    2. Add new revenue. Money from brand-new customers signed during the period.
    3. Add expansion revenue. Upsells and cross-sells from existing customers who bought more.
    4. Subtract contraction revenue. Revenue lost from existing customers who downgraded.
    5. Subtract churned revenue. Revenue lost from customers who canceled entirely.
    6. Land on ending ARR or MRR. This becomes next period’s starting number.

    That sequence, start, add, subtract, end, is the whole model. The value isn’t in the math (it’s addition and subtraction). The value is in forcing every contract to get classified consistently, so finance, sales, and RevOps are all looking at the same definitions.

    A Worked Example With Real Numbers

    Abstract steps are easier to follow with numbers attached. Here’s a made-up quarter for a small SaaS company.

    Line Amount What happened
    Beginning ARR $2,000,000 Recurring revenue on day one of the quarter
    + New $300,000 Twelve new customers signed
    + Expansion $150,000 Existing customers added seats and tiers
    – Contraction $50,000 A few customers downgraded
    – Churn $100,000 Several customers canceled
    Ending ARR $2,300,000 $2,000,000 + $300,000 + $150,000 – $50,000 – $100,000

    Ending ARR grew by $300,000, or 15%. That looks healthy. But the waterfall shows something the top-line number doesn’t: $150,000 of the revenue the company had at the start of the quarter either shrank or left. Net of expansion, existing customers contributed $0 of growth. Every dollar of net growth came from new business.

    That’s a very different story from “we grew 15%.” It tells a RevOps team to look at retention, not just pipeline.

    What Are the Core Components of a Revenue Waterfall?

    Most revenue waterfalls track the same handful of movement types, though naming varies slightly by company:

    • New revenue from newly acquired customers
    • Expansion revenue from upsells or cross-sells to existing accounts
    • Contraction revenue from downgrades on existing accounts
    • Churned revenue from cancellations
    • Renewal revenue from contracts that simply continued

    Getting these categories consistent across teams is harder than it sounds. One breakdown of the process notes that consistent definitions across sales, finance, and RevOps are essential, because if sales calls a downgrade “churn” and finance calls it “contraction,” the waterfall won’t reconcile to anything. Honestly, this is where most waterfall projects quietly fail: not the chart, the definitions behind it.

    A few edge cases come up constantly and are worth deciding in advance. What counts as a downgrade versus a plan change that’s revenue-neutral? If a customer cancels and comes back two months later, is that churn plus new, or a reactivation? When a customer moves to a different product and pays less in total, is that contraction or churn plus new? There’s no universal answer. What matters is that you pick one rule and apply it every month.

    Pro tip: before you build anything in a BI tool, get sales, finance, and RevOps in a room (or a shared doc) and agree on one definition for each movement type. Write it down. Revisit it every time someone argues about a number.

    Revenue Waterfall vs. ARR Waterfall vs. Deferred Revenue Waterfall

    Here’s where it gets a little confusing, because “revenue waterfall” gets used for two related but different things.

    The version most RevOps and sales teams care about is the ARR or bookings waterfall: it tracks how your recurring revenue base grew or shrank through new business, expansion, contraction, and churn. This is the one that shows up in board decks and GTM reviews.

    The other version lives in accounting and finance. It tracks how booked or billed revenue gets recognized over time under revenue recognition standards like ASC 606, moving from deferred revenue on the balance sheet into recognized revenue on the income statement as you deliver the service. One comparison puts it plainly: a revenue waterfall in this sense shows what hit the profit and loss statement, as opposed to tracking the health of your customer base.

    Both are legitimate and both matter, they just answer different questions. RevOps typically owns or heavily influences the ARR version. Finance usually owns the recognition version. If you’re new to this, assume people mean the ARR/bookings version unless the conversation is specifically about accounting compliance.

    Why Does a Revenue Waterfall Matter for RevOps Teams?

    Because net revenue growth can lie to you. A company can post flat revenue while actually losing a chunk of its customer base to churn and masking it with one large expansion deal. Without a waterfall, nobody notices until it’s a much bigger problem.

    A waterfall gives you a single, shared view of revenue movement instead of three teams pulling three different numbers from three different systems. It also becomes a genuine diagnostic tool: when contraction or churn spikes in the waterfall, that’s a signal worth chasing down before it shows up in next quarter’s board meeting, not after.

    This kind of cross-functional reporting discipline is a good marker of RevOps maturity too. If your team can’t yet produce a clean, reconciled waterfall every month, that’s worth knowing. It’s one of the signals we cover in our breakdown of RevOps maturity stages, since the ability to build and trust a waterfall usually tracks with how far along your RevOps function actually is.

    Questions a Waterfall Helps You Answer

    Once you have a reliable waterfall, it starts answering questions that used to take a week of spreadsheet work:

    • Is growth coming from new customers or from the ones we already have?
    • Is churn getting worse, or did one large account distort the quarter?
    • Are customers expanding enough to offset the ones who leave?
    • Which period had the biggest drop, and what changed around then?
    • Does the number we told the board match what billing and the CRM say?

    That last question is quietly the most valuable one. A waterfall that reconciles between the CRM and billing is a sign your data is in decent shape. One that never quite adds up usually points to deals classified inconsistently, or contract changes that never made it into the CRM.

    Who Actually Owns the Revenue Waterfall?

    It depends on the company, but it shouldn’t live in a silo. RevOps usually owns the data pipeline and category definitions, finance usually owns the accounting accuracy, and sales and customer success leaders use the output to manage their teams.

    That shared ownership is part of why distinguishing these functions matters. If you’re unclear on where RevOps responsibilities end and sales ops or marketing ops responsibilities begin, our post on RevOps vs. sales ops vs. marketing ops walks through exactly where those lines sit.

    How to Build a Simple Revenue Waterfall: A Starter Checklist

    You don’t need enterprise software to start. A basic waterfall can live in a spreadsheet or a simple BI dashboard. Here’s a practical starting sequence:

    1. Pull your beginning ARR or MRR for the period from your CRM or billing system.
    2. Export every contract change (new, renewal, upgrade, downgrade, cancellation) that happened in the period.
    3. Classify each change into one of the standard buckets: new, expansion, contraction, or churn.
    4. Sum each bucket separately. Don’t net them against each other yet.
    5. Stack the buckets between your beginning and ending totals to confirm they reconcile.
    6. Review the result with sales, finance, and customer success before calling it final.

    That last step matters more than people expect. A waterfall that only RevOps has looked at isn’t trustworthy yet; it needs other eyes on it to catch misclassified deals.

    Common Mistakes to Avoid

    • Netting buckets together. Showing “net expansion” hides how much was churned and how much was upsold. Keep each bucket visible.
    • Skipping the reconciliation. If beginning plus movements doesn’t equal ending, something is misclassified or missing.
    • Changing definitions midstream. Redefining churn halfway through the year makes month-to-month comparisons meaningless.
    • Building it once and never refreshing. A waterfall is only useful on a regular cadence, usually monthly.
    • Using it only for the board. The biggest value comes when sales, customer success, and RevOps use it to ask what changed and why.

    Summary

    A revenue waterfall bridges beginning revenue to ending revenue for a period by breaking out every movement in between: new, expansion, contraction, and churn. It shows where growth actually came from, which a single top-line number can’t. The worked example in this guide shows how a company can grow 15% while existing customers contribute nothing net, a pattern only the waterfall makes visible.

    The model itself is simple addition and subtraction. The hard part is agreeing on definitions across sales, finance, and RevOps, and applying them consistently every month. RevOps usually owns the ARR or bookings version, while finance owns the revenue recognition version. To build your first one, pull beginning ARR, classify every contract change, sum each bucket without netting, confirm the totals reconcile, and review with the other teams before you trust it.

    FAQ

    Is a revenue waterfall the same as a sales funnel?

    No. A sales funnel tracks leads moving through stages toward a first deal. A revenue waterfall tracks how your existing recurring revenue base changes over time, including renewals, upgrades, downgrades, and churn, long after that first deal closes.

    Do I need special software to build a revenue waterfall?

    Not to start. A spreadsheet works fine for an early-stage company. As your contract volume grows, most teams move to a BI tool or a revenue recognition platform because manually classifying every contract change stops scaling.

    How often should we update our revenue waterfall?

    Monthly is the most common cadence for RevOps and GTM reporting, since it lines up with how most SaaS companies track MRR. Finance teams tracking revenue recognition under ASC 606 often need it on the same monthly cycle for compliance reasons.

    What’s the difference between an ARR waterfall and an MRR waterfall?

    They’re the same model applied to different time horizons: ARR waterfalls use annual recurring revenue, MRR waterfalls use monthly recurring revenue. Companies with shorter sales cycles or month-to-month contracts tend to lean on MRR waterfalls for faster signal.

    Why do sales and finance sometimes disagree on waterfall numbers?

    Usually because they’re using different definitions for the same movement type, like calling a downgrade “churn” in one system and “contraction” in another. Getting everyone aligned on shared definitions before you build the waterfall is the single biggest thing you can do to avoid this.

    What should we do if the waterfall doesn’t reconcile?

    Start by checking for contract changes that exist in billing but not in the CRM, or the reverse, then look for deals classified into the wrong bucket. A gap between beginning plus movements and ending ARR almost always traces back to a missing record or an inconsistent definition, not a flaw in the model itself.