How to Calculate Pipeline Coverage by Stage

What is pipeline coverage by stage?

Stage-level pipeline coverage divides the open pipeline sitting in one stage by the revenue that stage is expected to produce, rather than dividing all open pipeline by the full quota. The total coverage ratio treats a discovery-stage opportunity created yesterday and a contract-out deal in legal as the same dollar. They are not the same dollar. One converts at a rate you can bank on and the other converts at a rate that requires four or five times the volume to produce the same revenue.

Splitting coverage by stage answers a sharper question. Instead of asking whether there is enough pipeline in total, you learn which part of the funnel is short and how much time remains to fix it. That distinction is what makes the metric operational. See the pipeline coverage definition for the base formula this builds on.

How do you calculate coverage for a single stage?

Divide the open pipeline value in the stage by the revenue that stage is expected to deliver for the period.

``` Stage coverage = Open pipeline in stage / Expected revenue from stage Expected revenue from stage = Period quota x Share of quota assigned to that stage ```

Start by filtering to opportunities with close dates inside the period. Group them by current stage. Then assign each stage a share of the number based on where revenue has historically come from. If your quota is $5,000,000 and proposal-stage deals have historically produced 30% of closed revenue, that stage carries $1,500,000. Holding $4,000,000 of open proposal pipeline gives you 2.7x coverage on that stage.

Run the same calculation for every stage. The output is a row per stage rather than a single headline number, and the row that is short tells you what to work on.

What coverage ratio should each stage carry?

Back the target out of the historical close rate for that stage, because required coverage is the inverse of conversion. A stage where deals close 25% of the time needs about 4x. A stage where deals close 60% of the time needs about 1.7x. The example above holds $15,700,000 against a $5,000,000 quota, which reads as 3.1x in total and looks reasonable. Across ORM customer data, 3x to 5x is the standard range and most companies sit around 3.5x. The stage view tells a different story. Discovery and negotiation are covered. Solution fit and proposal are both under the ratio their own conversion history requires, and those are the stages that have to produce revenue inside this period.

Why does total coverage hide stage risk?

Because a single ratio averages away composition, and composition is what determines whether the quarter lands. A company can carry 4x coverage and still miss badly if the pipeline is concentrated in the wrong stage, dependent on a few large deals, inflated by stale opportunities, or built on close dates that sellers keep pushing forward.

The trap is that the total number feels like an answer. Coverage is an input to the forecast, never the conclusion. Two teams reporting identical 3.5x ratios can have completely different quarters ahead of them, and only the stage decomposition separates them. This is the core problem with treating a fixed multiple as a health check, covered in why the 3x pipeline coverage rule is wrong.

How do you turn stage coverage into a revenue expectation?

Multiply each stage's open pipeline by that stage's historical close rate, then add the results. Using the table above, discovery contributes $720,000, solution fit contributes $924,000, proposal contributes $1,368,000, and negotiation contributes $1,235,000. Total expected revenue is $4,247,000 against a $5,000,000 quota, a gap of $753,000.

That gap is the number worth managing. It is specific, it points at the stages that produced it, and it converts into an action: create more solution-fit pipeline now, or accelerate proposal-stage deals that are already in flight. This weighting method and its limits are covered in more depth in the guide to weighted pipeline.

What breaks stage coverage math?

Three data problems distort the ratio faster than anything else: aged deals, inflated amounts, and moving close dates.

Aged pipeline is the most common. Across ORM customers, 10% or more of open pipeline has not been touched in 12 months. Those opportunities still sit in a stage and still count toward the coverage ratio, so they inflate every number they appear in. Filter them out before you calculate anything.

Inflated deal amounts do similar damage. Most deals close for less than the amount recorded against them. A pipeline carrying an average deal size of $80,000 against closed-won deals averaging $40,000 is the shape of the problem. Every stage ratio built on the first number is overstated by half. Compare the average value of open deals in each stage against the average value of what actually closed from that stage, and discount accordingly.

Close-date movement is the third. Deals that keep sliding forward pile up in a stage without ever converting, which makes coverage look stable while the underlying quarter deteriorates.

How often should you recalculate stage coverage?

Weekly during the quarter, and always on day one. Day one is when the number has the most value, because there is still time to create pipeline, shift capacity, or pull marketing spend toward the stage that is short. Getting the coverage read right in the last week of the quarter does not help anyone, since the quarter has already happened by then.

Track the stage rows over time rather than reading them once. A proposal stage that drifts from 3.0x to 2.2x over four weeks is telling you deals are exiting the stage as losses or pushes, and that signal shows up well before the forecast moves.