Stalled Deals in Your Pipeline: How to Spot Them

The most reliable way to spot a stalled deal in your pipeline is to compare how long each deal has spent in its current stage with that stage's normal duration. A deal that runs well beyond the norm is at risk. Add two more checks: the date of the last meaningful customer interaction and whether there is a clear, dated next step. If all three signals are trending the wrong way, the deal has most likely stalled, even if your CRM still shows it as "open."

The problem is that most B2B teams notice this far too late. A deal sits in "Proposal sent" for weeks. The rep is optimistic, the manager accepts the number at face value in the forecast meeting, and at quarter end it turns out that a large share of the pipeline has actually been dead for months. In this article, we cover the signals you can use to catch stalled deals early, how to set threshold values, a simple risk scoring model, and the recovery steps to take once you've identified them, all with concrete examples.

What exactly is a stalled deal?

A stalled deal is an opportunity that hasn't closed but isn't moving forward either. It shouldn't be confused with a lost deal. In a lost deal, the customer has said no. In a stalled deal, nobody says anything, and the silence just continues.

In practice, a deal can be considered stalled when at least two of the following three conditions occur together:

High stage age: The deal has been sitting in its current stage much longer than that stage's typical duration.
Engagement has dropped off: The buyer's last meaningful reply, meeting, or action happened a long time ago.
Unclear next step: There is no next step in the CRM with a set date and owner, or its date has long passed.

There's an important distinction here: not every long-running deal is stalled. Legal review at an enterprise customer can take six weeks. If the customer keeps getting back to you regularly during that time and the timeline is clear, the deal is slow but healthy. What defines a stall isn't the duration itself, but the absence of any sign of progress.

Why is it so important to catch stalled deals early?

Stalled deals damage your pipeline in three different ways.

1. They inflate forecasts. A deal that has been inactive for months keeps being included in the forecast at its weighted probability. If you want to build a realistic sales forecast from your pipeline, you first need to weed out these "ghost" deals.

2. They slow down pipeline velocity. In the pipeline velocity formula, sales cycle length is in the denominator. Stalled deals lengthen the average cycle and also drag down the win rate. That's why tracking stalled deals separately when calculating pipeline velocity helps you understand where a drop in velocity is coming from.

3. They eat up reps' time. Chasing a dead deal because "it might come back" steals time that should go to new, warm opportunities. And because the team believes the pipeline is full, motivation to generate new opportunities drops too.

Consider an example scenario: a team has 40 open deals in its pipeline with a total value of TL 6 million. Filtering by stage age and engagement data shows that 14 of them have had no buyer interaction in the last 30 days. If these 14 deals are worth a combined TL 2.2 million, the team's "real" active pipeline is roughly TL 3.8 million, not 6 million. Quota planning and the need for new opportunities should be based on this figure.

What signals show that a deal has stalled?

It helps to split the signals below into two groups: quantitative signals that can be pulled automatically from the CRM, and qualitative signals drawn from call notes or email content.

Quantitative signals

Stage age threshold exceeded: The deal has been in the same stage for longer than 1.5–2 times the stage's median duration.
Last buyer interaction is old: The last reply, meeting, or document open is older than the threshold you've set (for example, 14 days).
Next step date is overdue or empty: The "next step" field in the CRM was either never filled in or its date has passed.
Close date pushed back repeatedly: The expected close date has been moved out two or more times. This is one of the strongest leading indicators of a stall.
Single point of contact: Only one person on the customer side is active in the deal. If that person leaves the company, goes on leave, or shifts priorities, the deal stops instantly.
One-way communication: Over the last few weeks, the number of emails and calls going out from you has increased while the number of replies from the customer has dropped to almost zero.

Qualitative signals

Vague language: Phrases with no date or owner, such as "we'll take a look," "we're doing an internal review," or "we're busy right now, let's reconnect later."
The decision-maker is nowhere to be seen: Several calls have taken place, but the budget holder or final decision-maker hasn't attended any meeting.
Unclear evaluation criteria: There has been no discussion of what the customer will base the decision on or which alternatives they're considering.
Urgency has disappeared: The problem or deadline raised in the first call (for example, "the system needs to be in place by the new year") is never mentioned in later calls.
Organizational change: Your champion's role has changed, or there's news of a restructuring or budget freeze at the company.

The hardest part of catching qualitative signals is that they usually stay in the rep's head. That's why systematizing call notes is critical. Automating sales call notes with AI ensures that information such as "did the decision-maker attend?" or "is the next step dated?" lands in the CRM as structured fields.

How do you determine a stage's "normal" duration?

Accurate thresholds are the foundation of stall detection. Using a single fixed number of days for every stage (for example, "everything should move within 30 days") is misleading. A discovery stage might take a few days, while a contract stage can take weeks.

Follow these steps to set your thresholds:

Make sure your stages are clearly defined. If each stage's entry and exit criteria are vague, measuring stage age becomes meaningless. Our guide to defining sales pipeline stages is a good starting point.
Pull the deals you've won over the last 6–12 months. Use won deals, not lost ones; the goal is to answer the question "how long does a successful deal stay in this stage?"
Calculate the median time spent in each stage. Use the median rather than the average, because a few extremely long deals will skew the average.
Set a threshold multiplier. As a starting point, 1.5 times the median works well as the "warning" level and 2 times as the "critical" level.
Break it down by segment. SMB and enterprise customers have very different cycles. If possible, calculate thresholds separately by segment or deal size.

Example calculation

Suppose a hypothetical B2B software company derives the following median stage durations from its won deals:

Discovery / needs analysis: 7 days → warning 11 days, critical 14 days
Demo / solution presentation: 10 days → warning 15 days, critical 20 days
Proposal: 12 days → warning 18 days, critical 24 days
Negotiation / contract: 15 days → warning 23 days, critical 30 days

In this case, a deal that has been in the "Proposal" stage for 26 days automatically lands on the review list because it has crossed the critical threshold. A deal that has been in the same stage for 16 days, on the other hand, is still within the normal range.

You can also look at the sum of these median values to get a sense of your overall sales cycle length and check whether your thresholds are reasonable. In the example above, the total median is about 44 days. If a deal was created 90 days ago and is still in the proposal stage, it should be questioned regardless of the stage-based check.

How do you build a system to detect stalled deals, step by step?

Knowing the signals one by one isn't enough. The real value emerges when you build a structure that checks them regularly and automatically every week.

1. Make the required CRM fields mandatory

A detection system is only as good as its data. Every open deal should have these fields filled in:

Stage entry date (most CRMs track this automatically; if yours doesn't, create a timestamp on stage change)
Next step (text) and next step date
Last buyer interaction date (not an email you sent, but a reply from the customer or a meeting they attended)
Number of close date changes
Number of active contacts on the deal

Configuring the CRM so that a deal can't change stages while the "next step date" field is empty can significantly improve data quality on its own.

2. Define a simple stall risk score

You can prioritize deals by assigning points to each signal and adding them up. An example model:

Stage age exceeded the warning threshold: +2 points (+4 if it exceeded the critical threshold)
Last buyer interaction older than 14 days: +3 points (+5 if older than 30 days)
Next step empty or overdue: +3 points
Close date pushed back 2 or more times: +3 points
Only 1 active contact on the deal: +2 points
Decision-maker hasn't attended any calls: +2 points

Interpretation:

0–4 points: Healthy
5–9 points: At risk; the rep should take action this week
10+ points: Stalled; should be reviewed with the manager, and a decision made on a recovery plan or closing the deal

This logic is very similar to lead scoring models. The difference is that the score measures progress risk rather than purchase intent. Adjust the weights over time based on your own data. For example, if "close date push-backs" is the strongest leading signal in your past lost deals, increase its weight.

3. Set up a weekly automated report

Set up an automation that sends each rep and the sales manager the following list every Monday morning:

Deals with a risk score of 10 or higher
Deals whose score rose above 5 this week
Deals whose next step date will pass this week

Having this report arrive automatically via email, Slack, or Teams means nobody has to remember to set up filters in the CRM.

4. Restructure your pipeline meeting around the signals

In a traditional pipeline meeting, each rep walks through all of their deals one by one, and most of the time is spent on healthy deals. Instead, build the meeting solely around the deals on the risk list. Ask three questions for each deal:

What was the last concrete progress, and when did it happen?
Who on the customer side wants to move this deal forward, and why?
What is the one action in the next 7 days that will either advance the deal or close it?

5. Make a decision mandatory

For every deal at the critical level, one of three options must be chosen at the end of the meeting: recovery plan, postpone (with a realistic new date and a lowered probability), or close as lost. "Let's wait a bit longer" is not an option.

How do AI and automation help find stalled deals?

Most quantitative signals can be caught with simple rules. AI's real contribution is processing the qualitative signals humans miss, along with large volumes of engagement data.

Email content analysis: If customer replies contain postponement language ("next quarter," "once the budget is finalized"), a competitor's name, or the names of new decision-makers, the deal can be tagged automatically.
Call recording summaries: AI can extract from a call transcript whether the next step is dated, whether a pricing objection came up, and what roles the participants hold.
Engagement pattern detection: A customer's response time getting steadily longer is an early indicator of a stall. For example, if a buyer who replied the same day in the first few weeks now takes 5–6 days, automation can flag that trend.
Organizational change tracking: Changes in your champion's title or company can be checked periodically using data enrichment tools.
Automated reminders and task creation: Workflows such as opening a task for the rep or notifying the manager when the risk score crosses a threshold can be built with n8n or similar tools.

The key point here is that AI's role is not to make decisions but to direct attention. The model can say "this deal is at risk," but the decision to recover or close should be made by the rep who knows the customer and their manager. Also, processing email and call content with AI tools counts as personal data processing. So check the data retention and transfer terms of the tools you use in advance.

Building these kinds of workflows from scratch varies depending on your CRM setup and the tools you use. Teams that want to tackle strategy and automation together can also explore Corner Group's approach to strategy and automation, our group's parent company.

What should you do after identifying a stalled deal?

Detection is only half the job. Continuing to follow up on a deal you know has stalled in the same way, such as sending the same person a third "were you able to get back to me?" email, rarely changes the outcome. Instead, try these recovery tactics:

Requalify the deal

To understand why the deal stalled, go back to the basic qualification questions: Is the problem still relevant? Is there budget? Have the decision process and timeline changed? Sometimes a deal hasn't stalled; it was never a real opportunity in the first place. In that case, the right move is to close it and review your ICP criteria.

Multi-thread

A single point of contact is one of the most common causes of stalls. Try to reach the decision-maker, the manager of the user team, or procurement within the same account. When you do, involve your current champion rather than going around them: an offer like "Shall we put together a summary that will help you when you present this project to the board?" both adds value and opens access to new people.

Give them a new, value-driven reason

Instead of simply asking "what's the status?", bring new information: a use case specific to their industry, a short analysis of the problem the customer described, or a simple calculation showing the cost of delay. For example, if the customer said they spend 15 hours a week on manual lead research, reminding them how many hours of labor each month of delay represents can reignite urgency.

Send a clear "closing" email

If there's still no response after all your attempts, send a polite, clear email: "It looks like this isn't a priority for you right now. I'm closing the file for now; if things change, a single reply is all it takes to pick this back up." Emails like this get replies surprisingly often. And if they don't, your pipeline is cleaned up.

Analyze what you lost

When closing unrecoverable deals as "Lost," always record the reason: "no response," "no budget," "competitor chosen," "timing," and so on. Over time, this data shows you at which stage and for what reason your deals stall. To make this systematic, you can follow the steps in our lost deal analysis guide.

Rebalance the pipeline with new opportunities

When you honestly clean out stalled deals, you may find that your pipeline is thinner than expected. That isn't bad news; it's reality becoming visible. The solution is to ramp up new opportunity generation at the top of the funnel rather than clinging to dead deals. For B2B SaaS companies that struggle to build this capacity in-house, SAAS Corner's outbound sales and lead generation service may be an option.

What are the most common mistakes?

Using a single general threshold: A rule like "any deal older than 30 days is stalled" unfairly flags long contract stages while catching problems in short stages too late.
Mistaking seller activity for progress: Six emails sent by the rep don't mean the deal is moving forward. What needs to be measured is action on the buyer's side.
Pushing close dates without question: Every push-back should be recorded along with a reason and a new next step.
Penalizing stalled deals: If reps feel criticized for reporting risky deals, they'll hide information. The goal isn't to assign blame but to intervene early.
Never closing deals: Deals that aren't closed as lost distort reports, forecasts, and team morale. Closing a deal doesn't mean ending the relationship with the customer; it can be reopened later.

Frequently asked questions

How many days of inactivity before a deal is considered stalled?

There's no universal number of days. The soundest approach is to calculate the median duration of each stage in your won deals and use 1.5 times that as the warning threshold and 2 times as the critical threshold. In addition, no meaningful interaction from the buyer for 14–30 days, regardless of stage, is also a strong stall signal.

Should stalled deals be removed from the sales forecast?

Stalled deals at the critical level should either be removed from the forecast or have their probability lowered significantly. Keeping them in the forecast at the stage's standard probability leads to a major variance at quarter end. Deals with a recovery plan can be tracked in a separate "at risk" category.

Do you need special software to detect stalled deals?

No. Most modern CRMs let you handle basic detection with stage age, last activity date, and next step fields. Automation tools and AI speed up tasks such as calculating the risk score automatically, analyzing email content, and sending weekly reports. What matters is that data is entered consistently and completely.

When should I close a stalled deal as lost?

If you still get no response after trying requalification, multi-threading, and a new value-driven approach, the deal should be closed. As a practical rule, if a deal that has crossed the critical threshold shows no concrete progress within two weeks, closing it as lost and recording the reason is better for the health of your pipeline.

Conclusion

Spotting stalled deals in your pipeline isn't a matter of intuition; it's a matter of measurement. Define your stages clearly and derive thresholds for each stage from your own data. Make stage age, last buyer interaction, and next step fields mandatory, and combine these signals into a simple risk score. With weekly automated reports and signal-driven pipeline meetings, you'll see problems weeks in advance. And for stalled deals, you can make the call to recover or close without delay.

As a result, your forecasts get closer to reality, your reps spend their time on winnable deals, and you always know how healthy your pipeline really is. If you'd like to add a stall risk score, automated alerts, and AI-powered call analysis to your CRM, schedule a call with Sales Corner to design a workflow that fits your team's structure together.