SaaS Revenue Waterfall Template: Free Download

A revenue waterfall — also called an MRR bridge — is the single most diagnostic view a SaaS finance team can produce. It answers the question board members always ask: "We grew MRR by $42K this month. Where did that come from?" Without the waterfall, you cannot answer precisely. With it, you have a decomposition of every dollar gained and every dollar lost in a given period.

The mechanics are not complicated. What is hard is keeping the data clean enough, and structured correctly enough, to produce accurate numbers every month without manual reconciliation. This guide gives you the template structure, the formulas, and the worked example you need to build it — or to evaluate whether the one you already have is correct.

The Five Components of MRR Movement

Every change to your MRR balance falls into exactly one of five buckets. Getting the bucketing right is the most important step — imprecise categorization is why many waterfall models produce numbers that do not reconcile to billing system totals.

1. New MRR

Definition: MRR generated from customers who had no active subscription in the prior month. First-time subscribers, new logos, and accounts that signed up this period.

Common errors: including reactivations in New MRR (they belong in their own bucket), or including upgrades from existing customers (those are Expansion MRR).

2. Expansion MRR

Definition: Additional MRR from customers who were already active in the prior month and increased their subscription value. Includes plan upgrades, seat additions, add-on purchases, and usage tier increases.

Expansion MRR is the most capital-efficient growth signal. When expansion regularly exceeds churn, the existing customer base grows revenue without requiring new acquisition spend.

3. Contraction MRR

Definition: MRR lost from existing customers who downgraded to a lower plan, reduced seat count, or negotiated a lower rate — without cancelling entirely.

Contraction is entered as a negative value in the bridge. It is distinct from churn: the customer relationship continues, but the revenue has compressed. The underlying signal differs — contraction typically points to a pricing, packaging, or value-delivery problem, not a fit failure.

4. Churned MRR

Definition: MRR lost from customers who cancelled their subscription entirely this month. The account that was active last month is not active this month.

Churned MRR is entered as a negative value. Separating churned from contracted MRR is essential: a customer who cancels entirely generates zero future expansion opportunity, while a customer who downgrades can still be recovered.

5. Reactivation MRR

Definition: MRR from customers who previously churned and have resubscribed this month. They are not new logos — they had an account, left, and returned.

Reactivation is typically a small line item, but it matters for cohort analysis and product signals. A spike in reactivations after a new feature release, pricing change, or marketing campaign is a meaningful data point.

The Core Bridge Formula

With the five components defined, the MRR bridge formula is:

If your Ending MRR does not match your billing system's total MRR for the month, there is a categorization error somewhere. The bridge should always reconcile to zero unexplained variance.

The MRR Waterfall Template: Monthly Bridge Table

Below is the canonical waterfall table structure, followed by a fully worked three-month example with realistic numbers for a growth-stage SaaS company at roughly $200K MRR.

Template Structure

Worked Example: Three Months of MRR Movement

The following example uses a B2B SaaS company at $198,000 starting MRR (roughly $2.4M ARR). Numbers reflect a company in a healthy but not exceptional growth phase — useful for calibrating what each component looks like at realistic scale.

Reading these three months: The company is growing consistently. Churn is elevated relative to expansion in February and March — the Quick Ratio of 2.1 and 2.2 is in the "unsustainable growth" zone (below the 4.0 benchmark). April improves meaningfully: new MRR jumped, expansion grew, and churn declined, pushing the Quick Ratio to 2.9. Still below best-in-class, but the trend is moving in the right direction.

The contraction line is small and consistent — a good sign. Contraction above roughly 1.5% of starting MRR would warrant investigation into whether certain customer segments are systematically downgrading.

The month-to-month pattern matters as much as any individual month. A CFO who only reviews the ending MRR misses that April's improvement came from lower churn, not just higher new business — a structurally different (and more defensible) growth profile.

MRR Movement Benchmarks for 2026

These benchmarks are drawn from the 2026 SaaS Benchmarks reports published by Eagle Rock CFO, Benchmarkit, and MRRSaver, covering hundreds of private B2B SaaS companies. Use them to evaluate each waterfall row against your peer cohort.

The monthly MRR churn rate benchmarks translate to annual rates: below 1% monthly is below 12% annually (best-in-class), 1–1.5% monthly is 12–18% (healthy), and above 2% monthly (above 24% annually) signals a retention problem that new logo growth cannot outrun indefinitely.

For NRR, B2B SaaS companies with NRR above 120% are considered best-in-class in 2026. The strategic shift in SaaS is reflected in how high-performing companies allocate growth effort: approximately 40% toward expansion features, 30% toward retention, and 30% toward acquisition — compared to a historical weighting that skewed heavily toward acquisition.

The SaaS Quick Ratio: Your Waterfall Summary Metric

The SaaS Quick Ratio is the single ratio derived directly from the waterfall that most clearly summarizes growth quality. It compares inflows to outflows:

A Quick Ratio of 4 means for every dollar lost to churn or contraction, four dollars are gained from new and expanding customers. This is the investor benchmark made famous by Mamoon Hamid at KPCB. At 1.0, the business is exactly replacing what it loses — no net growth. Below 1.0, the business is shrinking regardless of how many new customers it signs, because churn is consuming new revenue faster than it arrives.

Using the worked example above: February's Quick Ratio of 2.1 means the company is growing, but churn is consuming roughly one dollar for every two dollars gained. The April improvement to 2.9 reflects both lower churn and higher new MRR — a better-quality month even though the absolute growth difference appears small in the table.

How CFOs Use the Revenue Waterfall

For SaaS finance leaders, the waterfall is not a metric — it is a diagnostic framework. The same table that satisfies a board reporting requirement also answers the operational questions that drive resource allocation decisions.

Board and Investor Reporting

Most Series A and later investors expect an MRR bridge in their monthly or quarterly update packages. The waterfall allows investors to evaluate whether growth is being driven by new logo acquisition (high risk, high cost) or by expansion from an installed base (lower risk, more efficient). A company with flat new MRR but rising expansion MRR is telling a fundamentally different story than one with the same net growth driven entirely by new logos.

Churn and Retention Diagnosis

The waterfall separates churned MRR from contraction MRR — a distinction that is invisible in a single NRR number. Elevated churn in one segment while contraction spikes in another suggests two separate problems requiring two separate responses. Without the component view, both issues hide behind a single retention figure.

Forecasting and Operating Plan Alignment

Once a company has six to twelve months of waterfall history, each component develops a pattern. New MRR has a seasonal cadence tied to the sales cycle. Expansion MRR often correlates with product release timing. Churn may cluster around annual renewal months. These patterns make component-level forecasting more reliable than top-down MRR projection.

Fairview's Operating Dashboard surfaces MRR movement components in real time, pulling from billing systems (Stripe, Chargebee) and CRM data to produce a live waterfall view without manual reconciliation. The pattern recognition layer flags when any component deviates from its historical trend — so operators catch a churn acceleration or an expansion slowdown before it compounds into the following quarter's numbers.

Customer Success and Sales Alignment

The waterfall creates a shared language across teams. Customer success owns the churn and contraction lines. Sales owns the new MRR line. Account management owns expansion. When each team sees its line in the same table as every other team's line, conversations about resource allocation and cross-functional priorities are grounded in the same data. That shared grounding is what allows operators to make the trade-off decisions — whether to invest the next dollar in acquisition, retention, or expansion — with clarity rather than assumption.

Fairview structures its Margin Intelligence layer around this component logic precisely because the component view of revenue is what makes operating decisions defensible. The question is not "did MRR grow?" — it is "which components drove growth, which are leaking, and what does each trend imply about next quarter's number?"

Common Waterfall Errors to Avoid

• Mixing reactivations into new MRR: Returning churned customers are not new logos. Including them in New MRR overstates acquisition performance and masks the true CAC-to-LTV picture for first-time customers.
• Netting expansion against contraction: Reporting a single "net expansion" line eliminates the signal. A company with $15K expansion and $12K contraction in the same month has a very different retention story than one with $3K expansion and no contraction — even though the net figure is identical.
• Using bookings instead of recognized MRR: The waterfall is a cash-flow-adjacent view. It should reflect billing events, not signature dates. Annual contracts should be divided into their monthly MRR contribution rather than booked in full at contract execution.
• Ignoring reconciliation: Ending MRR must match the billing system. Any unexplained variance belongs in a reconciling items row until categorized. "Close enough" reconciliation produces compounding errors in multi-month trend analysis.