What does “stalled deal” actually mean?
There is no universal clock that makes a deal stalled after a fixed number of days. The useful question is whether the opportunity is still showing the movement expected for this sales motion and this stage.
CRM products use different operational heuristics. HubSpot, for example, can surface deals that have remained in a stage longer than the relevant average, as well as deals with no activity scheduled or a stale close date. Salesforce teaches teams to identify opportunities that are not moving through the sales cycle and to review the action required to move or reprioritize them. Those are useful signals. They are not, by themselves, explanations for why the deal stopped.
“This deal has stopped moving” is observable. “Why it stopped” still has to be resolved from the actual deal evidence.
Six signals that deserve a closer look.
A single signal does not prove a deal is dead. Together, however, these are useful prompts for a manager review:
Time in stage is unusually long.
The opportunity remains in the same stage beyond the normal range for comparable deals.
No dated next step exists.
The deal has no concrete buyer or seller continuation scheduled in time.
Buyer movement has gone quiet.
Recent activity exists, but nothing meaningful has advanced the buyer’s decision.
The close date keeps moving.
The expected close is repeatedly pushed without equivalent evidence of progress.
A blocker stays unresolved.
Security, legal, budget, procurement, stakeholder access or another decision boundary remains open.
The next stage has no clear entry condition.
The team can describe activity, but not the buyer evidence required to move forward.
First diagnose the deal. Then diagnose the repeat.
For one opportunity, ask ordinary deal questions first. What changed since the last review? Who is actually involved in the decision? What buyer action happened most recently? What is the next dated step? Which blocker still has to be removed? Should the deal advance, change plan, remain open, or leave the active forecast?
That is deal management. It matters. But it still answers only what should happen with this opportunity.
The second pass asks a different question: where else did the same sequence appear under comparable conditions?
ILLUSTRATIVE MECHANIC / DEMO DATA
The stall can repeat before anyone calls it a pattern.
A proposal may leave without a dated buyer continuation.
Before a proposal leaves, set the next dated buyer step.
The repeating sequence is evidence. It is not automatically the rule.
This distinction matters. “Proposal → no dated next step → inactivity → close date moves” is an observed mechanic. It shows what keeps happening. It does not, on its own, prove the operating rule that permits the sequence.
The current rule is a separate claim. It may require business confirmation when the CRM cannot resolve the meaning cleanly. If the rule cannot be supported, the correct answer is not a confident AI explanation. The case stays unresolved until the missing evidence or business meaning is supplied.
Do not “fix” a recurring stall by changing five things at once.
If the same mechanic is genuinely recurring, the cleanest test is a local rule change at the point where the current process still allows the old path. Keep the change narrow enough that the next comparable deals can tell you something.
Activation is not proof. One new deal is not proof either. New comparable deals can follow the new path, the old path, remain unclear, or fail comparability altogether. Keep those outcomes separate instead of compressing them into a success percentage.
A recurring mechanic is a process-level observation, not an employee score or psychological profile.
If the field or history is not observable, the absence cannot be treated as evidence that no next step existed.
A pushed date can be legitimate. The surrounding sequence and comparable context decide whether it belongs to the same mechanic.
The observed repeat and the current operating rule are separate claims and should remain separate.
How should stalled deals show up in the weekly pipeline review?
Keep the normal deal review. Surface opportunities with weak movement, missing next actions, stale dates or unresolved blockers. Then add a cross-deal view: which stalls belong to an already-known recurring mechanic, which appear new, and which cannot yet be compared cleanly?
That changes the management conversation. Instead of repeatedly asking different reps to rescue apparently different deals, the team can see when one operating rule is producing the same path again.
One stalled deal needs a deal decision. The same stall across comparable deals may need an operating-rule decision.
Related: build the recurrence pass into your pipeline review.
The weekly review is the natural place to separate isolated stalls from repeating mechanics. The companion guide shows how to keep the deal-level review intact while adding a cross-deal recurrence pass.
Read the Sales Pipeline Review guide
Sources & further reading
HubSpot — Stalled deals, no activity scheduled and stale close-date viewsHubSpot — Pipeline review signals: stage, last touch, dated next step and close dateSalesforce Trailhead — Identify stuck sales dealsSalesforce Trailhead — Decide how to move or reprioritize stuck opportunitiesSEE THE SYSTEM
Find the stall that keeps coming back.
Open the synthetic workspace and follow one recurring mechanic from evidence to current rule, one change, comparable retest and history.