Pipeline Coverage Ratio: Derive It From Your Win Rate, Not From Folklore
By Sarah Rodriguez · October 19, 2026
Category: pipeline-generation
The coverage multiple most teams plan with is a conversion-rate assumption in disguise. Here is how to derive your own ratio by source and stage, and why it should fall as the quarter runs.
Key takeaways
The problem Teams size a quarter around a coverage multiple they inherited, without ever checking the conversion rate and cycle length that multiple silently assumes.
Core insight Required coverage is the reciprocal of your own conversion rate, and it is a curve that descends through the quarter rather than a line you hold at every point.
Practical outcome Derive the requirement per source, per deal band and per stage from four quarters of closed business, count only deals whose cycle fits the period, and report raw and achievable coverage side by side.
Ask ten revenue leaders what coverage they run and most will answer with a number they inherited. Nobody in the room remembers who measured it, on which business, in which year. A multiplier that arrived without a method is not a planning input. It is folklore that has been given a column in the forecast sheet.
This is for heads of sales and RevOps owners who build a quarter on top of some coverage number. The claim here, in one line: the multiplier you need is the reciprocal of your own conversion rate, applied source by source, and counted only on opportunities that can realistically land inside the period.
Where That Famous Number Came From
Coverage itself is uncomplicated. Take the open opportunity value, divide by the number you owe for the period, and you have it. The reference entry Metabase keeps on the metric defines it as "open pipeline divided by the quota or target it has to cover in a period" and describes the familiar range as a heuristic rather than a law. That is an accurate statement of its standing.
Salesforce is more specific about the conditions in its own guide to pipeline coverage, which says the ratio holds only when a team converts exactly a third of what it opens and takes exactly a year to do it. The same guide names the two variables that genuinely move the answer: the share of pipeline you convert, and how long conversion takes. Neither is a constant. Neither is even the same for two reps sitting on the same team.
The Rule Survives Because It Is Easy to Inspect
Give the heuristic its due. It fits on a slide, a new manager can apply it on day one, and it hands a pipeline review a shared vocabulary. A crude rule an organisation actually follows beats a precise model that lives in one analyst's notebook. Plenty of teams have run on it for years without harm, and if their conversion sat near a third, they were right to.
The damage starts when the conditions quietly stop holding and nobody re-derives the figure. Ebsta's 2025 GTM Benchmarks announcement, built on $48 billion of pipeline data and a survey of 2,000 chief revenue officers, reports that 78% of sellers missed quota in 2025, against 69% the year before. An inherited multiplier is one of the quieter routes to that outcome, because the coverage reads as healthy right up until the week it does not.
Run the Reciprocal, Not the Rumour
The mechanism is arithmetic, not research. Required coverage is one divided by your conversion rate. Convert half of what you open and you need twice your target in play. Convert a quarter of it and you need four times the target. Metabase sets the same relationship out next to a weighted variant, which sums each deal's value times its stage probability before dividing by the target, because raw coverage treats an early deal and a late one as equals and they are plainly not equal.
- Converting about half of opened opportunities: roughly two turns of pipeline.
- Converting about a third: roughly three turns, which is where the famous rule sits.
- Converting about a quarter: roughly four turns.
- Converting about a fifth: roughly five turns.
- Converting about one in seven: closer to seven turns.
Read that list as a sensitivity table, not as a set of benchmarks. The point is the slope. A team that believes it converts a third, and in fact converts a fifth, is carrying a shortfall of two full turns of pipeline and will not discover it until the back half of the quarter, when there is no time left to build anything new.
Coverage Is a Moving Quantity, Not a Snapshot
The second condition is timing, and it is the one that produces the late surprise. The ratio you measure in week one and the ratio you measure in week ten are not the same quantity. The remaining target shrinks as the period runs, and the open deals still standing are the ones that have already proved slow. Jeff Ignacio, who heads go-to-market operations at Keystone AI, put it plainly on the RevOps Lab podcast in March 2025: coverage "converges from three and it shrinks down to one" across a quarter, and he treats a fall below parity as the real alarm rather than any fixed multiple.
That reframes what a coverage target is for. It is not a line you hold all period. It is a curve you expect to descend, and the useful question is whether you are descending on schedule. For the weekly version of this problem, our piece on the week your pipeline review is actually measuring covers the reporting habit that hides the slope.
Four Moves That Replace the Inherited Figure
You can have a number of your own inside a single quarter. It takes four passes over data you already hold.
- Pull four quarters of closed business and split it by source. Referral, partner, inbound and outbound almost never convert alike, so a blended rate hides the mix risk. Work out a requirement per source, then add the requirements rather than averaging the rates.
- Split again by deal size band. Bigger deals carry longer cycles and more approvers, so they push the requirement up and the timing out at the same time.
- Weight by stage, or at the very least separate early from late. Lean on the conversion each stage has actually produced, not the probability somebody typed into the CRM during implementation and never revisited.
- Filter by achievable close date before you count anything. An opportunity opened today with a cycle longer than the time remaining is next quarter's pipeline. Counting it flatters the ratio and does nothing else.
Do the clean-up before the arithmetic, never after. Dead opportunities inflate coverage more effectively than anything a rep could manage on purpose, and the exercise in a five-day pipeline clean-up leaves you with a denominator worth dividing into. If the resulting number says the gap is structural rather than seasonal, the repair sits upstream, in building pipeline that sustains itself.
Two Sources, One Target, Two Different Answers
Here is the shape of the problem, with invented inputs you should swap for your own. A team owes $1,000,000 of new business this quarter and draws from two sources that behave nothing alike.
- Partner and referral work converts at roughly two in five. If the plan expects $400,000 from that source, it needs about $1,000,000 of it open.
- Outbound converts at roughly three in twenty. If the plan expects $600,000 from outbound, it needs about $4,000,000 open.
- Total requirement: about $5,000,000, which is five turns of the target rather than three.
A blanket rule would have declared $3,000,000 sufficient, and the team would have opened the quarter short by two turns without a single warning sign on the dashboard. Notice what drives the answer. It is the channel mix, almost entirely. Shift the expected split between those two sources and the requirement moves further than any realistic improvement in rep behaviour could move it, which is why the mix belongs in the coverage conversation and why the short list of pipeline numbers worth reviewing ought to carry conversion by source.
The Part of This Worth Arguing With
Here is the position: a fixed coverage multiple is not harmless simplicity, it is an unsigned forecast. When a team adopts one, somebody has committed to a conversion rate and a cycle length without anybody saying so aloud, and the commitment stays invisible precisely because it wears the costume of a convention. The three sources here, a vendor's own guide, a metric reference and an operator describing what he watches, land in the same place from different directions: the multiple is downstream of conversion, so conversion is the thing to measure.
On a small book of business, the case above weakens. Close a handful of deals a quarter and a reciprocal computed from your own history is a very noisy estimate, and a stable convention may genuinely beat an over-fitted number that swings every time one large deal lands or slips. If that is you, keep the simple rule, but keep it honestly. Write down the conversion rate it implies, put that figure on the same slide as the target, and revisit it once you have enough closed business to say anything. The failure mode is not using a rule of thumb. It is using one while pretending it contains no assumption.
What to Put in Monday's Review
Bring two numbers where you used to bring one. The raw ratio, and the ratio restricted to opportunities whose cycle can finish inside the period. When those two sit far apart you do not have a coverage problem, you have a timing problem, and the remedies look nothing alike. Then bring the reciprocal you derived from your own closed business, with the four quarters it came from attached, and let the room argue about the inputs instead of the multiple. Arguments about inputs produce better plans. Arguments about whether the answer should be three produce nothing at all.
Frequently Asked Questions
What is a pipeline coverage ratio?
It is open opportunity value divided by the target for the period. Carrying three dollars of live pipeline against every dollar you owe gives you a ratio of three. It is a sizing check, not a forecast.
How do I work out the coverage my team actually needs?
Divide one by your conversion rate for the segment, using four quarters of your own closed business rather than a published benchmark. Do it per source and per deal size band, then add the requirements together instead of averaging the rates.
Why does my coverage ratio fall as the quarter progresses?
Because the remaining target shrinks while the slowest deals stay open. A descending ratio is normal. What matters is whether it is descending on schedule and whether it stays above parity in the closing weeks.
Should early-stage and late-stage pipeline count equally?
No. Apply each stage's own historical conversion rate, or at minimum report early and late pipeline as separate lines. A ratio made mostly of first-meeting opportunities is weaker than the same ratio made of deals in legal review.