Sales velocity calculator

By Giorgio Bonan. Updated October 21, 2026, published October 21, 2026.

Sales velocity is the revenue your pipeline produces per day: qualified opportunities times average deal size times win rate, divided by the sales cycle in days. Enter your four numbers below for one segment and one period.

The formula

Sales velocity = (opportunities x average deal size x win rate) / sales cycle length in days

Worked example

The calculator's default: 60 opportunities, $24,000 average deal, 22% win rate, 84-day cycle.

60 x $24,000 x 0.22 / 84 = $3,771 per day, or about $113,000 per 30 days.

Which lever moves velocity most

Same base case, each input improved by 10% on its own:

The three numerator inputs are interchangeable: a 10% gain on any of them gives 10%. Shortening the cycle gives slightly more, because it divides. In practice, the cheapest lever is often the cycle: deals that sit for weeks without activity stretch the average cycle, then usually close lost.

Compute each input in Salesforce

Use the same period for the last three inputs, and the same segment for all four. Two quarters is a reasonable window: long enough to smooth one large deal, short enough to reflect the current team.

Velocity by segment

Averages across very different deals hide where revenue comes from. The same team, split by segment:

Adding the segments gives $4,757 per day. A single calculation on blended averages would not give the same result, because averages of deal size, win rate and cycle do not multiply the way the real segments do. SMB carries more than half of the daily revenue here, while enterprise deals dominate the pipeline value. Compute velocity per segment, then add.

Velocity per rep

Divide the opportunities by rep, keep the team's deal size, win rate and cycle, or measure each rep's own. Per-rep velocity is useful to spot a rep whose pipeline is full but whose cycle is twice the team's: often a sign of deals that stopped moving and were never closed.

Which number to watch weekly

Common mistakes

• Counting unqualified opportunities. They inflate the first input and lower the win rate; the product looks fine, the forecast does not.
• Mixing segments. Enterprise and SMB deals have different sizes and cycles. Compute velocity per segment, then add.
• Using open-deal age as the cycle. The cycle is measured on won deals. Open deals that never close are a coverage problem, see the pipeline coverage calculator.

What cleaning the pipeline does to velocity

A useful test: take the default case and remove 10 opportunities that have had no activity for months and will not close.

Velocity does not change, because the dead deals were never going to produce revenue: the expected wins are the same. What changes is everything around it. The win rate becomes honest, pipeline coverage falls to its real level, and the forecast stops counting deals that cannot close. Velocity is a flow measure; it is robust to dead deals. Coverage and the forecast are not.

Tracking velocity month by month

Read the change with its cause: in August, more opportunities, a slightly higher win rate and a shorter cycle all helped; in September, nothing moved. A table like this, per segment, is enough to see which lever moved before anyone debates the total.

Small gains on every lever compound

Improving all four inputs a little beats improving one a lot. From the default case, a 5% gain on each:

Velocity would go from $3,771 to about $4,596 per day. A 5% gain on four inputs is easier to obtain than a 22% gain on one, and it is more robust: no single initiative carries the whole result.

One rep, worked

9 x $22,000 x 0.25 / 95 = $521 per day, about $15,600 per 30 days. With a monthly quota of $20,000, this rep's velocity covers about 78% of it. The gap points to the levers: more qualified opportunities, or a shorter cycle. A cycle 11 days longer than the team's 84 often means deals carried for weeks without activity before they close.

Work backwards from a target

The formula can be turned around to answer the planning question: how many qualified opportunities do we need?

Opportunities needed = target revenue per day x cycle / (deal size x win rate)

Each line is the number of qualified opportunities that must be open in the flow. Compare it with what you have today: if the answer is 212 and the team carries 60, the plan needs pipeline generation, a shorter cycle, a higher win rate, or a lower target. Usually some of each.

Velocity in HubSpot

The same four inputs come from HubSpot deal reports: count of open deals in qualified stages, average amount of closed-won deals, closed-won divided by closed-won plus closed-lost, and average days to close for won deals. The formula does not change with the CRM; only the report names do.

Why we do not publish a benchmark

Velocity depends on deal size, market and segment, so a "good" figure for one company means nothing for another. A $500 per day velocity can be excellent for an SMB product sold by two reps and worrying for an enterprise team of twenty. Compare your velocity with itself, period over period, for the same segment.

How to raise velocity, lever by lever

• Opportunities. More qualified opportunities, not more opportunities. An unqualified deal adds to the first input and lowers the win rate, so the product barely moves while the pipeline looks bigger.
• Deal size. Packaging, multi-year terms, or targeting larger accounts. Watch the cycle: larger deals usually take longer.
• Win rate. Better qualification upfront, multi-threading inside the account, and earlier exits from deals that will not close. Measure it with the win rate calculator.
• Cycle. Mutual close plans, faster legal and security reviews, and closing out deals that went silent instead of carrying them for months. Every deal carried without activity lengthens the measured cycle once it finally closes.

Using velocity in the forecast call

Velocity is a cross-check, not the forecast. Two ways to use it in the weekly or monthly call:

• Sanity check of the quarter. Velocity per day times the days left in the quarter gives the revenue the current flow should produce. If the committed number is far above it, either deals will close faster than usual, or the commit is optimistic. Ask which deals justify the difference.
• Per-rep conversation. A rep whose velocity dropped since last month has one of four causes: fewer opportunities, smaller deals, lower win rate or a longer cycle. The table above shows which one in a minute, and the conversation starts from that input rather than from the total.

Velocity in one sentence

If you remember one thing: velocity grows when more good deals enter, when they are bigger, when more of them are won, and when they are won sooner, and it is the last one that dead deals quietly damage.

Choosing the period

Use a window long enough to contain several won deals per segment, usually two quarters for the last three inputs, and the current count for open opportunities. Shorter windows make velocity jump with every large deal; longer ones hide changes in the team. Keep the window fixed once chosen, and note it next to the number.

Velocity, coverage and win rate: how they fit

The three metrics answer different questions and use overlapping inputs:

A team can have good coverage and poor velocity (a lot of pipeline that moves slowly), or good velocity and poor coverage (fast deals, but not enough of them). Reading the three together tells you which lever to pull. The pipeline coverage calculator gives the second number.

Dashboard mistakes to avoid

1. Showing velocity without its four inputs: nobody can act on the total.
2. Mixing open-deal age and won-deal cycle in the same chart.
3. Recomputing the inputs over different windows each month.
4. Comparing velocity across segments with very different deal sizes.

Velocity and the forecast

Velocity describes the flow; the forecast commits to a number. If velocity drops while the forecast stays flat, one of them is wrong. Track how often your committed number lands with the forecast accuracy formula.