Module 10 — Speed Kills: Lead Management, Routing & SLAs

"A lead is a perishable good with a half-life measured in goddamn minutes. You either move or you're scraping spoiled meat off the funnel floor and explaining it to the board." — Dr. Tanya Vex, The Velocity Doctrine (self-published, 280 pages, every single one of them this sentence at different font sizes)

A lead came in at 9:02 a.m. It was hot — pricing page, demo request, real corporate email, a title with "VP" in it, the kind of inbound that makes your heart do a little shit-eating jump of hope. It sat in an unrouted queue for nine hours because the round-robin rule had a typo, and the one rep who might have caught it was at a "leadership offsite" doing trust falls in a hotel conference room in Scottsdale. By 6 p.m. that VP had booked a demo with your competitor, who answered in ninety seconds with a real human being who was ready to talk. You paid marketing real money — good money, probably money you argued for in a planning meeting with a spreadsheet — to generate that lead. Then you murdered it with bad plumbing and called it a pipeline problem. This module is about not doing that.

THE JOB

Lead management is the unglamorous, deeply unsexy plumbing between demand and a human who can sell — capturing inbound interest, matching it to the right account and the right owner, and getting it into capable hands fast enough that the buyer's intent hasn't already evaporated and they haven't already signed with someone else. Routing is the how. SLAs are the contract that prevents everyone from quietly dropping the ball and looking surprised at the QBR. Speed-to-lead is the physics that makes all of it matter or renders it irrelevant.

The brutal, expensive, embarrassing truth: organizations spend fortunes generating demand (see Module 9, which you just read, because you're not a masochist who skips chapters) and then lose half of it in the handoff. The leak isn't at the top of the funnel. The leak is in the plumbing between teams, where leads die quietly and without ceremony, blamed on no one, mourned by no one, noticed by no one until the funnel math stops adding up and some analyst starts pulling reports at 2 a.m. RULE No. 10: the fastest growth lever in most orgs isn't generating more leads — it's not torching the ones you already fucking have.

THE PLAYBOOK

1. Speed-to-lead — the response-time decay curve that should scare the hell out of you

This is the most important number in the module and the one most orgs treat like an afterthought because "operational" is apparently less glamorous than "strategic," even though strategy executed like shit is just expensive confusion with a better font. The probability of successfully qualifying an inbound lead decays exponentially with response time:

• Respond in 5 minutes vs. 30 minutes → up to ~100x more likely to actually connect with the prospect; famously ~21x more likely to qualify them (Lead Response Management study — old data, consistently replicated, the physics don't change).
• Wait an hour → you're an order of magnitude worse off than the rep who called at minute four. One hour. An order of magnitude.
• Wait a day → you're sending a "sorry we missed you, still interested?" email to someone who has already signed with the competitor who answered at minute six. That email is not a follow-up. It is a receipt for your own fuckup, mailed to the crime scene.

The decay curve is steepest in the first five minutes. Every single minute of routing latency is a measurable tax on conversion — you can see it in your own funnel data if you have the courage to pull the report. Your routing system's entire job is to compress time-to-first-touch toward zero. Measure it on a dashboard. Make it visible. Make it uncomfortable. It is a real KPI, not a vibe, and it belongs next to the numbers the board actually reads.

2. Lead-to-account matching — do this before routing, or everything downstream is bullshit

You cannot route correctly if you don't know what account an inbound lead belongs to. This sounds painfully obvious. It is ignored constantly, by smart people, at companies with real budgets, who then act baffled when the routing turns to shit. Lead-to-account matching (L2A) resolves an inbound lead — [email protected] — to the correct account record in your CRM (Acme Corp, $2.4M ACV target, Territory: West, Owner: Marcus), so you can:

• Route to the account owner if one exists, rather than handing an existing customer's contact to a cold AE who will cheerfully try to sell them something they already have.
• Detect if the account already has open opportunities — this is an expansion signal, not net-new pipeline, and it needs to be treated like the goldmine it is.
• Apply correct territory, segment, and ownership rules based on account-level data.

Match on email domain, company name, enriched firmographic data, and handle the edge cases that will absolutely destroy you if you ignore them: free email domains (gmail, outlook, yahoo — these go to a qualification queue, not directly to a rep), subsidiaries and parent-child relationships, franchises, the hapless lead who fat-fingered their own company name in the form field, the shell company email that traces back to a Fortune 500 that already has an AE. Bad L2A matching is the silent root cause of most routing catastrophes. Garbage match in, wrong rep out, pissed-off existing customer, lost expansion deal, mysteriously terrible funnel conversion rate, everyone screaming about data quality at the QBR like that will help. Fix the fucking matching first. Everything else is just rules built on top of a clean foundation — and without the clean foundation, the rules are fantasy.

3. Pick a routing model — or a sane hybrid, because your IRL situation is always messier than the theory

In real life — not the whiteboard, real life — most orgs run a hybrid waterfall cascade: if the lead matches a named account with an owner → send to that owner; else if the lead fits a defined territory → send to the territory rep; else → round-robin the qualified pool. Build that cascade explicitly in your CRM or routing tool. Write down every branch. Define the fall-through at every node. The places you leave undefined are the places leads go to die, and they will go there, cheerfully and quietly, for months before you notice.

4. The routing rules you actually need — minimum viable, non-stupid, non-optional

Don't architect a 60-branch routing flow that takes three months to build, collapses the moment one rep quits, and requires a RevOps PhD to update without breaking something. Build the minimum viable ruleset that covers 95% of cases, then iterate when reality reveals the gaps — and reality will reveal the gaps, usually at the worst possible time, usually a week before the board meeting. Here are the rules you absolutely cannot skip without paying for the omission in torched leads and a messy post-mortem:

Rule 1 — Assignment logic. Who gets the lead. The waterfall above. Write it down. Put it in the tool. Make it auditable.

Rule 2 — Fall-through / default owner. Where unmatched leads go when no rule fires. This is the rule everyone forgets, and it is exactly where leads go to rot in the dark until someone stumbles over the corpses in Q3. Name a real, breathing human as the default catch-all owner. A queue that generates an alert to a living person. Never, under any circumstances, route to NULL. Routing to NULL is not routing — it is a trapdoor, and every lead that hits it disappears without a trace, and you will not find them until some poor bastard runs a "leads with no activity ever" report and discovers three months of marketing spend sitting at the bottom of a digital hole with no one's name on it.

Rule 3 — Capacity caps. Maximum active leads per rep so you don't bury one poor bastard under 80 leads while the rep two rows over has four and is blocking off Thursday afternoon to play golf on the company's dime. A rep buried under 80 leads works exactly none of them well; he just clicks through the queue feeling increasingly dead inside until he starts dispositing everything "no answer" after one call. Distribute the volume. Enforce the caps.

Rule 4 — Working-hours and time-zone logic. Don't route a 2 a.m. lead from a Sydney prospect to your sleeping San Francisco rep and log it as "assigned, SLA met." It is not met. It is assigned to a person who is unconscious and snoring, and the SLA clock is ticking against a human who has no idea. Route to whoever is actually awake, or to a queue with appropriate SLA windows by time zone, or to a bot that can engage with lightweight qualification while the human sleeps. The lead doesn't care what time it is in your office. The lead cares whether someone responds before the competitor does.

Rule 5 — Auto-reassignment on SLA breach. If the assigned rep hasn't logged a contact attempt within the SLA window, the system automatically reassigns to the next available rep and notifies the manager. The clock creates movement. The clock is not cruel. The clock is the only damn thing that makes the contract real instead of aspirational. Without auto-reassign, the SLA is a suggestion printed in a policy document that lives in a Google Drive folder nobody has opened since the quarter it was written.

Rule 6 — Round-trip and recycle path. Rejected leads — leads the rep worked, dispositioned as "not a fit," and kicked back — go to marketing for nurture, not into a shallow grave. They go back with a reason code attached. Define this path explicitly. Build the recycle queue. Make it visible to marketing.

5. Marketing → Sales SLAs — the bilateral contract that ends the blood feud

An SLA is not a marketing deliverable that gets handed to Sales as an apology. It is not a dictate that Sales issues unilaterally because they feel like holding someone accountable for once. It is a written, mutual, bilateral agreement — both sides owe something measurable, tracked by a system, enforced by a clock, visible to both teams. If one side can't see the other side's metrics, it's not an SLA, it's just a complaint dressed up in documentation. Here is what each side actually owes:

Marketing owes Sales: a defined volume of leads meeting an agreed MQL definition — real fit against ICP criteria, real demonstrated intent, complete enough data to actually work. Not "anyone who opened an email." Not "anyone who registered for our webinar about a topic we never sell." Actual fit and intent. Plus every data field the rep needs to make a first call that doesn't embarrass everyone involved.

Sales owes Marketing: every routed lead worked to a defined standard — first contact attempted within X minutes of routing (five minutes for hot inbound is not unreasonable), minimum N contact attempts over Y days, and every lead dispositioned with an honest status code before it's closed. Not "attempted." Dispositioned.

The loop closes like this:

MQL → (routing fires) → SAL (Sales Accepted Lead) → SQL (Sales Qualified) → Opportunity
                            │
                            └─ Rejected → reason code → Marketing nurture queue

The rejection reason code is the most underrated field in your entire CRM, and nobody fills it out honestly without enforcement and consequences for not doing it. "Not ICP fit." "Bad contact data." "No current intent." "Already a customer, you idiots." "Evaluating competitor." Those codes are how marketing learns which lead sources produce prospects who actually buy things, and which ones produce a gorgeous MQL number that dies the moment a human rep breathes on it. Without those codes, both teams sit in the same conference room every quarter and scream "your leads are garbage" and "your reps are lazy bastards who won't work the queue" at each other until someone's boss steps in and declares the problem "a communication challenge." It is not a communication challenge. It is a missing data field. The SLA with a functioning disposition loop replaces that blood feud with a number, and numbers can be investigated and fixed. Blood feuds just fester and make the QBR a miserable, expensive therapy session.

6. What happens to leads that fall through — the graveyards and how to build the safety nets

They die. Quietly. No fanfare. Here are the known graveyards and the fix for each:

• Unrouted — no rule matched → default-owner catch-all plus a daily alert for "leads in queue >60 minutes, no owner." Someone reads that alert every morning. This is not negotiable.
• Routed but never touched → SLA timer starts at assignment. Auto-reassign fires on breach. Both tracked on a dashboard the rep's manager looks at every day.
• Worked and rejected without disposition → no rep closes a lead without a reason code, full stop. Lock the field in the CRM so it can't be skipped. Yes, reps will click the fastest available option to get through the damn form and move on. Audit the distribution quarterly — if 80% of rejections say "bad timing," that's a rep gaming the field, not a market phenomenon. Address the gaming or the data is worthless.
• Recycled without tracking → every lead re-entering nurture after rejection carries the rejection reason, the dates, and the rep's name. Marketing can see what happened. Both sides are accountable.
• Stuck in MQL purgatory, aging and untouched → a "leads created more than 24 hours ago with zero activity" report, delivered to the RevOps Martyr who actually reads it, every morning, before the coffee is cold.

Build every safety net. Then monitor the safety nets, not just the happy path. The happy-path reporting makes everything look fine. The safety-net reports show you where money is leaking.

HOW IT GOES TO HELL

The RevOps Martyr built a gorgeous, airtight, 40-branch routing flow at 2 a.m. over two weekends and documented exactly none of it because she was already 11 sprints deep on the next thing that leadership declared urgent without defining. A rep quits in February — no two weeks, just gone, Slack message on a Monday. His leads route into a deactivated user record. No fall-through rule catches it because the fall-through rule also referenced the same deactivated bastard. Two hundred leads rot for six weeks in a system no living human is monitoring. The Martyr discovers it in March while pulling a totally unrelated report, fixes it in four hours, says nothing in the all-hands, and writes the post-mortem herself. She is thanked exactly never. Six months later, when the routing breaks again for a different reason, leadership asks why there's no documentation. She writes the documentation too.

The VP of Vibes stands at Q1 kickoff in his Patagonia vest with the energy of someone who just read a Medium post about urgency and declares — with conviction that is almost moving in its wrongness — "speed-to-lead is our number one goddamn priority this year, we are going to win on speed." He does not set a formal SLA. He does not build measurement for response time. He does not implement auto-reassignment. He does not build a dashboard. He declares the priority and considers the work done. Average first-response time for Q1 is 31 hours. He is genuinely shocked at the conversion review. He was, he explains, focused on strategy. He is always focused on strategy. The strategy is never "set up auto-reassignment."

The Brilliant Jerk — your top AE, the one with the AMG and the Whoop strap and the On Clouds and the utter, unshakeable conviction that his time is worth approximately eight times the value of any routing policy written by the RevOps team — cherry-picks the five high-ACV named accounts out of the round-robin queue and quietly lets the remaining 47 leads sit unworked and aging. No capacity cap enforced. No disposition requirement. No manager looking at per-rep contact-rate dashboards because the manager doesn't want the conversation. The rot is invisible until some analyst pulls an "leads assigned, no activity, >7 days" report out of morbid curiosity and discovers that 60% of all routed leads were never touched by a human being, that the funnel conversion rate has been a well-dressed fiction for two full quarters, and that the Jerk has been farming a system that nobody was watching. Then comes the meeting. Nobody in that meeting is happy. The Jerk is not sorry. He closed 140% last quarter and he knows it.

The Founder — who is convinced, with the serenity of someone who has never actually worked a lead queue, that "good leads will find the right person" through some organic, vibes-driven alignment process he has never once articulated — refuses to build routing rules because rules feel bureaucratic, and bureaucratic feels like a thing that happens to companies that aren't visionary. There is no default owner. There is no fall-through rule. Eighteen percent of inbound — the pricing-page, demo-request, real-title, real-intent people who represent the hottest traffic that money can buy — routes to NULL and vanishes. Absolute silence. They are never seen by human eyes. By the time anyone notices, they've signed with a competitor who had a routing rule and a human who answered the phone. They become that competitor's case study. Their logo is on that competitor's website. My attorney advises this does not technically constitute negligence, but only because no one has passed legislation for it yet, and based on what he's seeing in the industry, he genuinely expects one by 2027.

FIELD RULES

• Minutes matter, exponentially. Five-minute response vs. thirty-minute response isn't a little bit better. It is 21x better. Compress time-to-first-touch toward zero or accept a conversion rate that reflects your indifference.
• Match before you route. Bad lead-to-account matching is the silent root cause of almost every routing catastrophe. Clean L2A first; the routing rules are just logic on top of it.
• Name the goddamn default owner. The fall-through rule is where leads go to die. Every unmatched branch needs a real, awake, accountable human at the end of it. Never the void.
• An SLA is bilateral and enforced by a clock, not a conversation. Both sides owe something. Auto-reassign fires on breach. If there's no auto-reassign, there's no SLA — there's a PDF nobody reads.
• Reason codes end the blood feud. Disposition every rejected lead with an honest code. Recycle it to nurture. Let marketing learn what's worth generating. The alternative is the Marketing-vs-Sales screaming match, and that meeting is hell.
• Monitor the safety nets, not just the happy path. The happy path metrics look fine right up until they don't. The safety-net reports — unrouted leads, SLA breaches, untouched aged leads — show you where the money is quietly vanishing.

---

From the field, 3:48 a.m. — The competitor answered in ninety seconds because they wired a Slack alert to a phone that is always in someone's hand. That is the entire secret. No guru, no methodology, no $2,000 course on velocity frameworks, no keynote about buyer journeys. A clock. An alert. A human who picks up the fucking phone. The lead I'm reading about in the routing logs — the pricing-page VP who sat unrouted for nine hours — is closing with them in Q3. I found the typo. I fixed the rule. I am writing this module so you don't have to sit here at 3:48 a.m. finding yours.