Most inbound routing is broken before a rep even sees the lead

Speed-to-lead gets all the attention. Five-minute response windows, instant notifications, Slack pings. The obsession is real.

Why does inbound routing break before a rep sees the lead?

The conversion problem usually sits one step earlier than speed: leads arrive at the routing layer with almost no context. Name, email, company, maybe job title if the form asked. The rep gets pinged, opens the record, and has to decide whether the lead is worth their next 20 minutes with nothing to go on.

So they either punt (slow follow-up) or spray-and-pray (bad first message).

What does a 3-step enrichment pass before routing look like?

Run three steps before the lead routes: a firmographic gate in Clay that scores ICP fit, an intent overlay that flags accounts already researching your category, and an AI-drafted first message built from the enriched record. Only leads that pass the firmographic gate route to a rep.

1. Firmographic gate. Run the company through Clay, pull headcount, revenue range, tech stack. Does this account fit ICP? Score it. Only route the ones that pass.

2. Intent overlay. Check if the account is showing intent signals. If yes, flag it. The rep’s opening line changes completely when they know the account has been researching your category for 3 weeks.

3. AI-drafted first message. Claude API call against the enriched record. One sentence personalised to their tech stack or a relevant signal. Rep edits and sends in 30 seconds instead of writing from scratch.

How much does enrichment before routing improve conversion?

In a recent build, adding the enrichment pass before routing took qualified lead routing accuracy up from ~55% to 88%. Rep first-message send rate (within 10 mins) went from 22% to 71%, because reps opened the record with context instead of a bare name and email. Speed-to-lead matters. Context-at-lead matters more.