Sales Methodology

Pipeline velocity

Pipeline velocity is the dollar amount of weighted pipeline closing per day — a realized, in-flight metric that measures how fast revenue converts through the funnel right now.

TL;DR

Pipeline velocity equals weighted closing pipeline divided by days in the window. It measures realized closing pace — not forecasted potential. The four levers are qualified count, slip rate, cycle compression, and deal size. Segment before computing: SMB and enterprise pipelines cannot share a single velocity number.

Definition

Pipeline velocity is the dollar amount of weighted pipeline that closes per day. It is a realized, in-flight metric — not a forecast. The formula takes the sum of weighted open opportunities expected to close in a period and divides by the number of days in that window. The output is one number, in dollars per day, that says how fast revenue is converting through the funnel right now.

Pipeline velocity matters because it fuses speed and dollar value in a single number. Win rate alone says nothing about pace. Cycle length alone says nothing about value. Pipeline velocity captures both, which is why revenue operators use it as the in-quarter execution metric while reserving sales velocity for forward forecasting.

A common misuse: treating pipeline velocity as a single team-wide number. Pipeline velocity is only meaningful when segmented — SMB deals at $8K per day and enterprise deals at $80K per day cannot be averaged into a useful figure. Segment first, then compute.

The formula

The pipeline velocity formula is intentionally compact: sum of weighted open pipeline expected to close in a period, divided by the number of days in that window.

Weighted pipeline

Sum of open opportunities forecast to close in the window, multiplied by stage probability. A stage-2 deal at 20% probability contributes one-fifth of its value, not the full amount.

Period length

Number of calendar days in the window. Most teams use 30, 60, or 90 days. A 90-day window suits mid-market and enterprise; 30-day windows work only in transactional SMB.

Output

Dollars of pipeline closing per day, per rep or per team. A single number that says how fast revenue is converting.

Segmentation

Compute separately by deal segment — SMB, mid-market, enterprise. Mixing segments produces a figure that describes no one.

Worked example. A mid-market team has $4.5M of open pipeline scheduled to close in the next 90 days. After applying stage weights — 20% at stage 2, 40% at stage 3, 70% at stage 4, 90% at stage 5 — the weighted total comes to $1.8M. Divide by 90 days: pipeline velocity is $20,000 per day. At a five-rep team that is $4,000 per day per rep, which sits at the low end of the mid-market benchmark.

Pipeline velocity vs sales velocity

Sales velocity is forward-looking and prescriptive. Pipeline velocity is realized and diagnostic. Operators who treat the two as interchangeable produce forecasts that look healthy and bookings that miss.

A useful analogy: sales velocity is the speed limit on the road; pipeline velocity is the speedometer. The first describes what the funnel could theoretically produce given its inputs; the second describes what it is producing right now, given current pipeline composition and stage health. A team running well below its sales velocity ceiling has a stage discipline problem.

A practical way to hold both: sales velocity sets the annual plan; pipeline velocity runs the quarter. Sales velocity tells the head of sales how many reps to hire and what quota to assign. Pipeline velocity tells the manager whether the team is on pace to hit number this week.

The 4 levers to lift pipeline velocity

Every pipeline velocity gain traces to one of four levers. Pick one per segment per quarter — chasing all four at once dilutes attention and produces no measurable lift.

1 — Lift qualified opportunity count

More qualified pipeline in the window directly raises the numerator. Focus on opportunity quality, not raw count — unqualified pipeline inflates the metric without lifting bookings.

2 — Reduce slip rate at each stage

Every deal that slips past the close window erases its weighted contribution. Tighten stage exit criteria, require a confirmed next step in CRM, and review slipped deals weekly.

3 — Compress cycle by stage gates

Cut dead time between stages. Auto-trigger the next outreach when a stage moves, enforce a 48-hour proposal SLA, and shorten procurement loops with pre-built MSAs.

4 — Raise average deal size

Deal size is direct pressure on the numerator. Test multi-product bundles, push annual prepay over monthly, and let strong reps work upmarket accounts.

Common mistakes

Pipeline velocity is simple to compute and easy to break. These five mistakes account for most of the cases where a reported velocity number fails to predict bookings.

Confusing pipeline velocity with sales velocity. Sales velocity is forward-looking potential; pipeline velocity is realized closing pace. Treating them as interchangeable produces forecasts that look healthy and bookings that miss.

Using TCV instead of ACV. Total contract value inflates multi-year deals into a single window. A three-year $300K TCV deal is $100K of ACV per year. Always normalize to ACV before plugging into the formula.

Mixing segments in a single metric. An SMB rep at $8K per day and an enterprise rep at $80K per day average to $44K, which describes neither. Segment first, then compute.

Ignoring weighted probability. Adding raw open-pipeline dollars without applying stage weight overstates velocity by 2 to 4 times. Use the forecast-category weight your CRM applies, or build one from historical conversion data.

Measuring on too-short a window. Weekly pipeline velocity for an enterprise rep is noise. Use a rolling 90-day window for mid-market and enterprise; 30-day windows only make sense in transactional SMB.

See it in the product

Pipeline velocity — tracked in a real Gangly workflow.

Gangly runs the Velocity-Per-Rep diagnostic across your pipeline — stage weights, segment splits, and four-lever coaching built into one sequence.

Frequently asked questions

What is pipeline velocity in simple terms?

Pipeline velocity is the dollar amount of weighted pipeline that closes per day. The formula takes the sum of weighted open opportunities expected to close in a period and divides by the number of days in that window. A mid-market team running at $20K per day with 30 selling days will close roughly $600K of pipeline in that window.

How is pipeline velocity different from sales velocity?

Sales velocity is forward-looking and prescriptive — it multiplies opportunities, average deal size, and win rate, then divides by cycle length, to estimate potential revenue per day. Pipeline velocity is realized and diagnostic — it measures dollars of weighted pipeline actually closing per day right now. Sales velocity tells you what the funnel could produce; pipeline velocity tells you what it is producing.

What is a good pipeline velocity benchmark for 2026?

Benchmarks vary by segment. SMB AEs target $5K to $15K per day; mid-market AEs target $10K to $40K per day; enterprise AEs target $30K to $150K per day; strategic and named-account AEs run at $100K and above per day. Compare your team to the row that matches your average contract value, not your title.

What are the main levers to increase pipeline velocity?

There are four. Lift qualified opportunity count by raising ICP-fit pipeline. Reduce slip rate by enforcing stage exit criteria and a confirmed next step on every deal. Compress cycle by tightening stage gates, proposal SLAs, and procurement loops. Raise average deal size through bundles, annual prepay, and upmarket motion. Most teams pick one lever per segment per quarter rather than chasing all four at once.

Should I use TCV or ACV in the formula?

Always use annual contract value. Total contract value inflates multi-year deals into a single window. A three-year $300K TCV deal is $100K of ACV per year — not $300K of velocity in the close month. If a team measures with TCV, the number will look high but bookings will lag.

Know the term. Run the workflow.