// Guides · Pipeline
Why do deals go quiet, and how do you catch it before the quarter ends?
Deals go quiet because the buyer's priority changed and nobody on your side noticed in time. The signal shows up in the inbox and the calendar weeks before it shows up in the pipeline: replies slow down, meetings shrink, the agreed next step passes without a date. You catch it by measuring days since the last inbound reply on every open deal, comparing that against how old the deal is for its stage, and reviewing the outliers every week instead of at quarter end.
What does "quiet" actually mean?
A deal is quiet when the buyer has stopped replying, not when the rep has stopped logging. Most CRMs measure the wrong side of that. "Last activity" on a deal record usually counts anything the rep did, including a logged call attempt that never connected, so a rep can keep a deal looking alive for a month by sending follow-ups nobody answers. I spent the better part of a decade on the CRM engineering side at HubSpot, and I watched a lot of pipelines go quiet from inside the tool that was supposed to catch it.
The number that matters is inbound: the last time a person at the buyer wrote back or accepted a meeting, or the last time a thread got forwarded inside their company. Count from that date. A deal with three outbound touches and zero inbound in twelve days is quiet, whatever the stage field says.
Teams use different words for this. Stalled, dark, cold, and one phrase I heard more than once in sales calls this year, "deal delays and attrition." They all describe inbound silence past the point where it is normal for that deal, and the method below treats them as one condition.
Quiet is also relative. A two-week gap in a nine-month enterprise cycle is normal, and the same gap in a three-week self-serve upgrade usually means the deal is over, so silence has to be measured against the deal's own cadence rather than a fixed number. Your numbers will differ from the ones I use below.
Why do deals go quiet?
Five causes account for most of it, in my experience. From the outside they look identical, and the stage field in the CRM has no way to tell them apart.
The compelling event moved. The renewal got pushed a quarter, or the hire who was going to own the rollout did not happen. Nothing is wrong with you; the reason to buy this month evaporated. This is the most common cause I see and also the most recoverable, because the reason usually comes back.
Your champion lost the argument, or left. They took the idea to a manager and got a "not now." Or they changed jobs, and the deal went with them. A single-threaded deal has no way to survive that, and when we go through a team's pipeline during a free audit, most of the quiet deals turn out to be single-threaded.
The next step was never actually agreed. "Great, I'll send the proposal" is not a next step. A next step has a date and a person attached to it, and a deal that ends a call without one goes quiet about as fast as you'd expect from a conversation with no scheduled continuation.
They are comparing, and have not told you. Silence after a proposal often means the buyer is running the same process with two other vendors and would rather not say so. You can recover this one by asking the direct question. Waiting does not recover it.
The price landed badly. The proposal arrived, the number was higher than the champion expected, and rather than say so they went dark. Sellers usually find out weeks later, when the silence finally breaks and the answer is already no.
What are the early signals?
Every cause above leaves a trace in email and calendar data before it changes anything in the CRM. These are the six I would watch, where each one lives, and the threshold at which to act.
| Signal | Where it lives | When to act |
|---|---|---|
| Reply latency doubles | Email threads with the buying group | A contact who replied within a day now takes three or more, twice in a row |
| Meeting declined and not rescheduled | Calendar | Any decline without a counter-proposal inside five business days |
| Buying group shrinks | Email recipients, meeting attendees | A stakeholder who was on the thread stops appearing on it |
| Next-step date passes | The commitment made on the last call | The day after; not the next pipeline review |
| Close date moves twice | Deal record history | Second slip, regardless of the reason given |
| Internal forwards stop | Email (new names cc'd, threads forwarded) | A deal that was gaining internal readers stops gaining them |
Four of the six are inbound signals, things the buyer did or stopped doing, and a rep cannot log them because the rep is not the one doing them. A CRM that only knows what the rep typed will never show them. A revenue leader put this to us this summer as her one question for any CRM: "where does our pipeline stagnate, and why?" Most of the answer to that is in those four rows.
How do you catch it before the quarter ends?
Run a fifteen-minute sweep once a week. This is not the pipeline review, which is about the whole board. It is one filter, applied to every open deal.
- Sort every open deal by days since last inbound reply. If your CRM cannot produce that number, sort by last activity and correct by hand for outbound noise. It is worth the ten minutes.
- Compare against stage age. Write down the normal number of days a deal spends in each stage for your motion. A deal past that number with no inbound touch is drifting; a deal past double that number is dark.
- Sort into three buckets. Fresh (inbound inside its cadence), drifting (past cadence, past stage age), dark (past double). Only drifting deals get action this week. Dark deals get a decision.
- Attach one action to each drifting deal with a date, and put it on the calendar, not in a notes field.
A worked example. A team runs a fourteen-deal pipeline with a typical thirty-day cycle: seven days in Discovery, ten in Evaluation, ten in Proposal, three in Negotiation. On a Monday sweep, nine deals have inbound activity inside seven days, so they are fresh. Three are in Proposal with fourteen to eighteen days since the buyer last replied; those are drifting, and each gets a re-engagement action dated this week. Two are in Evaluation with more than thirty days of silence, which makes them dark. One of those gets a closing question by email, and the other is moved to a "parked" stage and out of the forecast. The forecast is now honest, and the three drifting deals got attention twenty days earlier than the quarter-end scramble would have given them.
What do you do with a quiet deal?
Not "just checking in." That message tells the buyer you have nothing new and gives them nothing to reply to. There are four moves that work, listed roughly in order of how quiet the deal is.
Give them a reason to reply. A relevant customer story, or a number from their own data that you noticed. Make replying easy and worth their time. Reminding them that you exist is not the goal.
Open a second thread. If the champion has gone quiet, the deal is single-threaded and you need another voice at the account, which usually means asking the champion for an introduction, or going through a mutual connection if they have stopped answering. A deal with two active contacts survives a champion's bad week.
Ask the closing question. "Is this still a priority this quarter, or should I check back in October?" In my experience buyers answer that honestly far more often than sellers expect, and either answer is better than silence.
Move it out. A quiet deal in your commit number is a forecast miss you have already scheduled. If two attempts get nothing, park it and take it out of the forecast. Parked deals come back; deals that sit in Proposal for ninety days do not.
Why doesn't the CRM tell you?
Because the traditional CRM is a system of record. It stores what someone typed into it, and the stage field is a rep's opinion about where the deal is, entered whenever they last had time. Nothing in that design watches the inbox for the buyer going quiet, and "last activity" counts the rep's own follow-ups as signs of life. This is where I'd push back on the usual advice about data hygiene: the record can be perfectly accurate and the deal still goes quiet, because nothing in the design reads the buyer's half of the thread.
What you want is a system that reads the signals itself. If you are evaluating tools for this problem specifically, these are the questions I would ask:
- Does it capture inbound email and calendar activity automatically, without the rep logging it, so that "days since last reply" is a real number?
- Does it know the normal stage age for your motion and flag deals that are past it, rather than leaving you to build the report?
- When it flags a drifting deal, does it prepare the re-engagement for you, or just add a task to the pile?
- Does it keep the human in the loop? A tool that emails your buyers on its own is a different risk, and most teams do not want it.
This is the problem Ahoy was built around. It captures every email, call, and meeting on its own, watches for deal drift against your pipeline's real cadence, and drafts the re-engagement for one-tap approval. The judgment stays with the rep. If you want to see it against your own pipeline, the free CRM audit is a 45-minute look at how many of your deals are quiet right now, with no data connected and nothing to install.
Frequently asked questions
What is a stalled deal?
A stalled deal is an open opportunity where the buyer has stopped responding and the agreed next step has passed without being rescheduled. The defining measure is inbound silence: days since anyone at the buyer replied, accepted a meeting, or forwarded a thread. Outbound activity from the rep does not count.
How long before a deal counts as quiet?
Longer than the deal's normal reply cadence, and longer than the normal age of its stage. For a thirty-day cycle, a week of inbound silence is worth a look and two weeks is a drifting deal. For a nine-month enterprise cycle, two weeks is routine. Measure against your own motion, not a fixed number.
Should you remove quiet deals from the forecast?
Yes, once two re-engagement attempts have gone unanswered. A quiet deal left in commit is a miss you have already scheduled. Park it in a stage that stays out of the forecast and revisit it monthly; parked deals return more often than deals left to age in Proposal.
How do you re-engage a deal that went quiet?
Give the buyer a specific reason to reply, open a second thread at the account so the deal is no longer single-threaded, and ask the closing question directly: is this still a priority this quarter? Avoid "just checking in," which gives them nothing to answer.
What is deal drift?
Deal drift is the gap between where a deal sits in the pipeline and what the buyer's actual behavior says. A deal marked Proposal with eighteen days of inbound silence has drifted. Catching drift early is the whole point of a weekly sweep, and it is what an AI-native CRM watches for automatically.
Related guides: Which deals are at risk this quarter? · How do you run a weekly pipeline review in 30 minutes? · Why don't sales reps update the CRM? · Sales velocity calculator · All guides