How to increase sales velocity: find the driver that's holding revenue back

Sales velocity increases when you know which driver is holding revenue back and fix that one first. Gains across several drivers do compound, but only when each change is aimed at a cause you have confirmed. A plan that pushes all four at once without that diagnosis spreads the effort thin, and afterwards nobody can tell which change made the difference.

The method below has four parts: find the driver that moved, confirm what caused it, choose one change and check that it worked. For the calculation itself, our sales velocity formula guide works through an example in pounds.

The four drivers, and why the total hides the problem

Sales velocity combines four drivers: the qualified opportunities in your pipeline, the average value of the deals you win, your win rate and the length of your sales cycle. Multiply the first three, divide by the fourth, and the answer is revenue per day.

The total is useful for tracking. It is much less useful for deciding what to do, because very different problems produce the same number. A business that is winning fewer deals and one whose deals now take twice as long can show the same fall in velocity. Each needs a different fix.

Step 1: Rebuild the drivers by segment and over time

Calculate each driver month by month for at least the last 12 months, and split it by new business and expansion. Add any other split that changes how you sell, such as product line, region or deal size.

Then look for the driver that moved. Usually one or two have shifted while the rest held steady, and that is where the investigation starts.

Agree the definitions before you compare anything: what counts as a qualified opportunity, which contract value you use, whether win rate divides by all closed deals, and whether cycle length includes lost deals. Merlin5's data discipline starts here for a reason. If a definition changed halfway through the period, the trend you find may be a change in how deals were recorded.

Step 2: Read the driver against its likely causes

Each driver has a handful of common causes. Use the table as a starting point for the evidence to check. It points you somewhere to look; it doesn't make the diagnosis.

Step 3: Confirm the cause before you change anything

The CRM shows you where deals went. It rarely shows you why. A lost reason picked from a dropdown at the end of a quarter is a weak basis for a decision.

Look for a second source that agrees: stage history, a sample of lost deals reviewed with the account owner, or conversations with buyers who chose someone else. If only the CRM points to a cause, treat it as a hypothesis.

Cycle length needs particular care. A long enterprise deal can still be moving, and a young deal can already be dead. Check whether the buyer is doing anything, such as agreeing next steps or bringing in colleagues, before you call a deal slow. Our short guide to stalled deals lists the signs to check.

Look across the whole commercial system as well as the sales team. A falling win rate can start with weak value messaging, a pricing problem or the wrong segments. A longer cycle can start with a buying process nobody mapped. The Growth Assessor™ is built for this, and it models its recommendations against the same four drivers.

Step 4: Choose one change, and write it down first

Pick the change that addresses the confirmed cause, then record the plan before you start. A simple worksheet is enough. Here is an illustrative example for a business whose cycle has lengthened at the proposal stage.

The last row matters. Without it, any movement in the number gets credited to the change.

When the cause sits in the sales process itself, the fix usually belongs in the stage definitions. Our guide to sales process stages shows how to write exit criteria a deal has to meet.

Step 5: Check the result, and watch for paper gains

Track the change's own measure weekly and the driver monthly. Give it time to show up. With a long sales cycle, win rate and cycle length need at least a quarter before the result means much.

Be wary of changes that move the number without moving revenue. Closing out stale opportunities shrinks the pipeline and can shorten the average cycle overnight. Tightening qualification can lift the win rate while the number of wins stays flat. Both can be the right call, because they make the pipeline more honest. Report them as clean-up rather than growth.

Check the other drivers too. A push to shorten the cycle can lower deal value if sellers start discounting to close sooner, and the gain in one driver disappears in another.

What this looks like in a real programme

When Source 1 Solutions set out to grow revenue by 40% over two years, Merlin5 started with diagnostics, using Sales Velocity Analysis™ and the Growth Assessor™, before designing anything. The work that followed included improved qualification standards, forecasting disciplines and pipeline governance. The Source 1 case study shows how each phase built on the one before.

Where to start

1. Rebuild the four drivers for the last 12 months, split by new business and expansion.

2. Find the driver that moved most, and pull the evidence for that one only.

3. Write down one change, its owner and its review date before you act.

Frequently asked questions

What is the fastest way to increase sales velocity?

There isn't one lever that works everywhere. The quickest gains usually come from removing a delay or a leak in the deals you already have, because new pipeline takes a full sales cycle to turn into revenue. Find the constrained driver first.

Which of the four drivers matters most?

In the formula, a 10% change in any of the three multipliers moves velocity by 10%, and a 10% shorter cycle moves it by about 11%. In practice, the driver that matters most is the one that is currently constrained.

How often should we measure sales velocity?

Monthly, by segment, on a trailing six or 12-month basis, so a few large deals can't swing the result. Check the specific measure for any change you are testing every week.