Pipeline Velocity Formula and How to Improve Each Input
Pipeline velocity formula with a worked example, what moves each of the four inputs, and a four-check audit for deals that never reached the CRM.
CEO of ZUUZ. He scaled Cloud Box Technologies from 0 to $25M ARR in IT services and distribution before building ZUUZ. Connect on LinkedIn
Pipeline velocity is the rate at which a sales pipeline turns into revenue, usually stated in dollars per day. The formula is number of qualified opportunities times win rate times average deal size, divided by sales cycle length in days. Its real use is showing which of the four inputs is holding revenue back.
TL;DR: Pipeline velocity = (opportunities x win rate x average deal size) / sales cycle length. In the IT channel, two inputs are usually wrong before anyone does the math: deals that live in email never become opportunities, and the cycle clock starts when someone creates a record, not when the buyer first wrote. ZUUZ, revenue intelligence for the IT channel, connects to the sales inbox and writes those deals and dates to the CRM.
- Count open opportunities as of today; take the other three inputs from deals closed in the same segment.
- Deals that never reach the CRM undercount opportunities and inflate win rate. Late record creation shortens the reported cycle.
- The Velocity Input Audit checks all four inputs against one mailbox before the number is trusted.
- ZUUZ does not calculate velocity or forecast. It makes the inputs under the team's own report complete.
Picture a regional MSP whose pipeline velocity, pulled from the CRM, has held steady for two quarters. Meanwhile three vendor referrals went unlogged, two prospects chose another provider by email, and a project ran five weeks in a thread before anyone opened an opportunity (an illustration, not a client story). Each fact changes an input to the formula, and none reached it.
What Is Pipeline Velocity?
Pipeline velocity measures how much revenue a pipeline produces per day from four inputs: deal count, win rate, deal size and time to close. HubSpot's sales velocity guide calls it "the measurement of how quickly deals move through your pipeline and generate revenue."
The value is diagnostic: it shows whether the team has too few deals, loses too many, sells too small or waits too long. It measures speed, unlike pipeline coverage, which compares pipeline value to quota.
How to Calculate Pipeline Velocity
Pipeline velocity = (qualified opportunities x win rate x average deal size) / average sales cycle length in days. The result is revenue per day; multiply by 30 for a monthly rate. Salesforce and Pipedrive publish the same formula, and Salesforce adds that the opportunity count should focus on sales-qualified leads.
- Qualified opportunities. Open deals meeting the written qualification rule today.
- Win rate. Deals won divided by deals closed, won plus lost.
- Average deal size. Total value of won deals divided by their count, the basis Zoho's explainer also uses.
- Sales cycle length. Average days from the start of a deal to close. The definition of "start" is where most errors hide.
The opportunity count is a snapshot of today; the other three come from closed deals in the same segment over the last two to four quarters. Blending new logos, renewals and one-off projects produces an average that describes no real deal.
Calculating it from a CRM report or a spreadsheet
Few CRMs ship a native velocity report, so most teams export opportunities with amount, outcome, created date and close date. In a sheet with the four inputs in B2 to B5, the formula is =B2*B3*B4/B5, with win rate as a decimal and cycle length above zero. Segment by pipeline, owner and deal type before averaging.
A Worked Pipeline Velocity Example
The numbers below are illustrative, for a mid-sized MSP's new-business pipeline, not drawn from any client.
| Input (illustrative) | CRM value | How it was counted |
|---|---|---|
| Open qualified opportunities | 30 | Open deals past qualification today |
| Win rate | 30% | 18 won of 60 closed in two quarters |
| Average deal size | $24,000 | First-year contract value of wins |
| Sales cycle length | 60 days | Opportunity created date to close |
| Pipeline velocity | $3,600 per day | (30 x 0.30 x $24,000) / 60 |
That is about $108,000 a month of new first-year contract value, if the four inputs are true.
Four Inputs, One Mailbox. Check the Count First.
ZUUZ connects to the sales inbox and writes the deals it finds to the CRM, so the opportunity count includes the deals still living in email.
What Most Guides Get Wrong
Several popular guides present velocity as a way to predict revenue. It applies past win rates, deal sizes and cycle lengths to today's opportunity count, so it describes how the pipeline has behaved, not what will close.
The bigger miss is the data. Nearly every guide assumes the CRM holds the inputs. Where deals start and die in email, the CRM holds a filtered pipeline, and the filter is not random.
Why IT Channel Inputs Are Wrong Before the Math
IT channel deals rarely begin as CRM records. They begin as a vendor rep's referral, a distributor's lead or a client's email about two new sites, and the opportunity gets created once the deal looks worth the typing.
| Input | What email-only deals do to it | Direction of error | Where to check |
|---|---|---|---|
| Opportunities | Active threads with a scoped need never become records | Too low | Rep and account manager mailboxes |
| Win rate | Losses that ended in a thread are never logged, so the denominator shrinks | Too high | Threads that went silent or ended with "we went another way" |
| Average deal size | Scope changes agreed by email are not written back | Either way | Final figure in the last thread or signed order |
| Sales cycle length | The clock starts at record creation, weeks after the first buyer email | Too short | Date of the buyer's first message about the need |
| Pipeline velocity | Errors partly offset, so the total can look stable while the diagnosis is wrong | Unknown until checked | All of the above |
The last row is the dangerous one: a low opportunity count pulls velocity down while the inflated win rate and short cycle push it up. A steady number built on offsetting errors points the team at the wrong lever, one of the reasons a CRM pipeline drifts from the real one.
The Velocity Input Audit
The Velocity Input Audit is a four-check test of whether a velocity number describes the pipeline or only the CRM. It takes an afternoon with one rep's mailbox and no new tool.
The Velocity Input Audit: four checks before the number is trusted
- Opportunities. List every buyer conversation from the last 30 days with a scoped need and a budget signal. Count the ones with no open opportunity.
- Win rate. Find threads from the last two quarters where the buyer said no, chose someone else or went silent, and that never became a record. Add them as losses.
- Deal size. For ten closed-won deals, compare the amount field to the final agreed figure, and confirm monthly fees and one-time projects use one basis.
- Cycle length. For the same ten deals, compare the opportunity created date with the buyer's first message about the need. Add the average gap.
Rule of thumb: if any input moves by more than about 10 percent, the number describes data entry habits, not the pipeline.
Run the Audit on 90 Days, Not One Afternoon.
Connect one mailbox and ZUUZ reads the last 90 days, showing which conversations never became opportunities and when each deal really started.
The Same Pipeline After an Inbox Check
Here is the illustrative MSP from the worked example after one account manager's mailbox goes through the audit.
- Opportunities rise from 30 to 38. Eight active conversations had no record: two vendor-rep referrals, one distributor lead and five clients asking about new sites or a security add-on.
- Win rate falls to about 25.7 percent. Ten threads ended with the buyer choosing another provider or going quiet, never logged. Wins stay at 18; closed deals become 70.
- Deal size holds at $24,000. The sampled amount fields match the signed figures.
- Cycle length rises from 60 to 81 days. The first buyer email came an average of 21 days before the opportunity was created.
- Recalculate. (38 x 0.257 x $24,000) / 81 is about $2,895 per day, roughly 20 percent below the CRM's $3,600.
The diagnosis changes more than the total. The CRM version argued for more top-of-funnel spend; the corrected one shows a cycle three weeks longer and a win rate flattered by unlogged losses, which points at qualification and follow-through.
What Moves Each of the Four Inputs
The inputs trade against each other: tighter qualification cuts opportunities but lifts win rate, and larger deals usually take longer.
Number of qualified opportunities
The cheapest gain is usually capture, not generation: referrals, distributor leads and expansion requests arrive by email and only count once they become records. The MSP sales pipeline guide shows where those signals arrive.
Win rate
Win rate improves when weak deals leave early, for example under a BANT- or MEDDIC-style rule that no named decision maker after two meetings means disqualify. Logging every loss with a reason, including quiet ones in email, makes the rate worth acting on.
Average deal size
For MSPs and resellers, deal size grows through attached services such as security, backup and monitoring, or a longer agreement term. Use one basis, such as new MRR times 12, and keep projects and hardware resale separate, since resale lifts deal size without the margin.
Sales cycle length
Measure from the first buyer message, then shorten. Tactics are in the guide to shortening the sales cycle, and stalled deals with moving close dates are covered under deal slippage.
What Is a Good Pipeline Velocity?
A good pipeline velocity is one that rises against the team's own trailing quarters in the same segment. Published benchmarks vary too much by deal size and motion to judge one company against, and most give no sample or source.
Track segments separately over rolling two-quarter windows and compare each input to its own history. The monthly sales pipeline review is the natural place to read it.
Compare Quarters on Complete Inputs. Not on Typing Habits.
ZUUZ writes deals, contacts and dates from email, calendar and meetings into the CRM the team already runs, so every quarter is counted the same way.
What Operators See in the Cycle Clock
From an operator's seat. In IT services and distribution sales, a channel deal's clock usually starts with an email: a vendor rep's forward, a distributor's lead or a client's note about a new requirement. The opportunity record tends to arrive later, once someone decides the deal is real.
The part teams do not plan for is what that delay does to their own metrics. A cycle measured from the record shows when the team started paying attention, not when the buyer started buying. Improvement work then gets aimed at stages that were never the slow part.
Pipeline Velocity Inputs: How ZUUZ Captures the Missing Deals
ZUUZ is revenue intelligence for the IT channel: MSPs and the vendors, distributors and resellers they work with. It is an AI layer on top of the CRM the team already runs, not a CRM. It reads the sales inbox, calendar and meeting tools for deal signals and updates Salesforce, HubSpot, Zoho, Attio or Pipedrive automatically, with full change history and one-click rollback.
Deals that lived only in email become opportunities on the right account, with the conversations behind them on the record, and won customers are written to ConnectWise PSA. It does not forecast, score deal health or set velocity targets.
That is pipeline surfaced, not revenue. At Cloud Box Technologies, a UAE cloud and IT services business, inbound email turned into leads and renewals, so leadership sees live pipeline and 10 to 12 renewals are tracked in minutes.
Check the inputs before the next monthly review. Connect one mailbox, and ZUUZ reads the last 90 days and writes what it finds to the CRM automatically, with full change history and one-click rollback. Missing opportunities and first-email dates land on the records the velocity report reads. 30-day free trial, no credit card: https://zuuz.ai/trial
When Pipeline Velocity Is the Wrong Metric
Velocity needs volume. A team closing a handful of large deals a quarter gets averages that swing on one result. Renewal-heavy MSP books belong in a separate view, as covered in sales pipeline health.
ZUUZ is not the fix for every gap either. Teams whose deals start in web forms and stay in the CRM may already have honest inputs.
Frequently Asked Questions
What is the pipeline velocity formula?
The pipeline velocity formula is (qualified opportunities x win rate x average deal size) / average sales cycle length in days, which gives revenue per day. Use today's open qualified opportunities, and take the other three inputs from deals closed in the same segment over the last two to four quarters, so every input describes one kind of deal.
What causes low pipeline velocity?
Low pipeline velocity comes from one of four inputs: too few qualified opportunities, a low win rate, small deals or a long sales cycle. Compare each input to its own trailing history to find which one moved. In IT channel teams, check the data first, because deals that never reached the CRM can make the wrong input look like the problem.
What is the difference between pipeline velocity and sales velocity?
For most teams there is no difference, since both names describe the same four-input formula, though some vendors reserve pipeline velocity for open pipeline and sales velocity for closed revenue. Deal velocity is separate: it tracks how fast one opportunity moves through stages. Write down one definition and keep it stable across quarters so trends stay comparable.
What is a good pipeline velocity?
A good pipeline velocity is one that improves against the team's own trailing quarters in the same segment. Published benchmarks span ranges too wide to use and rarely state a sample. Compare new-logo, expansion and project deals separately, and check each input against its own history, because a flat total can hide one input improving while another slips.
Can pipeline velocity be used as a sales forecast?
Pipeline velocity is not a forecast. It applies past win rates, deal sizes and cycle lengths to today's opportunity count, so it describes how the pipeline has behaved rather than which deals will close, and its best use is finding the weakest input. A forecast needs deal-level evidence about each opportunity, which velocity does not contain.
Which pipeline velocity input should a team improve first?
Fix measurement first, then the weakest input. Run the Velocity Input Audit to confirm the opportunity count, win rate, deal size and cycle length are real, then act on the input that moved most against its own history. Improving a number that was wrong to begin with wastes a quarter.
How often should pipeline velocity be measured?
Monthly suits most B2B teams, using rolling two-quarter windows for win rate, deal size and cycle length. Weekly readings swing on a single closed deal and mostly add noise. Read the trend by segment in the monthly pipeline review, and rerun the input checks each quarter or after a change to stages.
Does ZUUZ calculate pipeline velocity?
ZUUZ is not a velocity calculator or a forecasting tool. It connects to the sales inbox, calendar and meeting tools and writes missing deals, contacts and dates to the CRM the team already runs. The velocity math stays in the team's own CRM report, which then runs on complete inputs.
