The definition
Sales velocity is the amount of revenue your pipeline generates per day. The formula multiplies three things and divides by a fourth. Number of qualified open deals, times average deal value, times win rate, divided by the average sales cycle length in days. The result is money per day.
Each input has a precise meaning, and sloppiness in any one of them corrupts the whole number. Deal count means qualified opportunities, not raw enquiries. Average value means the average of won deals, defined the way average deal size describes. Win rate means won divided by closed, as pinned down in the win rate entry. Cycle length means days from deal creation to won, taken from won deals only.
Why it matters
Work an example. A team has 40 qualified open deals, an average won deal of €8,000, a win rate of 25 percent and a 60 day cycle. Velocity is 40 times 8,000 times 0.25, divided by 60. That is €80,000 divided by 60, so roughly €1,333 per day, or €40,000 per month. If the revenue target is €55,000 per month, the gap is now a maths problem instead of a mood.
The power is in the levers. To reach €55,000, the team can raise deal count from 40 to 55, or lift win rate from 25 to 34 percent, or cut the cycle from 60 to 44 days. Each is a different project with a different owner. More deals is a marketing and prospecting question. Better win rate is qualification and sales craft. A shorter cycle is usually process: faster follow-up, fewer deals parked between stages. Velocity tells you which project pays best, because you can simulate each change before committing a quarter to it.
How to measure it in Pipedrive
Pull the four inputs from places that already exist. Deal count comes from a filter on open deals, restricted to the stages past qualification. Average won value and win rate come from Insights deal reports over a trailing period, twelve months for stability if volume is modest, six if the business changes fast. Cycle length comes from the deal duration report, won deals only. Keep the trailing window identical for all inputs, or the number stops meaning anything.
Then compute velocity outside Pipedrive, in the spreadsheet or dashboard where your monthly numbers live, and log it monthly. The discipline that keeps the inputs honest is unglamorous: stages with real exit criteria, dead deals actually marked lost, and activity on everything open. That is data hygiene territory, and it is why two teams with identical selling can report very different velocities.
Where teams get it wrong
The first mistake is inflating the deal count. Every half-interested enquiry gets a deal, the count doubles, and velocity looks great while nothing closes. Qualify into the pipeline through the lead inbox and the count stays real. The second mistake is mixing windows: this quarter's deal count with last year's win rate produces a number nobody can interpret. Third, gaming one lever at the cost of another. Discounting shortens the cycle and lifts win rate while it quietly sinks average value, and velocity can fall even as more deals close. Always read the four inputs alongside the composite.
Last, do not turn velocity into a rep target. It is a diagnostic for the system, not a quota for a person. The moment individual bonuses hang on it, the inputs get managed instead of the selling, cycle dates get massaged, and the metric loses the only thing it had: honesty.