Pipeline velocity is one of the most useful numbers in a B2B revenue system and one of the most rarely calculated. Most sales leaders track pipeline value and close rate. Few track how fast the pipeline is actually moving. And the speed at which deals move through a pipeline tells you things the volume and value numbers cannot: whether the process is working, where deals are stalling, and whether the pipeline number represents genuine forward motion or accumulated inertia.
The pipeline velocity formula
Pipeline velocity is calculated as: (Number of qualified opportunities x Average deal value x Win rate) divided by Average sales cycle length in days. The output is revenue generated per day. A business with 20 qualified opportunities, an average deal value of $15,000, a 25% win rate, and a 45-day average sales cycle has a pipeline velocity of $1,667 per day.
What the formula measures is the output of your entire pipeline system in a single number. Change any one variable and the velocity changes proportionally. This is why velocity is a better diagnostic metric than pipeline value alone. A $2M pipeline with a 45-day cycle and 20% win rate generates less velocity than a $1.5M pipeline with a 30-day cycle and 28% win rate.
What a low velocity number is actually telling you
Pipeline velocity has four inputs. When velocity is low, one of four things is happening: you do not have enough qualified deals, your win rate is too low, your average deal value is smaller than it should be, or your deals are taking too long to close. These have different causes and different fixes. Treating all four the same way produces the most common velocity mistake: adding more deals to a pipeline where the underlying problem is cycle length or win rate.
In our diagnostic work, the most common velocity problem we find is a pipeline integrity failure sitting underneath a velocity problem. The business calculates velocity using all the deals in the pipeline, including deals that have not moved in 60 days, deals where the buyer has gone dark, and deals that never should have been qualified. When we apply exit criteria and remove the phantom pipeline, the denominator shrinks. The velocity calculation becomes accurate. And the actual velocity is often significantly worse than the business thought, because the phantom deals were masking how few real deals were progressing.
How to use velocity to find where deals are stalling
Stage-by-stage velocity analysis is more useful than overall velocity for identifying where the process is breaking. Calculate conversion rate and average days spent at each stage. The stage where conversion rate drops most sharply, or where deals spend disproportionately long compared to other stages, is your stall point.
A common pattern: deals move quickly through Discovery and Qualification but sit in Proposal for three to four weeks with low conversion to Negotiation. This is not a proposal quality problem. It is a follow-up process problem. There is no defined sequence that triggers when a proposal goes unanswered. The fix is structural: a time-based re-engagement trigger fires after five business days with no buyer response, and a deal that does not advance within 21 days of proposal delivery moves to a re-engagement stage or is archived from the active pipeline.
The four levers that move pipeline velocity
Lever 1: Increase the number of qualified deals
Adding more deals increases velocity only if they are genuinely qualified. Adding unqualified deals to a pipeline increases the numerator while also increasing cycle length (because unqualified deals stall) and decreasing win rate (because unqualified deals do not close). The net effect on velocity can be negative. Qualification criteria must be defined and enforced before adding more volume produces any velocity improvement.
Lever 2: Increase win rate
Win rate increases when the right deals enter the pipeline and the process handles them correctly. Improving win rate requires knowing why deals are currently being lost. If loss reasons are not tracked systematically in the CRM, there is no data to act on. The Learning Loops layer of the five-layer revenue system diagnostic covers this directly. Loss tracking is not an administrative task. It is a velocity lever.
Lever 3: Increase average deal value
Deal value increases through better qualification (entering only deals that fit the right profile), better positioning (presenting value against the buyer's specific problem rather than a generic solution), and structured expansion (defining when and how to discuss scope beyond the initial purchase). None of these are sales training questions. They are process questions.
Lever 4: Shorten the sales cycle
Sales cycle length shortens when stage criteria are clear, follow-up is systematic, and stale deals are removed from the active pipeline promptly. The most reliable way to shorten average cycle length is to define maximum days-in-stage rules and enforce them. A deal that has been in Proposal for 30 days is not an active deal. Removing it from the active pipeline does not shorten the cycle for that deal. It makes the average cycle length for genuinely active deals visible and accurate.
How to track pipeline velocity over time
Calculate velocity monthly, using closed data from the previous 90 days for win rate and cycle length (to smooth out noise). Track each input separately so when velocity changes, you can identify which variable drove the change. A velocity drop caused by a win rate decline is a different problem from a velocity drop caused by a lengthening sales cycle. Both require a different response. The number tells you something is changing. The inputs tell you what.
Not sure what your pipeline velocity is or why it is declining?
Run the Revenue Diagnostic free in 5 minutes. No call required. See exactly which layer is costing you the most.
Run The Revenue Diagnostic →