What this tells you
Sales velocity measures how much revenue your pipeline generates each day. The formula is:
Sales Velocity = (Qualified Opportunities x Average Deal Value x Win Rate) / Sales Cycle Length
The result is a dollars-per-day figure. Multiply it out and you get your monthly run rate, your quarterly capacity, and the weighted value already sitting in your pipeline. A higher number means revenue is moving faster, but the figure matters less than knowing which of the four inputs is holding you back.
Same metric as pipeline velocity, viewed from the rep's side
Sales velocity and pipeline velocity use the identical formula. The difference is the question you are asking. Sales velocity frames it from the rep and quota angle: how much revenue per day is the sales motion producing right now. Pipeline velocity frames the same math from the funnel angle: how fast revenue is flowing through the stages of the pipeline. One metric, two vantage points. Use this page when the conversation is about rep productivity and quota coverage, and use the pipeline velocity calculator when the conversation is about funnel health and stage conversion.
The input that quietly controls the result
After two decades building revenue models, I keep seeing teams treat all four inputs as equal. They are not. Win rate and sales cycle length carry the most leverage in B2B SaaS. Moving win rate from 22% to 25% lifts velocity more than adding ten deals to the pipeline, because the gain compounds across every deal at no extra cost. Sales cycle length is the input most teams quote as a single average, even though enterprise deals can run several times longer than mid-market and expansion deals close faster than new business. Segment the cycle and the one velocity number splits into several very different revenue engines.
ORM's take: the number is a starting point
This calculator hands you a snapshot. It cannot tell you why your velocity sits where it does, which segments drag it down, or which change moves it most. That is the work ORM's custom prescriptive models do. We decompose sales velocity by segment, by rep, by deal source, and by stage, then prescribe specific actions: accelerate these deals, add pipeline in this segment, reallocate these resources. Our forecasts run at 95%+ accuracy because they are built on your data, not a generic benchmark. The velocity figure is the diagnostic. The prescription is where the value gets created.
Common questions
How do you calculate sales velocity?
Multiply open opportunities by average deal value and win rate, then divide by sales cycle length in days. The output is revenue per day. It is the only metric that combines all four levers, which is why it moves before any of them show up in the forecast.
What is the difference between sales velocity and pipeline velocity?
In practice they use the same formula and the terms are used interchangeably. Where teams distinguish them, sales velocity is measured per rep or per team and pipeline velocity across the whole funnel. Pick one definition and hold it, because mixing the two makes trends meaningless.
Which input should you improve first?
Cycle length, usually. It responds fastest to qualification discipline and to clearing dead deals, and it is the input that has moved most against B2B SaaS teams: cycles have lengthened 22% since 2022.
Why does sales velocity fall when the pipeline looks healthy?
Because velocity divides by days. A cycle stretching 20% cuts velocity by roughly a sixth even when deal count, deal size and win rate are all unchanged. That is why it is an early warning rather than a lagging report.
How often should sales velocity be reviewed?
Weekly. Teams tracking pipeline weekly report 87% forecast accuracy against 52% for those tracking irregularly, and velocity is the number that makes a weekly review worth holding.
Get the full diagnostic
This tool tells you your velocity. ORM tells you what to change.
Schedule a Demo