An ARR Snowball is a multi-period rollforward of recurring revenue that compounds beginning ARR forward across quarters or years to show trajectory. An ARR Waterfall (also called an ARR bridge, ARR rollforward, or recurring revenue rollforward) is a single-period decomposition of ARR change into new, expansion, contraction, and churn. The Snowball answers where is ARR going; the Waterfall answers what just happened to ARR. Most PE-backed SaaS teams need both, but they answer fundamentally different questions. This post breaks down when to use each, where they overlap, and how to avoid the reporting gaps that surface during board reviews and due diligence.

What Is an ARR Snowball?

An ARR Snowball is a model that starts with your beginning-of-period ARR and rolls it forward by adding new bookings and expansion revenue while subtracting contraction and churn. The result is an ending ARR figure that becomes the starting point for the next period — hence the “snowball” metaphor. Each period builds on the last.

The Snowball is a top-down, longitudinal view. It answers the question: How is my total ARR evolving over time, and what is driving the trajectory?

A well-built Snowball makes it immediately clear whether your growth is coming from new logo acquisition, expansion within the existing base, or simply strong retention. For Operating Partners and CFOs reviewing portfolio companies, the Snowball is often the first model they look at because it reveals where compounding is actually happening — or where it is stalling.

What Is an ARR Waterfall?

An ARR Waterfall — also called an ARR bridge, ARR rollforward, recurring revenue rollforward, or MRR/ARR walk — is a component-level decomposition of ARR movement within a defined period. It visually separates the “adds” (new logos, expansion) from the “subtracts” (churn, contraction) to show you the net change. The same model is sometimes called a SaaS revenue waterfall when applied to monthly recurring revenue.

Where the Snowball gives you trajectory, the Waterfall gives you anatomy. It answers: What exactly happened to my ARR this quarter, and in what proportions?

Waterfalls are the model of choice for monthly and quarterly business reviews because they force precision. You cannot hide behind a net number when the waterfall shows that your $2M net new ARR came from $4M in gross adds offset by $2M in churn. That is a very different story than $2.5M in adds and $500K in churn — even though the net figure is the same.

How Do the ARR Snowball and Waterfall Compare?

Dimension	ARR Snowball	ARR Waterfall
Primary question	Where is my ARR heading over time?	What changed my ARR this period?
Time orientation	Multi-period, cumulative	Single-period, decomposed
Best for	Board decks, investor reporting, long-range forecasting	Monthly/quarterly reviews, variance analysis, operational debugging
Key strength	Shows compounding and trajectory	Exposes component-level health
Key weakness	Can obscure within-period dynamics	Loses longitudinal context on its own
Audience	Board, PE sponsors, CEO, CFO	RevOps, FP&A, CRO, VP Sales
Typical visualization	Stacked area or line chart over 12-24 months	Bridge/waterfall chart for a single quarter or month
Data granularity needed	Period-level totals by movement type	Transaction-level or account-level movements

When Should You Use the ARR Snowball?

Use the Snowball when you need to communicate trajectory and compounding dynamics to an audience that cares about direction more than mechanics. Specific scenarios:

• Board reporting: Boards want to see whether the business is accelerating, decelerating, or flat-lining. The Snowball shows this at a glance across multiple quarters.
• Fundraising and due diligence: Investors and acquirers evaluate the quality of your growth engine. A Snowball that shows increasing contribution from expansion (rather than solely from new logos) signals a healthy, capital-efficient business. Bessemer’s growth efficiency benchmarks reinforce that net revenue retention above 110% is the clearest sign of product-market fit at scale.
• Annual planning: When building next year’s ARR targets, the Snowball lets you model scenarios: “If churn drops 2 points and expansion holds, where does ARR land?” This is exactly the kind of driver-level analysis that separates a real operating plan from a spreadsheet exercise.
• PE portfolio reviews: Operating Partners comparing five portfolio companies need a standardized view. The Snowball normalizes the story across different business models and contract structures.

When Should You Use the ARR Waterfall?

Use the Waterfall when you need to diagnose what is happening inside the business during a specific period. Specific scenarios:

• Monthly revenue cadence: RevOps and FP&A teams running weekly or monthly pipeline reviews need the Waterfall to identify whether misses are coming from new business shortfalls, unexpected churn, or contraction in the expansion pipeline.
• Variance analysis: When actual ARR diverges from forecast, the Waterfall tells you which component drove the miss. You cannot fix “ARR was below plan” — you can fix “expansion was 30% below plan because mid-market upsells stalled.”
• Churn forensics: The Waterfall quantifies the gross churn and contraction numbers that a net-ARR view obscures. SaaS Capital’s benchmarks show that gross churn above 10-12% annually is a red flag regardless of how strong expansion looks.
• GTM team accountability: When sales, customer success, and product each own different components of the Waterfall (new, expansion, retention), the model becomes a shared operating framework rather than just a finance artifact. The SaaS CFO’s waterfall framework illustrates how this decomposition drives cross-functional alignment.

Can You Use Both Models Together?

Yes — and you should. The Snowball and Waterfall are not competing models. They are different lenses on the same underlying data.

The most effective ARR reporting stacks work like this:

1. Waterfall for monthly and quarterly operations. Use the component breakdown to run the business week to week. Track gross adds, gross churn, expansion, and contraction separately. Hold teams accountable to each lever.
2. Snowball for quarterly and annual strategy. Roll the monthly Waterfall outputs into a cumulative Snowball to show the board, investors, and executive team the trajectory and compounding dynamics.
3. Reconciliation between the two. The ending ARR from your Waterfall for any period should exactly match the corresponding data point on your Snowball. If it does not, you have a data integrity problem — typically caused by inconsistent churn definitions, mid-period contract modifications, or misclassified movements.

This layered approach is what separates PE-grade revenue intelligence from ad-hoc reporting. Mosaic’s revenue forecasting guide describes a similar multi-model approach, noting that the Snowball is most powerful when fed by granular Waterfall-level data.

What Are Common Mistakes When Choosing Between These Models?

Three patterns cause the most pain:

1. Using the Snowball as your only model. The Snowball is excellent for trajectory, but it can mask problems. A business growing ARR 30% year-over-year looks healthy in a Snowball — until the Waterfall reveals that gross churn doubled and the growth is entirely dependent on unsustainable new logo acquisition rates.
2. Building a Waterfall without standardized movement definitions. If your team counts a downgrade as “churn” in one quarter and “contraction” in the next, your Waterfall is noise, not signal. Lock the definitions before you build the model: what exactly constitutes new, expansion, contraction, and churn.
3. Manually maintaining both in spreadsheets. When the Snowball and Waterfall live in separate Excel files maintained by different people, reconciliation breaks. The models drift apart. Board decks and operating reviews tell different stories. This is exactly the failure mode that drives finance teams to purpose-built platforms.

Key Takeaways

• The ARR Snowball tracks cumulative revenue trajectory over time, making it the right model for board decks, investor reporting, and annual planning in PE-backed SaaS companies.
• The ARR Waterfall decomposes revenue changes within a single period, making it the right model for monthly reviews, variance analysis, and operational accountability.
• Both models should be used together — the Waterfall feeds the Snowball, and the two must reconcile exactly to maintain data integrity.
• The most common mistake is treating these as competing frameworks rather than complementary views of the same underlying customer and contract data.
• Standardized movement definitions (churn, contraction, expansion, new) are a prerequisite for either model to produce trustworthy outputs.

Frequently Asked Questions

Is the ARR Snowball the same as an ARR rollforward?

The terms are often used interchangeably, but there is a subtle difference. A “rollforward” typically refers to the period-over-period reconciliation of beginning and ending ARR — which is the mechanical core of the Snowball. The Snowball adds the visual and analytical layer of showing this rollforward across multiple periods to reveal compounding dynamics and growth trajectory. In practice, if someone asks for an “ARR rollforward,” they usually want either a Snowball or a single-period Waterfall, depending on context.

Which model do PE firms prefer to see during due diligence?

Both. PE firms conducting due diligence on a SaaS acquisition will typically request a multi-year Snowball to assess the growth trajectory and the quality of compounding, alongside quarterly Waterfalls to validate the components. The Snowball tells them whether the business compounds; the Waterfall tells them whether the growth is healthy. Inconsistencies between the two are one of the fastest ways to lose credibility in a diligence process.

How does Pacer AI handle ARR Snowball and Waterfall reporting?

Pacer AI’s Customer Data Cube unifies the underlying customer, contract, and transaction data so that both the Snowball and Waterfall are generated from a single source of truth. Built on Microsoft Fabric and Power BI, the platform ensures that movement definitions are standardized, the two models reconcile automatically, and reporting is board-ready without manual spreadsheet work. Teams get the Waterfall for operating reviews and the Snowball for strategic reporting — without maintaining parallel models.

What data do I need to build both models?

At minimum, you need contract-level data with start dates, end dates, ARR values, and a customer identifier. From there, you need a reliable way to classify each contract change as new, expansion, contraction, or churn. The challenge is not collecting the data — most billing systems have it. The challenge is standardizing the classification logic so that both models tell a consistent story. This is where most spreadsheet-based approaches break down as the business scales past 200-300 customers.