What is Pipeline Velocity?

Pipeline velocity is the revenue your open pipeline produces per day, worked out from four numbers (qualified opportunities, average deal value, win rate and sales cycle length) so a team can see which one is slowing revenue down.

At a glance

• Formula: (opportunities × average deal value × win rate) ÷ sales cycle length in days.
• Salesforce, HubSpot and Clari all publish the same four-part formula, sometimes under the name sales velocity.
• The result is a rate, revenue per day, so you can compare it month to month.
• Three inputs raise it and one lowers it: a longer cycle cuts velocity even if nothing else changes.
• Calculate it per segment. An enterprise deal and a small-business deal don’t belong in one average.

How to calculate pipeline velocity

Use the same window for every input, usually the last two to four quarters. Count only opportunities past your qualification stage, use the average value of deals you actually won, and measure cycle length from opportunity creation to close.

Example (illustrative): 40 qualified opportunities × $25,000 average deal × 25% win rate = $250,000 of expected revenue. Divide by a 50-day cycle and velocity is $5,000 per day. If the cycle stretches to 70 days with nothing else changing, velocity drops to about $3,570 per day.

What each input tells you

• Opportunities: whether top-of-pipeline work is producing enough qualified deals. This is usually where outbound and inbound show up.
• Average deal value: whether you’re selling to the right size of account. Compare it with your ACV targets.
• Win rate: how well qualification and the sales process hold up from opportunity to close.
• Sales cycle length: how long deals take, and where they wait.

Two teams can post the same velocity with opposite problems. One wins often but deals sit for months. The other closes fast but loses most of what it works. The fix is different for each, which is why the inputs matter more than the total.

Common pipeline velocity mistakes

• Padding the opportunity count. Adding unqualified deals raises the first input and drags win rate down, so velocity barely moves while the pipeline looks bigger.
• Blending segments. A 120-day cycle is normal for a large deal and a problem for a small one. One blended number hides both.
• Using a CRM default win rate. Use your own closed-won ÷ closed history, or the result is a guess with a decimal point.
• Chasing the total. Pick one input to move, change one thing, and measure that input next month.

How pipeline velocity shows up in a revenue system

Velocity is a RevOps number: it only works if stages, close dates and amounts are kept current in the CRM. Keeping those fields clean and the reports honest is part of the RevOps work we run inside partners’ systems.

Terms that sit next to pipeline velocity

Velocity is calculated from the pipeline itself and depends on pipeline hygiene to mean anything. Pipeline coverage tells you whether there’s enough volume, and velocity tells you how fast it turns into revenue. Both feed forecast accuracy.