Sales Velocity Calculator

The underlying calculation

Sales velocity is (opportunities × average deal value × win rate) ÷ sales cycle length in days. It gives revenue generated per day and combines the four variables a sales operation can influence.

Its value is that it shows which of the four to work on, since they are multiplicative and one is a divisor.

Shortening the cycle raises velocity as directly as raising the win rate, and it is frequently easier.

Worked through

1,344 opportunities a quarter, $58 average deal value, a 75% win rate and a 21-day cycle: (1,344 × 58 × 0.75) ÷ 21 = $2,784 a day.

Improving the win rate from 75% to 82% raises it to $3,044, a 9.3% gain. Shortening the cycle from 21 days to 18 raises it to $3,248, a 16.7% gain.

The cycle length is the more powerful lever here and it is the one nobody targets, because win rate is the metric sales teams are measured on.

Raising deal value by 10% would give the same 10% as a proportional win rate improvement, which puts the four levers in order for this business.

Where it goes wrong

It assumes the four variables are independent, and they are not. Pushing to shorten the cycle frequently lowers the win rate, and raising deal value usually lengthens the cycle.

Averages also conceal segment differences: a business with small fast deals and large slow ones has a blended velocity describing neither.

Making it useful

Calculate it per segment rather than in aggregate, so the fast and slow parts of the business are managed differently. A single figure across mixed deal types produces the wrong priority for both.

Then look at cycle length specifically, since it is the divisor and the least-worked term. Most cycle time is waiting rather than working, and removing waiting stages costs nothing in win rate.

Where cycle time actually goes

In most sales processes the elapsed time is dominated by gaps between activities rather than by the activities themselves: waiting for a reply, waiting for an internal approval, waiting for a scheduled call.

Mapping the process by elapsed time rather than by stage usually finds that a 21-day cycle contains two or three days of work, which makes the compression opportunity obvious.

Removing a single scheduling delay by offering a booking link, or pre-empting an approval step by supplying the documentation earlier, frequently takes several days out of a cycle. Those changes cost nothing and improve velocity more than a comparable effort on win rate would.

Deal value and cycle length usually move together, so raising average deal size will lengthen the cycle and the net effect on velocity has to be calculated rather than assumed.

Tracking the four components separately over time shows which are drifting, since a stable velocity can conceal a rising deal size offsetting a falling win rate.

Removing unqualified opportunities from the numerator improves the accuracy of every term, since a pipeline padded with deals that were never real distorts all four inputs at once.