What is an uncalled-lead ladder?
A ladder every new lead climbs if nobody calls or texts it. Each rung is a working-hours clock, and each rung has a person on it. The lead never sits still long enough to go cold.
Most teams talk about speed to lead. A ladder is what makes it happen when nobody is watching.
Why speed-to-lead talk doesn't move leads
The old fix on Ken Pozek's team was a conversation. A coach noticed a lead nobody called, brought it up in the 1:1, and the agent promised to call. By then the lead was days old.
That only worked when somebody noticed. Most of the time nobody did. And when a lead source looked bad, nobody could tell whether the leads were bad or just never worked.
A meeting can't call a lead. A clock can make sure someone does.
How Ken Pozek's team runs it now
- Two working hours, no call or text: the agent gets a nudge.
- Three hours: their coach hears about it.
- Four hours: the lead moves to the team's inside sales agent, who calls it.
The clock counts 9 to 5 Eastern, Monday to Friday, holidays off. It starts when the lead became its current agent's, so a lead handed over at 4 PM isn't already late. Every lead is re-checked right before a message goes out, so nobody gets nudged about a lead they called a minute ago.
In its first 12 days live, 13 leads reached the two-hour nudge. Two reached a coach. One got pulled. The ladder almost never has to climb, because the first rung does the work.
The template
Write your ladder. Three steps, three times, three names. Then decide what counts as a touch, in writing, so nobody argues about it later.
| Step | When | What happens | Who |
|---|---|---|---|
| 1 | ____ working hours, no touch | The agent gets a reminder | The agent |
| 2 | ____ working hours | The coach sees it | The coach |
| 3 | ____ working hours | The lead moves to someone who will call | ISA or next agent |
What counts as a touch on Ken's team:
- A call attempt. An attempt counts.
- A text a person sent.
- An inbound call someone answered.
- Not an automated drip. Not a missed inbound call.
Run it by hand for two weeks with a morning check. You'll see quickly whether your problem is the first call or everything after it.
Build your own with AI
The template tells you the rules. The kit builds you a tool that finds every lead that broke them, from your own call and text logs, every morning.
An uncalled-lead tool in Claude. Drop in your new leads, call log and text log. Get every agent's median time to first touch on working hours, every lead past each rung, a right-now list of untouched leads, and the message for each rung ready to send.
- Write your ladder.Use the template above: your three times and who catches a pulled lead.
- Export new leads from your CRM.Created date, assigned agent, assignment date if you have it, stage, source. Last 14 days.
- Export your call and text logs.Same 14 days. The text log needs to show whether a person or an automation sent each text.
- Trim the files.Delete email columns and anything you don't need. The tool needs names, agents, times and stages.
- Paste the prompt into Claude.Attach the files, fill in the brackets, and send. Answer its mapping questions. Run it again every morning.
Build me an uncalled-lead tool for my real estate team as an interactive artifact. About my team: - [NUMBER] agents
Build me an uncalled-lead tool for my real estate team as an interactive artifact. About my team: - [NUMBER] agents - Our CRM: [Follow Up Boss / Lofty / other] - Working hours: [9 AM to 5 PM, Monday to Friday], time zone [ET], holidays off - Our ladder: [2] working hours with no touch, the agent is nudged. [3], their coach hears. [4], the lead moves to [our ISA / the next agent up]. I'm attaching exports covering the last 14 days. Each file name says where it came from: 1. New leads: created date, assigned agent, the date it was assigned to that agent if we have it, stage, source, and whether there's a phone number 2. Call log: lead, agent, time, inbound or outbound, outcome 3. Text log: lead, agent, time, inbound or outbound, and whether a person or an automation sent it Build a tool that does this: 1. Map before you count. Show me the columns you found in each file and how you'll use them. Ask me how to tell an automated text from one a person sent. Ask me which sources are agents' own leads, so we can leave them out. Don't guess. 2. Find each lead's first touch. A touch is an outbound call (an attempt counts), a text a person sent, or an inbound call someone answered. Automated drips and missed inbound calls are not touches. 3. Start each lead's clock when it was assigned to its current agent, or when it was created if there's no assignment date. Count only our working hours. 4. Put every lead on a rung: touched in time, past rung 1 (the agent should have been nudged), past rung 2 (the coach should know), past rung 3 (it should have moved). Flag any lead that has never been touched. 5. For each agent, show the median working minutes to first touch, how many leads went past each rung, and their untouched leads right now, oldest first. 6. Give me a "right now" list: every untouched lead, how long it has waited in working hours, and which rung it's on. 7. Write the message for each rung in plain words: the nudge to the agent, the heads-up to the coach, and the hand-off note when a lead moves. One button copies each. Rules: - Never invent or estimate a time. If a column is missing, say what can't be measured and why. - Leave out leads with no phone, do-not-call, or a bad number, and tell me how many you left out. - Keep the data inside the artifact. - I'll upload new files every morning, so make it easy to run again.
Unlock the full prompt. Free. You'll also get every new blueprint Monday at 3 PM, a day before it's public.
What it won't do: Watch the clock for you. It's a snapshot of the files you give it, so it can't nudge an agent at the two-hour mark or move a lead at four. That part is what the platform does.
What a sheet can't do
A sheet can't watch the clock. Running this by hand means someone checking every new lead, every few hours, every day, and messaging the right person at the right minute. That is the job the platform does every 15 minutes on Ken's team. It's in the beta.
Questions owners ask
How fast should a new real estate lead be called?
Faster than your ladder allows. On Ken Pozek's team, two working hours with no call or text means the lead is late, and it starts climbing. Pick numbers your team can actually hold, then let a clock enforce them instead of a meeting.
Why count working hours instead of clock hours?
So the rule is fair and agents trust it. Ours counts 9 to 5 Eastern, Monday to Friday, holidays off. A lead that lands at 6 PM isn't late by 8 AM. A rule that punishes people for sleeping gets ignored.
What counts as touching a lead?
A call attempt, a text a person sent, or an inbound call someone answered. An automated drip doesn't count, and neither does a missed inbound call. If a machine did it, the lead hasn't heard from a person.
What happens to the agent when a lead gets pulled?
The lead moves to the inside sales agent, and it shows on the agent's report card as a pulled lead. One pull is a moment. A pattern of pulls is a conversation the coach can have with proof.
Won't the person who catches pulled leads get buried?
Not if you plan for it. The catch is capped at 10 pulls a day. When we turned the ladder on, leads that were already past two hours were left alone, so it didn't start with a backlog.
Do I need software to run this?
No. The ladder is three lines on a page and a daily check. The AI build kit gets you a tool in Claude that finds every uncalled lead from your own exports. The platform does it every 15 minutes.