Operations
How to calculate business-to-business pipeline velocity without inflating stage counts
B2b pipeline velocity calculation: how to define the inputs, read the stage durations honestly and know when the number stops earning its keep in a quarterly review.
What to take away
- Pipeline velocity is revenue per day: qualified opportunities multiplied by average deal value and win rate, divided by median cycle length in days.
- Use the median cycle length from closed-won deals. A mean across open deals flatters the number.
- Act when weighted pipeline coverage falls below 3x the period target, or when one stage's median duration grows more than 20 percent quarter over quarter.
- Velocity is a ratio. It moves when any input moves, and it says nothing about whether a named deal will close.
Define the metric before you calculate it
Pipeline velocity is the rate at which qualified opportunities become booked revenue, stated as revenue per day. The form most US revenue teams keep in Salesforce reporting multiplies qualified opportunities by average deal value and by win rate, then divides by median sales cycle length in days. Each input is a decision.
The word qualified carries the weight, and a stage count is not a qualification rule. Write down the exit criteria for stage 1 and count only deals that met them, which is the discipline behind sales funnels that hold up.
Four steps fix the definition for a quarter:
- Freeze the opportunity definition, including the exit rule for every stage.
- Pull closed-won deals from the trailing four quarters and take the median days from creation to close.
- Divide closed-won by closed-won plus closed-lost over the same period.
- Multiply the four inputs and record the result with the date you ran it.
How to read the four inputs
Stage names vary by team, and the sales funnel overview maps how the common four usually connect.
| Input | How to measure it | The version that misleads |
|---|---|---|
| Qualified opportunities | Deals that met the stage 1 exit criteria | Every form fill added to the pipeline |
| Average deal value | Mean of closed-won deals, trailing four quarters | New-logo deals padded with expansion value |
| Win rate | Closed-won divided by closed-won plus closed-lost | Open deal count used as the denominator |
| Cycle length | Median days from creation to closed-won | Mean days skewed by one long enterprise deal |
Read the table once a quarter. Anything that moved more than 20 percent needs a cause, not a note.
Weighted pipeline value and where it drifts
Weighted pipeline value assigns a probability to each open deal and sums the result. Those probabilities usually come from historical stage conversion. If a stage holds 60 deals and 8 close, the weight is about 13 percent whether a rep believes it or not. Drift starts when managers override weights by hand to protect a forecast.
A weighted pipeline is a forecast input, not a forecast. Hand-edited weights hide the deals that never had a champion.
Stage conversion rates inherit lead quality, and the inputs behind B2B lead generation are where that shows up first.
Example: two reps, same coverage
Two reps each hold 30 open opportunities and report identical weighted pipeline value. Rep A closes in a median of 45 days. Rep B closes in 90. If their win rates and deal values match, Rep A's velocity is roughly double, and the dashboard shows neither figure. Coverage looks the same until the quarter ends and half the pipeline slips.
What it cannot tell you
Velocity is a rate, not a level. It can rise because slow deals stopped being worked rather than because selling improved. It also cannot speak to capacity: four reps cannot work 300 opportunities well, and the ratio will not say so.
The median is built from closed-won deals only. Deals still open that will take longer are excluded by design, so the figure runs optimistic at the edges. Bought intent data adds a privacy exposure the NIST Privacy Framework asks you to manage, and velocity reports none of it.
Attribution and its limits
Channel credit changes the reading. A first-touch model gives all the credit to the campaign that sourced the deal. Last-touch gives it to the demo request. The same quarter can look efficient under one model and wasteful under the other. Pick one, hold it for four quarters, and note it beside the number.
B2B marketing analytics is where those credit models live, and it is worth knowing which one your own reports use before you argue about a change in velocity.
When to stop measuring and decide
Set the threshold in advance. If weighted coverage falls below 3x the period target, or a stage's median duration rises more than 20 percent for two consecutive quarters, stop tuning the model and change the process. Measurement past that point becomes a way to avoid the decision.
Revisit the inputs only when stage definitions change, not every month. B2B marketing automation will recalculate a number whose definition quietly shifted, and nobody upstream will notice.
Common questions
How do you calculate b2b pipeline velocity? Multiply qualified opportunities by average deal value and win rate, then divide by median cycle length in days. The result is revenue per day.
Should cycle length be a mean or a median? Use the median. One 400 day enterprise deal can move a mean enough to change the number by half.
What is a good pipeline velocity number? No universal benchmark exists, because every input is internally defined. Compare your own figure against your own prior quarters, with the definition attached.
Why does stage count inflate velocity? Adding stages splits one qualification step into several, which raises the count of qualified opportunities without adding a buyer. Weighted coverage then looks healthier than the pipeline is.
