At a glance
Pipeline velocity combines opportunity volume, value, win rate and sales-cycle length. A change in the total doesn’t tell you what to fix. This guide helps marketing and sales inspect the underlying stages, identify missing evidence or delayed decisions and assign a practical action to the right team.
Your marketing team is generating enquiries, your sales team has open opportunities, but revenue is taking longer than expected. You’re asked to improve pipeline velocity. Before adding another campaign, find out which decisions are taking longer and what your team can do to help.
Pipeline velocity summarises opportunity volume, average value, win rate and sales-cycle length. It’s useful for opening the discussion, but the total can’t locate the blockage. It can also change because the mix of deals has changed, even when the underlying process hasn’t.
Define the milestone before explaining the improvement
Our focused ABM programme for an AI software firm reports a reduction from a nine-month business average to three months from initial conversation to pilot launch. Eight enterprise accounts entered pipeline through tailored pilots, with more than £1.7m in potential contract value. Pilot launch is the relevant milestone; the figure should not be read as time to recognised revenue.
The published delivery account explains several connected interventions: selecting relevant clusters, adapting the proposition, developing individual sales assets and working with sales as conversations progressed. It does not isolate the causal effect of one asset or one channel. The useful diagnostic lesson is to define the decision being advanced and connect the support to the account’s specific requirements.
For an illustrative stalled evaluation, record the current milestone, the unresolved buyer question, who can answer it and the next agreed customer action. If the obstacle is integration evidence, commission that evidence. If the initiative has no confirmed owner or priority, more collateral may be premature. Do not assume every slow deal has a marketing-content problem.
Then measure the appropriate transition without changing its definition halfway through the review. A faster route to a pilot, a proposal and a signed contract are different outcomes and should remain separately labelled.
Check what goes into your velocity figure
Salesforce describes the standard sales-velocity formula using opportunities, deal value, win rate and cycle length. To use it responsibly, specify the population and period behind each input.
Don’t take the current open opportunity count, last year’s average won deal value and this month’s win rate without explaining the mismatch. Those values may describe different markets, stages and levels of maturity.
Use consistent opportunity definitions and comparable cohorts where possible. State whether the cycle begins at lead creation, qualification or opportunity creation, and whether it ends at a won decision or any closed decision. Different definitions produce different answers.
The output is a modelled rate under the chosen inputs, not a promise of daily cash receipts.
What a change in sales-cycle length does to the number
Imagine a fictional pipeline with 40 opportunities, £50,000 average value, a 25% win-rate assumption and a 100-day average cycle. The formula produces £5,000 per day: 40 × £50,000 × 0.25 ÷ 100.
If the cycle falls to 80 days while everything else remains unchanged, the result becomes £6,250 per day, a 25% increase. That is the arithmetic effect of the assumption, not proof that shortening every process by twenty days is feasible.
Check which deals became faster. If small, straightforward opportunities closed while the larger ones remained stalled, an improved average can hide the work your team still needs to do. Review the open pipeline alongside completed deals.
Find which part of the pipeline has changed
| Driver | Diagnostic question | Possible action if supported by evidence |
|---|---|---|
| Opportunity count | Are genuinely qualified opportunities entering? | Improve acquisition or qualification |
| Deal value | Has the use-case or customer mix changed? | Review scope and segment strategy |
| Win rate | Which comparable opportunities are being won or lost? | Address recurring decision barriers |
| Cycle length | Where do eligible deals wait or repeat work? | Resolve a specific stage dependency |
| Data quality | Have definitions, dates or exclusions changed? | Repair reporting before changing the campaign |
Give the problem to the team that can address it. Commercial review may need clearer terms; technical validation may need better evidence; low opportunity volume may point back to targeting. “Make the pipeline faster” isn’t a brief any of those teams can act on.
Inspect stage transitions and ageing together
For each meaningful stage, record entry, exit, current age and the next required decision. Distinguish time spent actively evaluating from time waiting for an owner, evidence or customer action.
HubSpot’s stage-calculated property documentation distinguishes different measures of time in stage. Check exactly what your reporting field measures; a completed-stage duration and the age of a record still in that stage answer different questions.
Review the open deals as well as the closed ones. A cycle measure based only on completed deals can look healthy while difficult opportunities accumulate. Show open-deal ageing separately and retain unresolved outcomes rather than excluding them from the story.
Use medians and distributions alongside averages where useful. A few very long deals can move an average, while a single median can still hide a problematic tail.
When technical questions are delaying the decision
Suppose a comparable cohort of opportunities progresses steadily through initial discovery but slows at technical validation. Sales notes repeatedly mention unanswered integration questions and unclear responsibility for confirming requirements.
The appropriate intervention may be a technical evidence pack and an agreed review with the relevant stakeholder. Increasing top-of-funnel volume would add more work without addressing the observed delay.
Before implementing the change, define what improvement would look like: fewer unresolved validation questions, shorter waiting time after requirements are received or a higher share progressing by a fixed cohort age. Keep the stage-entry criteria stable.
Then review whether the intervention happened and whether the pattern changed. A before-and-after improvement is useful operational evidence, but other changes may also contribute. Avoid calling it a proven causal uplift without a suitable design.
Compare similar types of opportunities
Separate materially different sales motions, such as new business and expansion, simple and complex deployments, or different markets. A shift towards larger strategic deals may lengthen the cycle while improving contribution potential.
Don’t conclude that a segment is worse solely because its velocity is lower. Compare the economics, effort and strategic purpose. The measure is a decision aid within a business model, not a universal ranking of all opportunities.
Keep source cohorts visible if evaluating demand generation. A campaign’s apparent velocity may reflect which accounts sales chose to work or how quickly the team acted. Follow-up completion and qualification consistency belong in the review.
Inspect repeated stages and stalled open deals
A deal can leave a stage and return to it. If the report only measures the latest completed visit, it may hide repeated rework. Track both current age and cumulative time where the system and decision require them, while making the definition clear.
Look at the reason for re-entry. A proposal returning to discovery may indicate that the original problem was not sufficiently qualified. A technical review reopening after a scope change may be a legitimate response to new requirements. The same numerical pattern can require different action.
Review open deals with no agreed next step separately from those waiting for a scheduled customer decision. An opportunity can be old without being neglected, and it can be relatively new while already lacking a credible route forward.
Ask the owner to provide evidence for the next stage, not merely a predicted close date. A repeatedly postponed date should prompt investigation of the underlying decision rather than another adjustment to the forecast field.
Avoid improving the metric by changing the population
Closing stale opportunities can improve data quality, but it may also change the reported count, win rate and average cycle. Explain the cleanup separately from a genuine improvement in selling effectiveness.
Likewise, excluding lost deals from one cycle measure and including them in another can make period comparisons misleading. Keep definitions stable or restate the comparison using consistent rules. Document material changes in stage criteria and opportunity qualification.
For a management review, present a short bridge explaining why velocity changed: new opportunities, deal mix, observed win-rate movement, cycle change and definition or data corrections. This is often more informative than a single percentage movement.
Give the bottleneck an owner and a response
For each bottleneck, name the evidence, owner, intervention and review date. “Improve pipeline velocity” is too broad to execute. “Resolve the integration questions blocking six qualified accounts before their next evaluation meeting” is actionable.
Use account progression measures to understand the work within strategic accounts, and the broader demand generation measurement framework to connect acquisition with later outcomes.
The value of the headline number is the investigation it prompts. Talk to ABM Logic about a programme that addresses the account and evidence gaps behind stalled progression.
