RevOps & CRM

Speed to lead is not a metric. It is a system, and most teams are winging it.

By Daniel Speiss, OpsPal · Published September 9, 2026 · 9 min read

Built from three recorded working sessions with an inbound sales team running paid ads. The team is anonymized. The quotes are real.

I was on a call with an owner a few weeks ago, screen shared, looking at his CRM together. He runs a two-person inbound team on paid ads and he is good at his job. Cares about it. Works every lead himself on top of a full-time role.

He was scrolling one of his best leads, a high score, exactly the kind he pays for. And he said, out loud, “I know I called this guy. Did I not log a call here?”

No call on the record. Then a minute later, scrolling down the list: “I’m not even calling the leads that we first started hitting. I bet you there’s deals in here. I’m only calling the new leads that come in. That’s it.”

He was paying for every one of those leads. Some of them had been sitting for 28 days, 36 days. And the honest thing he said at the end of that session is the sentence I want to put in front of every owner who thinks they have a speed to lead problem:

“I just fly by the seat of my pants, dude.”

That is not a lazy guy. That is a guy with no system, working harder than the system would have needed him to.

The belief I want to kill

Speed to lead gets talked about like a hustle metric. Call faster. Care more. Put a poster on the wall that says five minutes.

The owner in this story cared plenty. Caring was not the variable. The variable was that nobody in his business had ever decided what happens to a lead in minute six. Not him, not his rep, not the agency sending the leads. So the lead did whatever the person looking at it felt like doing, which on a busy day was nothing.

Here is the thing I keep saying on these calls, and I said it to him: “You already know it’s going to be texted and emailed. It’s already going to be in the cadence. But it needs to be touched. It needs to be dialed.”

The automated stuff is easy. The dial is where teams wing it. And winging it looks like effort, which is why it hides.

What speed to lead actually is

It is a routing question and an ownership question. That is it.

Lead comes in. Whose is it? How long do they have? What happens if they do not touch it? Where does it go next? When does it stop being theirs?

If you cannot answer those five questions without thinking, you do not have a speed to lead system. You have a rep who is fast on a good day.

I said this to the owner almost word for word: “If a lead goes into your rep’s name and she doesn’t touch it for five minutes, ten minutes, does she deserve that lead? Or should it go to the next person available? Because the last thing you want is she goes out for half an hour, and in that time leads are coming in.”

And I want to be clear, this is not about catching people. “It’s not always about the negatives. She could just be on a phone call for ten minutes and a lead comes in. Okay, cool, she’s unavailable. This needs to go to the other rep. And if she’s not available, it needs to go to you. And if it’s not you, it needs to go to your dog.”

Coverage, not punishment. The lead does not care who was busy.

Winging it versus the system, side by side

Here is what his process looked like before, next to the rule that replaced it. Every item on the left is something I watched happen, not something I made up for the article.

Winging it	The system
Leads land in a spreadsheet from the agency. Someone opens it when they remember.	Leads land in the CRM in a queue. “You want nothing in the queue. Because they’re waiting to be hit.”
The owner dials only the newest leads. Everything older than today goes cold.	Morning call order is set by score, then callbacks due, then open tasks. Reps do not re-sort. An empty afternoon is worse than a mid-score lead.
No call logging. “I know I called this guy” and no way to prove it.	A touch is a logged call with a disposition. Opening the record counts for nothing.
Engaged leads left sitting in “New” because a required field blocked the status change. Notes as the only record.	New means untouched. The moment there is activity it moves to Working. A hundred percent. Required fields live at the stage where you actually know the answer.
Deals aging 28 and 36 days with no rule. “Days in record, bro.”	Working with no activity for three days moves to Nurturing. Seven days releases it to the pool. Stale deals get flagged to a human, never auto-moved.
A rep finds leads she has “never seen” because old imports and test records are mixed into her list.	Only workable new leads enter rotation. Everything else lives in a holding list reps never open.
The owner’s fix for fairness is to watch a list view and reassign by hand.	Weighted rotation, an availability flag, and a load cap. “That should be automated. That’s what the lead queue is for.”

The left column is not a bad team. It is a team with no rules, covering for it with effort you cannot see and cannot replace when they leave.

The twelve rules

Already know you need this built, not read? That is our revenue operations work: routing, ownership, and the reporting that keeps score.

This is the give-away. These are the rules I built for that team, generalized so you can run them on a spreadsheet and a phone tomorrow. No software required to start. Each one has the reason it exists, because a rule without a reason gets ignored the first busy Tuesday.

If it is not logged, it did not happen. A touch is a logged call with a disposition. Not opening the record. Not “I’m pretty sure I called him.” This is the rule that makes every other rule ungameable. Reps learn to click fast when clicking counts.
First dial within five minutes of assignment. Miss it and the lead goes to the next available rep. The rep who missed it keeps their next turn in rotation. If missing a lead also skipped your turn, missing leads would be rewarded, and people are smart.
Every call gets one disposition from a fixed list of six or fewer. First attempt, second, third, qualified, callback scheduled, closing call. No free text in place of a disposition. Free text is where data goes to die.
One owner per lead, always. Ownership transfers through a shared pool. It is never shared. Two reps dialing the same customer is the one thing this whole system exists to prevent.
Only workable new leads enter rotation. Old imports, test records, bad phone numbers, anything from before your rules existed, lives in a holding list reps never see. This one rule permanently ends the “where did these leads come from” conversation.
Reps set themselves unavailable before breaks. Rotation skips them. The manager sees every toggle. Forgetting to toggle back on means no leads, and that is on the rep, not the system.
Cap open leads per rep. Above the cap, new leads go to the shared queue and the manager is told. That number is your hiring signal. It is also the guardrail that stops doubled ad spend from quietly burying the team you have. I will come back to this one.
Ten automated touches in six days, then stop. Paired text and email on days zero, one, two, three and five. Each one has a different job: checkpoint, value, follow-up, proof, breakup. Send only inside the lead’s local waking hours. A reply pauses the sequence and a human takes over. Setting the lead to Working stops it, so your rep is never competing with your own texts.
New means untouched. Working means a rep dialed. Move it the moment there is activity. Three days in Working with no activity moves to Nurturing. Seven days releases to the pool. Leads that are actively chasing documents are exempt and get flagged instead, because moving them drops the chase.
Deals never auto-reassign. A stale deal is flagged to a human who decides on the record. Auto-reassigning deals is where rep fights start. I have watched it: “Wait, that was my opportunity.” “Well, it was sitting for thirty days. We can’t just let it chill.” Make that a human decision with a written rule and the fight never happens.
A returning lead goes back to its last owner inside 90 days. After that it is fresh and enters rotation. Credit goes to whoever completes the whole package, stamped by the system, so it is never a memory contest.
Every disqualification carries a reason, and the reasons go back to marketing weekly. A clean disqualification with a reason on the record is a real output. It is how your team tells the agency which ads produce junk. When that owner’s team had only ever used one disqualification reason, his ad report was inconclusive. Not because of the ads.

The one that sounds backwards

I built that team a five-minute response clock. Assignment stamp, first touch detection, reassign at five, escalate at ten. It is done. It is sitting in the system switched off, and I refused to turn it on.

The reason is rule one. The clock only works if the dialer writes the call to the record automatically. Their phone integration had a logging bug, on the vendor’s side, not ours. Turn the clock on with broken logging and every rep who actually dials gets a breach alert for a call the system never saw. Within a week the reps stop trusting the CRM. Within two the owner stops trusting me.

So it ships inactive and switches on the day logging works. Anyone can write twelve rules. Knowing which one to wait on is the job.

Where I am wrong

A five-minute clock is theatre in some businesses. If you are a two-person shop, the owner is the only closer, every lead is high-ticket and referral-sourced, and you get four a week, do not build this. Build rule one, rule three and rule twelve, and spend the rest of the energy on the four conversations.

The system above is for teams with volume, more than one person touching leads, and paid acquisition where every lead has a cost. If that is not you yet, it will be, and you will want the rules written before the second rep starts, not after.

The rule I want you to sit with

Rule seven. The load cap.

That owner came to me asking for fair distribution between his two reps. He was worried about cherry-picking. “I just don’t want anybody going in and cherry-picking all the calls today. That’s not going to be fair.” Reasonable ask. We built the rotation.

But his own numbers, read off his own screen, said one rep was sitting on roughly 130 open records, most of them waiting on paperwork, not on a call. And he was about to roughly double his ad spend into that.

Routing fairly into a full team just distributes the backlog faster. Speed to lead looks fine on the dashboard. Conversion does not move. So the cap went in under the rotation. Above a set number of open records, a rep gets skipped, the lead lands in the shared queue, and the owner gets a flag. That flag is the honest answer to “should I spend more,” and it comes from the system instead of from a feeling.

“Imagine you had a team of ten people. How can you possibly track how everybody’s handling the leads? You’re paying money on these leads. Are your reps actually following through?”

You cannot know that by listening to calls one at a time. You do not have time for that. You can only know it if the system is keeping score.

Two minutes: are you winging it?

Five questions. Answer yes or no, no partial credit.

Can you say, right now, what happens to a new lead if the assigned rep is on another call for ten minutes?
Does your CRM distinguish between a lead that was opened and a lead that was dialed?
Is there a number of open leads above which a rep stops receiving new ones?
Can you pull a list of every lead that received zero logged calls in the last 30 days, in under a minute?
When a rep marks a lead “not interested,” is a reason required before the record saves?

Three or more no’s and you are not slow. You are winging it, and your reps are covering for it.

Score the rest of your sales system

What it feels like when it works

Here is what I told that owner his job looks like once the rules are running. “You really should only be coming in to do one or two things. Follow up when it makes sense, close the deals, and review what your rep is doing. That’s really where your time should be. Closing deals, looking at the dashboard, making sure they’re hitting their numbers.”

Not babysitting. “That’s the whole point of process and procedures. You won’t need to babysit. You’ll just be able to say, hey, you’re not following the program, or hey, you are.”

Stabilize a small team. Govern them so they are working the system the way it needs to be worked. Then make their life easier with automations. Then, and only then, ramp the marketing. Every owner wants to skip to the last step. The first three are the ones that compound.

If you answered no to three of the five questions above, the Free Business Checkup on our site scores the rest of your sales system the same way, in about ten minutes, and tells you which leak is costing you the most. It is a diagnosis, not a pitch. Run it, read the readout, and if you want a second set of eyes on it, that is what the scoping call is for.

Run the Free Business Checkup Book a Scoping Call

Questions people ask about speed to lead

What is speed to lead?

Speed to lead is the time between a lead arriving and the first logged human touch, usually a dial. It is measured from assignment, not from form submit, and it only counts if the touch is on the record.

What is a good lead response time?

Five minutes from assignment for paid inbound. Past five minutes the lead should move to the next available rep. For low-volume referral businesses a clock is theatre; get rules one, three and twelve right instead.

What are lead routing rules?

The written answers to five questions: whose lead is it, how long do they have, what happens if they miss, where does it go next, when does it stop being theirs. Round robin is the simplest version. Weighted rotation adds availability and a load cap.