Revenue Operations

Deal Velocity

2026-04-12 8 min read Revenue Operations
Deal Velocity measures how fast individual deals progress through each stage of a sales pipeline. Unlike sales velocity, which aggregates portfolio-level throughput, deal velocity isolates the pace of a single opportunity — expressed in average days per stage. It helps operators identify where deals stall and which stages need intervention.
TL;DR: Deal velocity tracks how many days each deal spends per pipeline stage. B2B SaaS companies with deal velocity under 12 days per stage close 28% more revenue per quarter than those averaging 20+ days (Pavilion COO Survey, 2025).

What is deal velocity?

Deal velocity (sometimes called deal cycle speed or opportunity velocity) is the measurement of how quickly a single deal moves from one pipeline stage to the next. Revenue operations teams use it to pinpoint bottlenecks — the exact stage where deals slow down, stall, or die. It answers a question that aggregate metrics cannot: where is this deal stuck?

Most operators track sales velocity as a portfolio metric. That number tells you how much revenue flows through the pipeline per day across all deals. Deal velocity works at the individual opportunity level. When your quarterly number looks healthy but three enterprise deals have been sitting in "proposal sent" for 19 days, deal velocity is the metric that surfaces the problem.

For mid-market B2B SaaS companies (50–200 employees), a healthy deal velocity is 8–14 days per stage. Anything above 18 days per stage for deals in the mid-pipeline typically signals a process breakdown — either the buyer lacks internal alignment, or the rep has lost momentum.

Deal velocity differs from sales cycle length in scope. Sales cycle length measures the total time from first touch to closed-won. Deal velocity breaks that total into its component parts, showing which stages consume the most time.

Why deal velocity matters for operators

When you only track total sales cycle length, you know how long deals take. You do not know where they lose momentum. A 45-day average cycle could mean smooth progression across 5 stages — or it could mean 3 stages move in a week while the "negotiation" stage consumes 25 days alone.

Without deal velocity by stage, operators cannot diagnose the root cause of missed forecasts. A COO running a weekly revenue review who sees $380K in pipeline at risk needs to know whether those deals are stuck in discovery or stalled at legal review. The intervention is completely different.

A typical 80-person SaaS company tracking deal velocity for the first time discovers that 40–60% of their total cycle time sits in just one stage. That single finding changes how they allocate rep time, structure handoffs, and set forecast confidence expectations.

Deal velocity formula

Deal Velocity = Total Days in Stage / Number of Deals That Passed Through Stage

Example:
Stage: "Proposal Sent"
Total days across 24 deals in Q1: 312 days
Deal Velocity (Proposal Sent) = 312 / 24 = 13 days per deal

What each component means:

  • Total Days in Stage: The cumulative number of days all deals spent in a given stage during the measurement period. Exclude deals that are still open in that stage unless you are calculating a rolling average.
  • Number of Deals: Count only deals that exited the stage (moved forward or were disqualified). Including stuck deals inflates the average.

Some teams calculate weighted deal velocity, which adjusts for deal size. A $200K deal sitting 20 days in negotiation matters more than a $15K deal sitting the same duration. Weighted deal velocity multiplies days-in-stage by deal value before averaging.

Deal velocity benchmarks by company type

How deal velocity varies across B2B company segments. Ranges represent average days per mid-pipeline stage.

SegmentGoodAverageBelow AverageAction Needed
Early-stage SaaS (<$1M ARR)5–8 days9–14 days15+ daysShorten discovery calls; tighten qualification criteria
Growth SaaS ($1–10M ARR)8–12 days13–18 days19+ daysReview handoff process between stages; check for missing decision-makers
Scale SaaS ($10M+ ARR)10–16 days17–22 days23+ daysAudit legal/procurement stage; add champion enablement content
B2B Services / Agencies6–10 days11–16 days17+ daysReduce proposal turnaround time; standardize scope documents

Sources: Pavilion COO Survey 2025, Ebsta B2B Sales Benchmark Report 2025, industry-observed ranges based on operator reports.

Common mistakes when measuring deal velocity

1. Averaging across all stages instead of measuring per stage

The whole point of deal velocity is stage-level granularity. A single average across the pipeline masks the bottleneck. Calculate velocity for each stage separately, then compare.

2. Including deals that never leave a stage

Deals that have been sitting in "discovery" for 90 days are not contributing useful data to your velocity calculation — they are dead deals that reps have not disqualified. Set a cutoff (e.g., 2x the average stage duration) and flag these as stale instead.

3. Ignoring deal size when comparing velocity

A $500K enterprise deal and a $20K self-serve deal should not be measured on the same velocity curve. Segment by deal size or ACV tier before drawing conclusions. Otherwise, a flood of small deals will make your velocity look artificially fast.

4. Measuring velocity without tracking stage entry timestamps

If your CRM does not log when a deal entered and exited each stage, velocity calculations are guesswork. Ensure your CRM hygiene process enforces timestamp logging on every stage change.

How Fairview tracks deal velocity automatically

Fairview's Pipeline Health Monitor connects to your CRM — HubSpot, Salesforce, or Pipedrive — and calculates deal velocity per stage without manual exports or spreadsheet formulas. Each deal's stage timestamps are pulled automatically, and velocity is computed in real time.

The dashboard shows average days per stage for the current quarter, with a comparison to the prior period. Deals exceeding 1.5x the stage average are flagged as "at risk" in the weekly operating view. Instead of scanning the CRM deal-by-deal, you see a ranked list of stalled opportunities with the stage where momentum stopped.

Fairview also segments velocity by deal size, rep, and source channel — so you can see whether enterprise deals from inbound convert faster through negotiation than outbound-sourced deals.

See how Pipeline Health Monitor works

Deal velocity vs sales velocity

People often use deal velocity and sales velocity interchangeably. They measure different things.

Deal VelocitySales Velocity
What it measuresDays per stage for individual dealsRevenue throughput across the entire pipeline per day
When to use itDiagnosing where specific deals stallForecasting total pipeline output for the quarter
Key differenceGranular, stage-level, deal-specificAggregate, portfolio-level, revenue-weighted
Who tracks itRevOps managers, sales managersCOOs, VPs of Sales, operators

Deal velocity tells you where deals get stuck. Sales velocity tells you how much revenue the pipeline produces over time. Use deal velocity to fix bottlenecks. Use sales velocity to forecast revenue and set capacity plans.

FAQ

What is deal velocity in simple terms?

Deal velocity is the average number of days a deal spends in each stage of your sales pipeline. It measures how fast opportunities move from one stage to the next. A lower number means deals progress faster, which typically correlates with higher close rates and shorter overall sales cycles for B2B companies.

What is a good deal velocity for a B2B SaaS company?

For mid-market B2B SaaS ($1–10M ARR), a healthy deal velocity is 8–12 days per mid-pipeline stage. Early-stage companies often move faster at 5–8 days. If any stage consistently exceeds 18 days, it usually signals a process issue — a missing decision-maker, unclear next steps, or stale deals inflating the average.

How do you calculate deal velocity?

Divide the total number of days all deals spent in a given stage by the number of deals that exited that stage. For example, if 24 deals spent a combined 312 days in "Proposal Sent," your deal velocity for that stage is 13 days. Calculate this per stage, not as a single pipeline average.

What is the difference between deal velocity and sales velocity?

Deal velocity measures how fast individual deals move through pipeline stages, expressed in days per stage. Sales velocity measures total revenue throughput across all deals, expressed in dollars per day. Deal velocity diagnoses bottlenecks at the opportunity level. Sales velocity forecasts aggregate pipeline output for the quarter.

How often should you track deal velocity?

Weekly. Deal velocity shifts faster than most pipeline metrics because a single stalled deal can skew a stage's average within days. Reviewing it weekly during your revenue review gives you enough signal to intervene before deals go cold without overreacting to daily noise.

How do you improve deal velocity?

Identify the slowest stage and diagnose the root cause. Common fixes: add mutual action plans to keep buyers accountable, require multi-threaded contacts before advancing past discovery, set automatic reminders when deals exceed 1.5x the stage average, and disqualify dead deals that inflate your numbers. Focus on one stage at a time.

Related terms

  • Sales Velocity — measures total revenue throughput across the entire pipeline per day, combining deal count, win rate, average deal size, and cycle length.
  • Win Rate — the percentage of deals that reach closed-won out of total qualified opportunities in a given period.
  • Sales Cycle Length — the total number of days from first meaningful contact to closed-won, measured across all pipeline stages combined.
  • Pipeline Health — an aggregate assessment of pipeline quality, factoring in coverage ratio, deal aging, stage distribution, and velocity.
  • Pipeline Coverage Ratio — the ratio of total weighted pipeline to quota or revenue target, typically expressed as a multiple (e.g., 3.2x).

Fairview is an Operating Intelligence Platform that tracks deal velocity automatically alongside sales velocity, pipeline health, and win rate. Start your free trial →

Siddharth Gangal is Founder at Fairview. He has spent the past decade building revenue operations systems for B2B SaaS companies from seed stage through Series C.

Ready to see your data clearly?

Stop reporting on last week.
Start acting on this week.

10 minutes to connect. No SQL. No engineering team. Your first dashboard is built automatically.

See your data in Fairview Start 14-day free trial

No credit card required · Cancel anytime · Setup in under 10 minutes