Stalled Deals: How to Spot Them Early and What to Do Next

A stalled deal has stayed in its current pipeline stage longer than deals of that type normally take, with no new call, email or meeting logged. There is no universal day count that defines it: set a threshold from your own closed deals, per stage, then run a fixed re-engagement sequence before you close the deal out.

Every deal sits in a stage of your pipeline until it moves, is won, or is lost. See how stages, deals and the rest of a CRM record fit together in what a CRM is and how it works. A few stalled deals are normal. The problem is a pipeline report that still looks healthy because nobody has agreed on what “stalled” means.

What is a stalled deal?

A stalled deal has stopped moving: no stage change, no new activity, no reply from the buyer, for longer than that stage usually takes. Deal slippage is a related but different problem: a deal that is still moving, just later than planned, usually visible as a close date pushed out more than once. A deal can slip without stalling, and it can stall without anyone touching the close date at all, which is why slippage shows up in a forecast report and a stalled deal often does not.

The distinction changes what you do next. A slipping deal needs a harder conversation about the real close date. A stalled deal needs to find out whether there is still a deal at all.

Why a fixed “30 days” rule gets stalled deals wrong

Most sales teams that flag stalled deals use one number for the whole pipeline: 14 days, 30 days, sometimes 60. It fails in both directions. A 30-day rule flags a healthy enterprise deal that is normally in legal review for six weeks, so reps learn to ignore the flag. The same rule lets a dead small-business deal sit for three weeks past the point a rep already knows it is over, because 30 hasn’t arrived yet.

Stage length varies by design (legal review is supposed to take longer than a first call), so the threshold has to vary with it. That means measuring your own stages instead of importing someone else’s number.

The formula: your stage baseline × a multiplier

For each stage, calculate the baseline from deals that actually closed, then multiply it by a stalled-threshold factor:

Stalled threshold (per stage) = median days in that stage across recent won deals × a multiplier, usually between 1.5× for early stages and 2× for stages with more moving parts, such as legal or procurement review.

Example: a company’s Proposal stage has a median of 9 days across its last twenty won deals. At a 1.5× multiplier, a deal sitting in Proposal for more than about 14 days with no new activity counts as stalled; one sitting for 9–14 days is simply on pace, even though both look identical on a “days since created” report.

How do you calculate your own stage baseline?

1. Pull your won deals from the last two to four quarters, enough for a stable median but recent enough to reflect how the team sells today.
2. Group them by stage and calculate how long each deal spent in each stage it passed through, using the date it entered and the date it left.
3. Take the median, not the average, per stage. One deal stuck for four months in legal review will drag an average far past what a typical deal looks like.
4. Set a multiplier per stage: tighter for stages a rep controls (discovery, demo), looser for stages that depend on someone else’s calendar (legal, procurement, budget approval).
5. Save it as a standing report and revisit it quarterly. A baseline built during a slow quarter under-flags stalled deals once volume, and rep attention, picks back up.

What warning signs matter beyond time in stage?

Time in stage tells you a deal might be a problem. These signs tell you what kind of problem it is:

How do you revive a stalled deal? A three-touch plan

Give a stalled deal a fixed, fair chance to move before you let it go, not an open-ended string of “just checking in” emails.

1. Touch 1: a value check-in. Owner: the rep. Reference something specific from the last real conversation, such as the outcome the buyer said they needed, not a generic follow-up. Output: a reply that restarts the conversation, or a logged no-reply.
2. Touch 2: multi-thread, about a week later. Owner: the rep. Bring something new to a second contact (an answer to a question raised earlier, a short reference story, a one-page comparison) rather than repeating the first email to the same inbox. Output: a new stakeholder engaged, or confirmation there isn’t one.
3. Touch 3: the direct question, about a week after that. Owner: the rep, reviewed by the sales manager before it goes out. Ask plainly whether the timeline still holds or whether the deal should move to a later quarter. Output: a clear next step and date, or grounds to close the deal.

Each touch has a deadline. If touch 3 gets no answer within an agreed number of business days, the deal moves to closed, not back to the top of the queue for another round.

When do you call it closed lost?

A “close it lost” rule only works if the team applies it the same way every time: no reply after the three-touch plan closes the deal, full stop, regardless of how large it looked in the forecast. The part teams get wrong is not the rule: it’s the reason they record when they apply it.

Closed Lost should mean the buyer made a decision and it wasn’t you: they picked a competitor, built it themselves, or the budget was cut. No Decision should be a separate reason for a deal that simply never got a real yes or no: the buyer went quiet, the project lost priority, or the person you were talking to changed roles. Folding both into one “Lost” bucket makes a real competitive loss look identical to a deal that just evaporated, and it hides which one is actually happening more, month over month. See how a clean set of loss reasons keeps your win rate calculation honest.

Example: a 12-rep B2B SaaS team in Austin, Texas, selling scheduling software to home-services companies, sets its Proposal-stage baseline at 11 days with a 1.5× multiplier, so anything past about 17 days with no new activity counts as stalled. In one Tuesday pipeline review, four proposals cross that line. Two get a reply on the first touch and move to a verbal commitment. One reveals, on the second touch, that the buyer’s accounting software vendor bundled a competing scheduling module for less, so it’s marked closed lost, reason: lost to a bundled competitor. The fourth gets no reply after all three touches over two weeks and is marked no decision, then reopened as a follow-up for the following quarter instead of quietly deleted from the forecast.

What mistakes keep deals stalled?

• Treating “still interested” as a stage. A verbal maybe with no scheduled next step is not progress: it’s a deal waiting to stall.
• Sending a weak first touch. “Just checking in” gives the buyer nothing to respond to; a specific value check-in does.
• Leaving the close-it-lost decision to the rep alone. Without a manager-reviewed rule, reps hold onto deals past the point they know are dead, because a full pipeline looks better than an honest one.
• Not recording stage-entry dates. Without them, nobody can calculate a real baseline, and every stalled-deal conversation falls back to a guess.
• Reassigning a stalled deal as the fix. A new rep rarely revives a deal that already went cold; it usually just resets the clock on the same problem.

How do you measure and reduce stalled deals over time?

Treat stalled-deal review as a standing item, not a one-time cleanup. A weekly pipeline review that sorts open deals by time in stage against each stage’s baseline catches a deal the day it crosses the line, instead of a quarter later when the forecast is already wrong. For what that meeting should actually cover, see running a pipeline review meeting.

Over a few quarters, track what share of deals in each stage cross the stalled threshold and how they resolve: revived, closed lost, or no decision. A stage that stalls a high share of its deals usually points to a step the team is skipping earlier, such as not confirming a decision date before a deal reaches that stage at all.

How do you spot and manage stalled deals in Senitix CRM?

In Senitix CRM, every deal carries an amount, a close date, a probability and an owner, moving through your own pipeline stages on a list or a Kanban board. On every plan, a deal’s own record keeps a field-history and an activity timeline, so the date it entered its current stage and the date of its last logged call, email or task are both there without any extra setup: the two numbers a stalled-deal rule needs.

A date-based automation rule can open a task for the deal’s owner a set number of days after its last logged activity, so a stalled deal surfaces on its own instead of waiting for the next pipeline review. Reports, available on every plan, can be built on stage and date fields to show aging across the whole pipeline at once rather than deal by deal. The pipeline section of the feature catalog covers what a deal record holds, and the automation section covers what a rule can trigger and do.

To set up your own stage baselines and re-engagement rules, compare plans and start on Free.

Frequently asked questions

Should a deal’s probability go down automatically once it stalls?

Senitix CRM does not predict or change a deal’s probability on its own: a rep or manager sets it. Once a deal crosses your stalled threshold, it’s good practice for the manager to lower the probability by hand during the pipeline review, so the forecast reflects reality before the deal is formally closed, not after.

Should a stalled deal be reassigned to a different rep?

Usually not as a first move. A deal stalls because of something in the buying process (no budget, no internal champion, a lost priority) that a new rep inherits along with the account. Reassign only when the evidence points at the rep specifically, such as missed follow-ups the buyer confirms never happened.

Does a stalled deal still count in the sales forecast?

It counts until someone changes its probability or closes it, which is exactly the risk. A deal that has crossed its stalled threshold but still carries its original probability overstates the forecast for every week it sits there untouched, which is why a stage-based review catches what a probability field alone will not.

How is a stalled deal different from a deal that’s simply early in a long enterprise cycle?

An enterprise deal several weeks into a stage that normally takes that long isn’t stalled: it’s on pace, which is exactly what a per-stage baseline is built to show. A stalled enterprise deal has also gone quiet: no new contact, no scheduled next step, past the point that stage’s own history says is normal, not just past a number that looked long from the outside.