What is a pipeline waterfall — and how do you actually use it?
Direct Answer
A pipeline waterfall is a movement report — not a snapshot — that shows how your sales pipeline changed period-over-period by walking through seven buckets: starting balance, plus newly created opps, plus stage-progressed, minus stage-regressed, minus closed-won, minus closed-lost, minus pushed.
The math is: starting + created + progressed − regressed − closed-won − closed-lost − pushed = ending. It is the canonical "where did our pipeline actually go this quarter?" report, and it is the single most diagnostic artifact in RevOps because the buckets between starting and ending are where every forecasting problem lives.
TL;DR
- A pipeline waterfall is a movement report (period-over-period), distinct from a pipeline coverage report which is a point-in-time snapshot.
- Seven buckets: starting balance, created, stage-progressed, stage-regressed, closed-won, closed-lost, pushed (close-date slipped).
- "Pushed" is the biggest hidden bucket and the most common indicator of broken forecasting discipline.
- A healthy $20M pipeline and a sick $20M pipeline look identical on a coverage report — the waterfall is what tells them apart.
- Tools: Salesforce Pipeline Inspection (free, native), Clari Flow ($60–100K/yr), or Sigma/Looker on raw SFDC data for data-mature teams.
The 7 Buckets Plus Worked Example
The honest 2027 take is that most companies report only "starting pipeline" and "ending pipeline" and skip the seven buckets in between. That is malpractice. The whole point of the waterfall is to expose where pipeline gets stuck, and a coverage report fundamentally cannot do that.
A company sitting on $20M in pipeline with 70% of new opps cleanly converting through stage 3 looks identical, on a coverage report, to a company where pipeline is "stable" only because 50% of new opps die before stage 3 and an equal volume of new opps replaces them every quarter.
One is a healthy business. The other is a treadmill. The waterfall is what separates them.
| Bucket | Formula | Healthy Signal | Red Flag |
|---|---|---|---|
| Starting balance | Open pipe at period open | Stable or growing QoQ | Shrinking three periods in a row |
| Created | New opps added this period | At or above quota coverage × velocity decay | Below replacement rate |
| Stage progressed | Opps that moved to a higher stage | 30–50% of starting pipe advances | Less than 20% advancing |
| Stage regressed | Opps that moved to a lower stage | Under 10% of starting pipe | Over 10% (premature advancement) |
| Closed-won | Won deals this period | Tracks to quota | Below historical win rate |
| Closed-lost | Lost deals this period | Concentrated reasons (e.g., price, timing) | Scattered, no learnings |
| Pushed | Close-date slipped to a later period | Under 20% of starting pipe | Over 30% (forecast accuracy is broken) |
Worked example. A $25M ARR Series B SaaS company opened Q3 looking at an $18M open pipeline and a clean 3.2x coverage ratio. By every executive dashboard the quarter looked fine.
Their new RevOps lead built a proper waterfall in Sigma against raw Salesforce data and the picture inverted. Of the $18M open at Q3 start, 38% — $6.8M — had been pushed at least once during the quarter (close-date slipped). Stage-regressed was running at 14%.
Created was healthy at $7M, but closed-won was only $4.2M against a $6M target. The team tightened forecasting discipline using the waterfall as the weekly artifact (no more than one push allowed per opp without a manager sign-off, stage regressions reviewed deal-by-deal in the weekly forecast call).
Next quarter pushes dropped to 18%, regressions dropped to 7%, and quota attainment moved from 71% to 86%. None of that diagnosis was possible on a coverage report.
The 4 Diagnostics the Waterfall Surfaces and Pipeline Coverage Hides
Four diagnostics fall out of the waterfall the moment you build it, and none of them are visible on a coverage snapshot. First, if pushed is greater than 30% of period-opening pipeline, your forecast accuracy is broken — AEs are either sandbagging close dates or genuinely cannot predict them, and either way the forecast number leadership is reading is fiction.
Second, if regressed is greater than 10% of starting pipe, AEs are advancing deals prematurely to look good on their stage-3+ pipeline metric, then quietly walking them back later. This is the most common forecasting pathology in mid-stage SaaS. Third, if created is less than your required quota coverage multiplied by your velocity decay, a top-of-funnel gap is forming that will not show up in revenue for two to three quarters — you need to know now, not then.
Fourth, if closed-won is greater than created, you are depleting pipeline faster than you are generating it, which means you are under-investing in pipeline generation regardless of how good the quarter looks. The waterfall surfaces all four mechanically. The coverage report hides all four.
Tooling — Salesforce Pipeline Inspection vs Clari vs Sigma
Salesforce Pipeline Inspection is the native option, included in Sales Cloud Enterprise and above at no additional cost. It shows changes since a snapshot date, supports filtering by stage and owner, and handles the seven buckets out of the box if you configure it properly. For 80% of companies under $50M ARR this is the right answer — free, integrated, and good enough.
Clari Flow runs $60–100K per year and is the right call for companies above $100M ARR who need cross-functional forecasting workflows, scenario modeling, and AI-driven deal scoring layered on top of the waterfall. The product genuinely is better than native SFDC at this scale; the price reflects that.
InsightSquared is the legacy option — still functional, generally being displaced by Clari in new RFPs. The cheapest power-user move for data-mature RevOps teams is to skip the BI vendors entirely and build the waterfall as a Sigma or Looker dashboard directly on raw Salesforce opportunity history data; this gives you full SQL control, runs for the cost of a BI seat, and forces you to actually understand the math instead of trusting a vendor's black box.
Frequently Asked Questions
Daily, weekly, or monthly waterfall? Weekly is the operating cadence for the forecast call. Monthly is the cadence for the board deck and the RevOps retro. Daily is overkill and creates noise — opp movements within a single day are rarely signal. Quarterly is too slow to course-correct.
How do you treat opps that get re-opened after closed-lost? Standard practice is to net them as a new "created" event in the period they re-open, with a flag in the opportunity history. Do not retroactively reverse the closed-lost bucket from the prior period — that breaks period integrity and makes historical waterfalls non-comparable.
Should expansion pipeline live in the same waterfall as new business? No. Run two parallel waterfalls — new business and expansion — because the buckets behave differently. Expansion has near-zero "created" volatility, much higher win rates, and a "pushed" bucket that correlates with renewal timing rather than buyer behavior.
Mixing them obscures both.
Sources
- Clari, "Pipeline Reports and the Waterfall Methodology," product documentation, 2024.
- Salesforce, "Pipeline Inspection in Sales Cloud," official documentation, 2025.
- Pavilion, "2024 Forecasting and Pipeline Health Survey," GTM benchmarks report.
- Gong Labs, "What Top-Performing Sales Teams Do Differently in Pipeline Management," 2024 study.
- Bessemer Venture Partners, "State of the Cloud 2025," sales efficiency benchmarks.
- Force Management, "Command of the Message and Pipeline Hygiene Frameworks," 2024.
- SaaStr, "The Pipeline Waterfall: The Most Important Report You're Not Running," Jason Lemkin, 2023.
- RevOps Co-op, "Building a Pipeline Waterfall in Sigma — A Practical Guide," community playbook, 2024.