TL;DR
- Sales velocity = (Qualified Opportunities × Win Rate × Average Deal Value) ÷ Sales Cycle Length (days) — a speed-of-revenue metric, not a growth metric.
- HubSpot has no native "Sales Velocity" report. Its "Deal Velocity" report only measures average time per pipeline stage — it isn't the same number and can't be dropped into the formula.
- Published $/day benchmarks disagree by more than 10x across sources with no consistent methodology — treat any single "average sales velocity" figure you find online with real skepticism.
- The biggest calculation error is counting every pipeline deal as a "qualified opportunity" — HubSpot's deal creation and lifecycle-stage mechanics make this easy to get wrong.
- Each of the four variables maps to a specific outbound or RevOps lever — lead routing speed, ICP tightening, deal-stage discipline, and no-show reduction all move this number.
Search "sales velocity formula" and you'll land on a CRM vendor's calculator widget, a recycled definition, and a benchmark number that doesn't match the benchmark number on the next site you open. Where a claim below is single-sourced, vendor-reported, or unverifiable against a primary source, it's flagged as directional rather than stated as settled fact.
The Short Answer
Sales velocity measures how fast qualified pipeline turns into closed revenue:
Sales Velocity = (Qualified Opportunities × Win Rate × Average Deal Value) ÷ Sales Cycle Length (days)
The output is a dollars-per-day number: how much revenue your pipeline is generating, on average, for every day it's in motion. It's not a growth metric on its own — a team can post a high velocity number while closing low-margin deals that don't help the business — but it's a useful diagnostic for finding where a slowdown is coming from, because it forces you to separate four things that usually get lumped together as "pipeline is slow."
Where This Formula Actually Comes From
Most posts on this topic open with a confident origin story — usually tracing it to operations research or naming a specific book. We couldn't verify a single documented inventor. The formula is consistent across every current source, including HubSpot's own explanation, but the "who first wrote this down" claim doesn't hold up under a source check (directional). The honest framing: it's an industry-standard heuristic that spread through SaaS and RevOps circles over the past decade, not a discovered law with a named author.
What It Isn't: HubSpot's "Deal Velocity" Report
Trap: HubSpot's Sales Analytics tools (Sales Hub Professional/Enterprise) include a report literally called "Deal Velocity." It measures the average time a deal spends in each pipeline stage — a stage-duration diagnostic. It is not the four-variable revenue-per-day formula above, and it can't be substituted for it. If a report or dashboard in your portal is labeled "velocity," check what it's actually measuring before you quote a number from it.
Sales velocity, as covered in this post, has no out-of-the-box HubSpot report. You have to build it.
How to Calculate It in HubSpot
All four inputs live in your deal data, but none of them arrive pre-qualified for the formula. Build it in the Custom Report Builder:
| Variable | HubSpot source | Watch out for |
|---|---|---|
| Qualified opportunities | Deal count filtered to a genuinely qualified stage (not raw deal count or lifecycle stage) | A deal can be created — and get an "Opportunity" lifecycle stage applied to its associated contact — the moment it's added, before anyone has actually qualified it (directional — HubSpot Community discussion describes this behavior; HubSpot's own docs don't spell it out explicitly) |
| Win rate | Closed Won ÷ (Closed Won + Closed Lost) over the period | Decide once whether disqualified/unqualified deals count as losses, and apply it consistently |
| Average deal value | Deal amount property, averaged over Closed Won deals in the period |
One enterprise deal can skew an average badly — consider reporting median alongside it |
| Sales cycle length | Custom formula field: DATE_DIFF([Close Date], [Create Date], "days") |
Calendar days vs. business days changes the denominator — pick one and label it in the report |
Once those four numbers exist as report outputs, the formula is a single calculation on top of them — but there's no button that produces the finished figure automatically.
Why the Benchmarks You'll Find Online Don't Agree
Search around for "average sales velocity" and you'll find numbers ranging from roughly $580/day to nearly $13,000/day, depending which site you land on (directional — every one of these figures traces to a different, mostly undisclosed methodology):
| Claimed figure | Basis | Why it's shaky |
|---|---|---|
| $687–$12,945/day across 5 tiers | A private research firm's blended client/database/third-party data | Opaque blended methodology; the tier progression is unusually smooth for real-world data |
| $8,219/day average | Cited "across 939 B2B companies," no named source | Could not be traced to a primary study |
| $583/day average | Vaguely attributed to a blend of older third-party reports | Multiple secondary sources merged into one figure with no direct quote traceable |
The one benchmark in this space that does hold up: a 2025 GTM benchmarks report from Ebsta and Pavilion, built on 655,000 opportunities and roughly $48B in analyzed pipeline, put average B2B win rate at 19%, down from 29% the year before. That's a real sample size with a named, checkable source — worth using as a directional reference point for win rate specifically, though it says nothing about the other three variables or about your own business (directional — treat as one data point, not a target).
The practical takeaway: don't benchmark your sales velocity against an internet number — benchmark it against your own trend. A velocity that's climbing quarter over quarter tells you something real about your pipeline; a velocity that matches or misses a stranger's average tells you nothing, because you don't know what went into their number.
Common Mistakes When Calculating Sales Velocity
- Counting every open deal as an "opportunity." This is the single biggest source of inflated, misleading velocity numbers — see the HubSpot trap above.
- Confusing HubSpot's native Deal Velocity report with the full formula. One measures stage duration; the other measures revenue per day.
- Mixing calendar days and business days for cycle length without picking one and being consistent.
- Using average instead of median deal value when a handful of large deals skew the distribution.
- Inconsistent treatment of closed-lost deals in the cycle-length calculation — some teams include them, some don't, and the two approaches aren't comparable.
- Treating a high velocity number as automatically good. Velocity measures speed, not margin — a team can post an impressive number by closing fast, low-value, low-fit deals that hurt retention later.
How to Improve Each Variable
Because the formula separates pipeline into four parts, "improve sales velocity" isn't one initiative — it's four different diagnoses with four different fixes:
| Variable | Lever | Where it shows up |
|---|---|---|
| Qualified opportunities | Tighter ICP targeting in outbound so fewer poor-fit deals enter the pipeline at all | Cold email / LinkedIn list-building and targeting |
| Qualified opportunities | Faster lead routing so interested replies reach a rep before they cool off | HubSpot workflow automation |
| Win rate | Explicit exit criteria per deal stage, so "advanced" deals are actually qualified | HubSpot pipeline design |
| Win rate | Faster first response to inbound replies and booked meetings | Outbound SDR process |
| Average deal value | Shifting outbound targeting upmarket or adding attach/expansion motions | RevOps + outbound targeting |
| Sales cycle length | Automated, templatized follow-up cadences instead of ad hoc rep follow-up | RevOps sequencing |
| Sales cycle length | Confirmation cadences that cut down rebooked meetings after no-shows | Outbound appointment-setting / RevOps |
A note on the "speed to lead" statistics that circulate around this topic: the widely repeated claim that responding within 5 minutes makes a lead 21x more likely to qualify is usually attributed to "an MIT study." That attribution doesn't check out — the research behind these speed-to-lead numbers traces to a Kellogg School-affiliated study published via Harvard Business Review, not MIT (directional — the underlying finding that fast response improves qualification odds is well-supported directionally; the specific "21x" multiplier and "MIT" label are not). Use the general point, not the specific number — see our breakdown of lead routing and speed-to-lead for the mechanics of fixing this in HubSpot.
Two of the other levers in the table above get their own deeper treatment elsewhere on this blog: tightening the top of the funnel starts with a documented ICP definition, and a large share of "cycle length" problems trace back to meetings that don't show up in the first place.
A pattern worth naming: several numbers that circulate in sales-velocity content — a "Forrester" benchmark tying a specific stat to meetings without a written next step, and a "study of 847 companies" behind win-rate-by-deal-size bands — could not be traced to any verifiable primary source during research for this post. Treat any sales stat with a suspiciously precise number and a vague or unfamiliar attribution with real skepticism before repeating it.
Frequently Asked Questions
What is a good sales velocity?
There's no universal benchmark. Published figures for "average sales velocity" range from under $700/day to over $12,000/day depending on company size and methodology, and none of the widely cited numbers share a consistent, disclosed methodology. Cross-company comparisons aren't meaningful — track your own velocity trend over time instead.
How do you calculate sales velocity in HubSpot?
HubSpot doesn't have a native "sales velocity" report. Build it in the Custom Report Builder using the deal amount property, a custom DATE_DIFF formula field between create date and close date, and a filtered count of deals that reached a genuinely qualified stage — then apply the formula manually. HubSpot's native "Deal Velocity" report only measures average time per pipeline stage, which is a different metric.
Sales velocity vs. sales cycle length — what's the difference?
Sales cycle length is one input to the formula — the denominator. Sales velocity is the full output, combining opportunity count, win rate, and deal value against that cycle length. A shorter cycle alone doesn't mean higher velocity if opportunity quality or win rate drops at the same time.
How do you increase sales velocity?
Improve any of the four inputs: bring in more qualified (not just more) opportunities through tighter ICP targeting and faster lead routing, raise win rate through deal-stage discipline and faster response times, increase average deal value through upmarket targeting, or shorten cycle length through faster follow-up and fewer no-shows.
What counts as a "qualified" opportunity in the formula?
A deal that has passed real qualification criteria — budget, authority, need, and timeline, or your team's equivalent framework — not merely a deal record that exists in the pipeline. In HubSpot specifically, don't rely on raw deal count or lifecycle stage alone, since a deal can be marked as an opportunity simply by being created, before anyone has actually qualified it.
What's a common mistake when calculating sales velocity?
Counting unqualified deals as opportunities, mixing calendar days and business days for cycle length within the same report, and using average rather than median deal value when a small number of large deals skew the number.
If your sales velocity has stalled, the fix is almost never "sell harder" — it's finding which of the four variables actually moved. See how deal-stage discipline factors in in our guide to HubSpot deal stages for outbound teams, check your inputs against our RevOps dashboard metrics guide, or talk to our team about auditing your pipeline.
By the GenFlows GTM engineering team. We build and run outbound and RevOps systems for B2B companies — cold email, LinkedIn outreach, and HubSpot pipeline design. Last updated August 2026.
The GenFlows team builds AI-powered cold outbound systems for B2B teams.