What is a pipeline waterfall — and how do you actually use it?
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.
Related on PULSE
- [How do you operationalize colo and hyperscaler partner-sourced pipeline handoffs between sales, finance, and delivery when no data engineer and leadership only reviews ARR waterfall monthly?](/knowledge/q10784)
- [How do you score ARR waterfall for event-sourced pipeline on Pipedrive without another point solution ?](/knowledge/q10260)
- [Top 10 revenue waterfall metrics for hyper-long sales cycles](/knowledge/q13574)
- [How do you build a lead-to-revenue waterfall in 2027?](/knowledge/q12931)
- [How do you operationalize multi-site colocation expansion motions handoffs between sales, finance, and delivery when multi-currency ARR rollups and leadership only reviews ARR waterfall monthly?](/knowledge/q10770)
- [How do you compare board-ready ARR waterfall exports from CRM vs billing system?](/knowledge/q10472)
Why Most Pipeline Waterfalls Are Wrong (And How to Fix Yours)
The most common mistake in building a pipeline waterfall is treating it like a simple accounting exercise — just tracking dollar amounts moving between stages. In practice, a waterfall that only shows dollar values masks the underlying deal behavior that actually matters. The real diagnostic power comes from layering in deal count alongside pipeline value.
A healthy waterfall should show roughly 1.5–2.5x your quota in created pipeline each quarter, with at least 60–70% of that creation happening in the first 4–6 weeks of the period. If you see a spike of created pipeline in the final month of a quarter, that’s a red flag — it suggests reps are gaming the system by dumping low-quality opps into the funnel to make their numbers look better on paper.
The second hidden dimension is velocity by bucket. Track how many days deals spend in the “progressed” versus “regressed” columns. A deal that progresses from demo to negotiation in 5 days is fundamentally different from one that takes 45 days, yet most waterfalls treat both as identical “progressed” events. The fix: add a weighted pipeline value that discounts deals based on how long they’ve been stalled in their current stage. A common heuristic is to apply a 10–15% value reduction for every 30 days a deal sits without moving forward.
How to Diagnose Specific Revenue Problems Using the Waterfall
The pipeline waterfall isn’t just a report — it’s a diagnostic tool that pinpoints exactly where your revenue engine is breaking. Here’s how to read the signals:
If “Created” is low relative to quota: Your demand generation is underperforming. Look at marketing-sourced versus sales-sourced creation. A healthy ratio is 40–60% marketing-sourced for new business. If creation is below 1.0x your quarterly quota, you need to either increase pipeline generation velocity or improve conversion rates downstream.
If “Progressed” is high but “Closed-Won” is low: Deals are moving through stages but not closing. This usually indicates a qualification problem — reps are advancing unqualified opportunities. Check if your stage progression criteria are being enforced. A common fix is to implement a “stage exit checklist” that requires specific proof points (e.g., budget confirmed, decision-maker identified) before allowing progression.
If “Regressed” exceeds 15–20% of starting pipeline: Your sales process has structural issues. Deals are falling backward, which typically means either pricing objections emerged late-stage or your champion lost internal credibility. Dig into which stages have the highest regression rates. If most regressions happen from negotiation to evaluation, your pricing team needs to be involved earlier in the cycle.
If “Pushed” is above 10% of ending pipeline: This is the most dangerous bucket. Pushed deals are the ones that get “rolled” into the next quarter — they’re not dead, but they’re not closing either. A high push rate indicates either unrealistic forecasting (reps are padding their numbers) or a compensation structure that rewards pipeline creation over actual closes. The industry benchmark for push rate is 5–8% for high-performing teams; anything above 12% requires immediate intervention.
Building a Waterfall That Your Executive Team Will Actually Use
The biggest barrier to waterfall adoption is that most executives find them confusing. To make yours actionable, follow three design principles:
Principle 1: Show only 3 time periods. Don’t try to show 12 months of data. A waterfall comparing the current quarter to the previous quarter (with a trailing 4-quarter average for context) is the sweet spot. Any more periods and the chart becomes noise.
Principle 2: Use absolute values, not percentages. Percentages hide the magnitude of problems. A 50% increase in “Created” sounds impressive until you realize it went from $200K to $300K when your quota is $2M. Always show raw dollar amounts with the percentage change as a secondary annotation.
Principle 3: Add a “Forecast Confidence” overlay. Color-code each bucket: green for buckets that are historically reliable (closed-won, closed-lost), yellow for moderately reliable (created, progressed), and red for unreliable (regressed, pushed). This instantly shows executives where the uncertainty lives. For example, if your “Progressed” bucket is 40% of your ending pipeline but it’s colored red because historically only 30% of progressed deals actually close, the team knows to discount that number immediately.
The final touch: include a one-sentence interpretation at the bottom of every waterfall. Something like: “This quarter’s pipeline is 15% thinner than last quarter because we lost 3 large enterprise deals in stage 5 — we need to rebuild our enterprise pipeline before Q3.” Without that narrative, the waterfall is just a pretty chart. With it, it becomes the single most valuable slide in your board deck.
FAQ
What’s the difference between a pipeline waterfall and a pipeline snapshot? A snapshot shows your total pipeline value at one moment—like a single frame of a movie. A waterfall shows the movement between two periods, breaking down exactly what was created, progressed, regressed, won, lost, or pushed. The waterfall reveals the "why" behind the change, not just the ending number.
Do I need a specific CRM or tool to build a pipeline waterfall? No, any CRM that tracks stage history and close dates can generate the seven buckets. Most teams build it in spreadsheets or BI tools by pulling opportunity-level data and applying date filters for the period. The logic is straightforward, though data cleanliness (like accurate stage timestamps) is critical.
How often should I review a pipeline waterfall? Monthly or quarterly is typical, depending on your sales cycle length. Monthly works well for shorter cycles (e.g., SaaS), while quarterly is common for enterprise deals that take longer to move. Reviewing too frequently (weekly) can be noisy, but you can run it ad hoc when forecasting goes off track.
What’s the most common insight from a pipeline waterfall? The "regressed" and "pushed" buckets often reveal hidden risks—deals that slipped stages or got delayed are early warning signs for missed forecasts. A high "created" but low "progressed" ratio might indicate weak qualification or too many early-stage deals that never advance.
Can a pipeline waterfall help with sales forecasting? Yes, indirectly. It doesn’t predict future closes, but it diagnoses why past forecasts were wrong. By seeing exactly where pipeline leaked (e.g., lost deals, regressions), you can adjust assumptions for future periods. It’s a diagnostic tool, not a predictive model.
Is a pipeline waterfall useful for small teams or startups? Absolutely. Even with a small pipeline, the waterfall shows whether new deals are replacing won/lost ones and if progress is real. For early-stage teams, it’s a simple way to spot if you’re just adding more leads without closing or advancing them.
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.