Decision Velocity: How Fast Your Buyers Say Yes or No

Decision velocity is the speed at which open deals reach a decision. A win counts. A loss counts too. A deal that sits in the pipeline with no answer does not count, however good it looks.

Leadership teams use the term for how fast they make their own calls. For a revenue team, the forecast turns on a different speed: how fast your buyers decide. In the first half of 2026, buyer decisions slowed across ORM customers, and the coverage ratio did not show it.

What is decision velocity in sales?

Decision velocity is the share of open deals that get a yes or a no in a period, plus the time they take to get there. Both halves matter. A team can win the same share of the deals it decides and still fall behind, because it is deciding fewer of them.

A lost deal has been decided. A deal that drifts from one quarter into the next has not. So the measure counts outcomes, and it gives no credit for activity that does not lead to one.

Why does pipeline coverage miss it?

Coverage tells you how much pipeline you have, and it says nothing about whether any of it is moving. The 3x to 5x rule works until it does not. It assumes the system underneath is stable, with deal sizes, cycle lengths and conversion rates that hold still.

That assumption broke in Q1 and Q2 of 2026. On paper, ORM customers had enough pipeline and coverage looked fine. But fewer deals were being decided. They were not being won. They were not being lost. They were just sitting there.

Days in stage crept up. Days to close went up. Sales velocity slowed. The market had changed, but a static coverage ratio had not. Most ORM customers run at about 3.5x coverage, and a ratio like that can sit still while the quarter under it stalls. See why the 3x coverage rule is wrong.

What slowed buyer decisions in 2026?

Buyers put off decisions they knew they had to make. One story came up again and again across ORM customers. Prospects knew they had a problem and knew there was a solution. They still wanted to give their own team more time to see what it could figure out with AI before they bought anything.

A second push came from outside. Geopolitical pressure moved the price of oil and added doubt in the second half of Q1 and the first half of Q2. Buying groups are large as well. Forrester's State of Business Buying 2026 puts the typical decision at 13 internal stakeholders and nine external influencers.

Whether AI was the real cause matters less than the signal. Buyers had changed how fast they decide, and the forecast needed to see it. For the wider picture, see what ORM saw across customers in H1 2026.

How do you measure decision velocity?

Measure it on groups of similar deals, week by week. Watch the trend more than the level. A single reading at one point in time is interesting. Change through time gives you perspective.

Start with a simple rate. Take the deals that were open at the start of a period, and count the share that were won or lost by its end. Then compare like with like. Within a quarter, ORM sees the third month as the largest and the first month as the smallest. So set week three of Q3 next to week three of Q1 or Q2.

A model can build the rest of the signals from CRM history. ORM groups deals and tracks variables such as time in stage and days since the last update. It then measures how those signals change over time. ORM counts a change in stage, close date or amount as meaningful activity, so a deal with none of those is standing still.

What should the forecast show when decisions slow?

The forecast should show a range, built by a model that reacts to the slowdown. When coverage says the quarter is fine, ask better questions. What does the statistical or machine learning forecast say? What is the confidence interval? Where are the floor and the ceiling?

A range is more useful than a point estimate. A dynamic model can react to a change in the business faster than a 3x or 5x rule of thumb. For how to present a range to leadership, see scenario forecasting vs a single number.

What do you do when decision velocity drops?

Force decisions. A no today is better than a no three months from now, because it frees the rep's time and clears a lost deal out of the forecast sooner.

Then work out why it is happening. Find the stages where deals stall, and the segments where it happens most. Adjust the talk track, and make sure the value proposition speaks to what buyers are worried about.

Get decision makers in early, too. Ebsta's 2025 GTM benchmarks found that win rates rose 55% when decision makers were active in the first two stages. And when a buyer does walk away without choosing anyone, record it. The no decision rate keeps those deals from hiding in open pipeline.

Does decision velocity apply to your own team?

It does, and the two speeds are linked. When buyers slow down, the revenue team has to make its own calls faster. Once the data shows decision velocity slowing, the operating response changes too.

That starts with where reps spend their time. If a deal has no clear path to close, stop spending time on it and move to the deals that can close. A team that waits for a stalled buyer to decide has slowed its own decisions to the buyer's pace.

Did decision velocity recover?

Across ORM customers, deals started getting decided faster again in Q3. More deals were decided in the first few weeks of the quarter than in the same weeks of Q1 or Q2.

That is the point. Pipeline coverage tells you how much pipeline you have. A good forecast should tell you how that pipeline is behaving.

---