The Pipeline Velocity Formula: Where Your Deals Actually Slow Down

Pipeline velocity equals (number of qualified opportunities multiplied by average deal size multiplied by win rate) divided by average sales cycle length in days. Say your team has 40 qualified opportunities, an average deal size of $18,000, a win rate of 20 percent, and a 60-day average sales cycle. In this example, that works out to $2,400 in expected daily pipeline revenue once you divide 40 times $18,000 times 0.20 by 60. Run this monthly and watch the trend, not just the single number.

Each of the four inputs moves velocity differently, and teams often chase the wrong one. Doubling opportunity count without touching win rate or cycle length doubles velocity, but so does cutting your sales cycle in half. If your cycle is genuinely long because of an unnecessary extra approval step or a slow proposal turnaround on your side, fixing that internal friction often moves the number faster than generating more top-of-funnel volume, and it's usually cheaper too.

Break your average cycle length down by stage instead of treating it as one block of time. Most teams find one or two stages eating a disproportionate share: often the gap between a verbal yes and a signed contract, or the wait between a proposal being sent and any response at all. Pull the actual stage-duration data from your CRM rather than guessing, because gut feel about where deals stall is wrong more often than sales leaders expect.

A new-logo win rate near 19 percent¹ is roughly the market average, so if your number sits meaningfully below that, look first at qualification rather than closing technique. Deals that get into the pipeline without a confirmed budget or a real decision-maker drag win rate down and inflate cycle length at the same time, because they linger in the middle stages before eventually dying. Tightening what counts as a qualified opportunity often improves both numbers at once.

Calculating pipeline velocity once a quarter tells you a trend happened after it's too late to act on it. Track it monthly, broken out by rep or segment if your team is large enough, and look for the input that moved most since last month. A sudden drop in average deal size, for instance, might mean reps are discounting to close faster, which helps this month's velocity number while quietly hurting the next several months of revenue.

Each month, review the four inputs and note which one moved most:

• Opportunity count: more qualified opportunities raise velocity, but only if win rate and cycle length hold steady.
• Average deal size: watch for a sudden drop, which can mean reps are discounting to close faster.
• Win rate: if it sits well below the market average, look at qualification before closing technique.
• Sales cycle length: break it down by stage and look for internal friction, such as slow proposal turnaround or an unnecessary approval step.

Say a team has 50 qualified opportunities, a $15,000 average deal size, a 60-day cycle, and a win rate that quietly dropped from 25 percent to 15 percent over two quarters. In this example, velocity falls by 40 percent purely from that one input, even if opportunity count and cycle length stay exactly the same, which is easy to miss if leadership only looks at the final velocity number instead of its parts.

In this example, the fix isn't more top-of-funnel activity, since the pipeline is already reasonably full. It's figuring out why deals that used to close a quarter of the time now close closer to one in seven, which usually points to a qualification or competitive issue worth investigating directly with the reps, not a lead-generation problem to throw more spend at.

The lesson generalizes: whenever velocity moves, decompose it back into its four inputs before reacting. A leadership team that responds to a velocity drop by demanding more outbound volume, when the real cause was a falling win rate, ends up with an even fuller pipeline of deals that still won't close at the old rate, which makes the underlying problem harder to see, not easier.