Pipeline velocity is a single number showing how much revenue your pipeline produces per day, calculated as: (number of opportunities multiplied by average deal value multiplied by win rate) divided by average sales cycle length in days.
At a glance
- Used by revenue and RevOps teams to track how efficiently deals convert to dollars over time.
- Four inputs drive the metric: opportunity count, average deal value, win rate, and sales cycle length.
- Measured in revenue per day, making it easy to project quarterly shortfalls before they happen.
- Should be segmented by deal size or customer type, not averaged across the whole funnel.
- Common pitfall: padding the pipeline with weak deals inflates the count but collapses the win rate.
How does the pipeline velocity formula actually work?
With 40 open opportunities, an average deal value of $25,000, a 30% win rate, and a 60-day sales cycle, the calculation is (40 x $25,000 x 0.30) / 60, which equals $5,000 per day. Run the same calculation next quarter and you have a concrete comparison instead of gut feel.
Pipeline velocity exposes which variable is dragging the number down. Two teams can have identical velocity scores with completely different problems: one closes fast but wins too few deals, the other wins often but deals sit idle for 90 days. The fix differs in each case.
Why does pipeline velocity matter for revenue teams?
Most pipeline reviews focus on total pipeline value, a lagging number that is often inflated. Velocity forces attention onto four inputs at once, so when any one shifts, the downstream impact on revenue per day is visible immediately.
For a head of revenue building a quarterly forecast, velocity provides a rate rather than a snapshot. If current velocity is $4,200 per day and the target is $1.2M over roughly 90 days, the gap is visible before the quarter starts, leaving time to shorten cycle times, improve win rate, or remove stalled deals instead of carrying false pipeline. It also gives marketing and sales a shared unit of measure tied directly to revenue output.
When does pipeline velocity break down?
Mixing segments
Enterprise and SMB deals should not share one velocity metric. A 120-day cycle on a $200,000 deal is not slow. That same cycle on a $12,000 deal is a real problem, and blending the two hides it.
Treating it as a lagging report
The point of tracking velocity is to catch deterioration early, not to explain a missed quarter after the fact. Teams that only review it at quarter-end lose the lead time that makes the metric useful.
What are the most common mistakes teams make?
- Padding opportunity count with poorly qualified deals. More opps look good on paper, but a win rate that drops from 30% to 15% more than offsets any volume gain.
- Chasing volume over deal quality. Adding more deals that close slower and win less often moves velocity down, not up.
- Ignoring the sales cycle denominator. Small improvements in average cycle length compound quickly across a large pipeline.
- Skipping segment-level tracking. A single blended number masks which part of the business is healthy and which is not.
How does pipeline velocity connect to adjacent concepts?
Velocity and Annual Contract Value (ACV) are tightly linked. Raising ACV without a corresponding drop in win rate or spike in cycle length is the cleanest way to improve the metric. Teams that run an account-based motion targeting high-fit accounts should expect higher win rates and higher ACV to appear in the velocity number within two to three quarters; if they do not, the targeting or the execution has a gap.
From a RevOps standpoint, velocity sits downstream of almost every process decision: how reps qualify, how discovery is run, how proposals get approved. Win rate, sales cycle length, and deal value are all outputs of those upstream choices, which means velocity serves as a summary score for GTM process health overall.