Pipeline Coverage

The question a sales team hears most often at the start of a quarter is whether the quarter is going to land. The answer used to come from memory — someone would run through the open deals, count the ones that felt likely, and give a number that moved depending on who was asking and how the week had gone. Looking at the same pipeline, a rep would say it was plenty and the CEO would say it looked thin, and there was no way to settle which of them was right.

The cost showed up in the last week of the quarter. Against a $150,000 target, $190,000 in open deals looked comfortable. Then three or four of those deals actually closed and the quarter came in at $60,000. Only afterward did anyone say there had been deals and none of them landed. Having money sitting in the pipeline and having enough money in the pipeline were two different claims, and the team had been treating them as one.

Pipeline coverage puts a ratio between those two claims. Divide what's in the pipeline by the target, then ask whether that multiple is large enough to survive the team's win rate — the share of worked deals that end up closing. A team that closes six deals out of twenty needs more than three times its target sitting in front of it for the arithmetic to work. One division replaced a gut call, and after that the shortfall became visible before the quarter ended rather than after.

Add up the value of the open deals and divide by the target for the period. A $150,000 quarterly target against $450,000 in open deals gives coverage of 3x.

The calculation has three steps.

1. Pick which deals count. Only a deal that is still open goes in. Anything already won drops out, anything marked closed lost drops out, and so does anything that has not been promoted to an opportunity because the budget and the decision date are still unconfirmed.
2. Line up the dates. Count only deals with a close date inside this quarter. Put a $230,000 deal that decides next quarter into this quarter's coverage and the multiple grows while its relationship to this quarter's result disappears.
3. Divide by the target. That target can be the whole team's number or one rep's quota; either way, the numerator and the denominator have to cover the same scope.

Two different calculations travel under the same name. One adds the deal values as they stand. The other weights each deal by the historical close rate of the stage it sits in — a $15,000 deal at the proposal stage counts as $15,000 in the first version and as $6,000 in the second, if that stage historically closes 40 percent of the time. The unweighted version is the standard form. The weighted number already has probability baked into it, so the benchmark multiple has to come down alongside it. Without agreeing on which one the team uses, the same pipeline gets reported as 3x and as 1.2x in the same week.

3x is the number people quote, but it isn't a constant handed down from anywhere — it's the inverse of the win rate. A team closing 30 percent of its deals needs $450,000 to land $150,000, which puts its benchmark at about 3.3x. A team closing 50 percent is fine at 2x. A team closing 15 percent needs 6x. Work out your own win rate over the last four quarters and divide one by it; that's the benchmark.

Timing matters as much as the ratio. 3x in the first week of a quarter is healthy; 3x halfway through is late. Once the time remaining is shorter than the sales cycle, a large share of what's in the pipeline cannot close inside the period at all. Pagedeck's team-level deals take 34 days on average, so a deal that arrives with a month left in the quarter is realistically next quarter's revenue.

A large multiple isn't automatically reassuring either. If $450,000 is in the pipeline but $370,000 of it sits at the discovery stage and only $80,000 has reached proposal or later, this quarter's result comes out of that $80,000. Coverage read stage by stage is more useful than one blended figure. Concentration causes the same trouble: a team whose average deal size is $7,500 can watch its multiple jump the moment a $230,000 deal appears, and watch the quarter collapse the moment that one deal slips a month.

"Coverage is 1.8x and our win rate is 30 percent. That puts us at half the target."

The multiple is below the benchmark, so the quarter is already in trouble.

"Coverage is 4x but half of it is still in discovery. We can't count that for this quarter."

The total is fine; the stage distribution means it won't close in time.

"Don't leave dead deals open just to prop up coverage."

Pushing back on inflating the ratio by refusing to close out deals that are gone.

At Pagedeck the first meeting of the quarter opens with this number. Sofia reads out the total on her deals and Grace divides it by the target. When the multiple falls short, two things get decided in the room: how much new pipeline has to be created, and how much of that could realistically close inside the quarter. With little time left, new deals can't fill the gap, so the conversation shifts to which existing deals could have their decision pulled forward.

The most common mistake is believing that raising coverage raises results. The two do move together often enough to make the assumption feel safe. But the ratio only signals whether the pipeline is thin, and some of the fastest ways to raise it have nothing to do with revenue. Leaving hopeless deals open is one; writing optimistic deal values is another. A 6x built that way gets cleaned up as a batch of losses in the final week, and from the next quarter on nobody uses the number to decide anything.

Reading anything above 3x as a guarantee is the other one. Clearing a benchmark feels like safety. But that benchmark rests on the assumption that the past win rate holds. In a quarter where a competitor cuts prices or customers freeze budgets, a 30 percent win rate can fall to 18 percent, and the same 3x becomes insufficient. A team that sets its benchmark once and reuses it for years finds out about a declining win rate a full quarter late.