Capacity-Based Lead Routing

Capacity-based lead routing assigns new leads only to reps who have room to work them, using a cap on concurrent open leads per rep. It replaces the assumption behind round-robin, which is that an even split of leads produces an even split of work. That assumption fails the moment reps differ in speed, tenure, deal load, or territory complexity.

The problem with even distribution

Round-robin sends every rep the same number of leads. It cannot see that one rep is carrying eight active opportunities and another is carrying two, or that a rep spent the week in a customer escalation. The leads still arrive on schedule. What changes is how many of them get a real first touch, and the ones that do not are invisible because they are technically assigned and technically owned.

The result is a queue that quietly stratifies. Overloaded reps triage by picking the leads that look best, which is a reasonable response to too much work and a terrible outcome for the funnel. Everything they skip ages past the point where a first touch matters, then converts far below its potential.

Setting a defensible cap

Start with the cadence you expect reps to run. A cadence of eight touches at roughly eight minutes each is about an hour of work per lead. A rep with twenty selling hours available for new leads each week can genuinely work about twenty new leads in that week, and that number sets the intake rate. Multiply by the average days a lead stays open before qualification or disposition to get the concurrent cap.

Then validate against outcomes. Chart conversion rate against each rep's open lead count over the last two quarters. Conversion is usually flat up to a threshold and then falls, and that inflection point is your real cap. Set the limit slightly below it.

Rules that make it work

- Define the overflow path before you turn on the cap, whether that is a manager queue, an adjacent team, or automated nurture with a defined return date. - Age leads out of the count. A lead nobody has touched in three weeks should not hold a capacity slot hostage. Close it or recycle it. - Weight by lead type. An enterprise inbound request consumes more capacity than a content download, so count them differently. - Report capacity utilization weekly. Sustained saturation across the whole team is a hiring signal, not a routing problem.

That last point is where routing meets planning. When every rep runs at the cap for several weeks, demand has outgrown the team, and the honest options are more headcount or a higher qualification bar. Either choice changes the conversion rates feeding sales forecasting, and both are better than the default, which is spreading more leads across a team that already cannot work the ones it has. Capacity data also strengthens pipeline coverage analysis, since coverage built on leads nobody touched is coverage on paper.