7. Lead Routing
(the transcript is below)
Action Step
Complete this before moving on.
Watch the full overview video above and read through the transcript below. Pay attention to the difference between round robin and territory-based routing, and how the 'Vlookup table' concept simplifies the core routing logic.
Part 1: Hook / Open
A VP of Sales pulls up the CRM on Monday morning and sees 200 leads from last week's trade show just sitting there unworked. Nobody touched them because nobody knew whose they were.
Meanwhile the ops manager has been spending ten hours a week manually assigning leads from a spreadsheet, and reps are still complaining that distribution is unfair.
That's a pattern we see constantly. Leads are coming in, but the handoff between lead generation and lead conversion is completely broken.
And the project that fixes it is what we call Lead Routing.
So what is lead routing? It's the infrastructure that automatically assigns every incoming lead to the right person based on predefined rules. So no lead sits unworked, no rep gets the wrong accounts, and no ops manager is the bottleneck.
My name is Yasin from LeanScale, and in this video I'm going to break down for you our entire Lead Routing Playbook... what it is, the core concepts, how it gets built, and what changes once it's in place.
Part 2: What Lead Routing Is
So when we talk about the lead routing project, what we're actually building under the hood is a set of rules, flows, and automations inside the CRM.
And what those do is look at every incoming lead, check it against your criteria, and automatically assign it to the right person.
Now on the input side of this project, there are territory definitions, team rosters, lead data — things like geography, industry, company size — and sometimes a named account list for high-value targets.
On the output side, once it's built, every single lead that comes through the door gets matched against those criteria and lands in the right rep's queue within minutes — not hours, not days.
Now those territory definitions — where they come from, how the accounts get valued and balanced — that's a separate project called Sales Territory Design. Territory design is the blueprint — it figures out who should own what and why. Lead routing is the construction — it takes those definitions and turns them into the automation that enforces them on every single lead.
So if you don't have territory definitions yet, you're either doing round robin — which works fine for smaller flat teams — or you need to start with territory design first.
But assuming those definitions are in place, then once the routing is built, the assignment is automatic. Every form fill, every demo request, every event registration gets evaluated and routed without anyone opening a spreadsheet, without anyone deciding "this one goes to Sarah, that one goes to Mike."
The way I like to describe it to clients is that lead routing is really just a Vlookup table. Think of a spreadsheet where every row is a territory, every column is a matching criteria like geography or industry or company size, and the last column is the rep who owns it. So when a lead comes in, the system runs a Vlookup, finds the matching row, and returns the right owner. That's all territory routing is at its core — a Vlookup that the CRM runs automatically on every single lead.
Now if you've seen our Automated Inbound playbook and video, you might be thinking — isn't this the same thing? It's not, and the difference matters. Automated inbound is the full pipeline — it captures the lead, enriches it, tiers it, and then decides what response to trigger — whether that's a human follow-up or an automated sequence. Lead routing is specifically the assignment logic — which rep gets which lead based on territory rules.
Automated inbound answers "what happens when a lead comes in." Lead routing answers "who gets it." Most companies that need one end up needing both — but they're different problems.
Part 3: Lead Routing Pro Tips
Now the Playbooks Library below this video goes deep on the full methodology behind the lead routing project — but before we get into how it gets built, here are a couple things you really don't want to get wrong when implementing this into a startup.
First — understanding the difference between round robin routing and territory-based routing is critical. Almost every company defaults to round robin because it's simple. But most companies actually need territory-based routing. And here's why — round robin distributes leads equally by volume, which sounds fair. But if a rep gets five leads in a month and three of them are garbage, that's not fair at all. Territory-based routing distributes by market opportunity, which is actual fairness. So if the team has any specialization at all — geography, industry, product — round robin is the wrong approach.
Second — you do not need an expensive dedicated routing tool to get territory-based routing working. For teams under ten reps, the Salesforce Territory Object approach works — it's basically a custom object that acts as a Vlookup table — and it gives you territory-based routing at zero additional tool cost. The flow pings the object, finds the match, assigns the rep. No LeanData license required. Build the foundation first, and most teams find that foundation handles everything they need for years.
Third — lead routing is not a set-it-and-forget-it project. Every hire, every departure, every PTO absence, every territory adjustment requires someone to update the system. At one of our clients, Tempo, the lead routing maintenance consumed 40 hours a month at scale. And we'll talk about why that matters in a minute.
Part 4: The Problem in Context
And the data backs up why this project is so key for startups who are scaling.
According to Kixie's analysis of B2B response data, the average B2B lead response time is 42 hours — nearly two full business days before a rep even touches a lead.
A study from InsideSales and Harvard Business Review found that responding within five minutes makes a company 21 times more likely to qualify the lead versus waiting just 30 minutes. And after five minutes, the odds of qualifying drop by 80 percent.
A separate study found that 35 to 50 percent of sales go to the first vendor that responds — and some studies put that number as high as 78 percent.
So lead routing is the single largest determinant of who responds first.
And Kixie also found that up to 73 percent of leads are never contacted at all, with reps making barely more than one call attempt before giving up.
So it's not just sales that feels this. Marketing spends millions generating leads that never get worked, which means their attribution data is unreliable and their ROI calculations are inaccurate. Ops teams are buried in manual assignment work that could be automated. And leadership can't tell if distribution is fair, which directly impacts rep morale and retention.
Part 5: How It Gets Built
So how does a lead routing project actually get implemented?
At LeanScale, for all of our projects, we follow a four-phase approach — Strategy, Engineering, Enablement, and Handoff.
Strategy
In the lead routing project, strategy is where the most important decisions get made.
This is where we work with sales leadership and RevOps to answer three questions. What approach fits this team — round robin, territory-based, or target account hybrid? What tool should we use — CRM-native or a dedicated platform like LeanData? And what does the routing hierarchy look like — meaning which criteria get checked first, second, third before a lead gets assigned?
Now the reason this matters is that choosing the wrong approach for the team's maturity level is the biggest risk in this project. Territory-based routing for a five-person flat team creates unnecessary complexity. Round robin for a specialized enterprise team creates unfair distribution. So nothing gets built until the approach is locked.
Now before the project even kicks off, our team reviews the company's existing routing setup, pulls the CRM data on current lead assignment fields and team structure, and assembles a V1 recommendation of which approach fits best. And that's based on best practices from having implemented this across companies like Tempo, Harbinger, and others.
We also lean heavily on AI agents throughout this process. These are agents trained on our playbooks that can pull the existing CRM setup, look at the team size, deal volume, and territory situation, and come back with a draft recommendation of which approach makes sense. We go deeper into how we use AI in the implementation of this project in the full playbooks in the library.
From there, we iterate on that recommendation with sales leadership and RevOps. And by the end of strategy, we've locked in which approach we're using, which tool we're building it in, and what the full routing hierarchy looks like — including what happens when a lead doesn't match any of the criteria.
Engineering
Phase two is the technical build.
This is where the routing flows, the territory objects, and the assignment logic actually get created inside the systems.
Now we follow a structured build sequence that varies by approach. For round robin, it's configuring the rotation pool, distribution settings, and out-of-office handling. For territory-based, it's building the decision nodes that match the routing hierarchy, creating the territory object in Salesforce, and wiring up fallback routing so no lead ever falls through unassigned. For target account hybrid, it's building the named account check as the first node and then layering in the fallback routing underneath.
And every routing flow gets built in inactive state first. Nothing goes live until every branch of the decision tree has been tested with real-looking data and the customer has signed off.
So what's changed in the agentic AI era for engineering implementation on this project? We've built a Lead Routing Agent — an AI that has our entire routing build process codified, knows every field and flow that needs to exist, and connects directly to the CRM to start building it out. So what used to be a purely manual effort — building dozens of flow nodes and decision branches by hand — now gets done significantly faster because the agent handles the repetitive build work and our engineers focus on the quality and the edge cases.
The full details of the AI agents we use and the build process are broken down inside the playbook library if you're curious.
Enablement
Phase three is enablement, because the system is useless if the team doesn't know how to use it.
For the lead routing project we train the ops team on how to make routing updates — how to add and remove reps, how to handle PTO coverage, and how to maintain the change log, which is essentially the version history of every routing adjustment.
We train the sales reps and SDRs on what determines their lead assignments, how to identify a misrouted lead, and who to contact if something looks wrong.
And we train sales leadership on how routing decisions work, how to request territory changes, and what the ongoing maintenance commitment looks like.
Handoff
From there phase four is the handoff, and this is where maintenance expectations get set.
Now one thing to understand — lead routing, especially territory-based routing, is not a one-time project. It can require anywhere from five to forty hours a month of ongoing maintenance depending on team size and change frequency. And here's why that matters.
Every time someone gets hired, every time someone leaves, every time someone goes on PTO, every time a territory gets rebalanced — someone needs to update the routing system.
If nobody owns that, what happens is new leads start flowing in and the system routes them to people who have left the company or to reps who are on vacation. Those leads sit unworked for days. And in the time it takes for someone to notice and manually reassign them, 35 to 50 percent of those prospects have already bought from whoever responded first.
Over the course of a quarter, that compounds — and suddenly the team is back to where they started, with leads falling through cracks and reps complaining about unfair distribution. That's how a well-built routing system degrades into a broken one.
So the handoff isn't just about transferring ownership. It's about making sure after we've completed the implementation, someone on the team understands the system deeply enough to keep it running clean.
Part 6: What It Unlocks + Close
So let's bring this all together to where we started. Once lead routing is in place, what actually changes?
Lead response times go from the industry average of 42 hours down to minutes, which means reps are reaching prospects while the intent is still hot.
Companies with proper lead management and routing see 20 to 50 percent higher lead-to-opportunity conversion rates. And Gartner found that companies automating lead management see a 10 percent or greater revenue increase within six to nine months.
Ops teams go from spending 10 to 40 hours a month manually assigning leads to spending less than two hours a month monitoring a system that runs itself.
And the biggest thing that changes after this project is confidence and certainty. That VP of Sales can pull up the CRM on Monday morning and instead of seeing 200 unworked leads, every single one has already been assigned to the right person, worked by the right rep, and the team trusts that distribution is fair.
Marketing can finally trust their conversion data because leads are actually being worked, which means the ROI numbers are real.
And leadership has a system that scales, whether the team is 5 reps or 50.
That's what lead routing does — it takes the operation from manual chaos to automated precision.
Everything covered in this video about this project — the concepts, the methodology, the full implementation process — all of it is broken down in detail in our Playbooks Library for you to go through. Our Advisory Overview Playbook covers the problem, approaches, and strategic understanding behind this project. The Methodology Playbook goes deep on every concept we talked about, from the routing hierarchy to the Vlookup table approach to round robin versus territory-based decision frameworks. And the Implementation walks through the step-by-step build process across all three routing approaches.
Now if you're a revenue leader at a fast growing startup who's feeling good about the lead routing side after watching this — but you're thinking, okay, now how do I make sure the right accounts are getting to the right reps based on actual territory design — we have a whole playbook on exactly that called Sales Territory. It's broken down the same way in our Playbook Library.
And while you're there, you'll see we have playbooks on every major GTM project — from Attribution and Automated Inbound to Quote to Cash, Growth Model, and beyond. Feel free to check those out next.
Again, this is Yasin from LeanScale, and I'll see you in the next one!
Comment in Slack
Post your answer in your onboarding channel.
What did you learn? What clicked?
Any questions — or will you have more questions once you actually get into the hands-on trainings? Either is fine. Just capture where you are right now.