Sales velocity is the amount of revenue your sales pipeline produces per day. You calculate it from four numbers: how many deals you are working, their average size, the share you win, and how long winning takes. One formula, one output, measured in money per day.
The name borrows from physics, and the metaphor holds up. Velocity measures speed toward a destination, and this metric measures how fast pipeline turns into closed revenue. Some teams call it pipeline velocity instead. Same formula, same output, different label.
I have run velocity reviews for teams of 3 reps and teams of 60. Honestly, computing the number is the easy part. The discipline behind the four inputs is where most teams stumble. So this guide covers the formula, a worked example with real numbers, the four levers, and the traps I keep watching teams fall into.
What is the Sales Velocity Formula?
The sales velocity formula multiplies opportunities, average deal value, and win rate, then divides by sales cycle length. It returns revenue per day.
Sales velocity = (Number of opportunities x Average deal value x Win rate) / Sales cycle length in days
Each input has a precise meaning, and sloppy definitions here corrupt everything downstream. Here is what goes into each slot:
- Number of opportunities. Open, qualified deals in your pipeline during the measurement window. Not raw leads, and not every name sitting in your CRM.
- Average deal value. The mean value of your recent closed-won deals. Subscription businesses usually use annual contract value here.
- Win rate. Closed-won deals divided by all closed deals, won plus lost, in the same window.
- Sales cycle length. The average number of days a won deal takes to travel from qualified to signed.
Notice the shape of the equation. Three inputs push the number up, and one drags it down. HubSpot’s guide describes the metric as how quickly deals move through your pipeline and generate revenue, which captures the spirit. The formula just makes that spirit auditable.
💡 Pro Tip: Measure all four inputs over the same window, usually a rolling 90 days. Mixing a quarterly win rate with an annual cycle length produces a number that looks precise and means nothing.
How Do You Calculate Sales Velocity? A Worked Example
You calculate sales velocity by pulling four numbers from one report and one window, then doing two multiplications and one division. Let me walk through a realistic mid-market SaaS team over a 90-day window.
| Input | Value | Where it comes from |
|---|---|---|
| Number of opportunities | 40 | Open, qualified deals in the pipeline report for the window |
| Average deal value | $12,000 | Mean of closed-won deals over the trailing two quarters |
| Win rate | 22% | Closed-won divided by closed-won plus closed-lost, same window |
| Sales cycle length | 60 days | Average days from qualified stage to signature, won deals only |
Now the math, step by step. First, 40 opportunities times $12,000 gives $480,000 of pipeline value. Multiply by the 22 percent win rate and $105,600 of it is realistically winnable. Divide by the 60-day cycle and you get $1,760 of revenue per day.
Stretch that over a 90-day quarter and the pipeline should produce roughly $158,400. For comparison, Salesforce’s worked example lands on $1,250 per day using the identical method. The absolute number matters less than the trend, but the units are always money per day.
📌 Example: Sanity-check the output against reality. If the formula says $1,760 a day but last quarter actually booked $90,000, one input is lying. In my audits the liar is usually the win rate, inflated by deals that were never really qualified.
Why Does Sales Velocity Beat Vanity Pipeline Metrics?
Sales velocity beats vanity metrics because it forces four competing numbers into one honest output. You cannot flatter it by inflating a single input, because the other three push back.
Think about the usual suspects on a pipeline dashboard. Total pipeline value sounds impressive and pays nothing if it never closes. Deal count rewards whoever creates the most records. Even pipeline coverage, a genuinely useful ratio, only says whether you have enough pipeline. It says nothing about how fast that pipeline converts.
This matters most in B2B sales, where a big, slow pipeline can hide behind healthy coverage ratios for quarters. Velocity exposes it immediately, because the long cycle sits right there in the denominator. Zendesk’s guide compares the pipeline to a river and velocity to the tool that finds the rocks where deals get stuck. That framing matches what I see in practice.
There is a second benefit, and it is organizational. Marketing owns part of opportunity count, sales owns win rate, pricing owns deal value, and operations owns cycle time. Velocity gives all four owners one shared scoreboard instead of four private ones.
Here is how velocity sits next to the metrics it usually shares a dashboard with:
| Metric | Question it answers | What it hides |
|---|---|---|
| Total pipeline value | How big is the pot? | Whether any of it will close, or when |
| Deal count | How busy are we? | Deal quality and deal size |
| Pipeline coverage | Is there enough pipeline for the target? | How fast that pipeline converts |
| Win rate | How often do we win? | Deal size and how long wins take |
| Sales velocity | How much revenue per day does the machine produce? | Nothing structural, if the inputs are clean |
None of the first four metrics is useless. Each answers a real question, and I still report most of them. The difference is that every one of them can improve while the business gets worse. Velocity is the only row where that trick is hard to pull off.
💡 Pro Tip: A quick test for any pipeline metric: can it go down when the business gets worse? Total pipeline value only ever grows. Velocity falls the moment deals slow or shrink, and that sensitivity is exactly what makes it useful.
What Are the Four Levers of Sales Velocity?
The four levers are opportunity count, average deal value, win rate, and cycle length. Every velocity improvement you will ever make is one of these four moving, so it pays to know how each one responds.
Before the details, look at how the levers compound. Small gains on several levers beat a heroic push on one:
| Scenario | Opportunities | Avg deal value | Win rate | Cycle (days) | Velocity per day |
|---|---|---|---|---|---|
| Baseline | 40 | $12,000 | 22% | 60 | $1,760 |
| +10% opportunities | 44 | $12,000 | 22% | 60 | $1,936 |
| +10% deal value | 40 | $13,200 | 22% | 60 | $1,936 |
| +10% win rate | 40 | $12,000 | 24.2% | 60 | $1,936 |
| 10% shorter cycle | 40 | $12,000 | 22% | 54 | $1,956 |
| All four together | 44 | $13,200 | 24.2% | 54 | $2,603 |
Ten percent on each lever compounds into 48 percent more revenue per day. That compounding is the strongest argument for working the levers together instead of chasing one.
Lever 1: More Qualified Opportunities
The first lever is feeding the pipeline more deals that are actually winnable. The qualifier carries all the weight in that sentence. Adding junk opportunities lifts the count, tanks the win rate, and stretches the cycle, so velocity often falls.
In practice, this lever responds to sourcing capacity and list quality. Tighter ideal customer profile filters, referral programs, and real alignment between marketing and sales all raise the share of new deals worth working. My rule from years of pipeline reviews: grow this input only as fast as quality holds. A pipeline that doubles while win rate halves has gained nothing except reporting noise.
Channel mix belongs in this conversation too. Referred deals typically close faster and win more often than cold-sourced ones, while event pipeline tends to arrive slow and speculative. Once you track velocity by source, you can grow the channels that produce fast revenue instead of the channels that merely produce records.
Lever 2: Bigger Deals
The second lever raises what an average win is worth. Multi-threading is the most reliable route. When you sell to the whole buying committee instead of one champion, scope grows, because more stakeholders bring more problems worth solving.
Expansion motions work the same lever. Multi-year terms, adjacent products, and pricing discipline all push the average up. Discounting pushes it down, which sounds obvious. Yet reflexive end-of-quarter discounting is still the most common self-inflicted wound I see on this lever, and I will come back to it in the mistakes section.
Lever 3: Higher Win Rate
The third lever is winning a larger share of the deals you work. Nothing moves it faster than lead qualification. Disqualifying poor-fit deals early concentrates rep time on winnable ones, and the win rate climbs almost mechanically.
Beyond qualification, loss-reason analysis tells you where deals actually die: price, competitor, or no decision. Fix the biggest bucket first. Just remember the trade built into the formula. Raising the qualification bar shrinks opportunity count while it lifts win rate, and velocity only improves if the exchange nets out positive.
Lever 4: Shorter Sales Cycle
The fourth lever is the denominator, and it is the only one where smaller is better. Cycle time responds to process discipline more than to rep effort. A documented sales process with plain exit criteria removes the dead air between stages where deals age quietly.
The evidence here is old but solid. A Harvard Business Review analysis found an 18 percent difference in revenue growth between companies with a formal sales process and companies without one. Mutual close plans, faster legal and security review, and fewer internal handoffs do the rest. None of it is glamorous, and all of it shows up in the denominator.
When I map where cycle time actually hides, selling is rarely the culprit. Deals sit waiting for security questionnaires, procurement queues, and a champion who went quiet for two weeks. Run legal and security review in parallel with the commercial conversation instead of after it, and keep more than one stakeholder engaged so a single silent contact cannot stall the clock.
Which Lever Should You Pull First?
Pull the lever your own numbers say is weakest, not the one that feels easiest to campaign on. Diagnosis comes first, and the symptoms usually point clearly:
| Symptom in your numbers | Weak lever | First move |
|---|---|---|
| High win rate, thin pipeline | Opportunity count | Add sourcing capacity and widen ICP-fit lists |
| Deals close fast but stay small | Deal value | Multi-thread into more stakeholders, sell wider scope |
| Full pipeline, low win rate | Win rate | Tighten qualification, run loss-reason analysis |
| Good win rate, deals crawl for months | Cycle length | Define stage exit criteria, use mutual close plans |
| Everything looks vaguely average | Unknown | Segment velocity before touching anything |
A story about why diagnosis matters. In 2024 I watched a 20-rep team run a full quarter of deal-acceleration training because leadership felt deals were slow. Cycle length improved 12 days, and velocity barely moved 6 percent. Their real problem was deal size, stuck 40 percent below segment peers. When they finally ran a multi-threading program the next quarter, velocity jumped 21 percent.
The lesson is not that training fails. It is that pulling a healthy lever wastes a quarter you could have spent on the sick one. Let the four inputs tell you which is which.
How Should You Segment Sales Velocity?
Segment velocity by market segment, by rep, and by lead source, because one blended number is almost always a lie. Averaging segments that behave nothing alike produces a figure no decision can safely rest on.
Here is what the same company can look like once you split it apart:
| Segment | Opportunities | Avg deal value | Win rate | Cycle (days) | Velocity per day |
|---|---|---|---|---|---|
| SMB | 60 | $6,000 | 30% | 25 | $4,320 |
| Mid-market | 25 | $18,000 | 22% | 55 | $1,800 |
| Enterprise | 8 | $70,000 | 18% | 140 | $720 |
Each row is a different business with different physics. SMB runs on volume and speed, while enterprise runs on deal size and patience. Comparing them on one blended number punishes the enterprise team for existing.
Per-rep velocity works as a coaching tool, with one caution: small samples swing hard, so judge reps on trailing six months, not six weeks. Per-source velocity is the quiet gem. It shows which channel produces fast revenue and which produces pipeline that merely looks good in reports. Pipedrive’s guide makes a related point: choose the window, month, quarter, or year, based on the question you are asking.
One practical note on cutting the data: keep segments few and stable. Three segments with clean definitions beat nine that reshuffle every quarter. I usually split by company size first, because size drives deal value and cycle length harder than industry does. An industry or region cut can come later, once the first split has survived two quarters of scrutiny.
🔍 Field Note: A 14-rep SaaS team I audited in 2023 showed a healthy blended $2,100 a day. Split by segment, SMB velocity was up 30 percent while enterprise had quietly halved over two quarters. The blended average had hidden the decline completely. Reallocating pipeline generation took a month once the split made the problem visible.
How Do You Use Sales Velocity for Forecasting and Planning?
Use sales velocity to translate a revenue target into a pipeline requirement, and to sanity-check the forecast before anyone commits it. The math runs in both directions, which is what makes it a planning tool.
Start with the target. Suppose next quarter’s number is $250,000 over 90 days, which demands about $2,778 of revenue per day. Our example team currently produces $1,760 per day, so the plan is 37 percent short before the quarter even starts. Better to know that in week one than in week eleven.
Then run the formula backwards to size the fix. Holding deal value at $12,000, win rate at 22 percent, and the cycle at 60 days, hitting $2,778 per day requires about 63 open qualified opportunities instead of 40. Now the pipeline generation conversation has a number attached, and so does the trade-off if you would rather chase deal size or cycle time instead.
Two cautions from painful experience. Velocity-based forecasts are directional, not commit-grade, because the inputs are averages that individual quarters ignore freely. And always plan against segment-level velocity. Planning enterprise headcount with a blended number that SMB is propping up is how capacity plans miss by half.
What Are the Pitfalls of the Sales Velocity Formula?
The formula is only as honest as its inputs, and every input is easy to corrupt. Let me be blunt about the three failure modes I meet most often.
First, garbage stage data. Deals parked in a stage for months, close dates set to last quarter, and amounts nobody updated all poison the calculation. In 2024 I opened a pipeline where 31 percent of open deals carried close dates in the past. After cleanup, the recomputed velocity came in a third lower than the dashboard had been reporting. Leadership had been planning against a fiction.
Second, mixed populations. Blending SMB and enterprise into one number hides both, as the segment table showed. The same trap applies to time: pulling win rate from one quarter and cycle length from a different one quietly breaks the math.
Third, cycle-length definition traps. When does the clock start: at deal creation, or at qualification? Do you average won deals only, or every closed deal? Either choice is defensible, but switching between them makes trends meaningless. Richardson’s guide on defining and measuring sales velocity exists precisely because these definitions vary team to team. Small samples deserve a mention too. An enterprise pipeline with six deals a quarter will see velocity lurch on every single outcome, so use longer rolling windows there.
How Do You Instrument Sales Velocity in a CRM?
Instrument sales velocity with four reliable fields, one saved report, and a definitions document nobody edits casually. The setup takes an afternoon. Keeping it honest is the ongoing work.
- Timestamp the qualified stage. Record the date every deal enters qualification. That timestamp is the clock start for cycle length.
- Require amount and close date. Every open deal needs both fields, and stale close dates get audited monthly.
- Build one saved report per segment. Rolling 90-day window, all four inputs, with the formula written into the report title so nobody misreads it.
- Write the definitions down. Window, win rate denominator, and clock start live in one document, reviewed quarterly at most.
- Review it monthly. Velocity belongs in the pipeline meeting next to coverage, not in a dashboard nobody opens.
Highspot’s guide adds one instruction I fully endorse: decide upfront whether you measure monthly, quarterly, or annually, and stick with it. Consistency beats precision here.
Stage exit criteria deserve one extra sentence. Write them as observable facts, such as a signed evaluation plan or a named budget holder, never as feelings. Cycle length only means something when a stage change records something that actually happened in the deal.
Segmentation adds a data-quality dependency people underestimate. Splitting velocity by segment only works when firmographic fields like industry and company size are current, and those fields rot as companies grow and pivot. Enrichment tools such as CUFinder can keep them refreshed automatically, which is what makes segment-level velocity trustworthy. That said, no enrichment tool fixes stage definitions a team refuses to follow.
📌 Checkpoint: Once a month, count open deals whose close dates sit in the past. Above 10 percent, stop trusting the velocity number and fix hygiene first. The metric recovers exactly as fast as the fields underneath it.
What Are the Most Common Sales Velocity Mistakes?
The most common mistake is improving one lever by quietly breaking another. Because the formula multiplies the inputs together, a win on one slot can still be a net loss.
Discounting is the classic case. In 2022 I worked with a team that pushed aggressive end-of-quarter discounts to close deals faster. It worked, in a narrow sense: cycle length dropped 19 percent. Average deal value dropped 26 percent in the same window, and velocity fell 9 percent overall. The dashboard celebrated the faster cycle while revenue per day quietly declined.
Pipeline stuffing is the same error on a different lever. Flooding the top with weak deals lifts opportunity count while win rate sinks and cycles stretch. Over-qualification inverts it: a 60 percent win rate on a starved pipeline is a smaller business, not a better one.
One more, and it is subtle: paying reps on velocity directly. The inputs are self-reported stage data, so comping on the output invites sandbagging and stage gaming. Use velocity to diagnose and coach. Keep compensation tied to closed revenue, which nobody can massage.
🧠 Worth Remembering: Judge every sales initiative by its net effect on velocity, not by the lever it was named after. A program that shortens cycles while shrinking deals has a sign problem, not a speed problem.
Frequently Asked Questions
What is a good sales velocity number?
There is no universal benchmark, because deal size and cycle length vary wildly across markets. A good number is one that rises quarter over quarter within the same segment and the same window. Compare against your own trailing quarters first, and compare reps only within the same segment.
What is another name for sales velocity?
Pipeline velocity is the most common synonym, and some teams say revenue velocity. All three names describe the same formula: opportunities times average deal value times win rate, divided by sales cycle length. The output is revenue per day in every case.
What is the sales velocity rate?
Sales velocity is not a rate in the percentage sense. The output is currency per day, such as $1,760 per day. When people say velocity rate, they usually mean that daily figure, or they are mixing it up with win rate, which is the percentage input inside the formula.
What is sales velocity in B2B?
In B2B, sales velocity measures how much revenue per day a pipeline of company deals produces. Long cycles and committee buying make the metric especially useful there, because slow, expensive pipelines hide problems well. B2B teams should always compute it per segment over a rolling window rather than as one blended number.
What is sales velocity on Amazon?
In e-commerce, sales velocity means units sold per day or week for a specific listing. Amazon sellers track it for inventory planning and ranking, and Amazon monitors it on seller accounts. It shares a name with the B2B pipeline metric but uses a completely different calculation.
Is sales velocity the same as sales volume?
No. Sales volume counts how much you sold, in units or currency, over a period. Velocity, by contrast, measures how fast your pipeline converts into revenue, expressed per day. Volume tells you what happened, while velocity tells you how efficiently the machine that produced it is running.
How often should you measure sales velocity?
Monthly, computed over a rolling 90-day window, works for most teams. Weekly readings on small pipelines are mostly noise, because a single deal swings every input. Enterprise teams with few, large deals often stretch the window to 180 days to keep the trend readable.
So that is sales velocity in full: one formula, four levers, and a number measured in money per day. Keep the definitions fixed, segment before you compare, and pull the lever your own data points at. The teams that treat it as a diagnostic habit, not a dashboard trophy, are the ones whose revenue per day actually moves.
Bad
Okay
Good
Amazing
