Most sales teams can tell you which deals are open. Fewer can tell you how quickly those deals are actually moving.
That gap matters. Two teams with the same pipeline value can produce very different revenue if one closes deals in 21 days and the other in 60. Deal velocity is the metric that makes this visible.
The problem is that deal velocity is usually locked inside a sales CRM as raw activity data, and few teams surface it as a single number worth watching. This guide walks through the formula, a worked example, and how to read the result.
Key Advantages
- Diagnose slowdowns early: A dropping deal velocity often signals a bottleneck long before revenue misses appear on a report.
- Compare segments fairly: Deal velocity normalizes for cycle length, so you can compare a fast-moving SMB team against an enterprise team without confusion.
- Forecast with grounded numbers: Multiplying deal velocity by working days gives a revenue projection tied to how the team actually sells.
- Focus coaching: The formula’s four inputs point to the specific lever a rep or manager should work on.
What Deal Velocity Actually Measures
Deal velocity is the revenue your pipeline generates per day, given how you currently sell. It answers one question: at the current rate, how much revenue moves through your process every day?
It is not the same as pipeline value, and it is not the same as win rate. It combines both, along with average deal size and cycle length, into one number.
The Formula
Deal Velocity = (Number of Opportunities × Average Deal Value × Win Rate) ÷ Sales Cycle Length in Days
Each input has a specific definition:
- Number of opportunities: Qualified deals in the pipeline during the measurement period, not raw leads.
- Average deal value: Median or mean deal size for the segment you are measuring.
- Win rate: Percentage of qualified opportunities that close won, expressed as a decimal (e.g., 0.22 for 22%).
- Sales cycle length: Average number of days from opportunity created to close won.
A Worked Example
Suppose a B2B SaaS team looks at Q1:
- 80 qualified opportunities
- Average deal value of Rp 45,000,000
- Win rate of 22% (0.22)
- Average sales cycle of 40 days
Deal Velocity = (80 × 45,000,000 × 0.22) ÷ 40 = Rp 19,800,000 per day
Reading that number: at the current pace, the process generates roughly Rp 19.8 million in closed revenue per working day. If the team wants Rp 30 million per day, one of the four inputs has to change.
That is what makes the formula useful. It does not just show current speed; it shows the four levers.
Reading the Four Levers
Each input answers a different question:
- Low opportunity count → problem is at the top of the funnel or in qualification.
- Low average deal value → problem is in packaging, segment mix, or discounting.
- Low win rate → problem is in fit, competition, or how the team handles objections.
- Long sales cycle → problem is in the process, procurement steps, or handoffs.
Two teams can have the same deal velocity for very different reasons. Comparing the four inputs matters more than comparing the final number.
Common Mistakes When Tracking It
A few patterns break the metric:
Counting unqualified leads as opportunities. This inflates the pipeline count and drops the win rate for the wrong reasons.
Using mean deal value when the sample is skewed. One large enterprise deal can pull the mean up and make the team look faster than it actually is. Median is safer in mixed segments.
Measuring cycle length from first touch, not opportunity created. Marketing-touch time and sales-cycle time are different things and get treated the same by many CRMs by default.
Recalculating too often. Deal velocity is a trend metric. Monthly is usually enough; weekly starts to reflect noise more than signal.
Where Your Sales CRM Fits
The formula is trivial. The hard part is getting the four inputs cleanly from a CRM.
Most sales CRMs record every input in raw form: stage history for cycle length, closed-won records for win rate, opportunity records for count and average value. What they often do not do by default is expose the four alongside each other on the same view.
Platforms like Cekat combine CRM with the channels where deals actually move — WhatsApp, calls, forms — so cycle length reflects the real conversation history rather than gaps caused by data not being logged. That reduces one of the most common sources of inaccurate cycle-length numbers.
Where to Start
If your team does not measure deal velocity today, do not wait for perfect data. Start with the last completed quarter, pull the four inputs from your CRM, and calculate one number.
Compare it to the same quarter last year. If it moved, ask which of the four inputs moved with it. That question alone often reveals the constraint the team should focus on next.
For teams that want to structure how opportunities move through the CRM before measuring velocity, see Cara Mengelola Sales Pipeline untuk Tim Penjualan for a starting framework.
Deal velocity is one of the few metrics where the formula tells you both the score and the lever. Used monthly, it turns a CRM from a system of record into a system of insight.
