Guide · July 2026

How to build a daily who-to-call list from your sphere

Most agents don’t have a lead problem — they have a who-do-I-call-firstproblem. The database is right there; the paralysis is picking. Here’s a system you can run in 15 minutes a morning, with index cards or with software.

Step 1 — Segment once, roughly

Don’t over-engineer this. Four buckets cover a working database: A — advocates who’d refer you tomorrow (past clients who loved you, close friends in-market); B — people who’d take your call warmly; C — they’d remember you with a prompt; D — everyone else. Spend an afternoon tagging, accept imperfection, and move on. The system self-corrects as you call.

Step 2 — Score by relationship temperature, not recency

The mistake most CRMs bake in is sorting by last contacted. What actually predicts a good call is temperature: how warm is this relationship right now, and is there a reason to talk? A simple manual version: hot = life event or market event touching them this month (new baby, job change, a sale on their street); warm = A/B contact you haven’t talked to in 60–90 days; cool = C contact due a quarterly touch. Every morning, hot outranks warm outranks cool — regardless of when you last called.

Step 3 — Cap the list at five

A 40-name call list is a guilt list; nobody finishes it, so nobody starts it. Five calls is finishable before your first showing, and five finished calls a day is 25 real conversations a week — more than most agents have in a month. If you consistently finish early, raise it to seven. Never higher.

Step 4 — Attach the reason to the name

The list isn’t “call Susan.” It’s “call Susan — her home anniversary is Thursday and a comp on her street just closed 4% over ask.” Write the reason next to every name the night before or first thing, never mid-call-block. When the reason is attached, the call dials itself; when it isn’t, you’ll reorganize your desk instead.

Step 5 — Log one line, feed tomorrow

After each call, one line: what you learned, and when they should surface again (“kid starts college in fall → touch base June”). That single habit is what turns a static database into a compounding one — tomorrow’s list builds itself from today’s notes.

The honest part: this is a discipline problem before it’s a software problem

You can run everything above with a spreadsheet and 15 minutes a morning, and plenty of great agents do. Software earns its keep on steps 2, 4, and 5 — the scoring, the reasons, and the logging — because those are the parts humans skip when the day gets loud. That’s the exact job Roost’s Priority Action Center was built around: every morning it scores your database by relationship temperature, ranks the calls, and drafts the talking points from your own history with each person. You can see it working with sample data in the live demo — no sign-up.