Pipeline velocity is a composite metric that measures how quickly revenue moves through the sales pipeline, calculated by multiplying the number of opportunities, average deal size, and win rate, then dividing by average sales cycle length.
Quick Answer
Pipeline velocity is a composite metric that measures how quickly revenue moves through the sales pipeline, calculated by multiplying the number of opportunities, average deal size, and win rate, then dividing by average sales cycle length.
Improving any one of the four velocity drivers increases revenue output without adding headcount.
Segment velocity by lead source to identify which marketing channels produce the highest-quality, fastest-moving pipeline.
How Pipeline Velocity Works
Pipeline velocity formula: Velocity = (# of Opportunities × Average Deal Size × Win Rate) ÷ Average Sales Cycle Length (days). For example: 100 opportunities × $50,000 average deal size × 25% win rate ÷ 90-day cycle = $13,888 revenue per day. Pipeline velocity is a powerful single metric because it surfaces the interaction between volume, deal quality, conversion efficiency, and speed — improving any one driver increases overall velocity. It's typically tracked weekly or monthly in CRM and compared period-over-period to measure revenue engine health.
Why Pipeline Velocity Matters for B2B Marketing
Pipeline velocity is more actionable than revenue as a backward-looking metric because it's predictive. A sales team with 200 opportunities at $30K average deal size and a 20% win rate over 120 days generates the same quarterly revenue projection as a team with 100 opportunities at $50K, 30% win rate, and 75-day cycle — but the second team is much more efficient and scalable. Identifying which lever to pull (more opportunities, larger deals, higher win rate, or faster cycles) requires knowing where the biggest gap vs. benchmark lies.
Pipeline Velocity: Best Practices & Strategic Application
Calculate pipeline velocity for each segment separately: by territory, by product line, by lead source, and by rep. This segmentation reveals which channels produce the highest-quality pipeline (fast-moving, high win rate) vs. volume pipeline (slow, low win rate). Prioritize improvements to the metric with the biggest gap: if win rate is 15% against a 25% benchmark, invest in competitive enablement and lead qualification; if cycle length is 180 days vs. a 90-day benchmark, invest in executive engagement and decision-acceleration content.
Agency Perspective: Pipeline Velocity in Practice
MV3 Marketing builds pipeline velocity dashboards as part of our analytics setup engagements — giving revenue leaders a weekly view of the four underlying drivers and trend lines that predict next quarter's bookings with high accuracy.
Frequently Asked Questions: Pipeline Velocity
Pipeline velocity is a composite metric that measures how quickly revenue moves through the sales pipeline, calculated by multiplying the number of opportunities, average deal size, and win rate, then dividing by average sales cycle length.
Weekly tracking with a 30-day rolling average smooths noise and reveals genuine trends. Monthly snapshots are sufficient for board-level reporting. Daily tracking is only useful for high-volume transactional pipelines.
Diagnose using benchmarks: if win rate is below 20%, focus there first (it has a direct multiplier effect). If cycle length is double the industry benchmark, focus on deal acceleration. If deal size is low, evaluate upmarket positioning or bundling strategies.
Yes — multiply daily pipeline velocity by the number of selling days in the quarter to get a bookings forecast. Compare against quota and identify the gap, then calculate how much additional opportunity volume or win rate improvement is needed to close it.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes analytics setup for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
