Pipeline velocity tells you how much qualified revenue your pipeline produces per day. The standard formula multiplies the number of qualified opportunities, average deal size and win rate, then divides by the average sales cycle length in days. The result is a single dollars-per-day figure. It only becomes useful when you break it into its four inputs, track it as a trend, and pair it with stage-level metrics that show where deals stall.
Below we walk through the formula, a worked example, the companion metrics worth putting on a dashboard, and the data-definition traps that make most velocity numbers unreliable.
TL;DR
- Pipeline velocity = (qualified opportunities × average deal size × win rate) ÷ sales cycle length in days. The output is revenue per day.
- Four levers drive it: opportunity volume, deal size, win rate and cycle length. Each one points to a different fix.
- Judge velocity as a trend within a segment, not against a universal benchmark. Enterprise and SMB motions are not comparable in raw dollars per day.
- Define “qualified opportunity” once, store a qualification date, and keep historical snapshots, or the metric will drift without anyone noticing.
- Velocity is a diagnostic, not a forecast. Pair it with stage conversion, time in stage, deal aging and coverage.
Table of Contents
- What pipeline velocity actually measures
- The pipeline velocity formula, step by step
- The four levers and what each one points to
- Why you should not chase a universal benchmark
- Define “qualified opportunity” before anything else
- From a single number to pipeline velocity analysis
- Velocity by source: where marketing attribution meets RevOps
- Automating velocity reporting without losing trust
- Our perspective: treat velocity as a system, not a scoreboard
- Where we can help
- A 30-day plan to put this to work
- FAQ
- Sources
What pipeline velocity actually measures
Most pipeline reports answer “how much is there?” Velocity answers a harder question: “how fast is it turning into revenue?” HubSpot describes sales velocity as a measure of how quickly deals move through the pipeline and generate revenue, built from four metrics: number of opportunities, average deal value, win rate and sales cycle length.
That composite nature is the point. A team can add opportunities and still see velocity fall if deals shrink, win rates slip or cycles stretch. Outreach makes a related point: a large pipeline can still be unhealthy when it moves slowly. Coverage tells you whether enough pipeline exists. Velocity tests whether it is moving fast enough to support the forecast.
You will also see the terms “sales velocity” and “pipeline velocity” used almost interchangeably. In practice they share the same formula. What changes is the framing: sales velocity usually describes the rep or team view, pipeline velocity the revenue-engine view across marketing, sales and RevOps. We use the second framing here because it is the one a CMO or revenue leader has to act on.
The pipeline velocity formula, step by step
The commonly accepted version, which Factors.ai and most other practitioners use, is:
Pipeline velocity = (number of qualified opportunities × average deal size × win rate) ÷ average sales cycle length (days)
Two rules keep the arithmetic honest:
- Use one time basis. If the cycle is measured in days, the output is dollars per day. You can then roll it up to weekly, monthly or quarterly views using your organization’s reporting convention, as HubSpot’s guidance notes.
- Express win rate as a decimal. 25% becomes 0.25.
A worked example
Pipedrive’s guidance uses 40 qualified opportunities, an $8,000 average deal, a 25% win rate and a 45-day cycle:
(40 × $8,000 × 0.25) ÷ 45 ≈ $1,778 per day
The same example shows how each lever moves the result when the others are held constant:
| Change (all else equal) | New velocity |
|---|---|
| Win rate from 25% to 30% | about $2,133 per day |
| Average deal size from $8,000 to $10,000 | about $2,222 per day |
| Sales cycle from 45 to 36 days | about $2,222 per day |
This is the real value of the formula: it makes scenario planning concrete. A 20% shorter cycle and a 25% larger deal produce the same lift. Which one is cheaper to achieve depends on your business, and that is a conversation to have with data in front of you.
The four levers and what each one points to
When velocity moves, the first question is which input moved. Outreach’s breakdown maps each lever to a different kind of problem:
- Fewer qualified opportunities: a demand-generation or qualification issue. Marketing and SDR teams own this lever.
- Shrinking deal size: look at targeting, packaging and discounting. Commercial leaders own this one.
- Falling win rate: a fit, competition or execution problem. Sales owns it, with marketing contributing through audience quality.
- Lengthening cycle: buyer friction or internal bottlenecks such as approvals, handoffs and legal review. RevOps often owns the fix.
The temptation is to ask for more pipeline whenever velocity dips. That treats a numerator problem and a denominator problem as the same thing. If cycles have stretched from 45 to 60 days, adding leads only feeds a slower machine.
Shortening the cycle
Cycle length is usually the least-measured lever and the most stubborn. It helps to understand how buying processes work in your category before you set targets. For SaaS specifically, this practical guide to how SaaS sales cycles work explains the stages and where time typically accumulates. Then look at your own data: which stage holds deals the longest, and is that time buyer-driven or internal?
Why you should not chase a universal benchmark
It is natural to ask for “a good number.” There isn’t one. Outreach’s guidance is to evaluate velocity as a trend, because the same absolute figure can be healthy in one segment and weak in another. Enterprise deals carry different values, win rates and cycle lengths than SMB or mid-market deals.
Here is an illustration with hypothetical numbers, not client data:
| Segment | Qualified opps | Avg. deal | Win rate | Cycle | Velocity |
|---|---|---|---|---|---|
| Mid-market | 60 | $15,000 | 22% | 60 days | $3,300 per day |
| Enterprise | 12 | $120,000 | 20% | 150 days | $1,920 per day |
Read naively, mid-market looks nearly twice as productive. But the enterprise motion may carry larger accounts, longer expansion paths and different costs. The comparison tells you little. What matters is each segment’s own direction over time.
For trend reporting, compare the current period with prior periods using consistent cohort rules, and annotate the things that change a number without changing performance: seasonality, territory changes, pricing changes and CRM definition changes.
Define “qualified opportunity” before anything else
The most common reason velocity numbers mislead is a fuzzy numerator. As Salesforce-focused practitioner guidance points out, definitions matter more than dashboard polish. Does the opportunity count mean all open deals, or only deals that have passed qualification? Does it mean deals currently open, or deals that entered qualification in the period? Each reading gives a different result and a different meaning.
A practical setup:
- Write the definition down. Agree it across Sales, Marketing and RevOps. Our piece on aligning teams in RevOps covers how to get that agreement.
- Store a qualification date or an equivalent stage-entry event, so you can measure by cohort rather than by today’s snapshot.
- Use closed-won values for average deal size, and count-based win rates.
- Record explicit start and end dates for cycle length.
- Snapshot history. Dashboards should show trend and explain which lever changed, which requires inputs to be preserved rather than silently recalculated.
If lead scoring feeds your qualification threshold, the threshold deserves the same scrutiny. We cover signals, backtesting and CRM write-back in our guide to making predictive lead scoring actionable.
From a single number to pipeline velocity analysis
A headline velocity figure says that something changed. It does not say where. Outreach’s pipeline analysis guidance treats stage conversion and time in stage as the bridge between a KPI and a diagnosis. Leaders should ask “where did movement deteriorate?” before asking teams to create more opportunities.
Companion metrics for a useful dashboard
- Stage-to-stage conversion rates: strong early conversion paired with weak proposal-to-negotiation conversion is a different problem from weak lead-to-opportunity conversion.
- Average time in each stage: shows the exact stage where deals stall.
- Deal aging: flags opportunities that have outlived the norm for their stage. Outreach publishes a separate piece on identifying stalled deals through pipeline aging.
- Pipeline coverage: whether enough pipeline exists for the target.
- Win rate and average deal size, shown separately so the composite does not hide them.
- New qualified opportunities per period.
- Close-date slippage: deals whose expected close keeps moving out.
Guard against flattering numbers
Velocity can look better for the wrong reasons. Removing stale opportunities from the pipeline shortens the average cycle and lifts win rate on paper, while masking weak qualification or poor CRM hygiene. Outreach’s guidance is to pair velocity with data-quality checks for exactly this reason. If a velocity jump coincides with a cleanup, say so on the dashboard.
Also resist a single company-wide figure. Segment by sales motion, deal size, product, region, source and customer type. The average often hides a healthy segment and a struggling one.
Velocity by source: where marketing attribution meets RevOps
For CMOs, the most useful cut is velocity by source and cohort. Connect opportunity records to source, campaign, account, contact and engagement data, then calculate each lever per cohort. This separates “more pipeline” from pipeline that converts faster and at higher value. A channel that fills the funnel with small, slow deals can look excellent on volume and poor on velocity.
This is where attribution is better thought of as a map than a courtroom verdict. You are not trying to prove which touch deserves credit. You are trying to see which routes lead to revenue quickly. If you also use visitor identification or intent data to feed the top of the funnel, tracking how those named leads move through marketing attribution and cohort analysis helps you judge whether they are accelerating or merely padding the count.
On the data side, the plumbing matters. Our overview of marketing data pipelines describes the components that keep source data governed, and our marketing ops audit traces leads to revenue so gaps in source fields surface before they distort your cohorts. For the three metrics we find most predictive of revenue, see our AI sales pipeline analytics playbook.
Automating velocity reporting without losing trust
Manual velocity reports tend to die within a quarter. Automation helps, but only if it is designed carefully. Good automated reporting:
- refreshes inputs on a defined cadence;
- preserves historical snapshots;
- flags missing or stale fields, such as an opportunity with no qualification date;
- routes anomalies to a named owner instead of recalculating a changed metric in silence.
That last point is the one most teams miss. If last month’s number quietly changes because someone edited an old record, nobody can trust the trend. Our guide to CRM automation workflows and guardrails goes into how revenue teams set these controls, and reverse ETL for CRM covers syncing warehouse-calculated scores and metrics back into the system reps use daily.
Our perspective: treat velocity as a system, not a scoreboard
We work with marketing, sales and finance teams on the analytics and agents that sit behind their revenue numbers, and the same pattern shows up again and again. The formula is rarely the problem. The inputs are.
Three convictions shape how we approach it:
- Definitions come first. If two teams count opportunities differently, no dashboard can fix that. We start by agreeing what qualified means and where the date lives in the CRM.
- No black boxes. A velocity model should be inspectable. We favour open-source builds and integrations with the platforms teams already use, such as Salesforce and HubSpot, so you can see how every number is produced and change it when your motion changes.
- Automate the diagnosis, not just the report. The goal is not a prettier chart. It is an agent or workflow that notices a stage slowing, flags the owner and shows which lever moved, so a human decides what to do.
Velocity rewards patience in measurement and speed in response. Teams that snapshot honestly for two or three quarters usually learn more from the trend than from any benchmark.
— Don
Where we can help
If you want velocity reporting that is defined, segmented and automated inside your own environment, we design and run it. Our AI strategy and readiness work starts with a baseline assessment and a prioritized roadmap, and our custom agent deployment builds the production agents that monitor pipeline stages and flag stalls. For teams that need ongoing support on the process side, see marketing operations optimization and support. You can also start from our main site and tell us where your pipeline slows down.
A 30-day plan to put this to work
- Week 1: Define. Agree the qualified-opportunity definition, the win-rate method and the start and end events for cycle length.
- Week 2: Baseline. Calculate velocity for the last four to six quarters by segment, using cohort rules rather than today’s snapshot.
- Week 3: Diagnose. Add stage conversion, time in stage and deal aging. Identify the single stage with the largest drop in movement.
- Week 4: Choose one lever. Pick one intervention, assign an owner, and set a review date. Changing four things at once makes the result unreadable.
Keep the first pass small. A trustworthy number for one segment beats an elaborate dashboard nobody believes.
FAQ
How is pipeline velocity calculated?
Multiply the number of qualified opportunities by average deal size and win rate, then divide by the average sales cycle length in days. The result is revenue per day. Use the same time basis for every input so the output is comparable across periods.
What is a good pipeline velocity number?
There is no universal good number. Enterprise, mid-market and SMB motions have different deal values, win rates and cycles, so absolute dollars per day do not compare across them. Judge your own figure as a trend within a segment, against prior periods measured with the same rules.
Is pipeline velocity the same as sales velocity?
They use the same four-input formula. Sales velocity is often the rep or team framing, while pipeline velocity is the revenue-engine framing that spans marketing, sales and RevOps. What matters is that your organization uses one definition consistently.
Which lever should we improve first?
The one your data shows has moved. Falling opportunity volume points to demand or qualification, shrinking deals to targeting or discounting, lower win rate to fit or execution, and longer cycles to buyer friction or internal bottlenecks. Stage conversion and time-in-stage data will usually narrow it down quickly.
Can velocity replace a forecast?
No. It is a diagnostic that explains why revenue is moving as it is. Use it alongside stage conversion, deal aging, coverage and close-date slippage when you build forecasts.
Sources
- HubSpot: Sales Velocity, what it is and how to measure it
- Outreach: Pipeline velocity, how to measure and improve it
- Outreach: How to conduct a pipeline review with analytics
- Outreach: Sales pipeline aging, how to identify stalled deals
- Pipedrive: Sales pipeline metrics every sales team should track
- Factors.ai: Pipeline Velocity, definition, formula and strategies
- Salesforce Blogger: Pipeline Velocity, a less common sales metric
