Skip to main content
Home Solutions Approach About Blog
Let's Talk →
← All Articles
Pipeline Health

Pipeline Coverage Ratio: The Single Metric That Predicts Whether You'll Hit Your Number

Most revenue teams find out they're going to miss their quarter in the last two weeks of it. At that point, there's nothing to do — the pipeline that was going to close is either closed or not, and whatever didn't close is now a Q+1 problem. Missing a quarter this way isn't a close rate problem. It's a pipeline coverage problem that showed up too late to fix.

Pipeline coverage ratio is the metric that catches this problem in time to act on it. It's simple, powerful, and underused by most teams that aren't running a mature RevOps function.

What Pipeline Coverage Ratio Is

Pipeline coverage ratio = total open pipeline value ÷ quota for the period.

If you have $4M of open pipeline and your quota is $1M, your coverage ratio is 4x. If your historical close rate from qualified pipeline is 25%, you need 4x coverage to hit your number. If you have 2.5x coverage, you're likely to miss by a significant margin — and you know that now, not in week 12.

The coverage ratio that makes you "safe" depends entirely on your historical close rate. A team with a 40% close rate needs 2.5x coverage. A team with a 20% close rate needs 5x. The right coverage number for your business comes from your own historical data, not from an industry benchmark.

The calculation most teams miss: Pipeline coverage ratio should be calculated on qualified pipeline — deals that have actually progressed past initial qualification. Including early-stage or unqualified deals inflates your coverage number and gives you false confidence. A 4x coverage ratio full of discovery calls is not the same as a 4x coverage ratio full of proposals and verbal commits.

How to Calculate Your Required Coverage Ratio

Pull the last 6-8 quarters of data. For each quarter, calculate: how much total qualified pipeline existed at the start of the quarter, and how much revenue closed by the end. Divide closed revenue by starting qualified pipeline. That's your close rate from qualified pipeline. Take the inverse — 1 ÷ close rate — and you have your required coverage ratio.

Example: over 8 quarters, your average close rate from qualified pipeline is 28%. Your required coverage ratio is 1 ÷ 0.28 = 3.6x. You need 3.6x pipeline-to-quota to have a high probability of hitting your number.

Run this calculation by segment and by rep if your pipeline mix is diverse. A team with both enterprise and SMB deals will have different close rates for each — and aggregate coverage can hide a major gap in one segment.

When to Check It

Pipeline coverage should be checked at three points each quarter:

By week 10 of a 13-week quarter, coverage is destiny. The deals that are going to close are already in the pipeline. What changes in the last three weeks is close rate — deal execution — not coverage.

What to Do When Coverage Is Low

A coverage deficit has two causes: not enough pipeline was generated (a marketing and outbound problem) or too much pipeline was lost to stalls and losses faster than expected (a sales execution or qualification problem).

Diagnosing which one is the issue determines the response. If it's a generation problem, the fix is more outbound, a push on inbound content, or a partner/referral motion. If it's a loss/stall problem, the fix is rep coaching, qualification tightening, or deal review to identify what's stalling and why.

Both fixes take weeks to produce results. That's why mid-quarter is the last meaningful intervention point — and why tracking coverage at week one is so important. A coverage gap found in week one is fixable. The same gap found in week ten is a miss in progress.

For the full pipeline health toolkit, see the pipeline visibility guide and the RevOps KPIs guide.

Know whether you're going to hit your number — before it's too late to change it.

Take the free RevOps Scorecard to assess your pipeline health and forecasting infrastructure in about 3 minutes.

Take the Free Scorecard →