The demand unit waterfall is a demand model that measures buying groups instead of individual leads. Published by SiriusDecisions and carried forward by Forrester, it exists because B2B purchases are made by committees, and a funnel that counts contacts one at a time misrepresents how those purchases form.
The unit of measurement changes everything
In a lead funnel, five people from one company downloading the same report create five records, five scores, and five routing events. Sales works one account and reports one outcome, so the conversion math has a denominator that never matched reality. The demand unit waterfall collapses those five into one buying group and follows that group forward. Volume drops, conversion rates rise, and both numbers become comparable to what sales sees.
The stages
| Stage | What it holds |
|---|---|
| Target demand | Buying groups in the addressable market that fit the profile |
| Active demand | Groups showing a need through behavior or intent |
| Engaged demand | Groups interacting with the company directly |
| Prioritized demand | Groups that meet fit and engagement criteria worth working |
| Qualified demand | Groups sales has accepted and is actively pursuing |
What it costs to run
The model depends on identity resolution. Contacts have to resolve to the right account, and accounts have to be deduplicated, before any buying group can assemble. It also requires a rule for splitting an account into multiple demand units when two teams pursue unrelated needs. Teams that skip that rule end up with one giant demand unit per enterprise account, which hides real opportunities and makes the qualified stage look artificially thin.
Reading it against pipeline
The waterfall produces a count of qualified buying groups, and each of those becomes an opportunity or does not. That count is the honest input to a creation forecast, since it maps one to one against opportunity records. Multiply qualified demand by the historical create rate and average deal size to get the pipeline the model expects to produce, then compare it against the pipeline coverage the plan requires. Where the model earns its cost is in account-based motions, because that is where lead counting distorts the ratios most and where forecast accuracy on new business suffers as a result.
Frequently Asked Questions
What is a demand unit?
A demand unit is a buying group inside an account that shares one need and one budget. A single enterprise account can contain several demand units, such as one team evaluating forecasting software and another evaluating a CRM add-on. The model counts those as two units, because they convert independently.
How is the demand unit waterfall different from a lead funnel?
A lead funnel counts people and treats each contact as a separate conversion event. The demand unit waterfall counts buying groups and rolls every contact from the same group into one record. That change removes the double counting that happens when four people from one company download the same asset.
What has to be in place before the model works?
Reliable lead-to-account matching and a clear definition of what constitutes a distinct need inside an account. Without matching, contacts scatter across duplicate account records and the buying group never assembles. Most teams underestimate this step, and it is where implementations stall.
Does the demand unit waterfall improve forecasting?
It improves the input. Opportunities are created by buying groups, so counting buying groups produces a denominator that matches how deals actually form. A lead-based funnel overstates volume in account-based motions and understates conversion, which distorts every ratio built on top of it.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like demand unit waterfall into prescriptive action for your team.
Schedule a Demo