You closed $400K last quarter. Your pipeline looks healthy. Your CRM shows 80 open deals. And yet your VP of Sales is asking why you missed your number by $120K and nobody has a straight answer.
If you've been in that room, this post is for you.
Sales velocity is the metric that should have predicted that outcome six weeks earlier. Most B2B teams either don't track it or track it wrong. Here's what the formula actually tells you, where companies go wrong, and how to make it work inside HubSpot.
What the sales velocity formula actually measures
Sales velocity measures how fast your pipeline converts to revenue. The output is a dollar amount per day.
The formula:
Sales Velocity = (Number of opportunities × Average deal value × Win rate) / Sales cycle length in days
Or written short: SV = (N × V × W) / L
If you have 50 qualified opportunities, an average deal value of $20,000, a 25% win rate, and your average deal closes in 80 days:
(50 × 20,000 × 0.25) / 80 = $3,125 per day
Your pipeline generates $3,125 of closed revenue every day. Annualized, that's roughly $1.14M. Want to hit $2M? Your velocity needs to double.
That's the cleanest use of this formula: connecting current pipeline activity to future revenue outcomes without guessing. It answers the question your board asks every quarter before you have a chance to build a real answer.
Sources for those three, because a velocity page that quotes unattributed numbers has no business lecturing anyone about measurement. The quota figure and the cycle growth figure both come from the Ebsta and Pavilion B2B Sales Benchmarks, drawn from connected CRM data across hundreds of companies, which also notes that quota targets themselves fell about 19% year on year, so the miss rate would have been worse on flat quotas. The weekly-review figure comes from First Page Sage's 2026 pipeline velocity report, based on 247 North American B2B organisations analysed in 2025. That last one is a correlation in a vendor's dataset, not a controlled result, so read it as evidence that the teams reviewing velocity weekly are the teams growing, rather than proof that the review causes the growth. The L variable in particular deserves its own reading, and we have walked the published cycle length datasets against each other in the piece on B2B sales cycle length.
Why most teams get it wrong
The formula is simple. The inputs are not.
Mistake 1: counting the wrong opportunities
N in the formula needs to be qualified opportunities only. If your reps include prospects from first outreach, or deals that haven't had a discovery call, you're inflating N with noise.
The fix is a clear stage definition. In HubSpot, this means setting required fields at your "Qualified" stage transition. Until a rep fills in your qualification criteria, the deal doesn't count toward velocity.
Mistake 2: measuring cycle start from lead creation
This corrupts your L variable more than almost anything else. If you count cycle length from the moment a lead enters your CRM, you're mixing marketing time with sales time. A lead that sat in nurture for 60 days before getting a first meeting will make your cycle look much longer than it is.
Sales cycle length for velocity purposes starts at qualification, not lead creation. In HubSpot, you can use a workflow to stamp a custom "Qualified date" property when a deal enters your qualification stage, then use that as your cycle start.
Mistake 3: using one blended win rate
A blended win rate averages two motions that do not behave alike. Win rate falls as deal size rises, reliably enough that it has published shape: Optifai's benchmark, from anonymised CRM data across 939 B2B companies, puts deals under $10K ACV at a 28 to 35% win rate, $10K to $50K at 20 to 28%, $50K to $100K at 15 to 22%, and anything above $100K at 12 to 18%. Those are 25th to 75th percentile bands from one vendor's customer base rather than an industry constant, so use the gradient rather than the specific numbers. The gradient is the point. A single blended figure sits somewhere in the middle of that spread and describes neither end.
It matters because the two ends can produce similar velocity by opposite routes, higher conversion against higher deal value, and Optifai's own reading of the same dataset is that enterprise reaches comparable revenue on a fraction of the opportunity count. A blended number cannot tell you which route you are on, so it cannot tell you where an extra rep or an extra dollar of pipeline spend should go. That is not a small reporting flaw. It is the whole question you built the metric to answer.
Mistake 4: treating velocity as one company-wide number
One velocity number for your whole company is about as useful as one average temperature for the whole country. SMB and enterprise behave differently. Inbound and outbound have different cycle lengths. Geographic markets can have different deal sizes.
Run velocity calculations separately for each meaningful segment. The point of the metric is to show you where your pipeline is generating revenue efficiently and where it isn't.
Improving win rate by 5 points beats adding 20% more pipeline.
Win rate multiplies across every deal in your pipeline. From a 20% base, a 5-point win rate gain on 50 deals has the same velocity impact as adding 12 or 13 new qualified opportunities with no improvement in conversion. That is arithmetic, not a benchmark: W sits in the numerator alongside N, so a proportional gain in either moves velocity by the same amount, and the size of the swap depends on the base rate you start from. The difference is that the win rate gain costs no extra pipeline to acquire. We have no defensible public number for how growth budgets actually split between the two, so this page does not publish one. Look at your own split instead. In most of the plans we are shown, the volume side has an owner, a budget line and a weekly number, and the win rate side has none of the three.
The problem nobody writes about: CRM data quality
Here's the thing about the formula that gets ignored in most articles on this topic.
All four variables come from your CRM. If your reps aren't updating deal stages consistently, if close dates slide without anyone cleaning them up, if deals die but stay open because closing them feels uncomfortable, your velocity calculation is built on bad data.
This is the part we see first on every CRM audit we run. In the pipelines we have opened, a substantial minority of open records carry a problem that touches at least one velocity variable: a stage that no longer reflects reality, a close date nobody reset, a deal that died months ago and was never closed. That is our own observation across engagements rather than a measured benchmark, and we are not going to dress it up as one, because no published dataset we could find measures it. The formula still runs on records like these. The number still looks real. It is measuring a fiction.
Before you can trust your velocity number, you need:
- Stage definitions that are clear and enforced (required fields at key transitions in HubSpot)
- A deal hygiene rule: any deal with no activity in 30 days gets flagged automatically
- A clean close date policy: close dates must be within 90 days for deals to count as active pipeline
This sounds like admin work. It is. But without it, your sales velocity calculation is just math performed on guesses.
How to use velocity for headcount planning
Most articles stop at "track this metric and try to improve it." The more valuable use is capacity planning.
If you know your average per-rep sales velocity, you can work backwards from a revenue target to calculate how many ramped reps you need.
The math:
- Revenue target: $3M per year = $8,219 per day
- Average rep velocity: $1,500 per day (fully ramped)
- Reps needed: 8,219 / 1,500 = approximately 5.5 ramped reps
If you're at 4 ramped reps today and a new hire takes 4 months to ramp, you already have a capacity gap for the next two quarters. You know this now, not after the miss.
This is one of the most direct ways RevOps can shape headcount conversations. Instead of "we need more reps," you can say "at our current per-rep velocity, hitting $3M requires 5.5 ramped reps, and we're at 4."
The hidden velocity killer: legal and contracts
There's a velocity lever that RevOps owns but most content on this topic ignores.
Contract cycles. Specifically, the time between verbal agreement and signed contract.
World Commerce and Contracting, the trade body that benchmarks commercial contracting, puts the cycle time for a moderately complex B2B contract at around three to four weeks, and the cost of poor contracting at roughly 9% of annual revenue on average, with the best performers nearer 3% and the worst at 15% or more. Read those two together and the point lands: the contract phase is weeks long by default, it varies enormously by how well it is run, and every one of those days sits in your L variable. It shows up as "legal review" in your CRM stage and drags velocity without saying anything at all about how well your reps are selling.
Fixing this is a RevOps problem. A deal desk workflow, standardised contract templates, and a contract lifecycle management tool are the standard levers, and the mechanism is not subtle: a review that runs in parallel with commercial negotiation finishes sooner than one that starts after it.
What we will not do is put a percentage on the fix. Nearly every deal desk page on the web quotes the same trio, 25 to 40% shorter cycles, 15 to 20% better productivity, 5 to 10% higher profitability, attributed to PwC. We went looking for the study behind it and could not find one: the figures recirculate across vendor blogs, and the most specific sourcing any of them offers is a consultancy describing its own client experience. The direction is plausible. The measurement is not published. Build the business case on the size of the leak, which is measured, rather than on the size of the fix, which is not.
If you're looking for velocity gains that don't require hiring more SDRs, your contract process is the first place to look.
How to build this in HubSpot
HubSpot's Sales Hub doesn't calculate the full velocity formula natively as a single dashboard number. Here's the practical path to build it.
If you're on HubSpot Sales Hub Enterprise and want this as a native dashboard number, you'll need a third-party reporting layer. Tools like Revlitix can pull the four variables and compute velocity automatically, with segmentation built in.
What a velocity improvement actually looks like
Almost every velocity gain we have seen starts the same way, and it is not a new tactic. It is a segment that was hiding inside an average.
Here is the shape, as a worked illustration rather than a case study. The numbers below are invented to make the arithmetic visible, not measured from any engagement.
Take a company whose blended velocity reads about $2,100 a day. Nothing looks wrong. Split it by channel and inbound is running at $3,800 a day while outbound is running at $600. Same reps, same product, same price list. The difference sits in two of the four variables: outbound deals convert at a lower rate and take longer, because the accounts being worked do not match the profile of the accounts that actually buy.
Notice what the blended number did. It did not say outbound was broken. It said the company was fine. A team reading only the blended figure would spend the next year adding outbound volume on top of a targeting problem, which raises N, leaves W and L where they are, and produces a bigger version of the same result.
The fix that follows from this is a targeting fix, not a headcount fix: rebuild the outbound account list from the profile of the highest-velocity inbound deals, then re-measure the two channels separately. We cannot show you a client's before and after here, because the engagements that produced ours are not cleared for publication, and a number we cannot attribute is worth no more than a number we invented.
What we can show you is the method, which is the part that transfers anyway. On a velocity review we ask for four things before we ask anything else: which stage transition starts the clock, whether the pipeline is split by channel and by segment, how many open deals have had no activity in 30 days, and what share of closed-lost was never worked at all. Those four separate a velocity number you can act on from one that only looks like a measurement.
This is also the connection between sales velocity and go-to-market strategy: ICP precision directly affects win rate and cycle length, which are two of the four velocity levers. A tighter ICP isn't just good marketing hygiene. It's a measurable velocity driver.
Your velocity number might be hiding a problem.
We audit CRM data, segment pipeline by ICP and channel, and build the reporting that shows where revenue is being lost. Book a free 30-minute call.
Book an audit →FAQ
What is a good sales velocity number?
There is no universal benchmark, and the published ones disagree by an order of magnitude, which is itself the answer. First Page Sage's 2026 pipeline velocity report puts median velocity between about $743 a day in Marketing and Advertising and $2,456 a day in Real Estate and Construction, across 247 North American B2B organisations. Optifai, working from anonymised CRM data across 939 B2B companies, reports a B2B SaaS average nearer $8,219 a day, with SMB around $4,500 to $7,000, mid-market $12,000 to $18,000 and enterprise $25,000 to $50,000. Both are vendor datasets rather than random samples, and the gap between them comes from different populations and different definitions of what counts as an open opportunity. Which is why the useful comparison is your own velocity over time, or velocity by segment within your own pipeline. A number improving quarter over quarter tells you more than a number that is "good" against someone else's sample.
How often should we track sales velocity?
Weekly is the standard for high-performing revenue teams. First Page Sage's 2026 report found organisations reviewing velocity weekly growing revenue 34% a year against 11% for those tracking it irregularly, across 247 B2B organisations analysed in 2025. Treat that as a correlation in one vendor's dataset, not a causal result: the teams that review velocity weekly tend to be the teams that run everything else tightly too. The mechanical argument for weekly stands on its own anyway. A weekly cadence gives you six to eight weeks of lead time before a quarterly miss becomes visible in closed revenue, and that window is the difference between course-correcting and explaining what went wrong after the fact.
Can sales velocity be gamed?
Yes. The metric can be manipulated by removing stalled deals from the pipeline (which shortens average cycle length artificially), adding unqualified leads to inflate opportunity count, or sandbagging close dates. This is why CRM governance matters as much as the formula itself. If stage transitions aren't enforced with required fields, your inputs are whatever your reps choose to report. Build the governance first. Trust the number second.
Should I use sales velocity for individual rep performance reviews?
With caution. Velocity is a pipeline metric, not a pure rep performance metric, because several of its drivers are outside a rep's control. Contract delays, legal review, CRM data quality, and ICP targeting all affect velocity but aren't necessarily the rep's fault. Use it at the team or segment level for planning. For individual coaching, look at specific components: win rate and stage-to-stage conversion rates are more directly tied to rep behavior.
How does sales velocity connect to sales forecasting?
Sales velocity is one of the most direct inputs to bottom-up forecasting. If you know your velocity per segment, you can project expected closed revenue over any time period. A simple version: velocity × remaining days in the quarter = expected additional revenue. Compare this to your quota gap and you have a data-based forecast rather than a manager's gut estimate. This is the basis for most modern CRM forecasting tools, including HubSpot's forecast module and tools like Clari and Fullcast.