Sales Velocity

Sales velocity is the amount of revenue your pipeline produces per day, calculated as the number of qualified opportunities × average deal value × win rate ÷ sales cycle length in days. Forty open deals worth €25,000 on average, a 30% win rate and a 90-day cycle give you €3,333 a day.

The number is useful because it catches what a revenue total hides. Two reps can each close €180,000 in a quarter, one from 24 deals that took 130 days on average and the other from 12 deals that took 65. The scoreboard calls them equal. Velocity shows that the second rep turns pipeline into money about twice as fast, and its four inputs tell you why.

Where it goes wrong is almost always in those inputs. A team pulls the opportunity count from one report, the win rate from another and the cycle length from a third, each with its own date range, and then treats the result as precise to the euro. You'll also see the metric called pipeline velocity. The arithmetic is the same, and this entry is mostly about feeding it clean inputs and reading what comes out.

TL;DR

• The formula is opportunities × average deal value × win rate ÷ cycle length. With 40 opportunities, €25,000, 0.30 and 90 days, that's €300,000 ÷ 90, or €3,333.33 a day. Enter the win rate as a decimal.

• Give every input one fixed definition and the same time window: open qualified opportunities, the average amount on won deals, won ÷ (won + lost) with no-decision deals counted as lost, and created-to-close days on won deals.

• Raising any of the three top inputs by a fifth lifts velocity by a fifth, and so does cutting a 90-day cycle to 75 days. Improve all four by 10% and velocity rises by about 48%.

• Bigger deals can slow the whole machine down. Ten deals at €60,000 with a 150-day cycle and a 20% win rate produce €800 a day, less than the same ten at €25,000, 90 days and 30%.

• When velocity drops, find the input that moved before you act. Volume points to pipeline generation, win rate to qualification and coaching, deal value to packaging and targeting, and cycle length to process.

• Split it by rep and by segment to see who and what turns pipeline into revenue fastest, and pool two quarters of deals before you judge a single rep.

• No outside benchmark is worth chasing. Calculate it on a rolling window, look at it every week, and compare it with your own previous quarters.

The sales velocity formula, run with real numbers

Sales velocity = opportunities × average deal value × win rate ÷ sales cycle length (in days)

That's the version both Salesforce and HubSpot publish. Every input is an average over a period, and the output is a rate, which is why it reads as euros per day rather than as a total.

Take a mid-market software team with these numbers:

• 40 qualified opportunities open in the pipeline

• €25,000 average value of the deals it wins

• a 30% win rate, entered as 0.30

• a 90-day average sales cycle

Run it one step at a time. 40 × €25,000 = €1,000,000, the open pipeline at average deal size. Multiply by 0.30 and you get €300,000, the part of it you expect to win. Divide by 90 and the team produces €3,333.33 a day.

The €300,000 in the middle is the step worth remembering. It's roughly what those 40 deals should be worth once all of them have been decided, and the 90-day cycle says that will take about a quarter. Velocity spreads that amount over the days, so €3,333.33 × 90 brings you back to €300,000 for the quarter.

The logic behind dividing open deals by cycle length is plain once you see it. If 40 deals are open and each one takes about 90 days, around 40 of them get decided every 90 days, which is a little under half a deal a day. You win 30% of those at €25,000 each, and that's your daily revenue.

Two practical warnings. Type 30 instead of 0.30 into a spreadsheet and you get €333,333 a day, a hundred times too high and surprisingly easy to miss in a dashboard nobody checks. And the formula assumes the pipeline is fairly steady. After a big push of new opportunities it runs ahead of the cash for a while, because those deals haven't had time to close yet.

Getting the four inputs out of your CRM

Each input hides a definition, and most velocity figures we audit are wrong because two of the four were pulled with different rules. Settle these once and write them down next to the report.

The opportunity count depends on where a deal is allowed to start. If you only create opportunities once a deal passes your lead qualification criteria, the count means something, and it matches the denominator of your win rate.

For the win rate itself, use the definition from our win rate entry so the two numbers agree wherever they appear. Counting stalled deals as losses lowers the rate, but it stops velocity from looking healthy while half the pipeline sits untouched. Regular CRM hygiene that closes out abandoned deals matters more here than any formula tweak.

Cycle length is the easiest input to get in HubSpot, where the default Days to close property records the time between a deal's create date and close date. Salesforce holds the same two dates on every opportunity, so a formula field gives you the same thing.

Then pick one window for all four. HubSpot's guidance is to measure across at least a quarter and up to a year, and we'd tie it to your cycle: a window at least as long as one average sales cycle, so the deals you're averaging have had time to finish.

Which lever moves sales velocity most?

Go back to the team producing €3,333.33 a day and improve one input at a time:

• 48 opportunities instead of 40: 48 × €25,000 × 0.30 ÷ 90 = €4,000 a day

• a €30,000 average deal: 40 × €30,000 × 0.30 ÷ 90 = €4,000 a day

• a 36% win rate: 40 × €25,000 × 0.36 ÷ 90 = €4,000 a day

• a 75-day cycle: €300,000 ÷ 75 = €4,000 a day

A fifth more on any of the top three inputs is worth exactly as much as taking 15 days off the cycle. So the question isn't which lever is strongest on paper, it's which one your team can move most cheaply.

In our experience that's rarely volume. More opportunities usually means looser ones, and the win rate pays for it a quarter later. Win rate and cycle length tend to have more slack, because they improve when the same deals are worked better. Shorter cycles come from ordinary fixes: multi-threading early so a deal doesn't wait on one person, agreeing a mutual action plan with dates on both sides, and getting pricing approvals out of the way before the buyer asks.

The inputs also multiply. Improve all four by 10% and you get 44 × €27,500 × 0.33 ÷ 81. That's €1,210,000 × 0.33 = €399,300, divided by 81 days, or €4,929.63 a day, about 48% more than where the team started. Small, steady gains across the board beat one heroic push on a single input.

When a bigger deal makes the whole thing slower

Deal size looks like the easiest lever, until you see what tends to come with it. Ten opportunities at €25,000 with a 30% win rate and a 90-day cycle give 10 × €25,000 × 0.30 ÷ 90 = €833.33 a day.

Now move upmarket. The average deal climbs to €60,000, but larger buyers take longer and say no more often, so the cycle stretches to 150 days and the win rate drops to 20%. That's 10 × €60,000 × 0.20 ÷ 150 = €800 a day. Deal size went up 140% and velocity went down.

That isn't an argument against enterprise deals. Larger customers can bring better retention, references and expansion that the formula never sees. It's an argument for running the numbers before you change your target market, and for reading all four inputs together instead of celebrating the one that went up.

Reading a drop before you react to it

A falling velocity tells you that something is wrong and nothing about what. Say it comes in 22% lower than last quarter. The reflex in most sales meetings is to ask for more pipeline. Break it down first.

In that quarter, opportunities, deal value and cycle length held steady, and the win rate slid from 30% to about 23%. Because velocity moves in proportion to win rate, that one input explains the entire 22%. More pipeline would have fed more deals into the same losing pattern. The fix sat in qualification and coaching.

Each input points to a different kind of work:

• Fewer opportunities. A pipeline generation problem. Check your pipeline coverage against the target and look at which sources dried up.

• Lower win rate. A selling or qualification problem. Look at the stage-by-stage pipeline conversion rate to see where deals now leak, and at the lost reasons.

• Smaller deals. Usually packaging, discounting or a shift in which accounts reps work.

• Longer cycle. Process work: approvals, procurement steps, too few people involved on the buyer's side.

Watch for inputs that move in opposite directions with a delay. A rep who logs every conversation as an opportunity raises velocity this quarter, and the win rate drops when those deals lose next quarter. That's why we'd never put velocity on a bonus plan without also checking how opportunities are created. It works best as one view in a connected revenue engine, next to the numbers that feed it.

Sales velocity rep by rep, segment by segment

A company-wide figure is a summary. Calculated per rep, sales velocity compares people on how fast they turn pipeline into revenue instead of on how much they happened to close.

The inputs matter more than the ranking. In a four-person team, one rep might close the biggest deals but take 118 days to do it, while another works the most opportunities and wins only 18% of them. Both sit near the bottom of the table, and they need opposite coaching: the first on moving deals along, the second on walking away from poor-fit ones.

Be careful with small numbers. A rep with a dozen decided deals in a quarter sees their win rate move by more than eight points with every single deal, and velocity moves with it. Pool two quarters before drawing conclusions about one person.

Segments are where the split pays off most. Enterprise and small-business deals have different volumes, sizes and cycles, so a blended number hides which motion is efficient. Calculate them separately, along with regions if you sell in several, and you'll often find a segment with modest total revenue and high velocity that deserves more attention. It can also tell you where your ideal customer profile is strongest in practice, and whether your territory lines give each rep a fair mix.

No benchmark to chase, only a trend line

People ask what a good sales velocity is, and there's no useful answer from outside your company. The figure scales with deal size, cycle length and market. A low-price product sold in high volume and an enterprise platform with nine-month deals produce numbers that can't be compared, so any industry average mostly tells you about the companies in the sample.

Your own history is the benchmark that holds up, as long as the definitions stayed the same. We set it up as a rolling window of about one sales cycle, recalculated every week. Apollo describes RevOps teams that track velocity weekly as a forecast health indicator, and that matches what we see: a quarterly number can only explain a miss, while a weekly one can warn you about it with time left to act.

That early warning is the link to quota attainment. If velocity has been sliding for six weeks, the team is very likely heading for a shortfall, even if this month's closed revenue still looks fine. It's also a quick check on your forecast accuracy: multiply the daily rate by the days left in the quarter, and if the forecast is far above that figure, someone should explain where the difference comes from.

The bottom line

Sales velocity takes four numbers you already track and turns them into one rate that says how quickly the pipeline becomes revenue. The formula is simple enough to do on a napkin. What makes it worth using is the discipline around it: one definition per input, one time window for all four, and the habit of opening up the figure before reacting to it.

Used that way, it changes the conversation in a pipeline review. Instead of "revenue feels slow", you can say that the win rate on mid-market deals dropped while everything else held, and you know who should fix it. It also keeps you from trading one input for another without noticing, whether that's padding the pipeline or chasing bigger logos with longer cycles.

Track it on the same dashboard as coverage and conversion. Those two show how much pipeline your go-to-market machine produces, and velocity shows how quickly that pipeline, including the meetings your automated outbound books, becomes cash.

If you'd like it set up properly, Nebor builds the four inputs as fixed report definitions in your existing CRM, with a weekly velocity view per rep and segment, and hands it over with a short note on how each number is counted.

Frequently asked questions