Follow-up is a schedule, not a feeling
A follow-up that lives in somebody's memory is not a follow-up. Every conversation ends with a dated next action, or the lead closes with a reason.
Every sales manager believes his team follows up. Ask how, and the answer describes an intention: we stay in touch, we keep after them, nothing slips.
Intention is not a schedule. A schedule is a dated commitment that surfaces on the correct day whether or not anybody remembers it. Everything else is a feeling about a buyer, and a feeling does not appear on Monday morning's list.
Leads do not go cold, they go quiet#
"Cold" is a comfortable word because it puts the fault on the buyer. He lost interest. He was never serious. He was only comparing.
Sometimes that is true. More often what happened was a gap. The buyer walked the site, went home, and heard nothing for a week and a half. In that silence he spoke to two other people, and one of them rang back within a couple of days with the floor plan he had asked about.
Nothing was decided against you. You were simply absent during the only period in which he was actively thinking about it. By the time your call came, his question had already moved from which project to which bank.
This is why follow-up discipline pays better than any change to the pitch. The pitch competes on quality. The schedule competes on presence, and presence is the cheaper of the two to fix.
Two endings, and no third#
Every conversation with a prospective buyer must finish in one of two states.
- A next action with a date. One name, one sentence saying what will happen, and the day it happens on. "Send revised cost sheet with the corner unit — Thursday." Not "follow up soon".
- Closed, with a reason. He booked elsewhere. His budget is half of ours. He is not buying for two years. The unit he wanted is already sold.
Anything else is a lead in limbo, and limbo is where a pipeline turns into a number nobody trusts. A record with no next date and no closing reason is not being worked. It is being stored.
The reason matters as much as the date. A team that cannot close a lead without an argument will never close one, and the list grows until it is decorative. Make spoke, not interested a single, blameless action. The manager's job is to read those reasons, not to punish them.
Where the schedule breaks#
The method is trivial. The failures are specific, and most sales offices are running several of them at once.
"Will call next week." No day, so no list can carry it. Next week arrives and the item is invisible, because the only place it ever existed was the end of a sentence.
The reminder that fires at the wrong moment. It rings while the caller is on another call. He dismisses it to stop the noise. The dismissal is permanent and the record now reads as handled. An alert that can be silenced without recording an outcome is worse than no alert, and the whole failure class is an alert that rings for everything.
An overdue list longer than the working day. When the pending list is bigger than anyone can finish, it stops being a set of obligations and becomes wallpaper. A couple of overdue items get attention; a screen full of them gets scrolled past. The overdue count is the health measure of the whole system, and letting it grow without limit kills the system quietly.
Follow-ups timed for when the buyer is at work. Everything lands at ten in the morning because that is when the caller starts his day. Half the buyers are in meetings, the other half are driving. The item is attempted, unanswered and marked done. The record says contacted. Nobody was contacted.
The eternal reschedule. The same item is pushed forward week after week with no new information between pushes. Each push feels like diligence. Together they are a decision nobody is willing to make — the lead is dead and no one wants to write that down. An item rescheduled many times without a conversation should look different on the screen from one due tomorrow.
The shared spreadsheet. It has no notion of a date arriving, no notion of whose item this is, and no memory of what was promised. It is the most common follow-up system in the industry, and its particular failures are set out in leads that die in Excel.
What a working list looks like#
Small. That is the first property, and it decides all the others.
A caller opens his day and sees a handful of items due today, each carrying one line of context: who, what was last said, what was promised. If he has to open the record to remember the conversation, he will not open it. He will ring and improvise, and the buyer will hear it.
Every item needs a visible reason. "Call the customer" is an instruction. "Call — promised the revised cost sheet after he asked about the corner unit" is a conversation the buyer recognises from the first sentence. What the record itself has to carry for that to be possible is in what a lead record should hold.
And closing must be as easy as scheduling. If marking a lead dead means a long form and a dropdown nobody understands, the list only ever grows. Shrinking it is the healthy behaviour, so make it the cheapest action on the screen.
The ledger of what was not sent#
We built two things around this, and the second one surprised us.
The first was a ceiling. Every message has a home — a quiet feed, a daily bulletin, a knock, or the one tone that interrupts — and its home can only ever make a message quieter, never louder. Nothing promotes itself.
The second was a ledger recording who was told what and why, including the occasions when nothing was sent. That last entry is the one that earns its keep. When somebody says they were never informed, the useful record is not the list of messages that went out. It is the reasoned line explaining why one did not.
The manager reads reasons, not counts#
The weekly review in most offices is a count. Calls made, site visits done, bookings closed. Counts are easy to produce and easy to inflate — an unanswered call is still a call.
The useful review reads the closing reasons instead. A run of leads closed as budget too low is a pricing or a targeting problem, not a sales problem. A run closed as unit not available means the inventory the team is being asked to sell is not the inventory buyers are coming for. A run closed as no response usually means the first call went out too late.
None of that shows up in a count. All of it shows up in the reasons, and only if the reasons are cheap to record and honestly written.
The same principle governs work inside the office as governs buyers outside it. An obligation with a date can be watched, and something drifting can be seen before the deadline rather than after, which is the argument in work slips before it is late.
The short version#
A follow-up that lives in somebody's memory is not a follow-up. Every conversation ends with a dated next action or a closing reason, and there is no third ending.
Keep the due list small enough to finish, give each item a reason the buyer would recognise, and make closing a lead as easy as postponing one. Then read the reasons at month end — the count will tell you the team was busy, and the reasons will tell you what to change.