The math nobody does until it's too late

A sales team rolls into the quarter with a $200K target and $230K of open pipeline. It feels fine — there's more pipeline than target, after all. Then deals slip, a couple of "sure things" go dark, win rates do what win rates always do, and the quarter lands at $140K. Nobody was lying; the pipeline just never had enough in it to absorb the normal attrition of selling. The warning was visible in week one, in a single ratio nobody calculated.

Pipeline coverage ratio is that ratio: the total value of open pipeline divided by your target for the period. If you need $200K and you have $600K in open deals, your coverage is 3x. It answers the most basic forecasting question there is — do we have enough at-bats to hit the number? — and it answers it early enough to do something about a shortfall instead of explaining one after the fact.

Why you need more than 1x

The reason 1x coverage isn't enough is simple and unforgiving: you don't win every deal. If your historical win rate on qualified pipeline is 33%, then on average a dollar of pipeline becomes 33 cents of closed revenue. To close $200K at a 33% win rate, you need roughly $600K of pipeline — 3x coverage. The coverage ratio you need is essentially the inverse of your win rate, adjusted for the fact that not all of that pipeline will even reach a decision this period.

That's where the famous "3x rule" comes from. It's not magic — it's just what a one-in-three win rate implies. Which means 3x is only correct if your win rate is actually one in three. A team that wins half its qualified deals needs closer to 2x; a team winning one in five needs 5x or more. Quoting "3x" without knowing your own win rate is cargo-culting a number that may be wildly wrong for you.

Calculate the ratio that's true for your team

Don't borrow the rule of thumb — derive your own. Three honest inputs:

  1. Your real win rate on qualified pipeline — deals that reached a stage where they were genuinely in play, not every lead that ever entered. Pull this from history, ideally segmented, because win rates differ by source, segment, and deal size.
  2. Your target for the period.
  3. What counts as "pipeline." This is where teams fool themselves. Coverage built on a pipeline full of stale, mis-staged, never-going-to-close deals is a comforting fiction. The ratio is only as honest as the pipeline feeding it, which is why pipeline hygiene isn't a nice-to-have — it's a precondition for the number to mean anything.

Then: required coverage ≈ target ÷ (win rate × the fraction of pipeline that will resolve this period). A team with a 33% win rate needs about 3x; tighten or loosen from there based on your actual numbers. The point isn't the exact multiple — it's that you compute it from evidence instead of inheriting it.

Stage-weight it for a sharper read

Raw coverage treats a brand-new lead and a deal in final negotiation as equal dollars, which they obviously aren't. A more honest version weights each deal by its stage's historical conversion rate — the same logic behind forecasting you can actually defend. A $50K deal sitting in "qualified" at 20% historical conversion contributes $10K of weighted coverage; the same deal in "contract sent" at 80% contributes $40K.

Track both. Raw coverage tells you whether you have enough volume entering the funnel. Weighted coverage tells you whether the pipeline you have is mature enough to land this period. A team can have plenty of raw coverage and still miss because it's all early-stage — lots of at-bats, none of them in scoring position. Seeing both numbers is what separates "we have pipeline" from "we have committable pipeline."

What the ratio tells you to do

The number is only useful if it drives action, and a coverage gap drives two very different actions depending on when you spot it:

  • Early in the period: a coverage shortfall is a top-of-funnel problem. You don't have enough at-bats, so the fix is generation — more prospecting and outreach, reviving nurture-stage leads that are warming up. There's still time for new pipeline to mature.
  • Late in the period: new pipeline won't ripen in time, so the lever is conversion, not creation — focus reps on advancing and closing the late-stage deals already in play, and set honest expectations about the gap rather than pretending a miracle deal will appear.

Coverage that's too high is a signal too. Three or four times more pipeline than any reasonable win rate requires usually means the pipeline is inflated with deals that should have been disqualified — comforting on a dashboard, useless in the bank, and a sign your qualification bar is too low.

Make it a number you watch, not one you reconstruct

The teams that get value from coverage ratio don't compute it heroically at quarter-end in a spreadsheet — they watch it continuously, against a target they set deliberately. That requires a pipeline whose values and stages are trustworthy and a place to see total open value against target at a glance.

In Hitt CRM, pipeline value rolls up by stage and owner so coverage — raw and stage-weighted — is something you can read off a report any day of the quarter, not excavate at the end. Because the pipeline stages carry the conversion rates that feed the weighting, and because disciplined activity logging keeps deal stages honest, the coverage number reflects reality instead of wishful staging. That turns coverage from a postmortem statistic into an early-warning gauge you can actually steer by.

The takeaway

Pipeline coverage ratio is open pipeline divided by target, and you need more than 1x because you don't win every deal — your required multiple is roughly the inverse of your win rate, so derive it from your own numbers instead of reciting "3x." Weight it by stage for a sharper read, act on a gap differently depending on whether you spot it early (generate) or late (convert), and watch it continuously off an honest pipeline rather than reconstructing it at quarter-end. Done right, coverage is the gauge that tells you you're going to miss while there's still time to do something about it.