Deal Velocity
Deal velocity is the speed at which an individual deal advances through pipeline stages and reaches a closed outcome, often expressed as days per stage or days to close.
Key takeaways
- Deal velocity comes from stage-change timestamps, so stage history must be logged as it happens.
- Dwell time per stage locates the bottleneck; total days to close only proves one exists.
- An agreed next step with a date is the strongest accelerant on an individual deal.
- Advancing a deal before its exit criteria are met relocates the delay downstream.
- Judge dwell against that stage's own typical duration, never against other stages.
In depth
Deal velocity is derived from stage-change history rather than from two dates. Every time an opportunity moves, the CRM writes a timestamp, and the difference between consecutive timestamps is the dwell time in that stage. The profile of those dwell times, plus the total days from creation to close, is what people mean by the velocity of a single deal. The data is only as honest as the logging: if reps bulk-update stages at the end of a quarter, every dwell time collapses into the final week and the record becomes fiction.
At the level of one opportunity, the reliable accelerant is a next step with a date and a named participant agreed before the current meeting ends. Deals with more than one engaged contact also move faster, because the internal relay does not depend on a single champion's calendar. What slows a deal is undefined ownership of the next action and questions that surface late. The tempting shortcut, advancing a deal to the next stage before its exit criteria are met, moves the delay downstream instead of removing it.
The working artefact is an aging report: open deals sorted by days in their current stage, with anything past that stage's typical dwell flagged for review. Managers coach on the specific friction rather than on general urgency. Handoffs are the other lever, since the hours between a lead qualifying and a rep making contact are pure dead time. Where a scorecard funnel feeds the pipeline, the quiz answers travel with the opportunity, so the first conversation starts on the buyer's situation rather than on basic discovery.
Velocity measures motion, not fit. A deal pushed quickly through weak qualification closes fast and churns later, which shows up in retention rather than in any pipeline report. Part of every dwell time also belongs to the buyer: a board that meets monthly sets a floor no seller can lower. Individual comparisons are shaky too, because a rep who works six deals a quarter does not have enough of them for a dwell average to mean anything reliable.
Example in practice
How to measure it
Use median dwell time per stage, segmented by deal size, and put stage conversion rate beside it. Those two numbers together separate a stage that is genuinely efficient from one where deals are being pushed forward prematurely. Add time from qualification to first rep contact, because that handoff gap is usually the largest piece of dead time that a team can remove without touching the buyer.
For open pipeline, run an aging report weekly: the count and value of deals sitting beyond one and a half times their stage median, plus days since the last recorded activity. Deals that are old and quiet are the ones most likely to be lost without ever being marked lost. Reviewing them on a schedule turns velocity from a report into a working queue.
Common mistakes
The first failure is retroactive stage updates. A rep moves a deal through three stages on the last day of the quarter, and the history now shows two stages that took no time at all followed by one that apparently took eleven weeks. Require stage changes at the moment the exit criterion is met, define those criteria in a sentence each, and check the stage history during deal reviews rather than only the current stage.
The second is treating speed as the coaching target. Reps respond by advancing deals that are not ready, so early stages look fast and the proposal stage fills with opportunities that were never qualified. Coach on the stage where dwell is longest and conversion is weakest, and always read dwell time next to stage conversion rate. A stage that got faster while its conversion fell has not improved at all.
Frequently asked questions
What is the difference between deal velocity and pipeline velocity?
Deal velocity measures how fast a single opportunity moves through stages, while pipeline velocity is the aggregate revenue your whole pipeline generates per day. Improving individual deal velocity feeds into a higher overall pipeline velocity.
How do you measure deal velocity?
Track the time each deal spends in each pipeline stage and the total days from creation to close. Comparing dwell times across stages highlights where deals get stuck.
Can lead scoring increase deal velocity?
Yes. Routing high-fit, well-qualified leads with context to the right rep helps deals enter warmer and clear early stages faster. Automated CRM handoffs further remove manual delays.
How is deal velocity different from sales cycle length?
Sales cycle length is a single average across won deals, while deal velocity looks at how one opportunity moves between individual stages. Cycle length tells you a deal takes sixty days; deal velocity tells you that forty of them were spent waiting in the proposal stage. One is a reporting number, the other is a coaching and forecasting tool.
How do I find the stage that is slowing deals down?
Calculate median dwell time for each stage from your stage-change history, then compare each stage against its own past performance rather than against the others. A late stage is naturally slower than a first one. The stage worth attention is the one whose dwell time has grown, or where dwell is long and conversion to the next stage is poor.
Is a faster deal always a better deal?
No. Speed achieved by skipping qualification produces deals that close and then churn, and speed achieved through discounting costs margin permanently. The useful pairing is dwell time next to win rate and retention. If deals move faster and both of those hold, the improvement is real; if either falls, you have moved the problem rather than solved it.
How do I measure deal velocity when reps do not update the CRM?
You cannot, and that is the first problem to solve. Reduce required stages to the few that represent real decisions, write one clear exit criterion for each, and make the stage change part of the meeting follow-up rather than an administrative task done later. Automated reminders after a logged call help, but only if the stage model is simple enough to be honest.
What parts of a deal can automation actually speed up?
The handoffs and the waiting between human steps: routing a qualified lead to the right rep immediately, sending the meeting link without a scheduling exchange, triggering the follow-up when a proposal is opened, and reminding both sides of an agreed next step. Automation does not shorten a buyer's evaluation, but it removes the hours and days that sit between your own actions.
How many deals do I need before velocity data is meaningful?
Enough that a single unusual deal cannot move the median, which usually means looking at a team or a segment rather than one rep's quarter. With a handful of deals, dwell times reflect who those particular buyers were. Aggregate across a longer window for individual coaching, and use the shorter view only to spot deals that are currently stuck.