What is Waterfall Model?

The waterfall model is a demand generation framework that moves potential buyers through a sequence of progressively narrower stages: TAM (total addressable market), SAM (serviceable addressable market), ICP (ideal customer profile), MQL (marketing qualified lead), and SQL (sales qualified lead).

At a glance

• Used by B2B revenue teams to map and measure every stage from market to pipeline.
• Each stage has a conversion rate; knowing those numbers makes forecasting honest.
• Most useful when instrumented with real CRM data, not rough estimates.
• Originally built for inbound motion; pure outbound leads can distort the math.
• Common failure: skipping a defined ICP, which corrupts every downstream stage.

How does the waterfall model actually work?

Think of it as a volume problem with a filter problem attached. You might start with 50,000 companies in your TAM. After applying industry, geography, and revenue filters, your SAM might be 12,000. Overlay ICP criteria such as company size, tech stack, and buying signals, and you are at 3,000 accounts. From those, marketing converts a fraction into MQLs based on engagement, and sales then qualifies those down to SQLs that enter pipeline.

Each stage has a conversion rate. A team running this well knows their numbers at every step. For example: 3,000 ICP accounts generating 180 MQLs at 6%, with 90 of those converting to SQLs at 50%. If average ACV is $48,000, that waterfall shows exactly how much pipeline capacity exists before a single rep picks up the phone.

Why do revenue teams care about it?

The waterfall makes forecasting concrete. Instead of saying “we have a lot of leads,” a team can say “we have 90 SQLs at an average deal size of $48K with a 22% close rate, projecting roughly $950K in closed revenue this quarter.” That is a different conversation with a board or a CFO.

It also isolates where the real problem sits. Low MQL volume points to a marketing coverage or messaging problem. High MQL-to-SQL drop-off usually means the ICP definition is too loose or MQL scoring is broken. High SQL-to-close drop-off is a sales motion or competitive positioning problem. The waterfall separates those failure modes cleanly, so fixes can be targeted rather than scattered.

Common mistakes and misconceptions

• Skipping ICP entirely. Moving straight from SAM to MQL without a real ICP filter produces leads that burn rep time and drag down conversion rates across every stage.
• Treating MQLs as a vanity metric. A high MQL number means nothing if SQL conversion sits at 8%. Marketing and sales need shared definitions, not separate scorecards.
• Using static TAM and SAM numbers. Markets shift. A SAM built two years ago may exclude entire segments that are now buyers, or include segments that have left your category.
• Forcing outbound into the same model. The waterfall was originally built for inbound motion. Cold outbound and BDR-sourced pipeline often bypass the top stages entirely, so mixing them with inbound distorts conversion math.

How does it connect to adjacent concepts?

Waterfall vs. ABM

The waterfall model and account-based marketing pull in opposite directions by design. ABM flips the funnel: instead of letting leads cascade down from a broad universe, specific accounts are selected first and motion is built around them. Many mature GTM teams run both in parallel, using waterfall logic for inbound and broad outbound, and ABM for top-tier named accounts.

Waterfall and CAC

CAC sits downstream from the waterfall. If SAM-to-SQL conversion is inefficient, money spent on paid channels, BDR time, and content goes toward accounts that were never going to buy. That waste shows up in CAC without ever appearing in the waterfall itself, which is why both models need to be reviewed together.