Pipeline velocity is the one RevOps metric that connects marketing efficiency, sales effectiveness, and revenue predictability in a single number. Most growth-stage companies track pipeline volume and close rate but ignore velocity — how fast the pipeline actually moves. Slow velocity is expensive in ways that do not show up until the board meeting. A deal sitting in "Proposal Sent" for 45 days is consuming AE time, CRM real estate, and forecast confidence while tying up marketing budget that already converted it to an opportunity.
How to calculate pipeline velocity and what it reveals
Pipeline velocity = (Number of Qualified Deals × Average Deal Value × Win Rate) ÷ Average Sales Cycle Length in days. This gives you a daily revenue throughput number: how much revenue flows through your pipeline per day under current conditions. The formula is most useful not as a single number but when segmented by lead source, deal size, or customer segment. Deals sourced from referrals might carry a longer cycle but a higher win rate, making their velocity equivalent to or better than inbound leads with a shorter cycle at lower win rates. Without calculating velocity per segment, you cannot know where to invest sales capacity or where to direct marketing budget.
Why velocity slows at predictable points
Velocity slows at predictable failure points in growth-stage revenue systems. Stage bloat is the most common: deals accumulate in the middle stages because there are no clear entry or exit criteria, so an AE leaves a deal in "Negotiation" for three weeks rather than deciding it needs to be pushed back to "Qualified" or marked lost. Follow-up gaps are the second failure: the next step is not defined at the end of every call, so the deal stalls while the rep waits for the prospect to re-engage rather than owning the next action. Approval loops are the third: pricing exceptions, legal review cycles, and discount approval chains add days or weeks to deals that could close faster with pre-defined parameters and delegation authority.
Stage exit criteria as the most reliable velocity intervention
Defining stage exit criteria and enforcing them architecturally is the highest-leverage velocity intervention I have seen in growth-stage RevOps work. Each stage has a written definition of what must be true for a deal to advance. "Qualified" means: budget confirmed, decision-maker identified, timeline established, and business pain clearly articulated. A deal cannot move to "Proposal Sent" until all four criteria are met and logged in the CRM. This is not bureaucracy — it is pipeline hygiene. The immediate effect is that some deals get pushed back to earlier stages or marked lost, which shrinks the total pipeline number but makes what remains accurate and actionable.
The velocity dashboard the revenue team looks at every Monday
The pipeline velocity dashboard has three views: overall velocity trend (is the pipeline moving faster or slower than the trailing 90-day average), velocity by stage (which stage has the longest average duration, and is that duration growing week over week), and velocity by deal size (do enterprise deals move at a fundamentally different pace than SMB, and are they being managed with the appropriate cycle time expectation). Building this in Looker, HubSpot reporting, or Zoho Analytics requires the deal stage history table, not just the current stage snapshot. Every stage change should be logged with a timestamp. HubSpot stores stage history by default in the deal activity timeline. Salesforce has the Opportunity Stage History object.