Rocks, Pebbles and Sand: How to Protect Your Best Deals

Most real estate teams are busy. That is not the problem. The problem is that a day can look full while the best deals barely move.

A fresh enquiry comes in. A site visit needs confirming. Someone asks for a brochure. A team member needs an update. A customer says, “Call me later.” By evening, everyone has worked hard, and the serious opportunities are still waiting for a clear next step.

You have probably heard the jar story before. It lasts because it is simple.

Imagine your day is a jar. Fill it with sand first and there is no room for rocks. Place the rocks first, then the pebbles, and the sand fits around the edges. It is not a motivational idea. It is a priority filter.

Your pipeline never sits still. Leads arrive, change, go cold, revive and disappear. The goal is not to ignore messages, admin or new enquiries. The goal is to stop them from running the whole day.

Rocks: the work that moves deals

A rock changes a deal’s position in a real way. Before you do something, ask whether it will do at least one of these:

• Create a commitment: a visit booked, a decision call agreed, an offer step taken.
• Remove a blocker: budget confirmed, the decision maker involved, the shortlist narrowed.
• Set a dated next step: what happens next, by when, and who owns it.

If the deal would be in the same place after you do it, it is not a rock.

Often the rock is the uncomfortable action: asking for the decision, naming the price, calling the family member who has not seen the flat yet, or telling a lead who is not serious that you are moving on.

For a team leader, this means every serious lead has three things: an owner, a next action and a time. Without them, the deal is not being managed. It is sitting in the bucket.

Pebbles: useful, but not enough

Pebbles keep deals organised: sharing options, updating preferences, checking availability, collecting feedback after a visit, preparing documents and correcting listing details. They make the rocks easier. On their own, they rarely move the customer.

A team can spend a whole day on useful work and still avoid the one action that moves the customer forward. That is the trap. Do the pebbles. Just do not give them your best hours.

Sand: the noise that fills the day

Sand feels productive but creates no progress: vague follow-ups, endless “just checking” messages, calls with nothing decided and nothing recorded, leads with no owner, notes buried in WhatsApp, and admin that leads nowhere.

Some sand is unavoidable, and some days are rightly sand-heavy, such as month end or a launch week. Sand should be contained, assigned or batched. It should not decide the day.

“Won’t I lose new leads if I don’t reply instantly?”

Speed matters, so treat the first response as a rock, but keep it on a timer. A strong first response does one job: it turns interest into a next step. Reply quickly, confirm the requirement in one or two questions, and offer a clear next step with a time: a call, a visit or a shortlist. Then move on.

The practical rhythm

Start the day with reality, not theory. Check what is urgent: fresh enquiries, today’s visits, missed calls, hot follow-ups and owner confirmations. Then sort quickly. What needs action now? What can be scheduled and assigned? What is not worth chasing today?

Your tracking system is the jar. It can be a CRM, a spreadsheet or a disciplined notebook, but every meaningful interaction must leave a trail: what changed, what happens next, and when and who. A notebook works until a second person needs to see it. After that, the trail has to be shared.

If the next step is not written down with a time, it is not a plan. It is a hope.

The one rule

No serious lead should end the day without a next step. That step can be a call, a visit, a shortlist, an owner check, a document follow-up, a negotiation update, or a decision to close the lead.

A long lead list does not mean a healthy pipeline. A healthy pipeline is one where the right opportunities are owned, tracked and moving. Your market will always be noisy. Your process does not have to be.