Sales cycle improvement usually gets framed as urgency: push harder, follow up faster, create pressure. The bigger wins are in the gaps where nothing is happening at all.
- ›Measuring where deals actually wait
- ›The four common queues
- ›Fixes that shorten cycles without pressure
- ›What not to do
Measure the waiting
Total cycle time is the wrong unit of analysis. Break it into time per stage, and within that, time spent waiting versus time spent working.
Most teams discover that active selling occupies a small fraction of the cycle. The rest is waiting: for a reply, for an internal approval, for a legal review, for a meeting that could not be scheduled for eleven days.
You cannot fix what you have not located, and the location is almost always a queue.
The four common queues
Scheduling. Days lost to finding a meeting time. Fixable immediately with scheduling links and calendar connection, and it is the cheapest win available.
Internal approvals. Discount approvals, contract reviews, and security questionnaires sitting with someone who does not know they are blocking a deal. Fix with explicit routing, deadlines, and escalation rather than by asking people to be faster.
Buyer-side process. Procurement, legal, security review. Not controllable, but predictable. Start these earlier rather than treating them as a final step.
Rep attention. Deals that go quiet because the rep is working other deals. This is what stall detection catches, and it is more common than any team believes about itself.
Fixes that work
Start slow processes early. Send the security questionnaire and the standard contract at proposal, not after verbal agreement. Parallelize what does not need to be sequential.
Remove approval steps you cannot justify. Every approval should have a named reason. Discount approval for a discount inside standard bands is theater.
Set response expectations internally. An internal SLA on deal-blocking requests, with automatic escalation, removes the chasing that consumes managers.
Let the system detect stalls. A flag on day seven costs nothing; a manager noticing on day twenty costs the deal.
Book the next meeting in the current meeting. Trivially simple, consistently effective, rarely done.
Tip: Track the median time between the last activity and today across your open pipeline. It is the fastest read on whether your team is working deals or holding them.
What not to do
Artificial urgency. Fake deadlines and expiring discounts damage trust and train buyers to wait for the next one.
More follow-ups. Frequency is not the constraint when the buyer is waiting on their own internal process.
Compressing discovery. Cycles shortened by skipping discovery produce deals that close and churn, which is worse than slow.
The cross-department view
Some slowdowns are not sales problems. A deal waiting on a reference call that delivery has not scheduled, or on a question only finance can answer, is blocked outside the CRM's view. A connected system sees those; a standalone CRM cannot.
FAQ
What is a good deal velocity?
Yours, trending down, with win rate holding. Cross-company benchmarks are noise given how much cycle length varies by market.
Does velocity matter more than win rate?
They trade off. Velocity gained by disqualifying poor fits earlier is good; velocity gained by rushing good fits is not.
How do we spot the queues?
Time-in-stage per deal, and time since last activity. Both are standard reports, and most teams have never looked at either.
Brainis tracks stage duration and stall thresholds automatically, with delivery and finance context in the same system. See Revenue OS.
Sharing insights on business operations, AI, and modern team management.
Run your company on Brainis
All 11 Operating Systems on every plan, from $29 a month. No per-seat pricing — you pay for AI capacity, not headcount.
See pricing