Pipeline Velocity Metrics
One number that captures how fast revenue moves
Deal count, average deal size, win rate, and sales cycle length are each useful on their own, but none of them individually answers the question a revenue leader actually cares about: how much revenue is this pipeline going to generate per unit of time. Pipeline velocity combines all four into a single number, specifically so that an improvement in any one lever (more opportunities, bigger deals, a better win rate, or a shorter cycle) is visible as a velocity gain, and a decline in any one is visible as a velocity loss — even when the other three stay flat.
The formula
Pipeline velocity is calculated as:
Velocity = (Number of Qualified Opportunities × Average Deal Size × Win Rate) ÷ Average Sales Cycle Length
The result is typically expressed as a revenue-per-day (or per-month) figure — how much revenue the pipeline is generating, on average, for every day a deal is in the sales process. Each of the four inputs needs a consistent, agreed definition before the formula means anything: 'qualified opportunities' should mean the same pipeline stage every time it's measured, win rate should be calculated over the same trailing period as the other inputs, and cycle length should be measured consistently (first-touch-to-close, or opportunity-created-to-close — pick one and keep it).
INPUTS (trailing quarter)
Qualified opportunities: 120
Average deal size: $18,000
Win rate: 22% (0.22)
Average sales cycle: 45 days
CALCULATION
Velocity = (120 x $18,000 x 0.22) / 45
= $475,200 / 45
= $10,560 / day
INTERPRETATION
The current pipeline is generating roughly $10,560 of revenue
per day of sales-cycle time. Compare this number quarter over
quarter to see whether velocity is actually improving — and
which of the four inputs is driving the change.Diagnosing a velocity change by isolating the lever
Because velocity is a product of four inputs, a change in the total number alone doesn't say what to fix — you have to look at which input moved. A velocity increase driven by a rising average deal size (bigger deals, same win rate and cycle length) implies a different action (keep pursuing larger accounts) than a velocity increase driven by a shorter sales cycle (process improvement worked — look at what changed and replicate it). Tracking the four components alongside the composite number, every period, is what makes velocity actionable instead of just a vanity number.
What moved, and what it implies
| Lever that changed | Likely cause | Action implied |
|---|---|---|
| More qualified opportunities | Marketing/SDR volume increase, or routing improvement | Check if quality held — did win rate drop? |
| Larger average deal size | Upmarket shift, upsell motion, pricing change | Validate this is sustainable, not one large outlier deal |
| Higher win rate | Better qualification, stronger competitive positioning | Identify what specifically improved and reinforce it |
| Shorter sales cycle | Process change, faster approvals, better enablement | Isolate the specific change and roll it out team-wide |
A single large outlier deal can distort every input at once
Velocity is a trailing indicator, not a predictor by itself
What's next
Velocity measures how the pipeline has behaved — forecasting takes the current open pipeline and asks whether there's enough of it, and how confidently it will convert, to hit next quarter's number.
Next: Forecasting & Pipeline Coverage →
I build these systems professionally.
Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.