Someone told you to keep three times your target in pipeline. That advice is from the 1990s, and for most B2B firms it is quietly wrong. Here is the real math, from your own win rate.
// The short version
The "keep 3x your target in pipeline" rule is a 1990s relic. It is only correct for one win rate: 33%.
The real formula is coverage = 1 / your win rate. Close 20% and you need 5x; close 50% and you need 2x.
The average B2B win rate today is about 21% across all opportunities, 29% for qualified ones, so a flat 3x leaves most teams under-covered.
Win rate falls as deals get bigger: roughly 28-35% for SMB, 12-18% for enterprise. Use one win rate per segment, not a blend.
Coverage tells you if you have enough pipeline; velocity tells you how fast it turns into cash. They share the same win rate, so fixing it improves both.
Coverage lies when you count leads as pipeline, count out-of-period deals, or use a win rate that is too high.
Build it on qualified pipeline, an in-period view, and a measured win rate, then review weekly while you can still act.
At some point a sales advisor, a board member, or a blog post told you the rule: keep three times your revenue target in open pipeline. The famous 3x coverage. It is repeated so often it has the ring of physics. It is not physics. It is a heuristic from the 1990s enterprise software era, and applying it blindly will either make your team chase pipeline they do not need or walk confidently into a quarter they were always going to miss.
The right amount of pipeline is not 3x. It is not any fixed multiple. It is a number that falls directly out of one thing you can measure: how often your team actually wins. This post shows you how to calculate the real number, using real B2B benchmark data instead of received wisdom.
The core insight
3x is not a universal target. It is the right answer for exactly one win rate: 33%. The rule was born in a world of enterprise deals that closed about a third of the time. If your win rate is not 33%, the rule is not yours, and using it anyway is how teams discover a shortfall in week twelve that was baked in during week one.
Where the 3x rule came from, and why it broke
The 3x benchmark made sense in a specific world: large enterprise software deals, win rates around a third, long cycles, the era of Oracle and SAP. In that world, if you closed roughly one in three qualified deals, holding three times your quota in pipeline produced just enough wins, with a buffer for deals that slipped to the next quarter.
The arithmetic was sound. The problem is that the assumption underneath it, a 33% win rate, is not your assumption. The average B2B win rate across all opportunities is closer to 21%, and around 29% even for qualified opportunities. Plug those into the same logic and 3x is no longer enough. It is a shortfall waiting to be discovered.
This is not a number you set once and forget. Win rates move with your market, your pricing, and your mix of deals, so the coverage you needed last year may not be the coverage you need now. Anchoring on a fixed thirty-year-old multiple ignores that entirely.
The 3x rule was sound arithmetic for a 33% win rate. The trouble is that almost nobody closes at 33% anymore.
What pipeline coverage actually measures
What pipeline coverage actually measures
Coverage answers one question: do we have enough open, qualified pipeline, at our current close rate, to hit the number this period? It is a leading indicator. Unlike closed revenue, which reports what already happened, coverage tells you in week two whether the quarter is statistically winnable on current assumptions. That is why it sits at the top of every serious weekly forecast.
The basic formula is simple: total qualified pipeline value divided by your quota for the same period. Three dollars of pipeline for every dollar of target is 3x coverage. But that raw ratio hides the only variable that matters, and the next section fixes it.
The only coverage formula you need
Forget the multiple. The real required coverage is the inverse of your win rate.
The formula
Required pipeline coverage
Divide one by your historical win rate on qualified opportunities. That is the coverage you need. Everything else is a rule of thumb pretending to be a law.
required coverage = 1 / (your win rate)
Work it through. If you close 33% of qualified deals, you need 1 / 0.33, which is 3x. That is where the famous rule comes from, it is simply the answer for one specific win rate. If you close 20%, you need 1 / 0.20, which is 5x. If you close half your qualified deals, you need only 2x. The rule was never universal. It was one data point that got mistaken for a law.
Table 01 · Same target, four pipeline requirements
Quarterly target | Qualified win rate | Pipeline you need | Coverage |
|---|---|---|---|
$1.0M | 33% | $3.0M | 3.0x |
$1.0M | 25% | $4.0M | 4.0x |
$1.0M | 20% | $5.0M | 5.0x |
$1.0M | 50% | $2.0M | 2.0x |
Illustrative arithmetic: required coverage = 1 / win rate, applied to a $1M target.
Look at the spread. A firm targeting the same $1M needs anywhere from $2M to $5M in pipeline depending on nothing but its win rate. If you used a flat 3x, the 20%-win-rate firm would walk into the quarter $2M short and not find out until it was too late to fix.
Getting your win rate honest
The formula is only as good as the win rate you feed it, and this is exactly where most teams quietly fool themselves. The win rate that matters is your close rate on qualified opportunities over the last four quarters, not your best quarter, not a hopeful estimate, and not a number that includes deals that were never real.
Win rate also moves with who you sell to, falling as deal size rises: smaller deals close at a far higher rate than enterprise deals above $100K, which close in the mid-teens. Bigger deals, lower hit rate, more coverage required. If you sell across segments you cannot use one blended win rate; you need one per segment, or your coverage target will be wrong for all of them. The table below pairs the benchmark win rate for each segment with the coverage it actually demands, calculated straight from the formula:
Table 02 · Win rate and required coverage, by segment
Segment | Typical win rate | Required coverage |
|---|---|---|
SMB | 28-35% | 3-3.5x |
Mid-market | 20-28% | 3.5-5x |
Enterprise (>$100K ACV) | 12-18% | 5.5-8x |
Win rates from survey data drawn from HubSpot's 1,000+ rep survey (all-in B2B average 21%); coverage is 1 / win rate applied to each band.
The pattern is the point: the bigger the deal, the lower the win rate, so the more pipeline you need behind it. An enterprise team winning 15% needs nearly seven dollars of pipeline for every dollar of target, while an SMB team winning a third needs barely three. Run a flat 3x across both and the SMB team hoards pipeline it does not need while the enterprise team quietly walks into a miss, the identical dashboard number hiding opposite problems.
Where the deals actually leak: the funnel before the win
Your win rate is the last conversion in a longer chain, and the discipline that keeps coverage honest starts with knowing what counts at each earlier stage. Three terms matter:
MQL (marketing qualified lead). Someone who has shown buying intent and looks able to afford you. Marketing flags it. An MQL is interest, not an opportunity.
SQL (sales qualified lead). An MQL a salesperson has vetted and judged a genuine fit, usually with a meeting booked. This is where real pipeline begins.
Customer. An SQL that became an opportunity and closed. This is the only conversion your revenue actually feels.
Each handoff loses volume, and the drop-offs are larger than most founders assume. The cross-industry averages: lead to MQL around 31%, MQL to SQL near 13%, SQL to opportunity 30 to 55%, and opportunity to close 15 to 40% for software. The MQL-to-SQL step is the single biggest leak in most B2B funnels, which is why coverage must be counted from the SQL stage on, never from raw leads.
Coverage's sister metric: velocity
Having enough pipeline is only half the question. The other half is how fast that pipeline turns into cash, which is what sales velocity measures, and the two share most of their inputs, so they are best read together. Velocity multiplies your number of opportunities by average deal size and win rate, then divides by how long a deal takes to close: (opportunities × deal size × win rate) / sales cycle length. The result is revenue per day, the true speed of your pipeline.
Win rate and opportunity count sit in both formulas, so fixing your win rate improves coverage and velocity at once. The difference is what each protects you from: weak coverage means you miss because you never had enough, slow velocity means you miss because the deals arrive too late to count this period. Velocity deserves its own full treatment, and it will get one. For now the point is that coverage and velocity are two readings of the same engine: enough, and fast enough.
How coverage becomes theater
Even with the right target, coverage lies easily. There are three classic ways founders inflate the number until it stops meaning anything:
Counting leads as pipeline. Folding raw leads or MQLs into pipeline value can double your apparent coverage overnight while changing nothing real.
Counting deals that cannot close in the period. A deal that will land next quarter does not cover this quarter's quota. Coverage must be in-period or it is fiction.
Using a win rate ten points too high. The most common and most damaging. A flattering win rate shrinks your required coverage on paper, so you under-build pipeline and feel safe doing it.
Any one of these turns coverage from a forecast into a comfort blanket. A pipeline full of unqualified deals does not make the quarter safer; it only changes when you learn the truth.
Coverage without qualification does not protect you from a miss. It just delays the moment you find out by a quarter.
Building a coverage number you can trust
A coverage figure is only useful if the three inputs underneath it are real: qualified pipeline, an honest in-period view, and a measured win rate by segment. Get those true and coverage becomes the most valuable number on your weekly call, the one that tells you the quarter's outcome while you can still change it. Here is the order to build it:
Define qualified : Agree what makes an opportunity real, and count nothing else as pipeline. This alone fixes most inflated coverage.
Measure win rate by segment over the last four quarters : One blended number is not enough if you sell to more than one kind of buyer.
Set the target as 1 / win rate, per segment : Stop using 3x unless your win rate happens to be 33%.
Review weekly, in-period : Coverage is a leading indicator only if you look at it early enough to act.
The firms that do this stop being surprised by their own quarters. Not because they generate more pipeline, but because they finally know how much they need and whether they have it, early enough to do something about a shortfall rather than explain it after the fact. That is the entire point of the metric, and it is invisible to anyone still anchored on a rule from thirty years ago.
Worked examples: two firms, same target, opposite reality
Take two companies that both need $1M in new revenue this quarter and both proudly run "3x coverage," meaning $3M in open pipeline. On the dashboard they look identical. The math says otherwise.
Example 01 · The SMB firm that is over-covered
Acme Tools sells $8K deals to small businesses and closes 33% of qualified opportunities. Required coverage = 1 / 0.33 = 3x. They hold $3M against a $1M target, so they are exactly covered. In fact, with a high win rate they could safely run closer to $2.5M and redeploy the rest of the team's effort. Their 3x is fine, even slightly generous.
Example 02 · The enterprise firm walking into a miss
Beacon Systems sells $150K deals to enterprises and closes 15%. Required coverage = 1 / 0.15 = 6.7x. To land $1M they need roughly $6.7M in qualified pipeline. They are holding $3M. That is not 3x coverage, it is a $3.7M shortfall hiding behind a number that looks healthy. They will hit about $450K of their $1M target, and they will not know until the quarter is nearly closed.
Same target, same headline coverage, opposite outcomes, driven by nothing but win rate. Beacon does not have a pipeline-generation problem; it has a measurement problem, and the measurement was wrong before the quarter even started.
Frequently asked questions
1. Why does a CRM showing 4x coverage still miss the number?
Almost always one of three things: the pipeline is padded with leads or MQLs that were never real opportunities, it includes deals that cannot close this period, or the win rate you are dividing by is higher than what you actually close. Strip the pipeline down to qualified, in-period deals and recompute your win rate from the last four quarters of closed-won versus closed-lost. The honest number is usually lower than the dashboard.
2. Do "no decision" deals count as losses in the win rate?
For coverage purposes, yes. Track two numbers: a competitive win rate (won versus lost) and a pipeline win rate (won versus every outcome including no-decision). Coverage math should use the pipeline win rate, because a deal that dies in indecision consumed pipeline just like a deal you lost to a competitor. Using the flattering competitive figure is one of the most common ways teams under-build.
3. What coverage works without a reliable win rate yet?
If you genuinely have no history, start at 4x to 5x rather than 3x, since the current B2B average sits near 20% and starting conservative is cheaper than missing. But treat it as temporary. The moment you have one or two quarters of qualified closed-won and closed-lost data, switch to 1 divided by your real win rate, by segment. A borrowed multiple is a placeholder, not an answer.
4. Does pipeline coverage replace a sales forecast?
No, they answer different questions. Coverage is a capacity check at the start of the period: is there mathematically enough qualified pipeline to make the number possible. A forecast is a judgment call deal by deal about what will actually close. Coverage tells you whether the quarter is winnable; the forecast tells you what you currently expect to win. Healthy teams run both.
5. How is coverage different from sales velocity?
Coverage asks whether you have enough pipeline; velocity asks how fast that pipeline becomes revenue, measured in dollars per day. They share two inputs, win rate and opportunity count, so improving qualification helps both. You can pass the coverage test and still miss if velocity is too slow and deals land after the period closes, which is why mature teams watch them side by side.