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.

Frequently asked

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.