Pipeline coverage ratio is the total value of open pipeline for a period divided by the revenue target for that same period. If you need £1m and you’re carrying £3m of open opportunities, your coverage is 3x. It’s a quick read on whether you have enough in play to hit the number.
How it works
You take all open opportunities expected to close in the period, sum their value, and divide by quota or target. The output is a multiple. Most B2B SaaS teams treat 3x to 4x as “healthy”, on the logic that you close roughly a third of what’s open.
The right multiple isn’t universal, though. It’s just the inverse of your genuine win rate. A team that closes 40% of qualified pipeline needs about 2.5x; a team closing 20% needs 5x. Borrowing someone else’s rule of thumb without knowing your own win rate is how coverage lies to you.
Why it matters
Coverage is an early-warning system. Read at the start of a quarter, it tells you whether the problem is a pipeline-generation one (not enough coverage) or an execution one (plenty of coverage, poor conversion). Those need completely different responses, and confusing them wastes a quarter.
The common mistake
Coverage is only as honest as the pipeline underneath it. If deals sit in “stage 3” for months, if closed dates are fictional, or if stale opportunities never get purged, your coverage number is inflated by deals that will never close. In one review, a team’s reported 3.4x coverage dropped to a real 2.1x once opportunities untouched for sixty days were stripped out — they had a generation problem hiding behind stale-deal padding.
Coverage without deal stage hygiene is a comfort blanket, not a metric.
Related reading
See what pipeline velocity is and MQL-to-SQL conversion benchmarks.
More in Insights.