What is deal velocity?

The simplest deal velocity formula is: **Deal Velocity = Total pipeline time (won + lost) ÷ Total deals closed (won + lost)**. The result is a number of days — the lower, the better. Critically, this formula counts lost deals alongside wins, which gives a more honest read on process efficiency than a formula that only counts wins. Including lost deals surfaces the full cost of slow qualification and late-stage churn that won-only metrics hide.

The complementary **pipeline velocity formula** expresses throughput in dollars per day: **(Number of qualified opportunities × Average deal size × Win rate) ÷ Average sales cycle length**. For example, 50 opportunities at $80,000 average with a 25% win rate and a 120-day cycle produces $8,333 per day of pipeline velocity. This version is useful for revenue planning because it quantifies the dollar impact of improving any single variable.

Velocity can also be tracked at the stage level — total time spent in a specific stage divided by deals that passed through it — which is especially powerful for identifying where deals are stalling. Ebsta's 2024 data found that a 50% longer qualification stage correlates with a 120% higher chance of slippage, making stage-level velocity the most actionable diagnostic tool for RevOps teams.

The terms are related but measure different things. **Deal velocity** is a time-based metric: how many days does a single opportunity take to reach a decision? It treats all deals equally regardless of size and focuses on the efficiency of the sales process itself — the diagnostic.

**Sales velocity** (or pipeline velocity) is a revenue-throughput metric: how many dollars of revenue does the entire pipeline produce per day, accounting for deal size, win rate, number of opportunities, and cycle length simultaneously? It is the composite output of all four pipeline health factors and functions as the business outcome — what the revenue engine actually produces.

In practice, deal velocity is the root-cause tool. When average days-to-close rise, it surfaces in deal velocity before the revenue impact shows up in sales velocity. Improving deal velocity for your average deal directly lifts sales velocity — the diagnostic input drives the business outcome.

Revenue forecasting has historically relied on static snapshots: total pipeline value multiplied by a blended win rate. This approach is notoriously unreliable because it ignores how long deals have been sitting still. A deal that has been in 'Proposal Sent' for 90 days is not the same risk as one that entered that stage last week — but both count the same in a static model.

Velocity-adjusted forecasting weights deals by their age and stage-exit rate, producing far more accurate projections. First Page Sage's 2025 research across 247 B2B organizations found that teams tracking velocity weekly hit 87% forecast accuracy versus 52% for teams tracking ad-hoc — a 35-point gap that directly affects capacity planning, headcount decisions, and investor guidance.

Fast deal velocity also reduces a subtler risk: buyer disengagement. Deals that drag give procurement teams time to deprioritize, champions time to change jobs, and competitors time to enter. Ebsta's 2024 Benchmarks found that win rates drop 67% when deals slip more than eight weeks — confirming that velocity is not just an efficiency metric but a win-rate driver.

The most common velocity killers fall into three buckets. **Process friction**: lengthy legal review, slow procurement cycles, or unclear approval workflows. **Qualification gaps**: the economic buyer was not identified early, so the deal stalls when it reaches the person who actually controls budget. **Engagement drift**: reps do not follow up promptly after a demo or proposal, and the buyer cools or competitors enter.

The fixes map directly to the cause. For process friction: create pre-approved contract templates, engage legal earlier (share your MSA and DPA during technical evaluation, not after), and use mutual action plans that make the buyer a co-owner of the timeline — deals with MAPs close 18% faster on average. For qualification gaps: use a structured framework like MEDDIC and insist on economic buyer access before advancing a deal past the second stage. For engagement drift: implement follow-up automation and trigger-based cadences so no deal goes dark for more than a defined window.

Early stakeholder identification is particularly high-leverage. Ebsta and Pavilion's 2025 GTM Benchmarks — analyzing $48 billion in pipeline data — found that engaging the economic buyer actively in the first two stages of the sales process boosts win rates by 55%, while delayed deal progression reduces win rates by 113%.

Deal velocity benchmarks vary significantly by industry, deal size, and segment. First Page Sage's 2025 analysis of 247 B2B organizations in North America found that SaaS and technology companies generate a median pipeline velocity of $1,847 per day, with an average 67-day sales cycle. These figures reflect SMB-weighted deal sizes; enterprise deals ($100K+ ACV) routinely run 6–9 months, while SMB deals under $25K ACV average roughly 90 days.

The macro trend is unfavorable: the average B2B sales cycle expanded from 4.9 months in 2019 to roughly 6.5 months by 2025, driven by larger buying committees (now averaging 6.8 stakeholders), more rigorous security reviews, and tighter procurement processes (Gradient Works, 2025). A reliable improvement target for most B2B teams is a 10–15% quarter-over-quarter reduction in average cycle length.

Segment benchmarks from forecastio.ai (2024): SMB deals typically run 30–90 days; mid-market deals 90–180 days; enterprise 6–12 months; and strategic or consortium deals 12+ months. The right benchmark is your own trailing four-quarter average — external benchmarks set context, but internal trend direction is the metric that matters for management decisions.

Most of the friction that slows deals down is not strategic — it is operational. Reps forget to follow up because the CRM is stale. A buying signal fires (a champion posts about a new initiative, a prospect downloads a case study) and no one acts on it for days. Research for a proposal takes hours and arrives too late. These are not judgment failures; they are automation gaps.

Komo sits between your CRM and your inbox and runs that operational layer automatically. It monitors signals — job changes, intent spikes, funding events, product engagement — and surfaces them with pre-drafted, rep-editable follow-up messages while the context is still fresh. It researches accounts and stakeholders on demand, so a proposal or multi-threaded outreach can go out the same day a trigger fires rather than next week.

The human-in-the-loop model matters here because deal velocity is sensitive to tone. An auto-sent message that feels generic can damage a relationship and slow a deal more than a delayed one. Komo drafts; a rep approves and sends. The result is the speed of automation with the credibility of a human touch — which is exactly the combination that compresses sales cycles without burning trust.