The Question Pipeline Coverage Is Supposed to Answer
Pipeline coverage is a simple idea buried under a lot of vague shorthand: how much open pipeline do you need, right now, to have a reasonable shot at hitting a future revenue target, once you account for the fact that not every opportunity in the pipeline closes. Sales teams often reach for an informal multiple to answer it, but a multiple without the underlying assumptions attached is closer to a guess dressed up as a number than a real forecasting tool.
The Formula, Broken Into Its Real Inputs
Coverage math has three real inputs, not one: the revenue target, the average win rate on qualified opportunities, and the average deal size. Divide the revenue target by the average deal size to get the number of deals needed, then divide that by the win rate to get the number of qualified opportunities needed to produce enough wins. The output is your pipeline coverage requirement in dollar terms, and it is specific to your own funnel, not a shorthand multiple borrowed from a blog post, since win rate and deal size vary too much between companies for a single ratio to travel well.
Plugging Sourced Numbers Into a Worked Example
Take an illustrative example built from sourced benchmarks: if your median cost-per-SQL runs near the $762 figure reported by Directive Consulting via The Starr Conspiracy, and a target quarter needs 40 qualified opportunities to hit its pipeline requirement at your own win rate and deal size, that puts the SQL-generation cost for the quarter near $30,480 before any of those opportunities have closed. That is illustrative math built on a real, sourced input, not a guarantee your own cost-per-SQL will match the benchmark, but it shows how a single sourced figure turns an abstract coverage target into a real budget line.
Where Demo Show Rate Bends the Whole Model
None of the math above accounts for the gap between a booked demo and a shown demo, and that gap is large enough to change the plan. growthspreeofficial.com's 2026 data puts show rates at 78 to 88 percent for inbound branded demos versus 32 to 48 percent for cold outbound, meaning a cold-outbound-heavy pipeline needs roughly twice as many booked demos as an inbound-heavy one to land the same number of shown, qualified opportunities. Any coverage plan that books to a target without adjusting for source-level show rate is very likely to fall short of its own qualified-opportunity number, even if the booking number looks on track.
Why a Pay-Per-Meeting Rate Simplifies This Math
A fixed per-meeting rate turns the cost side of the coverage equation into a known constant instead of a variable shaped by ramp time, turnover, or a retainer's minimum spend, all covered in the companion SDR economics guides. At VA Horizon's $350 to $600 per held, double-confirmed SaaS demo rate, the cost of hitting a given coverage target is a straightforward multiplication once you know how many demos the show-rate-adjusted math above says you actually need, with Human + AI SDRs running the SMS conversations that book and confirm each one.
Run Your Own Numbers
The math above is a framework, not a substitute for plugging in your own revenue target, win rate, deal size, and source mix. VA Horizon's free pipeline coverage calculator is built to run exactly this calculation against your own numbers rather than a borrowed multiple, and the companion demo-to-close conversion guide covers the deal-size and win-rate side of the equation in more depth.
Common Coverage Math Mistakes
The most common mistake is blending win rate across segments that behave very differently, using one company-wide win rate to size coverage for both a fast-moving, low-ACV motion and a slow, high-ACV strategic motion, when the two likely need separate coverage targets built on their own win rates and cycle lengths. A second mistake is sizing coverage once at the start of a planning period and never revisiting it when the source mix shifts, if cold outbound starts carrying a larger share of the pipeline than it did when the plan was built, the show-rate assumption baked into the original coverage number is now stale. A third is forgetting that the cost side of hitting a coverage target is not fixed for an in-house team the way it is for a pay-per-meeting engine, ramp time and turnover both change how many demos a given headcount investment can actually produce in a given quarter, a point covered in more depth in the SDR economics guides linked below.
A fourth, quieter mistake is treating the coverage number as a one-time planning exercise instead of a running check against actuals. A quarter that starts on plan can still drift meaningfully by its midpoint if actual show rates or win rates land below the assumptions the coverage target was built on, and a team that only checks coverage at the start of the quarter will not notice the drift until it is too late to correct with additional booked demos. Revisiting the same formula against live numbers partway through the period is a small habit that catches a shortfall while there is still runway left to fix it.
What this means for you
- Pipeline coverage math has three real inputs, revenue target, win rate, and deal size, not a single borrowed multiple, since win rate and deal size vary too much between companies to travel well as shorthand.
- Sourced benchmarks like Directive Consulting's $762 median cost-per-SQL turn an abstract coverage target into a concrete budget line once plugged into your own funnel numbers.
- Demo source changes show rate by roughly two-to-one between inbound and cold outbound per growthspreeofficial.com, meaning a cold-heavy pipeline needs nearly double the booked demos to hit the same qualified-opportunity number.
Sources
The external data in this guide draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.
- The Starr Conspiracy, B2B lead generation platform benchmarks 2025
- growthspreeofficial.com, B2B SaaS demo show rate benchmarks 2026 by source, day of week, time to demo, ACV, vertical
