Pipeline Coverage vs Pipeline Velocity

What is the difference between pipeline coverage and pipeline velocity?

Coverage is a snapshot ratio of open pipeline to the goal. Velocity is a rate that estimates how much revenue that pipeline generates per day. One has no time dimension. The other is built entirely around time.

Coverage answers a sufficiency question. Do we hold enough open opportunity to hit the number if the funnel behaves normally? Velocity answers a throughput question. Given how fast deals actually move and how often they convert, how much revenue can this funnel produce before the period closes?

The gap between those two questions is where most missed quarters live. A pipeline can be large and slow. The ratio looks fine on day one and the calendar runs out anyway.

How do you calculate each one?

Coverage divides open pipeline by the goal. Velocity divides expected revenue by cycle length. For coverage, scope open pipeline to deals with close dates inside the period. Counting next year's opportunity against this quarter's goal produces a ratio that means nothing. The standard target is 3x to 5x. Across ORM's customer base the real figures run from 1.4x to 5x, with most sitting near 3.5x.

For velocity, the cycle length input does the heavy lifting. Use the average days from qualified stage to closed won, measured on deals that actually closed, and segment it. A blended cycle length across SMB and enterprise produces a velocity number that describes no real deal.

Why does high coverage fail to predict the quarter?

Coverage counts dollars without asking where they sit or how long they have been sitting. Composition is invisible to a ratio.

Four pipelines can all show 4x coverage and behave completely differently. One is concentrated in two large deals. One sits in the earliest stage. One is owned by reps still ramping. One is padded with opportunities nobody has touched in a year. The ratio treats them as identical.

Aging is the most reliable way coverage lies. Across ORM customers, more than 10 percent of open pipeline has typically gone untouched for twelve months. That dollar value inflates the coverage ratio while contributing nothing to the period. There is a harder number behind it too. Of the pipeline carrying in-quarter close dates on the first day of a quarter, roughly 20 percent closes in that quarter. The other 80 percent of the visible value does not land.

Velocity catches part of what coverage misses because a pipeline full of slow deals produces a low revenue-per-day figure regardless of how large it is.

What does velocity miss on its own?

Velocity assumes today's inputs hold for the whole period, and it says nothing about pipeline you have not created yet. It is a projection of the current funnel at the current conversion rate.

Three of the four inputs move constantly. Average deal size drops under competitive pricing pressure. Win rates fall when buyers get cautious. Cycle length extends when a buying committee adds a step. A velocity figure calculated in week one describes a funnel that no longer exists by week six.

Velocity also anchors entirely on visible pipeline. It cannot tell you about deals that will be created, qualified, and closed inside the same period, which in most SaaS businesses is a meaningful share of the number. That invisible motion is a forecasting problem rather than a metric problem, and it is covered in more depth in our breakdown of sales velocity.

When should you use each metric?

Use coverage during planning and use velocity during execution.

Coverage belongs in capacity and demand-generation planning. If you need four million in bookings and history says you convert at 3.5x, you need fourteen million in qualified pipeline built ahead of the period. That math sets marketing targets and SDR quotas months in advance.

Velocity belongs in the weekly operating rhythm. Track it against the days remaining. If velocity multiplied by remaining days falls short of the gap to target, the shortfall is arithmetic rather than opinion, and it shows up early enough to act. Pulling forward, discounting, or accelerating a stalled deal all have costs, and those costs are lower in week three than in week eleven.

The rule of thumb both metrics share: a number that arrives in the last week of the quarter is a report, not a forecast. By then the quarter has already happened.

How do you read them together?

Cross the two and you get four distinct diagnoses.

High coverage with high velocity is a healthy funnel, and the job is protecting it. Low coverage with high velocity means the machine works and the top of the funnel is starving, so the fix is demand generation. High coverage with low velocity is the dangerous quadrant, because the dashboard looks green while the pipeline is aged, oversized, or stuck. Low coverage with low velocity is a structural problem that no in-quarter play solves.

Most teams that miss a quarter with a full pipeline were in the third quadrant and only tracking the first metric. The 3x to 5x rule of thumb is a large part of why, and we have written about the limits of that rule in the 3x pipeline coverage rule is wrong.

Does either metric replace a forecast?

No. Both are inputs. Pipeline coverage tells you the raw material exists. Velocity tells you the conversion engine's current speed. A real forecast has to explain three sources of revenue: what closes from pipeline that already exists, what gets created and closed inside the period, and what gets pulled forward from later periods at a cost to future quarters.

Coverage speaks to the first source. Velocity speaks to the first source with a clock attached. Neither models the second or third, which is why teams that treat coverage as the answer keep getting surprised by quarters that were decided before they started.