Pipeline Velocity: The Formula and the Constraint It Finds
Pipeline velocity is the revenue a sales pipeline produces per day. It multiplies qualified opportunities by win rate and average deal value, then divides by the sales cycle length in days. The figure shows how fast pipeline turns into revenue, and comparing its four inputs shows which one is holding revenue back.
Stand across the street from a car wash on a Saturday morning. Count the cars that join the line, and the ones that give up and drive off. Then read the price board and time the bay. Those four numbers decide what the owner takes in by noon, and a line around the block doesn't help much when each car spends twenty minutes inside.
Founders judge their pipelines by the line out front. The CRM shows forty open deals, so the quarter should be strong. Then it ends with most of those deals still open. The pipeline was big. It just wasn't moving.
Pipeline velocity measures the whole car wash at once. It answers two questions: how fast your pipeline turns into revenue, and which of the four numbers is holding it back. The answer to the second is usually one number, and adding deals to the line rarely fixes it.
The pipeline velocity formula
A car wash owner can work out revenue per hour, and a pipeline runs on the same arithmetic. Multiply three numbers and divide by the fourth:
Pipeline velocity = ([qualified opportunities] x [win rate] x [average deal value]) / [sales cycle length in days] Qualified opportunities: deals that passed your qualification rule in the period Win rate: deals won / deals closed (won plus lost) in the period Average deal value: total value of won deals / number of won deals Sales cycle length: average days from opportunity created to closed won
Each input is a lever you can pull:
- Opportunities: the qualified deals in play. MQL vs SQL covers where a lead becomes one.
- Win rate: the share of closed deals you won.
- Deal value: what an average won deal is worth.
- Cycle length: how many days a won deal took, from qualified to signed.
The result is revenue per day. Multiply it by 30 for a month, or by 90 for a quarter.
A pipeline velocity worked example
A worked example makes the formula easier to trust. Harbor is a hypothetical B2B software startup with a founder and one rep selling. Here's its last quarter:
| Lever | Harbor |
|---|---|
| Qualified opportunities | 30 |
| Win rate | 20% |
| Average deal value | $15,000 |
| Cycle length | 50 days |
Thirty opportunities times 0.20 times $15,000 comes to $90,000. Divide by 50 days and Harbor's pipeline produces $1,800 a day, or about $54,000 over 30 days.
Now improve each lever by 20%, one at a time:
| Lever moved | New input | Velocity | Gain |
|---|---|---|---|
| Opportunities | 30 to 36 | $2,160 a day | 20% |
| Win rate | 20% to 24% | $2,160 a day | 20% |
| Deal value | $15,000 to $18,000 | $2,160 a day | 20% |
| Cycle length | 50 to 40 days | $2,250 a day | 25% |
Cycle length wins because it sits under the line. Cutting the days by a fifth means dividing by 0.8, which multiplies velocity by 1.25. The table still assumes every lever can move 20%, and real levers can't.
Finding the constraint
The lever worth pulling is the one with the most room to move, and your own history shows where that room is. Compare each input with the last two or three quarters, and the stuck one usually stands out:
| Sign | Cause | Fix |
|---|---|---|
| Opportunities flat | Too few qualified deals entering | Fix targeting and outbound before pushing harder on closing |
| Win rate falling | Poor-fit deals entering, or losses piling up at one stage | Tighten qualification, then find the stage that loses deals |
| Deal value shrinking | Discounts to close, or smaller buyers | Hold price, and check which segment the wins come from |
| Cycle length growing | Deals waiting on a decision-maker nobody met | Get the decision-maker into qualification |
Win rate hides where deals die, so break it down by stage. Follow 100 of Harbor's opportunities to a decision:
| Stage move | Deals | Rate |
|---|---|---|
| Discovery to Qualification | 100 to 80 | 80% |
| Qualification to Evaluation | 80 to 60 | 75% |
| Evaluation to Business case | 60 to 24 | 40% |
| Business case to Won | 24 to 20 | 83% |
Harbor's 20% win rate turns out to be three healthy stages and one weak one. Evaluation is the constraint, so a sharper demo or tighter qualification before it will do more than new pipeline would. Sales pipeline stages sets the exit rules that make these counts trustworthy. At a startup where the founder still runs every deal, the founder's calendar can set the cycle length, and founder-led sales covers when to hand deals off.
When velocity misleads: a startup that closes ten deals a quarter moves its win rate ten points on one lost deal. Read velocity across two or three quarters, and split it by segment before acting on it. A blend of large and small deals hides what each one needs.
Mistakes that skew velocity
The formula finds the constraint only when its inputs are honest. Four mistakes bend them:
- Dead deals counted: stale opportunities inflate the top number and stretch cycle length. CRM data hygiene covers the rules that clear them out.
- Mixed periods: a win rate from last year paired with this quarter's opportunities describes no real pipeline.
- The easy lever: more leads is the easiest thing to ask for, and it's often the wrong one when deals die at one stage.
- Speed bought with discounts: a discount can shorten the cycle and shrink the deal by more. Rerun the formula to see whether velocity moved at all.
Speeding up your pipeline
A car wash with a line around the block and one slow bay needs a faster bay before it needs more customers. Run the formula on your last two quarters and compare the four inputs. Then break the win rate down by stage, and fix the weakest one before you add pipeline.
Tracking these numbers weekly, and fixing the one that's stuck, is part of my fractional CMO work, where I lead sales and RevOps alongside marketing. The free diagnostic there gives you a written roadmap either way.
Fix the slow bay first.
Common questions
What is a good pipeline velocity?
A good pipeline velocity is one that rises quarter over quarter against the company's own history. Velocity depends on deal size and cycle length, so a startup selling $5,000 contracts can't compare its figure with one selling $80,000 contracts. Compare the same company, with the same definitions, a quarter apart.
How often should a startup measure pipeline velocity?
A startup should measure pipeline velocity monthly, using the last 90 days of closed deals for win rate, deal value and cycle length. The trailing window smooths out the swings a handful of deals can cause. A quarterly measure works once the company closes enough deals for one quarter to stand on its own.
Is pipeline velocity the same as sales velocity?
Pipeline velocity and sales velocity usually name the same calculation: opportunities times win rate times average deal value, divided by cycle length. Either name works if the definitions stay fixed. Write down what counts as an opportunity and when a cycle starts, then keep both the same every period.
Which deals count as opportunities in pipeline velocity?
The deals that count as opportunities in pipeline velocity are qualified ones, meaning deals that passed the company's qualification rule, rather than every lead or first call. Counting unqualified leads inflates the opportunity number and drags the win rate down, which points the team at the wrong lever.