The follow-up gap
Most leads are not lost because of what was said on the first call or in the first reply. They are lost to silence afterward — a genuinely good first conversation, followed by nothing, because the lead was not ready to decide in that exact moment and no one circled back. Buyers commonly need several touches before they respond or commit, and without something actively prompting the next follow-up, relying on memory alone fails predictably as the number of active leads grows.
Task reminders tied to pipeline stage
The fix is to attach a default expectation to every pipeline stage: what should have happened, and by when. The moment a deal moves into "Contacted," for example, a task is automatically created — "follow up in two days if there has been no reply." This removes the dependency on any one person remembering to set their own reminder, and it means a deal does not silently stall just because the person handling it got busy with something else.
Building a realistic follow-up cadence
A cadence is simply a planned sequence of touches spaced out over time, varying the channel rather than repeating the identical email five times in a row. A realistic cadence for most small businesses involves somewhere around four to six touches, spread across two to three weeks, mixing calls, emails and messages rather than leaning on just one channel.
A realistic cadence — spaced out, multi-channel, and finite. After the final touch with no response, move the lead to a nurture list rather than leaving it stuck.
The cadence needs an ending, too. If there has been no response after the final planned touch, the deal should move to "Lost" or a long-term nurture list — not sit indefinitely in an active stage where it quietly skews every report without anyone noticing.
The failure mode: a CRM nobody updates
A CRM only functions as a system, not just a database, when stage and task updates happen close to real time. If the whole team logs everything a week later from memory, the data quietly becomes fiction — a reminder fires based on stale information, or does not fire at all, because the trigger it depended on was never accurately recorded in the first place.
The practical fix is to build logging into the moment the work already happens, not into a separate end-of-day chore. Log the call right after hanging up, not from memory at 6pm. Keep the update itself fast — one click to change a stage, a short note rather than a full form — so the friction of using the system stays lower than the friction of skipping it.
- Does every pipeline stage have a defined "next action, by when"?
- Are reminders created automatically, or does each person have to remember to set their own?
- Does the follow-up sequence use more than one channel, not just repeated emails?
- Is there a defined point where an unresponsive lead moves to Lost or a nurture list instead of sitting untouched?
- Are updates logged the same day the interaction happens, not reconstructed from memory later?
A CRM that nobody updates is worse than no CRM at all — it gives false confidence that leads are being tracked.