Metric Definition
Diagnosing what speeds and slows deals
Track from
Deal velocity analysis
Deal velocity analysis is the practice of measuring how quickly deals close and breaking that speed down by stage, segment, source, and rep to find what accelerates or slows them. Where deal velocity gives you a single average, the analysis tells you the reasons behind it. It turns a lagging number into a set of specific, fixable causes of delay.
7 min read
What is deal velocity analysis?
Deal velocity analysis is the practice of measuring how fast deals close and then breaking that speed down by stage, segment, source, and rep to understand the causes. The headline figure is the same average days to close that deal velocity reports, but the analysis does not stop at the average. It asks which stages consume the most time, which segments move fastest, and which sources produce deals that close quickly versus deals that drag.
The distinction matters. A single deal velocity of 60 days is a number. Deal velocity analysis reveals that inbound deals close in 35 days while outbound deals take 85, or that 40 per cent of total cycle time is spent in legal review. Those findings are actionable in a way the headline average never is.
The purpose is diagnostic. By comparing velocity across dimensions and decomposing it across stages, you separate genuine process friction from natural differences in buyer complexity. You learn where to intervene, and you learn which differences are simply the cost of selling a larger or more considered deal.
Deal velocity analysis is only as good as its segmentation. Always slice by deal size and motion first, because comparing a self-serve cycle to an enterprise cycle as if they were the same thing produces conclusions that are worse than no analysis at all.
How to calculate deal velocity analysis
The core calculation is the same as deal velocity, the total days to close divided by the number of won deals, but you run it repeatedly across segments and stages rather than once across everything. The analysis lives in the comparison, not in a single output.
For example, calculate velocity for inbound and outbound separately. If inbound averages 35 days across 50 deals and outbound averages 85 days across 30 deals, the gap of 50 days is the analytical finding. You then decompose each cycle into time per stage to locate where the outbound gap comes from, whether it is slower qualification, longer discovery, or extended negotiation.
Stage-level decomposition is the heart of the analysis. For each stage, sum the days deals spent in it and divide by the deals that passed through, giving an average dwell time per stage. The stage with the longest dwell time relative to benchmark is the first place to investigate.
- 1
Calculate the baseline velocity
Work out the overall average days to close for won deals so you have a single reference number to decompose.
- 2
Segment the velocity
Recalculate velocity by deal size, lead source, segment, and rep. The differences between segments are the first layer of findings.
- 3
Decompose into stage dwell times
For each stage, average the days deals spent in it. This reveals which stage consumes the most time and is the true bottleneck.
- 4
Compare against your own baseline
Track stage dwell times and segment velocities over time so you can tell whether an intervention genuinely changed the pattern.
Deal velocity analysis in a metric tree
Deal velocity analysis is, in effect, a metric tree exercise. You take overall cycle time and decompose it into stage dwell times, then break each stage into the operational drivers that lengthen or shorten it. Modelling this explicitly as a tree means every driver has a place, a measurement, and an owner.
Metric tree insight
The tree shows not just that outbound deals are slower, but that the gap sits almost entirely in discovery dwell time driven by stakeholder count. KPI Tree attaches a RACI owner to each dwell-time driver, notifies the accountable owner when a stage starts to lengthen, and uses the verified impact loop to confirm whether the change to discovery actually closed the gap rather than just appearing to.
Deal velocity analysis benchmarks
Because deal velocity analysis is about comparison, the most useful benchmarks are the relative shares of time each stage consumes and the typical gaps between sources. These vary by motion, but the patterns below are common enough to orient against before you build your own baseline.
| Dimension compared | Typical fast end | Typical slow end | Usual cause of the gap |
|---|---|---|---|
| Inbound vs outbound | 30 to 45 days | 70 to 100 days | Outbound starts colder, longer discovery |
| SMB vs enterprise | 20 to 45 days | 120 to 300+ days | Stakeholders and procurement |
| Existing vs new logo | 15 to 40 days | 60 to 150 days | Trust and security review already done |
| Stage share of cycle | Qualification 10% to 20% | Negotiation 30% to 45% | Late-stage procurement friction |
A large gap between two segments is not automatically a problem to fix. Some of it reflects real differences in buyer complexity. The analysis is about separating the avoidable friction from the unavoidable cost of a more considered deal.
How to improve deal velocity analysis
Improving deal velocity analysis means making the analysis sharper and then acting on its sharpest finding. A better analysis isolates the one stage or segment that is genuinely draggy and gives a clear owner the evidence to fix it.
Segment before you conclude
The most common cause of a wrong conclusion is a blended average. Slice velocity by size, source, and motion first, so any gap you act on is a real difference and not an artefact of mixing deal types.
Decompose to stage dwell time
An overall slowdown means little until you know which stage caused it. Break the cycle into per-stage dwell times so the analysis points to a specific, fixable stage rather than a vague sense that deals are slow.
Compare against your own trend
A single snapshot cannot tell you whether a change helped. Track stage dwell times over time so you can see whether an intervention moved the pattern or whether the number drifted back.
Act on the single biggest gap
Once the analysis names the slowest stage or segment, concentrate effort there. A focused fix on the largest dwell time beats spreading small improvements across every stage at once.
Common mistakes when tracking deal velocity analysis
- 1
Analysing the blended average only
Running velocity once across all deals defeats the point of the analysis. The insight is in the differences between segments, so segmentation is not optional, it is the work itself.
- 2
Treating every gap as friction
A longer enterprise cycle is partly the natural cost of a complex deal. Mistaking unavoidable complexity for fixable friction leads to pressure that damages large deals without speeding them up.
- 3
Skipping stage decomposition
Knowing a segment is slow without knowing which stage is slow gives you nowhere to act. Always decompose the cycle into stage dwell times before deciding on an intervention.
- 4
Drawing conclusions from too few deals
Segmenting too finely leaves each segment with a handful of deals, where one outlier swings the average. Keep segments large enough that the velocity figure is stable before you trust it.
Related metrics
Sales pipeline velocity
Sales Metrics
Metric Definition
Pipeline Velocity = (Opportunities × Deal Value × Win Rate) / Sales Cycle Length
Sales pipeline velocity measures how quickly deals move through your pipeline and generate revenue. It combines the four core levers of sales performance into a single metric that reveals the rate at which your pipeline converts to closed revenue.
Win rate
Sales MetricsMetric Definition
Win Rate = (Closed-Won Deals / Total Closed Deals) × 100
Win rate measures the percentage of sales opportunities that result in a closed-won deal. It is the single most revealing metric of sales effectiveness, indicating how well your team converts qualified pipeline into revenue.
Average deal size
Sales MetricsMetric Definition
Average Deal Size = Total Revenue from Closed Deals / Number of Closed Deals
Average deal size measures the mean revenue value of closed-won deals. It is a fundamental sales metric that directly influences pipeline velocity, quota planning, and the economics of your go-to-market model.
Quota attainment
Sales MetricsMetric Definition
Quota Attainment = (Actual Revenue Closed / Quota Target) × 100
Quota attainment measures the percentage of a sales target that a rep or team achieves in a given period. It is the primary performance metric for sales organisations, connecting individual and team output to revenue goals.
Why did my metric change?
Metric Definition
This diagnostic framework helps you isolate exactly which factors are speeding up or slowing down deal velocity rather than guessing at the cause.
Metric trees for sales teams
Metric Definition
Deal velocity sits inside the wider sales metric tree, so this guide shows how it connects to the pipeline and conversion metrics it depends on.
Turn a slow cycle into a named cause
Model deal velocity analysis as a metric tree in KPI Tree so every stage dwell time has an owner, the accountable person hears about a slowdown the moment it starts, and the verified impact loop confirms which intervention actually moved the cycle.
