Every bid team has a version of the same story. A supplier never came back on a price. A buyer question sat unanswered over a long weekend. A clarification went out and the thread simply stopped, and by the time anyone looked, the window had closed.
What makes this category of loss unusual is that it produces no evidence. A lost bid is recorded. A late bid is recorded. A conversation that quietly ended is not recorded anywhere, so it never enters the analysis of why the quarter went the way it did.
A thread that dies produces no artefact. There is nothing in the pipeline to review, so nothing gets fixed.
Why follow-up is the first thing to go
Not because people are careless. Because it is structurally the least urgent task available at any given moment.
Chasing a supplier who has not replied competes with answering the buyer who just did. The buyer is in front of you, the supplier is a note in someone's head. So the follow-up moves to tomorrow, and tomorrow has its own buyer. Multiply that across a bid team and a large number of active pursuits, and a predictable percentage of your threads simply stop.
The scale makes it worse rather than better. A team running six pursuits can hold the outstanding items in memory. A team running sixty cannot, and the ones that fall out are not the unimportant ones, they are the ones that happened to be quiet.
What a follow-up has to be
Automatic follow-up has a bad reputation, deservedly, because most of it is indistinguishable from harassment. The constraints matter more than the capability.
- Scheduled, not immediate. A polite interval, not a nudge the next morning. The point is to be remembered, not to be a nuisance.
- Capped at one per day per contact, regardless of how many deals connect you to that person. Someone quoting three of your pursuits should never receive three chase emails.
- Stopped instantly by a real reply. The single most damaging automated behaviour is the follow-up that arrives after the person has already answered, because it proves nobody read what they sent.
- Carrying something new. A message that repeats the first one is noise. A message that narrows the question, or answers something the recipient is likely wondering, is a reason to respond.
The rule that makes it safe
Follow-ups stop at the deadline. Not soften, not switch to a different template. Stop.
A chase message arriving after a tender has closed tells the recipient that your system does not know what day it is, and it is the kind of small signal that costs more than the follow-up was ever worth. So the deadline is a hard stop, enforced where the sending happens rather than in the schedule.
What this actually buys
Not more emails. Fewer dead threads, which is a different thing.
The gain is concentrated in the unremarkable middle of the pipeline: the pursuits nobody is worried about, which get no attention precisely because nobody is worried about them. Those are where silence does its work, and they are the cheapest wins available to any bid team.
An empty state should say what is true and what happens next, never sit blank.