Every pipeline contains a few deals that are not really happening. They have a name, a value, a stage and a date, and they look exactly like the deals that are happening. The only difference is that nobody has spoken to the customer in a month.
Nobody notices, and it is worth being precise about why.
Silence produces nothing to notice
Everything else in a sales week arrives as an event. An email lands. A phone rings. A message appears. Someone asks for a quote and there it is, sitting in front of you demanding a response.
Silence has no arrival. It is the absence of all of that. A deal that has gone quiet does not send you anything — it simply stops sending you things, which feels identical to a calm week.
So the deal stays in the pipeline looking healthy. The stage still says "proposal sent", which was true in April and is still technically true in June. The forecast still counts it. And the salesperson, who has thirty other things making noise, attends to the ones making noise.
This is not carelessness. Attention follows signal, and silence has none. The only way to see it is to build something that turns the absence of contact into a visible thing — a number, a list, a flag. Otherwise it stays invisible right up until someone asks about that deal in a quarterly review and everyone goes slightly still.
A slow deal and a dead deal look the same from the outside
This is the part that makes people give up on the whole exercise. Long gaps are completely normal in some deals. A company buying a system with three approvers will go dark for weeks at a time while nothing is wrong at all. Chasing them every four days makes you look anxious.
The distinction is not about the length of the gap. It is about whether there is a known reason for it.
- ✓A slow deal has a stated cause. They told you the budget opens in July. They told you the operations director is away. You know what you are waiting for and roughly when it ends.
- ✓A quiet deal has no stated cause. Something was in motion, and then it was not, and nobody said why. That gap is not information — it is missing information.
Written like that it sounds obvious. In practice teams routinely mistake the second for the first, because the polite story is always available: they are probably busy, it is probably the holidays, they will probably come back. Sometimes true. But "probably" is doing an enormous amount of work in that sentence, and it costs nothing to find out.
The useful habit is to record the reason, not just the date. "Waiting" is not a status. "Waiting on their board meeting, 12 June" is. If you cannot write the second version, the deal is quiet rather than slow, whatever the pipeline says.
How long is too long
There is no universal number, and anyone who gives you one has not sold many different things. The right threshold comes from the deal itself, and there are three things that set it.
- ✓How urgent the customer's problem is. Someone whose equipment broke yesterday is a different animal from someone planning next year's refit. Urgency compresses everything.
- ✓How many people have to agree. One owner deciding is fast. A committee is slow, and the slowness is structural rather than a lack of interest.
- ✓Where the deal is in its own arc. A gap right after a first conversation means something quite different from a gap after a proposal and a pricing negotiation. Late silence is heavier than early silence, because more has been invested on both sides.
A rough shape that holds up across most businesses: for a transactional sale where one person decides, a week without contact is already long. For a considered purchase with a proposal on the table, two to three weeks. For a large, multi-approver purchase, four to six. Those are starting points to argue with, not rules — the point is that you should have a number per type of deal, chosen on purpose, rather than a general feeling that things seem fine.
Set the number once and the whole problem changes character. You stop asking "does this feel stale?", which nobody can answer consistently, and start asking "has this passed its threshold?", which is arithmetic.
What a good follow-up says after a gap
The instinct after three silent weeks is to send something soft. "Just checking in." "Hope all is well." "Bumping this to the top of your inbox." These are all the same message, which is: I would like something from you but I do not want to seem like I am asking. People can feel it, and they respond to it the way they respond to all low-stakes messages — later, or never.
A follow-up after a gap works when it does three things: it says how long it has been, it makes it easy to say no, and it asks for one specific thing that takes ten seconds to give.
Something like this:
Hi Marcus — we spoke on 14 May about the second warehouse, and I sent the revised quote the week after. I have not heard back since, which usually means the timing moved or you went another way. Both are completely fine and I would rather know.
If it has slipped to next year's budget, say so and I will leave it alone until then. If it is still live, I will hold the pricing to the end of the month. Either way a one-line reply is enough.
Nothing clever is happening there. It names the date, so there is no pretending the gap did not occur. It offers the exits — moved, or went elsewhere — which removes the awkwardness that is often the actual reason people do not reply. It gives one small reason to answer now. And it asks for a single line rather than a meeting, which is the difference between a reply and a task.
The counter-intuitive bit is that giving people permission to say no gets you more answers, not fewer. Most silence is not rejection. It is a person who has nothing good to tell you and would rather not compose a paragraph explaining that. Make the awkward answer cheap and it arrives.
Closing something as lost is a healthy act
Pipelines get clogged because marking a deal lost feels like admitting failure, so it stays open at 40% forever. The cost of that is not emotional, it is practical.
- ✓Your forecast becomes fiction. If a quarter of the pipeline is dead, every number built on it is wrong, and decisions get made on those numbers.
- ✓Attention gets spread over things that cannot convert. Every dead deal sitting in the list is a small tax on reading the list.
- ✓You lose the information. A deal closed as lost, with a reason, is data. A deal left open is nothing at all.
Closing something is also not permanent. A deal marked lost with the reason "budget moved to next FY" is a better prospect next year than a deal left rotting at 40%, because the reason is written down and you can come back at exactly the right moment. Lost means "not now, and here is why", and that is a genuinely useful record.
A workable rule: after two unanswered follow-ups spaced sensibly apart, send a short closing note. I am assuming this is not going ahead and closing it off my side — if that is wrong, just say and I will pick it straight back up. That message pulls a surprising number of deals back from the dead, precisely because it is the first one that does not need anything from them.
Where this goes wrong
All of the above can be automated, and automating it badly is worse than not doing it. Three failures are close to universal, and they are worth naming plainly.
Reminders that fire too often become wallpaper. A system that flags every deal touched more than seven days ago will produce a list of forty items every Monday. Nobody can act on forty. So people start clearing the list without reading it, and within a month the flag means nothing — including on the three deals where it genuinely mattered. A warning is only a warning while it is rare. If you are going to set a threshold, set it long enough that the list stays short enough to act on.
Chasing every quiet deal is a waste of a week. Not every deal deserves the effort. A small one-off order that went quiet may simply not be worth two follow-ups and a closing note. Silence on a large, late-stage deal is worth a phone call the same day. Same signal, wildly different response, and a system that treats them identically is teaching your team to ignore it.
Some silence is a straight no. This is the one people resist. A share of quiet deals are quiet because the person decided against you and does not want the conversation. No sequence of nudges changes that; it only converts a soft no into an irritated one, and occasionally into someone who will not take your call again in three years when the situation has changed. Two good attempts and a clean exit protects a relationship that a six-email cadence would burn.
The honest summary is that the value here is in noticing, not in automatic chasing. The system's job is to put the quiet deals in front of a person who can judge them. The judging should stay human, because the difference between a deal worth a call and a deal worth letting go is exactly the kind of thing software is bad at and experienced salespeople are good at.
The short version
Silence is the only thing in a sales pipeline that does not announce itself, which is why it is the thing most likely to be missed. Pick a threshold per type of deal, measure from the last two-way contact rather than your own last email, and treat a passed threshold as a prompt to find out where you stand.
Then write a follow-up that names the gap and makes no an easy answer — and when no arrives, close it properly with the reason. A shorter, truer pipeline is worth more than a long one full of deals that ended months ago and never told anybody.
Common questions
It depends on the deal, and using one number for everything is what makes these alerts useless. A rough starting point is a week for a simple sale with one decision-maker, two to three weeks for a considered purchase with a proposal out, and four to six for anything with a committee. Pick a number per type of deal deliberately, then adjust it after a couple of months of seeing what it catches.
Say how long it has been, offer them the exit, and ask for one small thing. Naming the gap directly reads as confident rather than needy, and explicitly saying that a no is fine removes the awkwardness that is usually the real reason nobody replied. Asking for a one-line answer instead of a meeting also helps, because a reply is easy and a meeting is a task.
Yes, after two sensible attempts and a short closing note. Leaving it open does not keep it alive, it only makes your forecast wrong and your pipeline harder to read. Closing it with the reason written down is far more useful later than an abandoned deal sitting at 40%, because the reason tells you when it is worth coming back.
No. Quiet is a state of not knowing; lost is a conclusion. Plenty of quiet deals come back, particularly when the silence was caused by something on their side that had nothing to do with you. The point of noticing silence is to convert not knowing into knowing, whichever way that lands.
You can automate the noticing, and you should. Automating the chasing tends to backfire, because a generic sequence firing at a real relationship is obvious to the person receiving it. The better arrangement is a system that puts a short list of quiet deals in front of a person each week and leaves the judgement to them.
Almost always because there are too many. A list of forty flagged deals cannot be acted on, so people clear it rather than read it, and after a few weeks the flag carries no meaning at all. Lengthening the threshold until the weekly list is small enough to actually work through usually fixes it faster than any change to the wording.
We build websites and run SEO & AEO for Singapore businesses. HeyAda is a Singapore web studio — design, copywriting, code and SEO, handled end to end. We write these guides to share what actually works, in plain English. If your site isn't getting found, say hi.
Do you know which of your deals have gone quiet?
Most teams cannot answer that without opening every record one by one, which is why nobody does it. If you want to know what it would take to see it at a glance, tell me how your pipeline works and I will tell you honestly whether it is a system problem or just a habit worth starting.