Deal Velocity and Pipeline Velocity: Formulas, Benchmarks, Levers
A practical perspective for connecting this idea to your revenue team’s next move.
Deal velocity is how fast your pipeline turns into revenue. It is usually measured with the sales velocity formula: qualified opportunities × win rate × average deal size ÷ average sales cycle length in days. The result is revenue per day, and each of the four inputs is a lever you can measure and improve.
This guide works through the formula with a hypothetical example, explains how to measure each lever, shows where velocity and win rate pull against each other, summarizes what published research says slows enterprise deals, lists benchmarks only from named sources, and explains how AI and deal signals help, within limits.
Last updated: 17 October 2026
What is deal velocity?
Revenue teams use “deal velocity” in two related ways:
- Sales velocity (pipeline level): the revenue your pipeline produces per day, calculated with the formula below. It tells leaders which of four levers is holding revenue back.
- Deal velocity (deal level): how quickly one opportunity moves from stage to stage, measured as days in each stage and total days to close. It tells managers which deals are stuck and where.
You need both. The pipeline figure points to the constraint (too few opportunities, a falling win rate, shrinking deals or longer cycles); stage timing shows which deals and which stages cause it. “Pipeline velocity” is often used as a synonym for sales velocity; our pipeline velocity guide covers pipeline management practices in more depth.
What is the sales velocity formula?
Sales velocity = (number of qualified opportunities × win rate × average deal size) ÷ average sales cycle length in days
Salesforce defines the formula the same way in its guide to sales velocity (12 March 2024): opportunities are the qualified leads in your pipeline during the period, deal value is average revenue per new customer, win rate is the share of opportunities that became customers, and cycle length is the average number of days from qualified lead to paying customer.
Worked example (hypothetical numbers)
The figures below are invented for illustration and do not describe any real company. A mid-market team has 150 qualified opportunities in a quarter, a 20% win rate, a $25,000 average deal and a 90-day average sales cycle:
(150 × 0.20 × $25,000) ÷ 90 = $750,000 ÷ 90 = $8,333 of revenue per day , or about $750,000 over a 90-day quarter.
Now improve each lever by 10% on its own, then all four together:
Scenario (hypothetical)
Qualified opportunities
Win rate
Average deal size
Cycle length (days)
Velocity per day
Change
Baseline
150
20%
$25,000
90
$8,333
none
10% more opportunities
165
20%
$25,000
90
$9,167
+10.0%
Win rate up by a tenth
150
22%
$25,000
90
$9,167
+10.0%
Deals 10% larger
150
20%
$27,500
90
$9,167
+10.0%
Cycle 10% shorter
150
20%
$25,000
81
$9,259
+11.1%
All four together
165
22%
$27,500
81
$12,324
+47.9%
Hypothetical example. Velocity = (opportunities × win rate × average deal size) ÷ cycle length in days, rounded to the nearest dollar.
Two things stand out. The levers multiply, so four modest gains add up to far more than any single one. And a shorter cycle helps slightly more than proportionally, because it divides rather than multiplies.
When the formula misleads
- Mixed segments. Blending a 30-day SMB motion with a 180-day enterprise motion produces a number that describes neither. Calculate velocity per segment.
- Period effects. Deals created this quarter often close next quarter. For win rate and cycle length, use cohorts (opportunities created in the same period) rather than whatever happened to close.
- It is a diagnostic, not a forecast. The formula assumes a steady state. Use it to find the constraint, and forecast from deal-level evidence.
What is pipeline velocity, and how is it different from deal velocity?
Pipeline velocity is the rate at which your current open pipeline is expected to turn into won revenue, in dollars per day. It uses the same four inputs as the sales velocity formula above, applied to the qualified opportunities open today rather than to a past cohort of closed deals. Deal velocity is narrower: how fast one opportunity moves through its stages.
Pipeline velocity = (open qualified opportunities × historical win rate × average deal size) ÷ average sales cycle length in days
Take win rate, deal size and cycle length from closed deals in the same segment over the last two to four quarters, and take the opportunity count from the pipeline as it stands today. The result answers a forward-looking question: if this pipeline converts the way it usually does, how much revenue does it produce per day?
Worked example: calculate it per segment (hypothetical numbers)
A team has 120 open mid-market opportunities and 30 open enterprise opportunities. All figures are invented for illustration.
Segment (hypothetical)
Open qualified opportunities
Win rate
Average deal size
Cycle length (days)
Pipeline velocity per day
Mid-market
120
25%
$30,000
60
$15,000
Enterprise
30
20%
$150,000
180
$5,000
Total (sum of the segments)
150
$20,000
Blended inputs (misleading)
150
24%
$50,000
84
$21,429
Hypothetical example. The blended row uses the expected win rate across both segments, the average expected won deal and the opportunity-weighted average cycle.
Adding the two segments gives $20,000 a day. Blending the inputs first gives $21,429, because averaging a 60-day and a 180-day cycle understates how long the enterprise half of the revenue takes to arrive. The blended view also hides change: if the enterprise cycle stretches from 180 to 210 days, enterprise velocity falls about 14%, to $4,286 a day, which is easy to miss inside one company-wide number. Calculate pipeline velocity per segment, then add the results.
Pipeline velocity vs deal velocity vs sales velocity
Measure
Question it answers
Unit
Built from
Who acts on it
Sales velocity
How much revenue per day did the pipeline produce last period?
Revenue per day
A past cohort of closed opportunities
CRO, RevOps
Pipeline velocity
At normal conversion, how much revenue per day will today’s pipeline produce?
Revenue per day
Open qualified opportunities, plus historical win rate, deal size and cycle length
Sales leaders, RevOps, forecast reviews
Stage velocity
Where does the pipeline slow down?
Median days in each stage, with stage conversion
Stage history of all opportunities
Sales managers, RevOps
Deal velocity
Is this deal moving at the pace of similar won deals?
Days in the current stage and days open, against the segment median
One opportunity’s stage history
Rep and frontline manager
Definitions used in this guide. Many teams use “pipeline velocity” as a synonym for sales velocity, and some for the stage-level view; write your definition into your metric dictionary and keep it.
The measures are connected. A deal that sits past the segment median in one stage shows up first in deal velocity, then in stage velocity, and only later in pipeline velocity, once longer cycles feed into the averages. That is why a weekly deal review catches a slowdown well before the pipeline number moves, and why stale close dates and abandoned opportunities, the subject of our pipeline hygiene guide, distort every one of these figures.
How to measure each lever
Qualified opportunities
Count opportunities that met your written qualification criteria, either entering the period or open at its start, and apply the same rule every quarter. Opportunities created to hit an activity target inflate this lever and drag down win rate, so report opportunity count and win rate side by side.
Win rate
Divide won deals by all closed deals (won, lost and closed with no decision) that reached a fixed stage. Leaving out “no decision” outcomes flatters the number and hides the most common enterprise loss. Track count-based and value-based win rate separately; a team can win more small deals while losing the large ones.
Average deal size
Divide won revenue by the number of won deals, using one definition of value (annual contract value or first-year value) throughout. Report the median next to the mean so a single large deal does not hide a trend, and watch discount depth as a separate metric.
Sales cycle length
Measure the median days from qualification (or opportunity creation, if that is all you track reliably) to closed-won. Also track median time in each stage and median time to a loss: deals you lose after five months cost far more selling time than deals you lose in week three.
Deal velocity vs win rate: where the trade-offs are
The four levers are not independent. Pushing one often moves another, which is why velocity is a better target than any single input. Using the hypothetical baseline above:
- Stricter qualification. Suppose tighter entry criteria cut opportunities by 20% to 120 but lift win rate from 20% to 26%. Velocity rises to $8,667 per day (+4%), and reps work 30 fewer deals. A small velocity gain with much less wasted effort is usually a good trade.
- Discounting to pull deals forward. Suppose a quarter-end discount cuts average deal size by 10% and shortens the cycle by 5%. Velocity falls to $7,895 per day (−5.3%), and buyers learn to wait for the end of the quarter.
- Bigger deals take longer. Raising deal size by moving upmarket usually lengthens the cycle. In Ebsta and Pavilion’s 2023 B2B Sales Benchmark Report (3.2 million opportunities from 364 companies, 2022 data), the optimal close window was 31-60 days for small deals, 61-90 days for medium deals and 150-180 days for enterprise deals.
- Multithreading does not have to slow you down. In the same report, medium-sized deals with 7-9 relationships had a 48% win rate, 39% higher than deals with 4-6, and closed 10% quicker. Enterprise deals peaked at a 42% win rate with 10-12 relationships. These are correlations in one vendor’s dataset, but they cut against the idea that adding stakeholders always slows a deal. See multithreading for the practice itself.
Which matters more? Neither on its own. A team can raise win rate by working only sure deals and starve the pipeline, or shorten cycles by discounting and shrink revenue. Set targets on velocity per segment, and review the four inputs together so a gain in one is not paid for by another.
What slows enterprise deals?
Published research points to the same few causes. Most are about how buyers decide, not how fast sellers work.
Larger buying groups and harder consensus
Forrester’s State of Business Buying 2024 (4 December 2024) reports that 13 people are involved in the average buying decision, 89% of purchases involve two or more departments and 86% of B2B purchases stall during the buying process. Ebsta’s 2024 B2B Sales Benchmarks: H1 Update (analysis of $57 billion in revenue) found that the number of stakeholders involved grew from 5 to 8, and that sales cycles grew 20% compared with 2023.
Indecision, not only competitors
In an interview with CustomerThink (12 October 2022), Matt Dixon described research behind The JOLT Effect that analyzed about 2.5 million recorded sales conversations and found that 40-60% of deals are lost because the customer does nothing. He reported that preference for the status quo explains less than half of those losses; the larger share comes from buyers’ fear of making a mistake. Velocity work that only adds urgency misses this; reducing perceived risk (a clear recommendation, a limited set of options, a staged rollout) addresses it.
Buying is complex for the buyer too
Gartner’s Customer Confidence research page (undated, accessed 16 October 2026) reports that 77% of B2B buyers described their latest purchase as very complex or difficult, and that buyers spend about two-thirds of the journey gathering, processing and reconciling information.
Executives and finance engaged too late
Ebsta’s 2024 H1 update reports that win rates are 42% lower when the C-suite is engaged late, that win rates fall 64% when ROI is discussed late in the deal, and that top performers are 241% more likely to have the economic buyer engaged before the solution is presented. These are vendor-dataset correlations, but the direction is consistent: late discovery of who signs and why slows deals and loses them.
Security, legal and procurement steps
In Conveyor’s B2B SaaS Customer Trust Benchmark (undated vendor survey of 100+ security and compliance professionals), nearly 80% said security questionnaires are important or critical for closing deals. When these reviews start only after the buyer has chosen you, they add weeks at the end of the cycle; started during evaluation, they run in parallel.
Poor-fit opportunities entering the pipeline
Ebsta’s 2024 H1 update also reports that win rates increase 3.1x when opportunities match the ideal customer profile. Opportunities that should never have been qualified take up rep time and stretch average cycle length before they are finally lost.
In your own pipeline, these causes show up in three places: poor-fit deals entering early stages, qualified deals stalling mid-cycle without a buyer-side next step, and late-stage surprises from procurement, legal or an unseen stakeholder. Audit each separately.
B2B sales velocity benchmarks: what named sources report
There is no credible universal benchmark for sales velocity itself. It is revenue per day, so it scales with team size and price point; a “good” figure for one company is meaningless for another. Benchmark against your own trailing quarters, by segment. Published benchmarks do exist for the inputs:
Benchmark
Figure
Source
Caveat
Optimal close window by deal size
31-60 days (small), 61-90 days (medium), 150-180 days (enterprise)
2022 data; vendor dataset of 3.2M opportunities
Chance of closing for deals open longer than twice the average cycle
3%
2022 data
Win rate at the most effective number of relationships
42% enterprise (10-12), 48% medium (7-9), 29% small (1-3)
Correlation; 2022 data
Change in 2024 vs 2023
Sales cycles +20%, win rates −7%, rep velocity −15%
Ebsta does not publish its velocity definition in the update
Deal slippage (close date missed)
37% of deals in 2022; 46% in Q1 2024, falling to 34%
Ebsta and Pavilion, 2023; Ebsta, 2024
Vendor datasets
Buying cycle length reported by buyers
87% of buyers (65% of enterprise buyers) completed their purchase within six months
TrustRadius and Pavilion, 2024
Survey of 2,164 technology buyers; self-reported
Proposal stage speed
Opened 34 minutes after sending; 2.5 days from opening to closed-won; 34% average close rate
Proposify, State of Proposals 2026
742,137 proposals in 2025; average won deal $16,388, far smaller than most enterprise deals
Benchmarks for the inputs to sales velocity, each from a named source. Vendor datasets reflect each vendor’s own customers.
Use these as reference points, not targets. If your enterprise cycle is well past 180 days, the Ebsta window suggests checking for stalled deals that should be closed out; it does not mean your process is broken.
How long does it take to close a B2B deal? Time-to-close benchmarks
In Revspire’s B2B SaaS win rate and sales cycle benchmark (about 40 B2B companies, closed deals from October 2025 to September 2026), the median won deal closed in 20 days under $10k annual contract value (ACV), 45 days at $10k-$50k and 90 days above $50k, measured from opportunity creation to closed-won. Time to close scales with deal size, so compare your deals only within the same ACV band.
ACV band
Median won deal
Median with a mutual action plan
Median without a plan
Under $10k
20 days
20 days
25 days
$10k-$50k
45 days
42 days
60 days
Above $50k
90 days
85 days
120 days
Days from opportunity creation to close, Revspire customer data, October 2025 to September 2026. The first column is from the win rate and sales cycle benchmark; the plan columns are from the separate mutual action plan benchmark, so the columns are not directly comparable. These are observed patterns, not proof that a plan shortens a cycle.
Third-party data defines deal sizes differently, so use it for direction rather than as a target:
- Late deals lose their chance quickly. Ebsta and Pavilion’s 2023 B2B Sales Benchmark Report (3.2 million opportunities from 364 companies, 2022 data) gives the optimal close windows shown in the benchmark table above, and adds that opportunities running past that window could lose up to 60% of their likelihood of closing within one more month, and up to 90% within two. The report does not define its deal-size groups in dollars.
- Close dates follow the calendar, not the buyer. In the same report, 89% of close dates fell on the last day of a calendar month, and 68% of opportunities had a close date earlier than the optimal window for their size.
- Security review is the biggest late delay. In G2’s 2026 Buyer Behavior Report (an online survey of 1,038 B2B decision-makers fielded in June 2026), IT security review was the biggest single source of delay between choosing a vendor and completing the purchase, named by 39% of buyers and 50% of enterprise buyers, ahead of budget approval (32%) and implementation planning (25%). In Revspire’s mutual action plan benchmark, security and legal review completion was the milestone most often overdue, in 34% of plans.
How to use time-to-close benchmarks
- Measure your own baseline first. Calculate median days from opportunity creation to closed-won by ACV band over the last four quarters, with the 25th and 75th percentiles to show the normal spread. Use medians, because a few very long deals pull averages up.
- Set close dates from the band median. If your median for deals above $50k is 90 days, a $60,000 opportunity created on 1 March has an expected close around 30 May (hypothetical example). A rep forecasting 31 March should be able to point to buyer evidence for the faster path, such as a compelling event or a plan the buyer has signed off.
- Set a close-out rule. Re-qualify any deal that has been open for more than twice its band median, and close it out if the buyer cannot name a decision date. The benchmark table above gives Ebsta’s figure for deals open longer than twice the average cycle.
- Start security and legal review during evaluation. Put the security questionnaire, legal review and procurement steps on the mutual action plan with buyer-side owners before the proposal goes out, so they run in parallel with the evaluation instead of after the decision.
Deal velocity metrics to track
Metric
How to calculate
What it tells you
Watch out for
Sales velocity
(Qualified opportunities × win rate × average deal size) ÷ cycle days
Revenue per day from the pipeline
Mixing segments with different cycles
Stage conversion rate
Opportunities moving to the next stage ÷ opportunities entering the stage
Where deals leak
Stage definitions changing mid-year
Median time in stage
Median days spent in each stage
Where deals wait
Averages skewed by abandoned deals
Sales cycle length
Median days from qualification to closed-won
Elapsed time to revenue
Inconsistent start dates
Time to loss
Median days from qualification to closed-lost
Selling time spent on deals you lose
Deals left open instead of closed out
Win rate
Won ÷ (won + lost + no decision)
Conversion quality
Excluding no-decision outcomes
No-decision rate
Deals closed with no vendor chosen ÷ all closed deals
Buyer indecision
Needs its own loss reason in the CRM
Average and median deal size
Won value ÷ won deals
Value per win
Discount creep
Close-date slippage rate
Deals whose close date moved out of the period ÷ deals forecast in the period
Momentum and forecast risk
Repeated small pushes
Stakeholder coverage
Engaged buyer contacts per opportunity, by role
Multithreading
Counting contacts who never respond
Mutual action plan on-time rate
Plan tasks completed by due date ÷ tasks due
Buyer commitment
Plans nobody updates
Days since last two-way buyer activity
Days since the buyer last replied, met or completed a task
Stall risk on a live deal
Counting one-way seller emails
Deal velocity metrics, from pipeline level to deal level.
A mutual action plan makes two of these measurable that usually are not: buyer-side commitments and their due dates.
How AI and deal signals help deal velocity
The evidence on AI and sales outcomes is mostly survey-based. In a Gartner survey of 1,026 B2B sellers (published 16 September 2024), sellers who effectively partner with AI tools were 3.7 times more likely to meet quota. That is an association in self-reported data, and it does not show that AI shortened cycles. The same survey found that 50% of sellers feel overwhelmed by the amount of technology they need, and that overwhelmed sellers are 45% less likely to attain quota, so adding tools can work against you.
Buyers are using AI too: 45% of B2B buyers in a Gartner survey published 9 March 2026 said they used AI during a recent purchase. That raises the cost of inconsistent or out-of-date seller material.
Where AI and deal signals do help is in catching slowdowns earlier than a weekly review would:
- Stall detection: flagging deals with no two-way buyer activity, repeated close-date pushes or overdue plan tasks.
- Evidence checks before stage changes: is the economic buyer identified, is the decision process documented, has security review started?
- Coverage gaps: showing which roles in the buying group have not engaged.
- Content by stage and role: suggesting the asset that answers the buyer’s next question.
- Win-loss patterns: finding what stalled and lost deals had in common, from calls and CRM history.
AI playbooks for deal velocity
A velocity playbook turns each signal into an agreed action, so alerts lead to a change rather than noise. Examples:
- No two-way buyer activity for a week and no meeting booked: the manager asks the rep for the buyer-side next step and its owner.
- Finance viewed pricing but no business case exists: the rep shares a business case summary with the champion.
- Security documents unopened two weeks before the target signature date: the rep escalates the security review in the mutual action plan.
- Close date pushed twice: the deal is re-qualified on decision process and compelling event before it stays in the forecast.
The limits are real. Signals are only as good as CRM and activity data. AI cannot create urgency the buyer does not have, and it cannot fix indecision on its own. Treat alerts as coaching questions, not forecast verdicts; our post on AI deal coaching and deal-risk signals covers how to design them. Revspire’s Digital Sales Rooms provide mutual action plans with owners and due dates, stakeholder mapping and buyer engagement analytics, and its AI Playbook Engine includes AI win-loss analysis of deals and calls.
A 90-day plan to improve deal velocity
- Weeks 1-2: baseline. Pull two to four quarters of closed opportunities. Calculate the four inputs and median time in stage per segment, using cohorts.
- Week 3: find the constraint. Compare each lever with its own trend and with your best-performing segment or team. Pick the one with the largest gap.
- Week 4: choose two or three changes aimed at that constraint, each with one owner and one measure. Examples: written exit criteria for the qualification stage, a mutual action plan on every deal above a set size, or an economic buyer meeting before any proposal.
- Weeks 5-12: run it weekly. Review stalled deals by signal in the pipeline meeting, and decide the next buyer-side step for each.
- Day 90: compare with the baseline. Keep, revise or stop each change. Note anything else that changed in the period, such as pricing, territories or seasonality, before crediting the result to one change. Feed findings into your win-loss analysis.
To make buyer-side steps and dates visible from the first week, start with Revspire’s free mutual action plan template.
Frequently asked questions
How do you calculate deal velocity?
Multiply the number of qualified opportunities by win rate and average deal size, then divide by the average sales cycle length in days. The result is revenue per day. For example, 150 opportunities × 20% × $25,000 ÷ 90 days is about $8,333 per day (hypothetical figures).
What is a good sales velocity for a B2B team?
There is no universal benchmark, because velocity scales with team size and price. Compare against your own trailing quarters by segment. For the inputs, Ebsta and Pavilion’s 2023 report put the optimal close window at 61-90 days for medium deals and 150-180 days for enterprise deals, based on 2022 data.
What is the difference between sales velocity and pipeline velocity?
Most teams use the terms interchangeably for the same formula: revenue the pipeline produces per day. Some use pipeline velocity for how quickly opportunities move between stages. Define the term once in your reporting and use it consistently.
How do case studies impact enterprise deal velocity?
We found no published study that isolates the effect of case studies on enterprise deal velocity. You can test it in your own data: compare stage conversion and time in stage for similar deals where a matched case study or reference was shared at the evaluation or business case stage versus deals where it was not. Peer proof is most likely to help where indecision, rather than competition, is slowing the deal.
Which matters more, deal velocity or win rate?
Velocity, because it includes win rate along with opportunity volume, deal size and cycle length. Optimizing win rate alone can shrink the pipeline, and optimizing speed alone can lead to discounting. Track the four inputs together.
How do you calculate pipeline velocity?
Multiply the number of open qualified opportunities by your historical win rate and average deal size, then divide by your average sales cycle length in days. Take the win rate, deal size and cycle length from closed deals in the same segment, calculate each segment separately and add the results. For example, 120 mid-market opportunities × 25% × $30,000 ÷ 60 days is $15,000 a day (hypothetical figures).
How long does it take to close a B2B SaaS deal?
It depends on deal size. In Revspire’s benchmark of about 40 B2B companies (October 2025 to September 2026), the median won deal closed in 20 days under $10k ACV, 45 days at $10k-$50k and 90 days above $50k, counted from opportunity creation. In Revspire’s separate mutual action plan benchmark, deals above $50k with a plan closed in a median of 85 days, against 120 without one.
Sources
All pages were accessed on 16 October 2026.
- How to Supercharge Your Sales Velocity for Quicker Wins, Salesforce, 12 March 2024
- 2023 B2B Sales Benchmark Report, Ebsta and Pavilion, 2023 (2022 data)
- 2024 B2B Sales Benchmarks: H1 Update, Ebsta, 2024
- To Master B2B Buying Mayhem, Providers Must Prioritize Buyers’ Needs (State of Business Buying 2024), Forrester, 4 December 2024
- The problem of customer indecision and how to get over it: interview with Matt Dixon, CustomerThink, 12 October 2022
- Customer Confidence, Gartner, undated
- B2B SaaS Customer Trust Benchmark Report, Conveyor, undated
- TrustRadius and Pavilion reveal 2024 B2B buying trends, MarTech Series, 2024
- State of Proposals 2026, Proposify, 2026
- Gartner Sales Survey Reveals Sellers Who Partner With AI Are 3.7 Times More Likely to Meet Quota, Gartner, 16 September 2024
- Gartner Sales Survey Finds 67% of B2B Buyers Prefer a Rep-Free Experience, Gartner, 9 March 2026
- G2 2026 Buyer Behavior Report, G2, 2026 (survey of 1,038 B2B decision-makers fielded June 2026; publication date not stated) (accessed 17 October 2026)
- B2B SaaS Win Rate and Sales Cycle Benchmark (2026), Revspire, 16 October 2026 (data October 2025 to September 2026) (accessed 17 October 2026)
- Mutual Action Plan Benchmark, Revspire, 2026 (data October 2025 to September 2026) (accessed 17 October 2026)