Pipeline coverage: why small pipelines fail quietly
I’ve written about small data pipelines that fail quietly: a nightly job stops running and the dashboard keeps showing yesterday’s numbers. This is about the other kind of pipeline, the one in the CRM, and it fails the same way.
A thin sales pipeline doesn’t throw an error. The forecast looks fine, the team is busy, and the quarter ends short. Coverage is the metric meant to catch that early. Usually it doesn’t, and the reason is how it gets reported.
What coverage means, and why one number isn’t enough
Pipeline coverage is open pipeline divided by the target you still have to hit. If the remaining number is one unit and you have three units of open opportunities, coverage is three times. The familiar rule of thumb, three to four times, is just an inverted win rate: it assumes you close somewhere between a quarter and a third of what you work.
That makes the ratio exactly as good as the win rate behind it, and win rates differ by segment, by deal size, and by stage. A single coverage figure averages all of that away. It says the pipeline is big enough. It doesn’t say big enough of what, or by when.
Coverage by stage and by close month
Split it two ways. By stage, because an opportunity in first discovery and one in contract review are not the same inventory. Weight each stage by its measured conversion to close, not by the probability field someone typed in, and the result is a coverage figure that reflects what the pipeline is likely to produce rather than what it adds up to.
By close month, because a pipeline can be three times the quarterly target while nearly all of it sits in the final month. That is the shape that fails. Only deals due this month can rescue this month. If there aren’t enough of them, later-dated pipeline is no help, however large it is.
Why thin pipelines show no warning until late
At the start of a quarter everything is open and nothing has been lost, so coverage looks healthy by construction. Then the slow leak begins. Early-stage deals rarely get marked lost. They get pushed. A pushed deal keeps its full value in the pipeline and moves its close date out, so the total stays flat while this quarter’s pipeline quietly drains into the next one.
The first hard signal is usually a wave of close dates slipping in the last few weeks. By then the shortfall has been there for two months and has merely become visible. The pipeline didn’t shrink late. It was never real for this quarter, and nothing on the page said so.
Aging and stalled deals
The other way a pipeline flatters you is age. An opportunity that has sat in one stage for twice the typical time for that stage isn’t pipeline. It is a record nobody has closed out. Track days in current stage against the median for that stage, and track how many times the close date has moved.
Deals that trip both tests are stalled and should come out of the coverage ratio, even if they stay in the CRM. Reps resist this, reasonably, because the deal might still happen. Fine. Count it on a separate line. Coverage should describe what is moving.
A weekly coverage view
Here is what I’d put on one page every week. The remaining target for the quarter, by month. Open pipeline due in each of those months, by stage, with stage-weighted value next to raw value. Stalled pipeline as its own line, excluded from the ratio. Then two numbers about direction: pipeline created this week, and pipeline pushed or lost this week.
Coverage is a level. Those last two are the flow that changes the level, and the flow is the earlier warning. Keep the layout identical from week to week so people learn to read it. The goal isn’t precision. It is that a shortfall which would otherwise surface in the last weeks of the quarter surfaces in the first few instead.
Short coverage is a sourcing problem first
When coverage is short, the instinct is to push harder on what is already open: more follow-ups, deeper discounts, an executive on the call. That helps at the margin. But a thin pipeline is the symptom of too few conversations started weeks or months ago, and the fix lives in the same place.
Work backwards from the gap. With a known win rate and cycle time, the number of first meetings needed is arithmetic, and so is the date by which they had to happen. If that date has already passed for this quarter, say so, protect the next one, and stop spending the whole team’s attention on deals that were never going to close in time.
Small pipelines fail quietly because the people watching them are looking at a total. Look at the shape, the age, and the flow, and they start failing loudly, early enough to matter.