Pipeline Velocity

Pipeline velocity is the dollar amount of revenue your sales team generates per day, calculated from four inputs: the number of qualified opportunities, the average win rate, the average deal size, and the average sales cycle length. It tells you how much money your pipeline is producing every 24 hours. A team running at $12,000/day in velocity will close $4.38M in a year if nothing changes. Every operator who has ever stared at a forecast eventually arrives at this formula, because it's the only one that exposes which lever — volume, conversion, ACV, or speed — is actually moving the number.

How Pipeline Velocity Is Calculated

The formula:

Pipeline Velocity = (Number of Qualified Opportunities × Win Rate × Average Deal Size) ÷ Average Sales Cycle Length in days

Each input pulls from a different system. Opportunity count comes from CRM stage data — usually anything past discovery. Win rate comes from closed-won divided by closed-total over a trailing window, typically 90 or 180 days. Average deal size is closed-won ACV over the same window. Cycle length is the median days from opportunity creation to closed-won. Use medians, not means. One whale deal that took 380 days will distort the mean by a quarter.

Worked Pipeline Velocity Example

A mid-market SaaS team has 240 qualified opportunities in pipeline, a 22% win rate, a $48,000 average deal size, and a 95-day average sales cycle.

Math: (240 × 0.22 × $48,000) ÷ 95 = $26,678 per day, or roughly $9.7M annualized. Now change one variable. Drop the cycle from 95 to 76 days — a 20% compression — and velocity jumps to $33,347/day, an extra $2.4M annualized. The same lift comes from raising win rate from 22% to 27.5%. The formula tells you which lever is cheaper to pull this quarter.

When Sales Orgs Use Pipeline Velocity

VPs of Sales use it to diagnose stalled quarters before the forecast call. RevOps teams use it to A/B test process changes — a new qualification framework, a tightened ICP, a shorter procurement template — by comparing velocity before and after. CFOs use it to sanity-check the ARR plan against actual pipeline math. Recruiters use it to interrogate AE candidates: a rep who claims $4M attainment but can't describe their average cycle length or win rate is selling a story, not a track record. PE-backed CROs run it monthly because it's the cleanest single number for board updates that hides nothing.

Pipeline Velocity Limitations and Gaming Patterns

The formula assumes the four inputs are accurate, which in most CRMs they are not. The gaming patterns are well-documented. Reps inflate opportunity count by leaving dead deals in stage 2 — pipeline padding — which raises the numerator without producing revenue. Cycle length gets manipulated by recreating opportunities under new IDs when deals slip past forecast, resetting the clock. Win rate gets juked by closing-lost the worst opportunities early in the quarter so the denominator shrinks. Average deal size is the easiest to distort: exclude the SMB segment, include only enterprise, and your "velocity" looks twice what it is.

Velocity also tells you nothing about why a number is what it is. A team with high velocity and a 6% gross margin is burning cash to chase the metric. A team with low velocity but 95% net revenue retention is fine. Treat it as one input on the dashboard, not the dashboard itself.