Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Free Tool

Pipeline Velocity Calculator

ORM Technologies
Home/ Tools/ Pipeline Velocity Calculator
Active deals your reps are working
Percentage of qualified deals that close
Pipeline Velocity
$6,118
revenue generated per day
$183,529
Monthly revenue run rate
$550,588
Quarterly revenue capacity
$1,890,000
Total pipeline value
$415,800
Weighted pipeline

What this tells you

Pipeline velocity measures how fast revenue moves through your pipeline. The formula is straightforward:

Velocity = (Opportunities x Average Deal Size x Win Rate) / Sales Cycle Length

A higher number means your pipeline is converting revenue faster. But the number itself is less important than understanding which lever to pull.

Where most teams get stuck

After twenty years building revenue models, I have seen the same pattern hundreds of times. Teams look at pipeline velocity as a single number and miss the structural insight.

The four inputs do not carry equal weight. In most B2B SaaS companies between $100M and $1B ARR, win rate and sales cycle length are the highest-leverage variables. A 3-percentage-point improvement in win rate (from 22% to 25%) creates more revenue impact than adding 10 deals to the pipeline, because it compounds across every deal without adding cost.

Sales cycle length is the hidden variable. Most companies know their average cycle is "about two months." But the average masks critical variation. Enterprise deals might run 4-5x longer than mid-market. Expansion deals close 3x faster than new business. When you segment pipeline velocity by deal type, you find that your "one pipeline" is actually three or four different revenue engines with fundamentally different dynamics.

ORM's take: the number is a starting point

This calculator gives you a snapshot. What it cannot do is tell you why your velocity is where it is, which segments are dragging it down, or what specific changes will improve it.

That is what ORM's custom models do. We decompose your pipeline velocity by segment, by rep, by deal source, and by pipeline stage. Then we prescribe specific actions: accelerate these deals, add pipeline in this segment, reallocate these resources. The velocity number is the diagnostic. The prescription is where value is created.

What is a typical pipeline velocity?

Pipeline velocity is expressed as revenue per day, so it varies widely by industry and deal size. Use these as a sanity check rather than a target.

IndustryDaily revenue flow
Financial services$2,134
SaaS and technology$1,847
Healthcare and medtech$1,523
Manufacturing$1,289
Professional services$876
Marketing and advertising$743

Source: Digital Bloom 2025 B2B SaaS benchmarks.

Common questions

How do you calculate pipeline velocity?

Multiply the number of open opportunities by average deal value and win rate, then divide by average sales cycle length in days. The result is revenue per day, which makes it the one metric combining all four levers into a single number.

What is a good pipeline velocity?

There is no universal target, because the figure scales with deal size and cycle length. B2B SaaS averages around $1,847 a day. The useful comparison is against your own trend, since falling velocity signals a problem before the forecast does.

Which lever should you pull first to improve velocity?

Cycle length usually moves fastest and costs least, because it responds to qualification discipline and to clearing dead deals. Win rate is the most durable lever but the slowest. Deal count is the most expensive, since it means generating more pipeline.

Why does pipeline velocity fall when everything else looks fine?

The most common cause is cycle length quietly stretching while deal count and win rate hold. Because velocity divides by days, a 20% longer cycle cuts velocity by roughly a sixth even when nothing else changed.

How often should pipeline velocity be measured?

Weekly. Companies tracking it weekly report 87% forecast accuracy against 52% for teams tracking irregularly, the largest single gap in the benchmark data.

Get the full diagnostic

This tool tells you your velocity. ORM tells you what to change.

Schedule a Demo