Nobody loses a lead. They just never call it back

Look honestly at the enquiries you did not convert last quarter. A few went to a better property, a few were never serious, and the rest — usually the biggest group — simply went quiet. Not because someone outbid you. Because nine days passed.

Why the pipeline lies to you

Most brokers can tell you their lead count and almost none can tell you which lead is due today. Those are different questions, and only the second one changes revenue. A pipeline view that shows everything you have ever touched, sorted by stage, quietly hides the one fact that matters: this person expected a call on Tuesday and it is Friday.

A stage is a description. A due date is an obligation.

The rule worth enforcing in software

Every time a lead moves, the next contact gets scheduled before you are allowed to move on. Not optional, not a reminder you might set — part of the move itself. It feels bureaucratic for about two days, and then your mornings change shape: the first thing you see is six names who are owed a call, not a board of ninety cards.

The corollary is that a lead with no next step is a bug. If your system lets one exist, it will accumulate them, and they will be the ones that go quiet.

What to say when you call back

The reason follow-ups get skipped is not laziness, it is awkwardness — there is nothing new to say. So make sure there is. If the requirement is recorded properly, matching should hand you a reason: two listings that fit their budget and locality since you last spoke, or a price drop on the one they liked.

That is the real argument for keeping requirements as structured records rather than notes. Not tidiness. It is what turns an uncomfortable check-in call into a useful one.