What is pipeline velocity?
Four numbers your CRM already has, combined into one answer: how fast your pipeline turns into revenue, and which of the four you can actually move first.
Toni MedicSalestructSeptember 30, 20267 min readCRM & Pipeline
Pipeline velocity turns four numbers your CRM already tracks into one figure: how much revenue your pipeline is producing per day. It's not a vanity metric. It's a diagnostic, because the four inputs that build it are the four places a sales process can actually break.
The short version
- Pipeline velocity = (Number of opportunities x Average deal size x Win rate) ÷ Sales cycle length. HubSpot, Salesforce and Pipedrive all publish the same formula, and Pipedrive confirms "sales velocity" and "pipeline velocity" are the same metric.
- Cycle length is usually the fastest input to move, because it acts on deals already in the pipeline rather than requiring new opportunities to be sourced or priced.
- The easiest calculation error to make is a unit mismatch: cycle length measured in days produces a revenue-per-day answer, measured in months produces revenue-per-month, and mixing vendor examples that use each blows the result off by roughly 30x.
- HubSpot recommends running the formula separately by segment (small, mid-market, enterprise) and over at least a full quarter, because a blended average or a short window hides more than it shows.
What is pipeline velocity?
Pipeline velocity is the rate at which your open pipeline converts into closed revenue, calculated as the number of qualified opportunities times the average deal size times the win rate, divided by the length of the sales cycle. It's also called sales velocity, sales funnel velocity, or sales pipeline velocity. HubSpot, Salesforce and Pipedrive each publish the same formula under one of those names, and Pipedrive says directly that the terms "mean the same thing; you can use them interchangeably."
The formula
There's one formula, and every vendor that publishes it writes it the same way:
Pipeline velocity = (Number of opportunities × Average deal size × Win rate) ÷ Sales cycle length
The result is revenue per unit of time, and the unit depends on how you measured cycle length. Measure your sales cycle in days and the answer is revenue per day. Measure it in months, the way HubSpot's own worked examples do, and the answer is revenue per month. That single choice trips people up more than any other part of the formula, and it's the first item in the mistakes section below.
The four inputs, and what each one actually measures
- Number of opportunities
A count of qualified deals currently in your pipeline, not every lead that has ever entered your CRM. HubSpot's own guidance is explicit about this: "Make sure they're qualified opportunities. If your pipeline is packed with bad leads and only a few that actually have a chance of closing, your bottom line will suffer." Counting raw leads instead of qualified ones is the single most common way this number gets inflated.
- Average deal size
The average value of the deals in that same set, in your own currency. Salesforce defines it as "the average revenue you generate from new customers over a set period of time." If your business sells to wildly different segments, an unweighted average across all of them hides more than it shows, which is why HubSpot recommends running the formula separately by segment (see mistakes, below).
- Win rate
The share of qualified opportunities that close as won, calculated as deals won divided by total qualified opportunities. Pipedrive's formula for this piece is direct: "Win rate % = Number of deals won ÷ Total number of deals." A win rate measured against a rolling window of closed deals, not a single month, is what most vendors recommend, because a single month's closes are a small and noisy sample.
- Sales cycle length
The average number of days (or months) between a deal opening and it closing, won or lost. Pipedrive's formula: total days for all deals to close, divided by the number of deals. HubSpot calls this "the only sales velocity factor you don't want to increase." Every other input in the formula sits on top; the cycle length sits on the bottom, so a longer cycle drags the whole number down even when everything else improves.
A worked example, with round numbers
Take a pipeline with 30 qualified opportunities open, an average deal size of $20,000, a win rate of 30% measured over the last two quarters, and a 45-day average sales cycle.
Multiply the first three, divide by the fourth: (30 x $20,000 x 0.30) / 45 = $4,000. That is $4,000 of pipeline value converting into closed revenue every day, or roughly $1,460,000 a year if none of the four inputs change.
Nothing about that $4,000 figure is meaningful on its own. What makes it useful is watching it move. If the same team closes the same 30 deals at the same 30% win rate but the cycle stretches to 60 days, velocity drops to $3,000 a day, a 25% fall in the pace of revenue with the sales team doing exactly the same work.
Which of the four inputs can you move fastest?
Cycle length is usually the fastest lever, because it's the only one of the four that acts on deals already sitting in your pipeline rather than on deals you haven't sourced or priced yet.
Increasing the number of opportunities means generating more qualified pipeline, through more outbound volume, more inbound demand, or both, and that takes weeks to show up as closed revenue because those new deals still have to run the full cycle. Raising average deal size usually means changing pricing, packaging, or the segment you sell into, all of which take a sales cycle or more to prove out. Improving win rate can move faster, but it depends on changing how reps qualify and handle deals that are already open, which is a behavior change that has to hold across an entire team.
Cutting cycle length is different. It's internal friction, not a market outcome: dead time between stages, deals sitting with no next step, slow internal approvals, a stage nobody exits on a consistent rule. Fix any of that and every deal already in the pipeline moves faster immediately, without adding a single new opportunity. That's the argument for tightening exit criteria on every pipeline stage before touching anything else in the formula, and for treating speed to first response as a cycle-length problem, not a lead-generation problem: a slow first response adds days to the front of the cycle before a rep has done anything wrong.
HubSpot's own Director of Sales makes the same point from the failure side. Dan Tyre, describing a portfolio company with a large pipeline heading into its last quarter:
We quickly saw that we were in trouble when none of the deals were progressing to the evaluation stage... Not taking careful account of how quickly something went from opportunity to opportunity to demo to price negotiation to contract really hurt us.
A big number of opportunities did nothing for that business, because the cycle itself had stalled.
Common mistakes when you calculate pipeline velocity
- Mismatching the time unit between cycle length and the result. If cycle length is in days, the answer is revenue per day. If it's in months, the answer is revenue per month. Mixing the two, a common slip when copying a formula between HubSpot's month-based examples and Pipedrive's or Salesforce's day-based ones, produces a number that's off by roughly a factor of 30.
- Counting every lead instead of qualified opportunities. Both HubSpot and Pipedrive flag this specifically: an unqualified lead sitting in the pipeline inflates the opportunity count and understates how selective the team actually is being.
- Averaging deal size and win rate across very different segments. HubSpot's own guidance is to separate small, mid-market and enterprise pipelines and "run a sales velocity equation for each one," because a single blended average hides which segment is actually dragging on the number.
- Measuring over too short a window. HubSpot recommends at least a quarter, and up to six months or a year, specifically to average out seasonality and one unusually long or short deal. A single week's or month's velocity swings on a handful of deals and tells you almost nothing.
- Letting the definition of "qualified opportunity" drift over time. If the bar for what counts as an opportunity changes between quarters, whether it's tied to a form fill, a specific page visit, or a booked call, the trend line stops measuring the pipeline and starts measuring the definition.
Related metrics
Pipeline velocity is a summary number built from other metrics that are worth tracking on their own. How to calculate win rate covers the second input in more depth. What is a sales pipeline covers the structure the opportunities move through. Sales forecasting methods is where this number feeds into a revenue projection rather than a rear-facing measurement. Sales KPIs and what is revenue operations cover where pipeline velocity sits alongside the other numbers a sales leader tracks weekly.
FAQ
Common questions
Sources
HubSpot, What Is Sales Velocity & How Do You Increase It?, by Meg Prater, updated 05/07/25. Formula, four factors, best practices, Dan Tyre quotes (2025)
Salesforce, How to Supercharge Your Sales Velocity for Quicker Wins, by Erin Hueffner, 12 March 2024. Formula, variable definitions, worked example (2024)
Pipedrive, What is sales velocity and how do you boost it?, read 29 September 2026. Formula, sales velocity vs. pipeline velocity, win rate and cycle length formulas, worked example (2026)
How these were checked
Every figure and quote above was read from the vendor's own page on 29 September 2026 and is linked above. The worked example in this post uses independent round numbers, not any vendor's published example. Salestruct has no commercial relationship with HubSpot, Salesforce or Pipedrive.
Finding which of your own four inputs is actually costing you revenue is a pull from your CRM, not a project.
If you want a second pair of eyes on your own setup, Salestruct runs a free diagnostic.
Read next.
All articlesCRM pipeline stages: give every one an exit criterion
Your CRM ships with stages named after things your rep did, and it multiplies your forecast by a number attached to each one. Booking a presentation does not make a deal 60% likely to close, but that is what the default pipeline asserts.
What is speed to lead? Definition, benchmarks and fixes
Speed to lead is the time between a prospect filling in your form and the first time someone on your team tries to reach them. Here's what the research says a good response time looks like, what most companies manage, and how to shorten yours.
