The Demand Waterfall is a B2B revenue funnel framework (developed by SiriusDecisions, now Forrester) that models the progression of buyer interest from Inquiries through Marketing Qualified Leads, Sales Accepted Leads, Sales Qualified Leads, and Closed/Won, with defined conversion metrics at each stage.
Quick Answer
The Demand Waterfall is a B2B revenue funnel framework (developed by SiriusDecisions, now Forrester) that models the progression of buyer interest from Inquiries through Marketing Qualified Leads, Sales Accepted Leads, Sales Qualified Leads, and Closed/Won, with defined conversion metrics at each stage.
The Demand Waterfall's primary value is creating shared stage definitions that align marketing and sales on lead quality standards, conversion metrics, and stage-specific accountability.
Typical B2B enterprise conversion benchmarks: 10–25% Inquiry-to-MQL, 40–60% MQL-to-SAL, 50–70% SAL-to-SQL, 20–30% SQL-to-Close — use these to identify your biggest waterfall conversion gap.
Modern ABM programs shift from contact-level waterfall stages to account-level engagement tracking — the 2017 Demand Unit Waterfall and subsequent ABM adaptations reflect this evolution.
Key Takeaways
The Demand Waterfall's primary value is creating shared stage definitions that align marketing and sales on lead quality standards, conversion metrics, and stage-specific accountability.
Typical B2B enterprise conversion benchmarks: 10–25% Inquiry-to-MQL, 40–60% MQL-to-SAL, 50–70% SAL-to-SQL, 20–30% SQL-to-Close — use these to identify your biggest waterfall conversion gap.
Modern ABM programs shift from contact-level waterfall stages to account-level engagement tracking — the 2017 Demand Unit Waterfall and subsequent ABM adaptations reflect this evolution.
How Demand Waterfall Works
The Demand Waterfall was introduced by SiriusDecisions in 2006 as a framework for modeling B2B revenue generation by defining standardized stages from first buyer interest to closed revenue. The original model tracks: Inquiries (raw form fills, event registrants, content downloads), Marketing Qualified Leads (inquiries that meet basic qualification criteria), Sales Accepted Leads (MQLs reviewed and accepted by sales development as worth pursuing), Sales Qualified Leads (accounts where a sales rep has confirmed active opportunity), and Closed/Won. Each stage has defined entry criteria, responsible team, and a conversion rate that can be benchmarked and optimized.
Why Demand Waterfall Matters for B2B Marketing
The waterfall's value for B2B organizations is in creating shared accountability vocabulary between marketing and sales. Without standardized stage definitions, "lead" means something different to a marketer (form fill), a sales development rep (qualified conversation), and an account executive (active opportunity). This definitional gap produces persistent friction between marketing ("we're generating thousands of leads") and sales ("the leads are terrible"). The waterfall forces both teams to agree on stage criteria, conversion rate benchmarks, and which function is responsible for lead quality at each handoff.
Demand Waterfall: Best Practices & Strategic Application
Conversion rate benchmarks across the waterfall vary by industry and deal complexity. Typical B2B enterprise software benchmarks: Inquiry-to-MQL 10–25% (reflecting MQL qualification thresholds); MQL-to-SAL 40–60% (how many marketing-qualified leads sales development accepts as worth a touch); SAL-to-SQL 50–70% (how many accepted leads produce a real conversation with a buying signal); SQL-to-Closed/Won 20–30% (how many sales-stage opportunities close). These benchmarks are useful for identifying which waterfall stage has the biggest conversion gap and directing investment accordingly.
Agency Perspective: Demand Waterfall in Practice
The original 2006 Demand Waterfall has evolved through multiple iterations as B2B buying behavior changed. The 2012 revision added Teleprospecting-sourced leads alongside marketing-sourced. The 2017 Demand Unit Waterfall shifted from individual contacts to buying groups ("demand units"), reflecting the reality that B2B purchases involve committees. The ABM-adapted waterfall replaces contact-level stage tracking with account-level engagement and intent stages — mapping named account progression rather than individual lead progression. SiriusDecisions-now-Forrester continues publishing updated versions, but most organizations implement a simplified version tailored to their sales motion.
Frequently Asked Questions: Demand Waterfall
The Demand Waterfall is a B2B revenue funnel framework (developed by SiriusDecisions, now Forrester) that models the progression of buyer interest from Inquiries through Marketing Qualified Leads, Sales Accepted Leads, Sales Qualified Leads, and Closed/Won, with defined conversion metrics at each stage.
An MQL (Marketing Qualified Lead) is a prospect that marketing has determined meets basic qualification criteria — typically based on firmographic fit and behavioral signals (content engagement, form fills, website activity). An SQL (Sales Qualified Lead) is an MQL that has been reviewed by a sales rep who confirmed an active buying intent through direct conversation. MQL is a marketing judgment; SQL is a sales judgment. The gap between MQL and SQL conversion rate is the most common source of marketing-sales friction in B2B organizations.
Start by mapping your current stage definitions and measuring conversion rates between each stage using CRM data. Identify the stage with the lowest conversion rate — this is where to focus investment. If Inquiry-to-MQL is low, review MQL criteria (are they too strict or is traffic quality low?). If MQL-to-SAL is low, investigate lead quality (are MQLs being generated from ICP sources?). If SAL-to-SQL is low, examine SDR follow-up quality and speed. Each conversion rate points to a specific intervention.
The contact-level Demand Waterfall is less relevant when ABM is the primary go-to-market motion, because ABM tracks account engagement rather than individual lead progression. However, the underlying principle — defining stages, setting conversion benchmarks, and aligning marketing and sales on shared definitions — remains valuable in any B2B model. ABM adaptations of the waterfall track stages like "Target Account Identified," "Account Engaged," "Opportunity Created," and "Closed/Won" at the account level rather than the contact level.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes our services for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
