Demand Waterfall

A staged model tracking volume as it falls from inquiry through qualification to closed revenue, giving marketing and sales a shared vocabulary.

What it standardised

Before it, marketing and sales counted different things and disputed the difference. The waterfall's contribution was a common set of stage names with defined transitions, which made the disagreement measurable rather than rhetorical.

Its limitation

It models a linear path. Real buying involves accounts entering mid-way, stalling, and re-entering months later. Use it as a measurement frame, not as a description of the buyer's journey.

The value is the shared definition

The specific stage names matter far less than both teams using the same ones with the same entry criteria.

How to use one

  1. Define every stage with an exit criterion before measuring anything. A waterfall built on inconsistent stages produces precise-looking noise.

  2. Measure on cohorts, following a fixed set forward, rather than dividing this month's stage counts by each other.

  3. Work backwards from the revenue requirement to the inquiry volume needed at your conversion rates. That is the waterfall's main practical use.

  4. Recalculate the required volume whenever conversion rates change materially, rather than annually by default.

  5. Segment by source before drawing conclusions. Blended conversion rates hide the channel actually causing a shortfall.

Where it misleads

  • It assumes a linear progression that real buyers do not follow, and it cannot represent accounts that re-enter or skip stages.

  • It is lead-centric, which fits poorly with account-based and product-led motions where the unit is not an individual.

  • Required-volume calculations compound every conversion assumption, so small errors in each stage produce a large error at the top.

  • Waterfalls encourage optimising the stage with the worst percentage rather than the one losing the most revenue.

RELATED TERMS

COMMON QUESTIONS

What is a demand waterfall?
A staged model tracking volume as it falls from inquiry through qualification stages to closed revenue, with a conversion rate at each step. Its main practical use is working backwards: how many inquiries are needed to produce a given revenue number at your current rates.
How do you use a demand waterfall for planning?
Start from the revenue target, divide by average deal value for required wins, then work up through each conversion rate to the inquiry volume required. The exercise is most useful for showing when a target requires a volume that is not achievable with current demand generation.
What makes a demand waterfall unreliable?
Inconsistent stage definitions, which produce precise-looking numbers built on inconsistent data. The second issue is compounding: the required-volume calculation multiplies every conversion assumption together, so modest errors at each stage produce a large error at the top.
Is the demand waterfall still relevant?
For lead-centric motions with a clear linear progression, yes — as a planning device rather than a description of behaviour. It fits poorly with account-based and product-led motions, where the unit is an account or a usage event rather than an individual inquiry.

Learn how to apply this: RevOps 101: Revenue Operations Foundations

Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.

See the course