The Deals Quietly Stalling in Your Pipeline
- Lolita Trachtengerts
- 9 minutes ago
- 4 min read
Deals rarely die in a meeting. They die by sitting. A deal that has been in the same stage twice as long as it should be is not paused, it is slipping, and the only reason no one is acting on it is that nothing flagged it.
The most dangerous deal is the one not moving
Every forecast has a few deals everyone is watching and a long tail nobody is. The tail is where the quarter leaks. A deal that entered a stage in week one and is still there in week seven has told you something, but only if someone is measuring how long it has been sitting. Most teams are not, so the deal ages quietly inside a pipeline that still reports it as active.
Time in stage is one of the few honest signals in a CRM. A rep can mark a stage optimistically, but they cannot fake the clock. How long a deal has actually sat is a fact, and it is usually the earliest warning that a deal is in trouble.
📊 Deals that stall well past their average time in stage are far less likely to ever close. — Gartner |
|---|
Why stalled deals hide
Nobody hides a stalled deal on purpose. It hides because the pipeline view is built around stage and amount, not time. A deal in the right stage with a healthy number looks fine at a glance, even if it has not moved in a month.
The forecast rewards the wrong thing
A rep asked to forecast will list the deals in late stages, because that is what the pipeline surfaces. A deal parked in a late stage for two months looks better on the board than an active deal in an early one. The aging is invisible until someone sorts for it.
The rep has already moved on
Reps triage. A deal that has gone quiet gets less attention than a deal that is talking, which is exactly backwards, because the quiet one is the one at risk. Without a nudge, the stalled deal keeps sliding down the priority list until it is a closed-lost at quarter end.
Sorted by stage and amount | Sorted by time in stage | |
What surfaces | Big, late-stage deals | Deals that stopped moving |
Risk visibility | Hidden | Front and center |
Rep behavior | Chase the loud deals | Re-engage the quiet ones |
Forecast | Optimistic | Grounded |
Put a clock on every stage
The fix is to make time in stage a first-class signal. When a deal crosses the point where healthy deals have already moved, someone should hear about it while there is still time to act. Spotlight's velocity and time-on-stage warning does exactly that: it watches how long each deal has sat against how long deals like it usually take, and flags the ones that have quietly stopped moving, so the stall becomes an action item instead of a post-mortem.
See it in the docs: Velocity: Time-on-Stage Warning
The point is not another dashboard. It is catching the deal on week four instead of finding it at quarter end. A stalled deal you know about is a deal you can still save. One you do not is a slip you explain later.
Measure time in stage, not just stage. The clock is the honest signal.
Surface the deals that stopped moving. Not just the big late-stage ones.
Flag the stall while there is time to act. Week four, not quarter end.
Re-engage the quiet deals first. Silence is the risk, not the safe sign.
Ground the forecast in movement. Aging deals are not commit deals.
FAQs About Deal Velocity and Time in Stage
What is time in stage in sales?
Time in stage is how long a deal has sat in its current pipeline stage. It is one of the few CRM signals a rep cannot fake, which makes it an early and honest indicator that a deal is stalling.
Why are stalled deals so easy to miss?
Because most pipeline views are sorted by stage and amount, not by how long a deal has been sitting. A deal in a late stage with a healthy number looks fine at a glance even if it has not moved in weeks, so the aging stays invisible.
What is a time-on-stage warning?
It is an alert that fires when a deal has sat in a stage longer than comparable deals normally take. Spotlight's velocity warning watches each deal against typical stage durations and flags the ones that have quietly stopped moving.
Why does a stalled deal predict a loss?
Because movement is what closing looks like. A deal that stops progressing has usually hit an unspoken objection, lost a champion, or slipped down the buyer's priorities. The longer it sits past its normal stage time, the less likely it is to close.
How is this different from a normal pipeline report?
A normal report tells you what stage a deal is in. A velocity signal tells you whether it is actually moving, and alerts you early enough to re-engage rather than surfacing the problem after the deal has already slipped.
Comments