The blended number cancels itself out
Every input in the formula moves in a different direction by segment. Small deals arrive in volume, convert quickly, and carry low value. Large deals arrive rarely, convert less often, and take months. Multiply and divide those together in one calculation and the opposing movements offset, which is why a blended velocity figure can sit flat through a year in which both motions changed substantially.
The consequence is practical. Velocity is supposed to answer where to add a rep, and a number that describes no real motion cannot answer it.
Cut all four inputs the same way
Segment the count, the value, the win rate, and the cycle length on the same boundary. Splitting only some inputs produces a hybrid that is harder to interpret than the blend it replaced.
Use average closed-won value for the value term. ORM has seen pipelines carrying an $80,000 average deal size against $40,000 in average closed-won value. Feeding the open-pipeline figure into a velocity calculation doubles the output for a segment whose real throughput never changed.
Read it as a diagnosis
| Segment pattern | What to check |
|---|---|
| High velocity, low deal value | Whether volume can scale without adding headcount |
| Low velocity, high deal value | Whether cycle length or win rate is the constraint |
| Velocity rising, value falling | Pricing pressure moving deals down-market |
| Velocity falling, count rising | Conversion or cycle length degrading under load |
Where it changes decisions
Segment velocity sets the pipeline requirement per segment rather than one company-wide ratio. ORM sees 3x to 5x pipeline coverage as the standard range, with most customers around 3.5x, and a segment view shows why the range is that wide. A segment with a short cycle and a high win rate needs less coverage than one that runs six months at half the conversion.
It also sets creation deadlines. A segment velocity model tells you the last date pipeline can be created and still contribute this quarter, which is the check most coverage conversations skip.
Use it alongside pipeline coverage rather than instead of it, and segment win rate on the same boundary so the inputs stay comparable. The sales velocity breakdown covers how the four terms interact.
Frequently Asked Questions
Why calculate sales velocity by segment?
Because all four inputs differ by segment. A blended figure averages a high-volume short-cycle motion against a low-volume long-cycle one and produces a number that describes neither, which makes it useless for deciding where to add capacity.
Which deal value should the formula use?
Average closed-won value, not average open pipeline value. ORM has seen pipelines carrying an $80,000 average deal size against $40,000 in average closed-won value, and using the open figure inflates velocity by a factor the model never earns.
How small can a segment be before the math breaks?
Each segment needs enough resolved deals for a stable win rate and cycle length. Below that, both inputs swing on individual outcomes and the velocity number moves for reasons that have nothing to do with performance.
Does higher velocity always mean better performance?
No. Velocity rises when deal size falls if cycle length falls faster, so a team can post improving velocity while shrinking revenue per deal. Read the four inputs individually before drawing a conclusion from the output.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like sales velocity by segment into prescriptive action for your team.
Schedule a Demo