Where brokerages actually lose leads

Ask a brokerage why it lost a deal and you will hear about price, or about a competitor, or about a client who was never serious. Look at the records instead and a duller answer appears. The enquiry arrived, somebody called once, and then nothing happened for eleven days.

Nobody decided to lose that lead. It simply fell through the gap between "I will call them tomorrow" and a Tuesday that turned out to be busy.

The shape of the problem

A lead has a half-life. The first hour after an enquiry is worth more than the whole of the following week, and every day after that costs you something you cannot get back. This is not a motivational poster; it is what the timestamps show. A lead contacted on the day it arrives converts at a multiple of one contacted three days later, because by day three the person has rung two other numbers.

The awkward part is that nobody in the office can see the delay happening. An agent with forty leads does not experience eleven days of silence on one of them. They experience a busy fortnight. The lead that went quiet is exactly the lead that generates no reminders, no calls, no notes — it disappears precisely because nothing is happening to it.

Silence has to be made visible

The fix is not exhortation. It is making the absence of activity into an event.

• Give every stage a deadline. An enquiry that has not been contacted in three days is not "in progress", it is stalled.
• When the deadline passes, take the lead back. Not as a punishment — as a routing decision. Somebody with capacity should have it.
• Say how long it sat. "No update for 11 days" is a fact an admin can act on. "Needs follow-up" is not.

BluPlots does this with per-stage timeouts. Enquiry, New and Contacted get three days each; Site Visit Scheduled, Site Visit Done and Negotiation get seven. Miss one and the lead returns to the admin queue with the number of days attached. Nobody has to notice. The system notices.

The second leak: the same person, twice

The other quiet loss is duplication. A buyer rings on Monday, fills in your website form on Thursday, and walks in on Saturday. Three records, three agents, three versions of the same conversation. The client experiences a firm that does not know who they are.

Matching on phone or email at the moment of creation catches most of this. The important design choice is what to do next: flag it, never drop it. A duplicate you can merge is a small administrative problem. A dropped enquiry, because a system decided it had seen that number before, is a lost client and you will never know it happened.

What to measure

Three numbers tell you most of what you need.

• Time to first contact. Median, not average — the average hides the disasters.
• Leads with no activity in seven days. As a proportion of open leads. If it is above ten per cent, you have a routing problem, not an effort problem.
• Stage age. How long leads sit in each stage before moving. The stage where everything piles up is where your process is actually broken.

None of this is exotic. It is the kind of arithmetic a spreadsheet could do, if anybody had time to maintain the spreadsheet. That is the whole argument for putting it in the system that already holds the leads: the counting happens whether or not anyone remembers to count.