Revenue Velocity

Revenue velocity is the speed at which a sales organization turns pipeline into booked revenue, expressed as a dollar amount per unit of time. It is the metric that tells you whether your sales machine is a sports car or a tractor — both move, but one covers ground faster. Revenue velocity is distinct from sales-velocity in that it is a pure output measure, not a diagnostic. Sales velocity is the formula; revenue velocity is the result that formula produces when you plug in real numbers. The metric matters because it is the single best leading indicator of whether the org can hit its bookings number with the pipeline it has, before the quarter ends.

The calculation is deterministic: Revenue Velocity = (Number of Opportunities × Average Deal Size × Win Rate) ÷ Sales Cycle Length. The unit of time is typically a month or a quarter. The number of opportunities is the count of qualified deals in the pipeline, not raw leads — sales-qualified-opportunities only. Average deal size is the mean average-deal-size of closed-won deals, not the average of everything in the pipeline. Win rate is the win-rate on qualified opportunities, not on all leads. Sales cycle length is the average number of days from opportunity creation to closed-won, measured in the same time unit as the other inputs.

A worked example: A B2B company has 80 qualified opportunities in the pipeline. The average deal size is $25,000. The win rate on qualified opportunities is 25%. The average sales cycle is 60 days. Revenue velocity = (80 × $25,000 × 0.25) ÷ 60 = $500,000 ÷ 60 = $8,333 per day. Over a 90-day quarter, that velocity implies $750,000 in bookings. If the quarter's quota is $1M, the org is short by $250K — and the VP of Sales knows immediately that the pipeline-coverage-ratio of 3.0 is not enough, because the velocity is too slow. The fix is not more pipeline; the fix is faster deal-velocity or a higher win rate.

Sales orgs use revenue velocity in three critical moments. At the start of the quarter, it sets the pace — if velocity is $8,333 per day and the quota is $1M, the team needs 120 days of selling in a 90-day quarter, which means they started behind. Mid-quarter, it is the early-warning system for forecast-accuracy: if actual bookings are tracking below the velocity line, the forecast is wrong. At the end of the quarter, it explains the gap between bookings and quota — the org either had too few deals, too-small deals, too-low a win rate, or too-long a cycle. The CFO uses it to model rule-of-40 performance, because velocity is the growth engine that funds the burn.

The limitations of revenue velocity are real and structural. The formula assumes linearity — that deals close at a constant rate across the quarter — when in reality bookings-linearity is almost always back-loaded, with 60% of deals closing in the final month. The metric also treats all pipeline as equal, which invites pipeline-padding: reps inflate the opportunity count with zombie-deals that have no budget or timeline, which artificially raises velocity without raising actual bookings. The gaming pattern is the phantom-pipeline — deals that are real enough to count in the numerator but have zero probability of closing, dragging the win rate down while the velocity number looks healthy. Revenue velocity is only as honest as the pipeline hygiene underneath it, and pipeline hygiene is where the system fails.