Your Sphere Isn't One List: How to Segment It Inside Cloze

Referrals convert at a dramatically higher rate than cold leads — often ten to twenty times higher, depending on the source. Most agents already know this. Fewer actually build their database to reflect it.

The usual pattern: every contact goes into the CRM the same way, gets the same newsletter, and gets remembered with the same level of detail — which, in practice, means barely at all. Someone about to list their home and someone who won't move for another year end up receiving identical outreach. That's not a system built around timing. That's a mailing list.

Why One-Size-Fits-All Outreach Fails

As a database grows, treating every contact the same becomes unsustainable. You can't send a truly personal note to five hundred people every month, and trying to forces you toward generic content that serves no one particularly well.

The agents getting the most out of their sphere aren't the ones with the biggest databases. They're the ones who know which twenty or thirty relationships deserve their full attention, and who let a system handle the rest without pretending it's personal when it isn't.

Hot and Warm: The Framework You Already Have

If you've been through Ninja Selling training, you already have this language: Hot and Warm. But the distinction isn't about how close the relationship is — it's about timing. Hot means someone is likely to buy or sell within the next six months. Warm means six to twelve months out.

That's a meaningful difference from how most agents segment their sphere, which tends to be based on how well they know someone rather than where that person actually is in their decision. A close friend who isn't moving for two years and a newer contact who's listing next month don't belong in the same outreach rhythm — and Hot/Warm, done correctly, sorts by actual timeline instead of familiarity.

The agents getting the most out of their sphere aren't the ones with the biggest databases. They're the ones whose Cloze pipeline actually reflects real transaction timing, instead of treating a six-month buyer and a someday-maybe contact exactly the same.

Setting Up Hot and Warm as Stages in Cloze

In Cloze, Hot and Warm aren't tags you apply manually — they're stages in your pipeline, sitting alongside In Contract, Closed, and Lost. This stage layer works alongside two others: a segment for relationship type (Buyer, Seller, Partner, Vendor) and tags for things like referral status. Stage tells you when. Segment tells you who. Tags let you pull specific lists, like everyone who's referred you business. This post is about the stage layer — getting the timing right is where most agents lose the thread first.

Hot contacts deserve individual, timely outreach — a call, a text, a same-day response, because a six-month window closes fast. Warm contacts can run on a consistent, less urgent rhythm — a check-in, a market update — since you have more runway before their decision point arrives.

Let Real Signals Move the Stage

The clearest signal for moving someone from Warm to Hot isn't an email open or a website click — it's something they actually tell you. A mentioned move date, a lease ending, a job relocation, a comment about wanting to list "sometime next year" that quietly becomes "this spring." Log it as soon as you hear it, and update the stage the same day.

This is where Cloze earns its keep. A note logged in the moment becomes the reason you catch the shift from Warm to Hot before the contact even realizes they're ready to act — instead of finding out when they've already called someone else.

Reviewing Hot and Warm

This isn't a one-time setup. Timelines shift constantly — a Warm contact moves to Hot the moment their decision window drops inside six months, and a Hot contact moves to In Contract once they're actually under one. The stage should reflect the real timeline, checked in regularly, not sit fixed at whatever you guessed when you first built the pipeline.

The Real Payoff

A well-segmented sphere isn't about doing more outreach. It's about making sure your best relationships never get lost in a database built for volume instead of depth. The size of your list was never the asset. The clarity of what to do with it is.

Segmenting a sphere this way, with the right tags and triggers built to support it, is exactly the kind of setup I walk agents through inside The Sandra Alexander Method.