The pipeline velocity myth

Pipeline velocity has become an obsession. Faster deals. Shorter cycles. Accelerated progression. The assumption is simple: if we can move deals through the pipeline faster, we will close more revenue.

This assumption is wrong. Speed is not the same as progress. Accelerating a broken pipeline does not fix it. It just reveals the breakage faster.

What velocity actually measures

Pipeline velocity is typically calculated as: (Number of opportunities × Win rate × Average deal value) ÷ Sales cycle length.

The formula implies that reducing cycle length — making deals move faster — directly improves revenue. But this only holds if the other variables remain constant. In practice, they do not.

Pushing deals faster through a pipeline with broken progression logic does not improve win rate. It often reduces it. Deals that needed more time to develop Trust get pushed to decision before the buyer is ready. Deals that needed more stakeholders involved get forced to close with incomplete buy-in. Deals that were never going to close get accelerated to "closed lost" instead of being properly disqualified earlier.

The velocity looks better. The outcomes do not.

The Movement problem

Movement, in ATMC terms, is the ability for opportunities to progress reliably from interest to decision. Not quickly. Reliably. The distinction matters.

A Movement-constrained pipeline is not slow because deals take too long. It is slow because deals do not progress at all. They enter the pipeline and then drift. They sit in stages that have no clear meaning. They age without advancing. Sales pushes. Buyers retreat. The pipeline looks active but feels stuck.

The solution to this is not acceleration. The solution is progression logic — a shared understanding between buyer and seller of what needs to happen at each stage, and what constitutes genuine advancement.

Why acceleration fails

When Movement is broken, acceleration fails for three reasons.

First, it mistakes activity for progress. A deal that moves from "Discovery" to "Proposal" is not necessarily progressing. It might just be that sales sent a proposal. If the buyer has not genuinely advanced in their decision process, the stage change is administrative, not meaningful. Accelerating administrative changes does not create real progress.

Second, it damages buyer relationships. Buyers have their own timeline. They have internal processes, stakeholders to consult, budgets to secure, risks to evaluate. Pushing them faster than they can move does not accelerate their decision. It creates pressure, which creates resistance, which creates stalled deals or lost trust.

Third, it obscures the real problem. When leadership focuses on velocity, the conversation becomes about speed rather than progression. Why are deals slow? Because they are not moving fast enough. This circular logic prevents diagnosis of the actual constraint — which is usually that deals lack clear progression logic, not that they lack speed.

What progression logic looks like

Progression logic is the shared understanding of what needs to happen for a deal to advance. It has two components:

Buyer-side progression: What does the buyer need to see, learn, or confirm before they can move forward? What internal steps must they complete? Who else needs to be involved? What would make them say no?

Seller-side progression: What does the seller need to provide, demonstrate, or clarify at each stage? What signals indicate genuine progression versus polite interest? When should a deal be disqualified?

When these two logics are aligned, deals progress naturally. The seller knows what the buyer needs. The buyer knows what to expect. Each stage has clear entry and exit criteria. Movement happens because both parties understand the path.

When these logics are misaligned, deals drift. The seller thinks they are progressing because they completed their activities. The buyer thinks they are still evaluating because they have not completed theirs. Neither is wrong — they are just operating on different assumptions.

The forecast problem

Broken Movement creates broken forecasts. When pipeline stages have no shared meaning, when deals can sit in "Negotiation" for months without negotiating, when "Verbal Commit" does not actually indicate commitment — forecasting becomes guesswork.

Leadership looks at the pipeline and sees numbers. They see deals in late stages. They see expected close dates. What they cannot see is whether those deals are actually progressing or just administratively categorised.

The result is forecasts that shift late. Deals that were "90% likely" slip to next quarter. Commits become maybes. The pipeline that looked healthy reveals itself to be full of stalled opportunities that were never going to close on time.

Velocity metrics make this worse, not better. They create pressure to move deals through stages faster, which inflates late-stage pipeline, which makes forecasts look stronger, which makes the eventual miss more painful. This dynamic is explored further in The forecast that satisfies the board but surprises no one.

Fixing Movement

The fix for broken Movement is not acceleration. It is alignment.

• Define what each pipeline stage actually means — from the buyer's perspective, not just the seller's
• Establish clear criteria for stage advancement that both parties would recognise
• Build qualification into progression — deals that cannot advance should be disqualified, not pushed
• Create visibility into buyer-side progress, not just seller-side activity
• Accept that some deals will take longer, and that is fine if they are genuinely progressing

A pipeline with clear progression logic will naturally move at the right pace. Deals that should close quickly will close quickly. Deals that need more time will take more time. Deals that were never going to close will be identified and removed early.

This is not slower than velocity-focused approaches. It is more reliable. And reliability is what forecasts actually need.