An ARR Waterfall is a single-period decomposition of annual recurring revenue that bridges beginning ARR to ending ARR by separating the four movement types: new ARR, expansion ARR, contraction ARR, and churned ARR. The model is also called an ARR bridge, an ARR rollforward, a recurring revenue rollforward, or an ARR walk; when applied to monthly recurring revenue it becomes an MRR waterfall or SaaS revenue waterfall. Operating Partners, CFOs, and RevOps leaders use the ARR Waterfall to diagnose what happened to recurring revenue inside a quarter or month, while the related ARR Snowball tracks the longitudinal trajectory across multiple periods.

What Is an ARR Waterfall in SaaS?

An ARR Waterfall is a component-level reconciliation of recurring revenue movement. It starts with beginning-period ARR, adds the gross movements that increased ARR during the period, subtracts the gross movements that decreased ARR, and lands at ending-period ARR. The standard formula is:

Beginning ARR − Churn − Contraction + Expansion + New = Ending ARR

The reason finance teams call it a “waterfall” is that the visualization — a bridge chart with floating columns — cascades from beginning ARR down through each component to ending ARR. Every dollar of recurring revenue change has to be classified into exactly one bucket, which forces precision that a single net-ARR number can hide.

The ARR Waterfall is the operating finance counterpart to the ARR Snowball. The Waterfall is single-period and component-level; the Snowball is multi-period and cumulative. Both models reconcile to the same ending ARR figure, and PE-backed SaaS companies typically maintain both. For a side-by-side breakdown of when to use each, see ARR Snowball vs. ARR Waterfall.

What Are the Components of an ARR Waterfall?

A basic ARR Waterfall has four movement types. At intermediate and advanced levels, the model adds more granular decomposition. The level of precision matters for due diligence and board reporting. At the basic level, every ARR Waterfall should always show dollar movements alongside % of Beginning ARR — without that column, it is not an analysis, it is a table.

Component Definition Direction
Beginning ARR Contracted recurring revenue from active customers as of the first day of the period. Always = 100% in the % of Beginning column. Starting balance
Churn ARR lost when a customer fully terminates the contract and is no longer a customer at period end. Subtract
Contraction ARR lost when an active customer downgrades, removes seats, or reduces scope but remains a customer. Subtract
Expansion Incremental ARR from existing customers via upsell, cross-sell, additional seats, or contractual price increases. Add
New ARR from net-new logos that did not exist as customers in the prior period. Add
Ending ARR Beginning ARR minus churn and contraction, plus expansion and new. The contracted recurring revenue on the last day of the period. Ending balance

At the advanced level (M&A-grade), these four movements decompose further: Churn splits into Churn (full account loss) and Product Churn (one product dropped within a retained account). Contraction becomes Downsell. Expansion splits into Upsell (more of the same product) and Cross-sell (a different product). New ARR includes Lapsed (customers who returned within 12 months) and Returning (customers who returned after more than 12 months). This is the level acquirers expect during Quality of Revenue diligence.

Two derived metrics fall directly out of the Waterfall and are the figures Operating Partners and Boards examine most closely:

  • Gross Revenue Retention (GRR) = (Beginning ARR − Contraction ARR − Churned ARR) / Beginning ARR. Measures retention before any expansion. Anything below ~90% in mid-market SaaS or ~95% in enterprise SaaS is a yellow flag.
  • Net Revenue Retention (NRR) = (Beginning ARR + Expansion ARR − Contraction ARR − Churned ARR) / Beginning ARR. The single most important durability metric in SaaS. Bessemer’s State of the Cloud benchmarks show that public SaaS companies with NRR above 120% trade at meaningfully higher revenue multiples than peers below 110%.

How Do You Build an ARR Waterfall? (Step-by-Step)

Building an ARR Waterfall takes five steps. The data lives in the billing system; the difficulty is in the classification logic and the period-over-period reconciliation.

  1. Pull contract-level data with a customer identifier. You need every contract or subscription line that was active at any point during the period, with start date, end date, ARR value, and a stable customer ID. Most billing systems (Stripe, Zuora, Chargebee, Salesforce CPQ, NetSuite ARR module) export this directly.
  2. Lock movement definitions before you compute. Decide once: a customer who downgrades in Q1 and re-upgrades in Q2 — is that contraction-then-expansion, or net expansion? A customer who churns in February and signs a new contract in March — churn-then-new, or lapsed? Without these rules, two analysts produce two different waterfalls from the same data. The SaaS CFO’s movement framework is a widely-used reference for these definitions.
  3. Compute period-over-period deltas per customer. For each customer ID, compare ARR at period-end to ARR at period-start. The delta classifies into exactly one bucket: new (no prior ARR), expansion (prior ARR > 0, ending > prior), contraction (ending < prior, ending > 0), or churn (ending = 0, prior > 0). At intermediate and advanced levels, previously churned customers who return are classified as Lapsed (<12 months) or Returning (>12 months) rather than lumped into New.
  4. Aggregate and reconcile. Sum each bucket. Verify that Beginning ARR − Churn − Contraction + Expansion + New = Ending ARR exactly. If it does not, a contract was double-counted, a date boundary was crossed, or a customer ID changed mid-period.
  5. Visualize as a bridge chart. Plot Beginning ARR on the left, each component as a floating column, and Ending ARR on the right. Color adds in green, subtracts in red. The chart is the artifact you put in the board deck and the QBR.

For PE-grade reporting, the Waterfall must reconcile both upward to the ARR Snowball for trajectory analysis and downward to GAAP recognized revenue for audit defensibility. CJ Gustafson’s ARR Waterfall guide on Mostly Metrics is a useful operator-level walkthrough of the reconciliation step.

What Does an ARR Waterfall Look Like? (Example)

A worked example for a hypothetical $50M ARR PE-backed SaaS company over a single quarter:

Component $ in Millions % of Beginning
Beginning ARR50.0100.0%
Churn(2.1)-4.2%
Contraction(1.4)-2.8%
Expansion3.26.4%
New4.59.0%
Ending ARR54.2108.4%
Derived Metric Value
Net New ARR$4.2M
GRR93.0%
NRR99.4%

The % of Beginning column is what makes this an analysis, not a table. Churn at -4.2% and Contraction at -2.8% tell you the base is leaking 7% per quarter. Expansion at 6.4% does not fully offset that. This is a business that looks fine on a net-ARR view but is actually treading water on the existing base — NRR under 100%.

This is a business that looks fine on a net-ARR view but is actually treading water on the existing base — the headline 9% quarterly growth is almost entirely new logo acquisition, with NRR under 100%. That diagnosis is invisible without the Waterfall.

Why Does the ARR Waterfall Matter for PE-Backed SaaS?

For PE Operating Partners and CFOs, the ARR Waterfall is the single most important operating finance artifact. Four reasons:

  1. Diagnostic clarity. A net ARR figure tells you the score; the Waterfall tells you which inning had the runs. Boards make different decisions when a $5M net-new ARR quarter came from $7M in adds offset by $2M in churn versus $5.5M in adds offset by $0.5M in churn.
  2. Cross-functional accountability. Each Waterfall component has a different owner: New ARR is sales, Expansion is account management, Churn and Contraction are CS and product. Splitting the model by component turns it into a shared operating dashboard rather than a finance artifact.
  3. Due diligence defensibility. Quality-of-earnings teams reconstruct the Waterfall from raw billing data during diligence. If your reported figures do not reconcile, the diligence team produces theirs — and the gap becomes a discount on the deal value. SaaS Capital’s benchmarks show that gross churn above 12% annually is a category-level red flag in any diligence process.
  4. Forecast credibility. A forecast built on Waterfall components — with separate assumptions for new logo velocity, expansion rate, and churn — is debuggable. A forecast built on a single net-ARR growth rate is not.

ARR Waterfall vs. ARR Bridge vs. ARR Rollforward — Are They the Same?

Yes, with minor regional and audience preferences. All three terms describe the same single-period reconciliation of beginning ARR to ending ARR through component-level movements. ARR Waterfall is the most common term in SaaS finance and operating partner circles and refers specifically to the bridge-chart visualization. ARR Bridge is the term most commonly used by investment banks and PE diligence teams; it is identical in math. ARR Rollforward is the formal accounting term and is most often used in audit and 10-Q/10-K disclosure work. Recurring revenue rollforward and ARR walk are alternate phrasings that appear in private equity LP reporting and quarterly board materials.

When the same model is built on monthly rather than annual recurring revenue, it is called an MRR Waterfall or MRR Bridge. The math is identical; only the time unit changes.

What Are the Most Common Mistakes When Building an ARR Waterfall?

  1. Using net deltas instead of gross movements. A customer who expands by $50K and contracts by $30K in the same period should appear as $50K expansion and $30K contraction, not $20K net expansion. Netting hides churn signal.
  2. Ambiguous downgrade vs. churn classification. A customer who reduces ARR by 90% but keeps a $10K floor is contraction, not churn. A customer who drops to zero is churn. Companies that flip these classifications mid-year produce reports that are not comparable across quarters.
  3. Mid-period contract modifications. A contract amended on day 47 of a 90-day period needs to be apportioned, not snapped to the boundary. Snapping introduces 1-2 points of noise that aggregate into systematic misstatement.
  4. Cross-product double-counts. When a customer expands one product and contracts another in the same quarter, both movements are real. Aggregating to the customer-level expansion-or-contraction (not both) hides which product line is driving health.
  5. Manual spreadsheets without reconciliation. Once the model lives in three Excel files maintained by three people, the Waterfall stops reconciling to the Snowball, the Snowball stops reconciling to GL recognized revenue, and the board deck contradicts the operating review. This is the single most common reason PE-backed companies move ARR reporting to a purpose-built platform.

How Often Should You Update the ARR Waterfall?

Three cadences cover most PE-backed SaaS use cases:

  • Monthly for operating reviews, RevOps cadence, and FP&A variance analysis. This is where teams catch issues before they compound.
  • Quarterly for board decks, investor reporting, and PE Operating Partner reviews. The quarterly Waterfall is the artifact that becomes the basis for the Snowball.
  • Annually for the audit footnote, the LP report, and the budget reconciliation. The annual Waterfall reconciles the trailing twelve months to the GL.

Key Takeaways

  • An ARR Waterfall — also called an ARR bridge, ARR rollforward, recurring revenue rollforward, or ARR walk — is a single-period decomposition of recurring revenue change into churn, contraction, expansion, and new.
  • The formula is Beginning ARR − Churn − Contraction + Expansion + New = Ending ARR, and every customer movement classifies into exactly one bucket. Always show % of Beginning ARR alongside dollar amounts.
  • The two metrics that fall directly out of the Waterfall — Gross Revenue Retention and Net Revenue Retention — are the durability metrics PE firms scrutinize most.
  • The Waterfall is the operating-finance complement to the ARR Snowball: the Waterfall diagnoses a single period; the Snowball tracks trajectory across periods.
  • Building a defensible Waterfall requires locked movement definitions, clean contract-level data, gross-not-net aggregation, and reconciliation to both the Snowball and to GAAP revenue.
  • Most PE-backed SaaS companies eventually move from spreadsheet Waterfalls to a unified Customer Data Cube because the reconciliation across Snowball, Waterfall, and GL revenue breaks under spreadsheet maintenance.

Frequently Asked Questions

What is an ARR Waterfall in simple terms?

An ARR Waterfall is a chart that shows how your annual recurring revenue changed during a period by separating the additions (new customers, expansion) from the subtractions (downgrades, churn) so you can see exactly what drove the net change. It is also called an ARR bridge or ARR rollforward.

What is the difference between an ARR Waterfall and an ARR Snowball?

An ARR Waterfall decomposes a single period’s ARR change into its components (new, expansion, contraction, churn). An ARR Snowball compounds multiple periods’ ending ARR forward to show trajectory over time. The Waterfall answers what happened this quarter; the Snowball answers where is the business heading. See ARR Snowball vs. ARR Waterfall for the full comparison.

Is an ARR Waterfall the same as an ARR Bridge?

Yes. ARR Waterfall, ARR Bridge, ARR Rollforward, recurring revenue rollforward, and ARR walk all refer to the same single-period reconciliation of beginning ARR to ending ARR through component-level movements. The math is identical; the term varies by audience — SaaS finance teams say “Waterfall,” PE diligence teams say “Bridge,” auditors say “Rollforward.”

What components make up an ARR Waterfall?

A basic ARR Waterfall has four movements: Churn (lost customers), Contraction (downgrades), Expansion (upsell, cross-sell, price increase), and New (net-new logos). Beginning ARR minus the subtracts plus the adds equals Ending ARR. At the advanced level, Churn splits into Churn and Product Churn, Contraction becomes Downsell, and Expansion decomposes into Upsell and Cross-sell. Always show % of Beginning ARR alongside dollar amounts.

How do you calculate Net Revenue Retention from the ARR Waterfall?

NRR = (Beginning ARR + Expansion ARR − Contraction ARR − Churned ARR) / Beginning ARR. New ARR is excluded because NRR measures the existing customer base only. Best-in-class public SaaS companies report NRR above 120%; PE benchmarks for mid-market SaaS typically target 105-115%.

What software builds an ARR Waterfall automatically?

Spreadsheet templates from The SaaS CFO, Mosaic, and HiBob work for sub-$10M ARR companies. Above that, dedicated platforms generate the Waterfall directly from billing and CRM data; Pacer AI’s Customer Data Cube on Microsoft Fabric is purpose-built for PE-backed SaaS, automating Waterfall, Snowball, and NRR reporting from a single source of truth.

How does Pacer AI build the ARR Waterfall?

Pacer AI’s Customer Data Cube ingests contract, billing, and CRM data, applies locked movement definitions, computes per-customer period deltas, and renders the Waterfall, Snowball, and GRR/NRR metrics in Power BI. Reconciliation between models is automatic, definitions are governed centrally, and outputs are board-ready without spreadsheet maintenance — which is why PE-backed SaaS finance teams adopt it for portfolio standardization.