Back to Blog
Deal velocity is a sales metric that measures how much revenue a pipeline generates per unit of time. It combines four inputs into a single formula: number of active deals, average deal value, win rate, and average sales cycle length. The formula is (Number of Deals × Average Deal Value × Win Rate) ÷ Average Sales Cycle Length, and the output is a revenue-per-day figure representing the throughput of your current pipeline. Revenue operations teams use deal velocity to diagnose pipeline health in real time, identify where the sales process is slowing down, and compare performance across segments, deal types, or sales reps.
Key Takeaways
- Deal velocity formula: (Deals × Avg Deal Value × Win Rate) ÷ Sales Cycle Length. The output is revenue per day, not a count or a percentage.
- Four distinct inputs: Each variable is a measurable lever; because the formula is multiplicative, a change in any single input has a compounding effect on throughput.
- Deal velocity ≠ pipeline velocity: Same formula, different scope. Deal velocity diagnoses current conversion efficiency; pipeline velocity projects forward revenue output.
- HubSpot’s native “Deal Velocity” report measures days to close only, not the four-factor formula. The full calculation requires custom property configuration.
- Sales cycle length is not stored natively in HubSpot or Salesforce. It requires a custom calculated property before the formula is usable.
Why Deal Velocity Matters for RevOps Teams
The most commonly tracked pipeline metrics (deal count, win rate, average deal size, and sales cycle length) are typically managed in separate dashboards. A team can show a healthy win rate while sales cycles quietly extend, or a full pipeline by count while average deal value has declined. Neither problem surfaces until a quarter closes short.
Deal velocity solves this by combining all four inputs into a single throughput figure. Because the formula is multiplicative, it captures interactions between variables that isolated metrics miss: a 20% win rate improvement paired with a 40% increase in cycle length produces a net velocity decline, even though one metric moved in the right direction.
A pattern we observe in scale-up B2B implementations is that pipeline health degrades as sales teams grow past 10 reps without standardized stage definitions. This distorts all four velocity inputs simultaneously, making the combined formula the first place the problem becomes visible.
Before vs. After: What Deal Velocity Changes
Without vs With Deal Velocity Tracking Comparison
| Without Deal Velocity Tracking | With Deal Velocity Tracking | |
|---|---|---|
| Pipeline visibility | Without: Four metrics tracked independently, no combined view | With: Single throughput figure surfaces the net effect of all inputs |
| When problems surface | Without: After quarters close and revenue targets are missed | With: In real time, as individual inputs shift |
| Diagnosis approach | Without: “Pipeline looks full" with no visibility into conversion efficiency | With: Formula narrows the failing input: volume, value, win rate, or speed |
| Cross-functional accountability | Without: Marketing, Sales, and RevOps optimize for separate metrics | With: Shared formula creates a shared definition of pipeline health |
| Forecast inputs | Without: Pipeline value × win rate only | With: Incorporates cycle length as a timing variable for more accurate close-date estimates |
Scope
This article covers the deal velocity formula, its four component inputs, a worked example using published benchmarks, the distinction between deal velocity and pipeline velocity, and CRM configuration in HubSpot. It does not cover attribution methodology or pipeline forecasting, which is partially addressed in our blog, “Revenue Forecasting for PE Firms.”
Deal Velocity: Core Definition
Deal velocity is a revenue operations metric that expresses how efficiently a sales pipeline converts active opportunities into revenue over time. Unlike win rate or average deal size, which each capture one dimension of sales performance, deal velocity captures the combined effect of all four pipeline variables in a single throughput figure.
The formula treats the sales process as a system: volume (number of deals) multiplied by quality (average deal value and win rate), divided by time (average sales cycle length). Because the relationship is multiplicative, the metric is sensitive to changes in any input. Improvements compound, and a decline in a single variable reduces throughput even when the other three are stable.
Deal velocity formula
01
Number of deals
Qualified active opportunities in the pipeline during the period
●Native in HubSpot02
Average deal value
Mean Amount on deal records in the measured period
●Native in HubSpot03
Win rate
Closed Won ÷ total closed deals in the same period
●Calculated report04
Sales cycle length
Avg days from deal creation to Closed Won
●Custom property
Revenue operations teams use deal velocity primarily as a diagnostic instrument. A stable or improving figure indicates a healthy, converting pipeline. A declining figure, even when total pipeline value or deal count is growing, signals a structural problem in one of the four inputs that requires targeted intervention. This is one of the core metrics tracked within a revenue operations framework.
Input 1: Number of Deals
The deal count represents the number of qualified, active opportunities in the pipeline during the measurement period. “Qualified” is the operative word. Including pre-qualification or early-touch deals inflates the count, raises apparent velocity, and masks win rate problems downstream.
In CRM terms, this typically means deals in active pipeline stages that have passed an explicit qualification gate, excluding any first-touch or lead-stage entries. For HubSpot users, deal count is pulled from deal records filtered by pipeline and date range, native and straightforward to report. The challenge is upstream: if qualification criteria are not consistently applied across reps and deal types, the input loses diagnostic value regardless of how the report is configured.
Input 2: Average Deal Value
Average deal value is the mean Amount across deals in the measured period. HubSpot stores this natively on every deal record, making it the most readily available of the four inputs.
The primary measurement risk is outlier distortion. A single unusually large or small deal in a low-volume pipeline can shift the average enough to produce misleading velocity readings. For teams with significant deal size variance across segments, calculating separate velocity figures by deal tier (SMB, mid-market, enterprise) produces more actionable signal than a single blended average. Mid-market B2B SaaS deals (ACV $15K–$100K) carry meaningfully different cycle lengths and win rates than enterprise deals, and blending them obscures both.
Input 3: Win Rate
Win rate is the percentage of deals closed as Closed Won over total deals closed in the measurement period. It is not stored as a standalone property in HubSpot. Calculate it by dividing Closed Won deal count by total closed (won + lost) deal count over the same window.
Win rate is the input most sensitive to qualification drift and competitive positioning changes. A 5-percentage-point decline, from 25% to 20%, produces a 20% reduction in deal velocity even with stable volume, deal size, and cycle length. This sensitivity makes win rate the first input to examine when velocity declines without an obvious pipeline volume or speed explanation. Per HubSpot’s 2024 State of Sales report, the average B2B win rate across all pipeline stages is approximately 21%, a useful calibration point, though segment and deal type significantly affect what’s realistic for a given pipeline.
Input 4: Average Sales Cycle Length
Average sales cycle length is the mean number of days from deal creation to Closed Won. This is the only input not stored natively in HubSpot. It requires a custom calculated property before it can be used in reports or the velocity formula.
Sales cycle length is also the input most commonly affected by process drift. As sales teams grow and stage definitions become inconsistent, deals accumulate in middle stages (particularly proposal or negotiation) and total cycle time extends without a visible point of failure. This makes it both the hardest input to maintain accurately and the most revealing diagnostic when it shifts. For setup instructions, see the HubSpot Knowledge Base guide to calculated properties. The broader CRM data architecture that supports accurate cycle length calculation depends on clean deal records, which is why data quality in HubSpot is a prerequisite for reliable velocity measurement.
Deal Velocity vs. Pipeline Velocity: What’s the Difference?
Deal Velocity vs Pipeline Velocity Comparison
| Deal Velocity | Pipeline Velocity | |
|---|---|---|
| What it measures | Deal Velocity: Revenue efficiency of currently active deals | Pipeline Velocity: Total revenue throughput of the pipeline as a system |
| Level of analysis | Deal Velocity: Active opportunities, aggregated by segment or rep | Pipeline Velocity: Full pipeline aggregate |
| Primary question | Deal Velocity: Are my current deals converting efficiently? | Pipeline Velocity: How much revenue will this pipeline produce over time? |
| Primary use case | Deal Velocity: Diagnosing bottlenecks; comparing reps, segments, deal types | Pipeline Velocity: Revenue forecasting; capacity planning |
| What a decline signals | Deal Velocity: Stage friction, win rate erosion, or deal quality issues | Pipeline Velocity: Volume shortfall, conversion problems, or pipeline structure gaps |
| CRM native support | Deal Velocity: Not fully native in HubSpot or Salesforce; requires configuration | Pipeline Velocity: Same: formula inputs must be assembled from separate reports |
Both metrics use the same four-factor formula. The distinction is scope: deal velocity is a real-time health check on current conversion efficiency; pipeline velocity is a forward-looking model of total revenue output. Most organizations start with one and use the same report for both purposes. The confusion in the market is compounded by CRM naming: HubSpot’s native “Deal Velocity” report measures average days to close (a single variable), while its “Sales Velocity” report approximates the four-factor formula. Neither is labeled “pipeline velocity.”
How to Calculate Deal Velocity: A Worked Example
Using published benchmarks: average B2B win rate of approximately 21% (HubSpot State of Sales, 2024) and mid-market B2B SaaS cycle lengths of 30–90 days (Optifai Sales Ops Benchmark, 2025).
Baseline scenario: mid-market B2B team
- Active qualified deals: 50
- Average deal value: $35,000
- Win rate: 22%
- Average sales cycle: 60 days
(50 × $35,000 × 0.22) ÷ 60 = $385,000 ÷ 60 = $6,417/day
Approximately $192,500/month in expected revenue throughput.
Same inputs: cycle length extends from 60 to 80 days
(50 × $35,000 × 0.22) ÷ 80 = $385,000 ÷ 80 = $4,813/day
A 33% increase in sales cycle length, with no deals lost and no change in win rate or deal count, produces a 25% decline in daily revenue throughput. No single-variable report surfaces that relationship. Deal velocity does.
When to Use Deal Velocity
When Pipeline Volume Looks Healthy But Revenue Is Missing
Deal velocity is most useful when headline metrics (total pipeline value and deal count) appear adequate but revenue targets are being missed. Coverage ratio tells you how much pipeline exists; deal velocity tells you whether it is converting efficiently. Teams that have historically managed pipeline by coverage ratio alone often find that introducing velocity as a secondary check reveals a cycle length or win rate problem that the coverage number was masking.
When Comparing Performance Across Reps, Segments, or Periods
Because deal velocity accounts for both deal size and cycle time, it normalizes comparisons that raw win rate or deal count cannot. A rep who closes fewer, larger deals in longer cycles can be compared to a high-volume rep on equal terms. Similarly, quarter-over-quarter velocity trends reveal whether process improvements or headcount additions have produced measurable throughput gains, not just more activity.
When Diagnosing Which Pipeline Input Is Failing
When deal velocity declines, the formula immediately narrows the diagnosis. Stable deal count and deal value with declining velocity points to win rate or cycle length. Stable win rate and cycle length with declining velocity points to pipeline volume. This prevents a common mistake: adding pipeline volume to address what is actually a stage-friction or qualification problem.
When Building Revenue Forecasts
A $2M pipeline with a 30-day average cycle is a fundamentally different forecast position than the same pipeline value with a 90-day average cycle. Incorporating cycle length into forecast models produces more accurate timing estimates than pipeline value and win rate alone. Deal velocity is the single metric that forces that input into the conversation.
When NOT to Use Deal Velocity
When CRM Data Integrity Is Unresolved
A velocity calculation built on deals with missing Amount values, inconsistent Closed Won timestamps, or unsegmented pipelines produces a number that can actively mislead revenue decisions. Before building deal velocity reporting, establish that CRM data hygiene standards are in place. A metric that appears precise but reflects dirty inputs is worse than no metric.
When Pipeline Sample Size Is Too Small
The formula requires enough closed deals per measurement period to produce stable averages for win rate and cycle length. For teams with fewer than 15–20 closed deals per period, a single large deal closing or missing can shift velocity significantly. In early-stage or low-volume pipelines, tracking the four inputs individually provides more reliable signal than combining them into a formula that amplifies variance.
When Attribution Is the Primary Question
Deal velocity answers how efficiently your pipeline is converting existing deals. It does not answer which channels, campaigns, or activities produced those deals, or where future investment should go to improve pipeline quality. If the primary question is credit allocation or marketing ROI, deal velocity is the wrong tool.
Use Cases
VP of Marketing Operations at a PE-Backed Scale-Up
The Problem: A VP of MarOps at a PE-backed B2B SaaS company is tracking win rate, pipeline value, and deal count in separate dashboards. Pipeline coverage looks adequate at 4x against target, but the team is consistently missing quarterly revenue targets. No individual metric explains the gap.
The Fix: Introducing deal velocity as a combined diagnostic reveals that average sales cycle length has extended from 45 days to 72 days over three quarters, driven by deals stalling in the “Proposal Sent” stage. Win rate and deal count are stable. The formula isolates cycle length as the failing input, directing the intervention to proposal-stage process rather than pipeline volume. HubSpot’s “Time Spent in Deal Stage” report (Sales Analytics, Pro and Enterprise) confirms which stage is accumulating the friction.
The Outcome: A common pattern in this scenario is that isolating the stall stage and addressing follow-up timing within that specific stage produces measurable velocity improvement within one quarter, without increasing pipeline spend or headcount.
Sales Ops Practitioner Building a RevOps Dashboard
The Problem: A Sales Ops manager building a RevOps performance dashboard for a 25-rep team has separate panels for deal count, pipeline value, win rate, and average deal size. Leadership asks for a single pipeline health indicator rather than four separate numbers to reconcile.
The Fix: Configuring deal velocity requires one custom property setup: a “Sales Cycle Length (Days)” calculated property (Time Between: Create Date → Close Date, condition: Closed Won only) in Settings > Properties > Deals. Once built, a custom report combining all four inputs produces the composite metric. The four component metrics remain as drill-down panels, visible when the composite signals a problem rather than as the primary view.
The Outcome: The single composite metric reduces diagnostic time from multi-panel review to a single dashboard check, with the underlying inputs surfaced on demand. For teams approaching the reporting limits of Sales Hub Professional, when HubSpot Pro becomes a bottleneck covers when this configuration requires an Enterprise upgrade.
B2B Marketing Leader Demonstrating Pipeline Contribution
The Problem: A marketing leader at a mid-market B2B company wants to show that marketing-sourced deals perform differently than outbound or referral-sourced deals, not just in volume but in conversion quality and speed. Standard pipeline reports show deal count by source; they don’t surface whether marketing-sourced leads are easier or faster to close.
The Fix: Segmenting deal velocity by deal source in HubSpot’s custom report builder allows marketing to demonstrate throughput contribution in revenue-per-day terms, broken out by source. If marketing-sourced deals carry a higher win rate or shorter cycle, the velocity calculation surfaces that advantage in a metric revenue leadership already tracks. This connects automated lead qualification outcomes directly to pipeline throughput metrics.
The Outcome: A marketing team that measures velocity by source builds a more defensible ROI case than one measuring lead volume alone, and establishes a shared metric with Sales and RevOps rather than a separate marketing-only KPI.
Related Concepts
Deal Velocity vs. Sales Cycle Length
Sales cycle length is one input to deal velocity, not a substitute for it. Teams that optimize for shorter cycles alone may achieve that improvement by disqualifying deals earlier, which reduces cycle length while also reducing deal count and can leave velocity unchanged or lower. Deal velocity captures the net effect: whether a shorter cycle is producing more revenue throughput or simply generating more early losses.
Deal Velocity vs. Pipeline Velocity
Both use the same four-factor formula; the practical distinction is when each is applied. RevOps teams typically use deal velocity week-to-week as a diagnostic check and pipeline velocity in quarterly planning as a forecasting input, two lenses on the same underlying data.
Deal Velocity vs. Attribution Metrics
Deal velocity and attribution models are designed for different questions and are not interchangeable. Deal velocity answers: how efficiently is my pipeline converting right now? Attribution answers: which activities produced the deals in that pipeline? A common RevOps measurement mistake is using attribution data, which is retrospective and allocation-focused, as a proxy for real-time pipeline health. Deal velocity is the right instrument for the health question.
Common Implementation Pitfalls
-
Treating HubSpot’s native “Deal Velocity” report as the four-factor formula. HubSpot’s built-in Deal Velocity report in Sales Analytics measures average days to close: a single-variable metric, not the revenue throughput formula. Teams who assume this represents the full formula are tracking time-to-close, not revenue throughput. The correct approach is a custom report combining all four inputs, or HubSpot’s“ Sales Velocity” report as an approximation (both require Sales Hub Professional or Enterprise).
-
Skipping the calculated property for sales cycle length. Sales cycle length is not stored natively in HubSpot. Using “Time Spent in Deal Stage” as a proxy gives stage-level data, not full-cycle time. The correct setup requires a “Time Between” calculated property (Create Date → Close Date, condition: Closed Won only). Without this property, the most diagnostically sensitive input in the formula is missing or estimated.
-
Including unqualified deals in the deal count. Including early-stage or pre-qualification opportunities inflates the deal count, raises apparent velocity, and masks win rate problems downstream. The count input should reflect only opportunities that have passed an explicit qualification gate, consistently applied across reps, pipelines, and deal types.
-
Calculating velocity from too small a sample. For teams with fewer than 15–20 closed deals per measurement period, win rate and cycle length averages fluctuate too widely to support confident diagnosis. A single outlier deal can shift the composite figure significantly. Extending the measurement window to a rolling 90 days stabilizes both inputs before the formula produces reliable signal.
-
Using a single blended velocity number for a mixed pipeline. Blending SMB, mid-market, and enterprise deals into one average produces a figure that accurately represents none of the segments. Per Optifai’s 2025 benchmark, mid-market B2B SaaS cycles average 30–90 days; enterprise deals commonly exceed 180 days. Segmented velocity reports, broken out by deal type, size tier, or source, provide the diagnostic specificity a blended figure obscures.
Next Steps
Deal velocity is a foundational RevOps metric, but it is only as reliable as the CRM infrastructure behind it. Sales cycle length requires a custom calculated property. Win rate requires clean stage-close data. Deal count requires consistently applied qualification criteria. If any of those foundations are missing, the formula produces a number that looks precise and misleads quietly.
Hypha HubSpot Development is a Diamond Partner agency specializing in technically complex HubSpot implementations for B2B companies. We work with RevOps and marketing operations teams on the property structures, reporting frameworks, and data quality standards that make metrics like deal velocity operational rather than aspirational.
Our CRM configuration work typically includes:
- Calculated property setup for sales cycle length and other derived RevOps metrics
- Custom report and dashboard configuration for pipeline performance tracking
- CRM data audit and cleanup to establish reliable measurement baselines
- Pipeline stage standardization to ensure velocity inputs are consistent across reps and teams
If your team is building a RevOps measurement infrastructure and wants to get the underlying configuration right, we’d welcome the conversation.
Frequently Asked Questions
Deal velocity is a sales metric measuring how much revenue a pipeline generates per unit of time. Formula: (Number of Deals × Average Deal Value × Win Rate) ÷ Average Sales Cycle Length. The output is revenue per day, a measure of pipeline conversion efficiency rather than deal count or stage progress.
Multiply the number of qualified active deals by average deal value and win rate, then divide by average sales cycle length in days. Example: (50 × $35,000 × 0.22) ÷ 60 days = $6,417/day. All four inputs must be measured over the same period for the formula to produce reliable results.
Both use the same four-factor formula. Deal velocity examines the revenue efficiency of current active opportunities, a diagnostic metric. Pipeline velocity uses the same inputs to model total forward revenue output, a forecasting metric. The terms are used interchangeably in most sales content and across CRM platforms.
A decline points to one of four root causes: fewer qualified deals (volume), lower average deal value, a falling win rate, or a longer average sales cycle. Because the formula is multiplicative, identifying which input moved reveals the appropriate intervention, and the response differs significantly depending on whether the problem is volume, quality, or speed.
Yes. Sales cycle length is one input to the formula. Optimizing for a shorter cycle alone can actually reduce velocity if it leads to faster disqualification: fewer deals in the numerator offset the improvement in the denominator. Deal velocity captures the net effect of all four inputs simultaneously.
HubSpot includes a “Deal Velocity” report in Sales Analytics that measures average days to close, a single-variable metric rather than the four-factor formula. A “Sales Velocity” report approximates the full formula. Both require Sales Hub Professional or Enterprise. For precise four-factor control, a custom report using a calculated “Sales Cycle Length (Days)” property is recommended.
Deal velocity is most useful as a trend metric compared against your own baseline rather than industry averages. For calibration: HubSpot’s 2024 State of Sales reports an average B2B win rate of approximately 21%; Optifai’s 2025 benchmark places mid-market B2B SaaS cycle lengths at 30–90 days. Segment-specific baselines are more reliable than cross-industry figures.
The most common cause is sales cycle length extension, with deals accumulating in middle stages (proposal, negotiation) without closing faster or at higher rates. A full pipeline by count with extending cycle times produces declining velocity even if win rate and deal value are stable. Stage-level time analysis in HubSpot isolates where cycle time is accumulating.
Yes. Segmenting velocity by deal source allows marketing to demonstrate pipeline contribution in revenue throughput terms. If marketing-sourced deals carry a higher win rate or shorter average cycle, velocity calculations surface that advantage in a metric that revenue leadership already tracks.
Monthly is the standard starting cadence, frequent enough to identify trends and stable enough to avoid noise from small sample variance. Compare monthly figures against a rolling three-month average to normalize seasonal variation. High-volume pipelines with average cycles under 30 days benefit from weekly measurement.
Related Articles
- What Is Revenue Operations (RevOps)? Definition & Architecture: Covers the RevOps framework and pipeline health metrics that deal velocity fits into. Read before configuring a velocity dashboard.
- What Is Dirty Data? How It Corrupts AI in HubSpot: Covers how CRM data quality problems distort velocity inputs. Read before building any velocity reporting.
- HubSpot Custom Objects and Properties: A Complete Guide to CRM Data Architecture: Covers deal property configuration in HubSpot, including calculated properties for sales cycle length.
