Pipeline Velocity Formula: Quick Answer
Pipeline Velocity = (Qualified Opportunities x Win Rate x ACV) / Sales Cycle Days. The result is the amount of revenue your qualified pipeline is expected to generate per day. It is useful because it combines four operating variables into one diagnostic: how many qualified deals you have, how often they close, how much they are worth, and how long they take to close.
This is the formula-first version of the topic. For benchmark bands, lever interactions, and how the metric behaves by company stage, use the broader pipeline velocity guide.
The Four Inputs
- Qualified Opportunities: active pipeline that has cleared your qualification criteria. Do not include raw leads, MQLs, SQLs, or nurture prospects.
- Win Rate: the percentage of qualified opportunities that close as won deals. Use a decimal in the formula, so 24% becomes 0.24.
- ACV: average contract value, usually first-year new ARR for B2B SaaS. Do not mix ACV with TCV unless your reporting policy explicitly uses TCV.
- Sales Cycle Days: the average number of days from opportunity creation to contract signature for the same qualified opportunity population.
The definition discipline matters more than the arithmetic. If opportunity count includes weak deals, win rate is measured against a different denominator, or ACV flips between ARR and TCV, the formula will produce a clean-looking number that does not describe the business.
Worked Example
Illustrative example: a Series A B2B SaaS company has 18 qualified opportunities, a 24% win rate, $18,000 ACV, and a 75-day average sales cycle.
(18 x 0.24 x 18,000) / 75 = $1,037 per day
That means the current qualified pipeline is producing roughly $1,037 of expected revenue per day, or about $93,000 over a 90-day quarter if the same inputs hold. That is not a guarantee. It is a diagnostic view of current pipeline conversion mechanics.
Free Tool
Calculate your pipeline velocity
Enter your four inputs and compare the result against stage-specific benchmark bands for Series A, B, and C.
Open the Velocity Calculator →Common Calculation Mistakes
Counting every pipeline record as qualified
If reps can create opportunities before buyer fit, budget, and decision path are verified, the opportunity count is inflated. That makes velocity look better through volume while win rate and cycle length deteriorate underneath it. Stage-exit controls are the operating fix for this problem.
Changing the win rate denominator
Win rate against all leads is not the same as win rate against qualified opportunities. Pick one denominator and keep it stable. For pipeline velocity, the denominator should match the same population used in qualified opportunity count.
Mixing ACV, ARR, and TCV
For SaaS revenue diagnostics, ACV is usually the cleanest input because it reflects first-year contract value. TCV can overstate velocity for multi-year contracts if the business is trying to understand annualized revenue generation.
Using the wrong sales cycle window
Sales cycle should be measured from opportunity creation to contract signature for the same population used in the numerator. Measuring from first touch, demo date, proposal date, or closed-won date will produce a different number.
What to Do With the Result
A single velocity number is a starting point. Compare the result against your prior quarter and against your stage-specific band in the pipeline velocity benchmarks page. Then run a lever sensitivity check: model what happens if opportunities, win rate, ACV, or cycle length improves by 10% independently.
That sensitivity view tells you which lever is worth fixing first. The implementation sequence is covered in the pipeline velocity improvement playbook, including how to avoid raising one input while damaging another.
