Deals don't fail suddenly. They stall gradually. A champion who was engaged becomes harder to reach. A next step that was agreed gets pushed twice. A prospect who was moving quickly now takes 10 days to reply to emails. These signals appear weeks before a deal is formally lost, and if you're watching for them, you have time to intervene. If you're watching only stage and close date, you see the stall only after it's already happened.
A deal progression tracker monitors the signals that precede stalls rather than just documenting stalls after the fact. This guide covers what to track, how to interpret what the data shows, and what to do when a deal is drifting rather than advancing.
What Signals Predict Deal Stalling#
The most reliable leading indicators of deal stalls fall into four categories. Understanding what each signals helps you choose the right response rather than applying a generic "re-engagement" approach to every at-risk deal.
Engagement decline#
Email response time increasing. Meetings being rescheduled. Replies becoming shorter and more perfunctory. These signals suggest the prospect's priority for this evaluation has shifted downward. The cause might be internal: a new project, a leadership change, a budget freeze, or competition from a different initiative. The response is a direct conversation with the champion about what's changed: "I've noticed our cadence has slowed down. I want to make sure we're still aligned on timeline, has something shifted on your end?"
Single-threading#
A deal where all communication flows through one contact is vulnerable to any disruption in that contact's attention, availability, or internal standing. If the champion leaves, gets pulled to a different project, or faces internal resistance, the deal loses its internal advocate with no backup. Single-threading doesn't cause stalling directly, but it makes any friction in the evaluation more likely to produce a stall because there's no second relationship that can carry momentum forward.
MAP milestone overruns#
When agreed evaluation milestones aren't being met, the IT security review that was supposed to happen by the 15th still hasn't started on the 25th, the MAP is revealing something about how the evaluation is being prioritized internally. Overrunning one milestone can be external circumstances. Overrunning two or more consecutive milestones suggests the evaluation isn't progressing as planned and requires direct conversation about what's causing the delays.
Close date vs stage mismatch#
A deal with a close date 30 days away that's still in the discovery stage has a mathematical problem. Either the close date is wrong (the deal will slip) or the process is wrong (critical steps are being skipped, which creates risk at contract time). Either mismatch deserves explicit attention rather than silent optimism that everything will accelerate in the last month.
Tracking progression signals across a large active pipeline requires consistent attention to deal-level details.
River's Sales workspace monitors deal progression automatically, engagement levels, MAP milestone completion, and stage-to-date alignment, with weekly at-risk deal reports built in.
Track My Deal MilestonesBuilding a Milestone Tracking System#
For deals with a mutual action plan, milestone tracking is built into the MAP itself: you have specific milestones with specific owners and specific dates, and you review completion at every call. For deals without a formal MAP, milestone tracking requires a simpler framework: what specific events need to happen for this deal to advance, by when, and who's responsible?
The minimum viable milestone tracker for any active deal has four fields per deal: the most recent meaningful prospect action (with date), the next committed step from the prospect side (with date), the next committed step from the seller side (with date), and the current health assessment (active, slowing, stalled). Reviewing these four fields weekly for every active deal takes about 20 minutes for a 10-deal pipeline and surfaces drift before it becomes a stall.
How to Interpret Progression Patterns#
Not all slow deals are stalled deals. Some deals move slowly because the evaluation process at the prospect company is inherently slow, complex organizations with multiple approval layers, regulated industries with mandatory review steps, or deals that happen to have landed in a quarterly planning cycle where decisions wait for the new quarter's budget confirmation. Distinguishing between slow-but-progressing and slow-and-stalling requires looking at the engagement quality, not just the pace.
A deal that moves at half the expected pace but where every interaction is substantive, the champion is engaged, and the prospect is taking buyer-initiated actions (requesting additional materials, involving new stakeholders) is a healthy deal that happens to be in a slow organization. A deal that moves at the expected pace but where every interaction is perfunctory, the champion is increasingly distracted, and the prospect is never initiating next steps is a stalling deal that looks active only because both sides are going through the motions.
Intervention Strategies by Stall Type#
For engagement decline stalls: Don't just send another follow-up. Change the approach. If emails aren't getting responses, try LinkedIn or a phone call. If the contact isn't engaging, ask the champion to introduce you to another stakeholder who's more directly affected by the problem you solve. If the champion is the problem, have a direct conversation about whether the evaluation is still active and what's preventing progress. Continuing to do the same thing that isn't working does not produce different results.
For single-threading stalls: The risk is that you have only one relationship supporting the deal. The intervention is multi-threading: ask the champion to introduce you to the economic buyer, the technical evaluator, or another functional leader who would benefit from your product. "I want to make sure the right people are involved in this evaluation so we can move efficiently. Could you introduce me to [specific person]?" This both advances the deal and de-risks the single-thread.
For MAP overrun stalls: Direct conversation with the champion. "I noticed we missed [milestone]. I want to make sure we understand what's blocking that so we can either address it or adjust our timeline. Can we talk about what's changed?" This conversation surfaces the real obstacle, internal prioritization change, budget freeze, competing project, so you can address it specifically rather than just continuing to follow up on a timeline that's no longer realistic.
When to Formally Mark a Deal as Lost#
Keeping deals open past the point where they're realistically closeable is one of the most common pipeline hygiene failures. It inflates pipeline, distorts forecasts, and consumes management attention that should go to genuinely active deals. The thresholds that justify formally closing a deal: 45+ days with no prospect engagement despite multiple attempts, explicit indication from the prospect that they're not moving forward, or a fundamental change in the prospect's situation (company acquisition, budget elimination, leadership change in the key stakeholder) that makes a near-term purchase unlikely.
Formally closing a deal isn't giving up on the account, it's honest accounting. You can close the deal, set up monitoring for future signals, and re-engage when circumstances change. Re-engaging after a gap, with a new signal as the hook, often produces better conversations than trying to revive a stalled deal with continued follow-up on the original approach. For teams using River's Sales workspace, deal progression tracking is integrated with pipeline health monitoring, so stall signals surface automatically and trigger timely intervention rather than being discovered only when a quarterly forecast misses.