Inbound: Enrich, Score & Route in Minutes
Responding to an inbound lead within 5 minutes makes you 21 times more likely to qualify it, yet the average first touch takes 42 to 47 hours. This playbook builds the Clay pipeline that enriches, scores and routes every lead while the buyer is still on your site.
The problem
The lead arrives with a name, an email and little else. Someone has to figure out who they are, whether they fit, and whose territory they belong to, and until that happens nothing moves. Manual triage batches into mornings, weekends stack up, hot leads cool, and the demo request you paid marketing to generate gets its first reply two days later.
This playbook is part of the companion set to Data Orchestration in 2026: Why Clay Sits Under Every Modern GTM Stack. Read that first for the strategy; this is the build.
What you will build
An Inbound Pipeline table triggered by webhook the moment a form submits. Clay enriches the person and company in seconds through a waterfall, scores fit against your ICP with a transparent formula, routes to the right owner, writes the enriched lead to the CRM, and alerts the rep in Slack with everything they need to respond immediately. Median speed to lead: under five minutes, around the clock.
The stack
Architecture
Event-driven, not batch: the form fires a webhook, Clay does the thinking in seconds, and the rep gets a ready-to-act alert instead of a raw form fill.
Clay tables and connected objects:
The build, step by step
Catch the lead with a webhook
Create a table from Import data → Monitor webhook and paste the generated URL into your form tool's webhook action (HubSpot workflows, Marketo webhook step, or Typeform connect).
{"email": "jane@acme.com", "first_name": "Jane", "last_name": "Doe",
"company": "Acme", "message": "interested in a demo",
"form": "demo-request", "page": "/pricing",
"submitted_at": "2026-07-07T14:02:11Z"}
Include the form name and page; they matter for scoring (a pricing-page demo request is not a whitepaper download).
Enrich at webhook speed
Add a short waterfall: person enrichment from the email (Apollo then Prospeo), and company enrichment from the domain (industry, employee count, tech stack, funding). Keep this chain to two or three fast providers; this is the one place where latency matters more than the last few points of coverage. Set every column to run automatically on new rows.
Score fit with a transparent formula
Resist the black-box scoring temptation; reps need to see why. Use an additive formula:
Start at 0. Add 30 if Employee Count is between 100 and 2000. Add 20 if Industry is in (Software, Fintech, Business Services). Add 20 if Title contains VP, Head, Director, or C-level. Add 15 if Form is "demo-request"; add 5 if Page contains "pricing". Add 15 if Tech Stack contains Salesforce or HubSpot. Cap at 100. Also return the list of reasons that fired.
Then a tier formula: 70+ is hot, 40-69 is warm, under 40 is nurture. Sales leadership signs off on the weights, and the reasons column travels with the lead.
Route with the lookup table
Add a lookup against the Routing Rules table on country + employee band + segment to resolve the owner. Round-robin within a territory by cycling a counter column. Because leadership edits the routing table directly in Clay, territory changes take effect without touching the pipeline.
Write to CRM and fire the alert
Write the enriched, scored, owner-assigned lead to the CRM, then send the Slack alert in the same run:
POST https://slack.com/api/chat.postMessage
Body: {"channel": "{{Owner Slack ID}}",
"text": "HOT inbound ({{Score}}): {{First Name}} {{Last Name}}, {{Title}}
at {{Company}} ({{Employees}} ppl, {{Industry}}). Asked: '{{Message}}'
from {{Page}}. Reasons: {{Score Reasons}}. CRM: {{Record Link}}.
Clock is running: respond within 5 minutes."}
For hot leads, optionally skip the human: route straight to a booking link in the auto-reply. For everyone else, the rep replies with full context in one glance.
Instrument the SLA
Timestamp each stage (received, enriched, routed, alerted, first touch from CRM activity) and build the SLA view on elapsed minutes. Post a daily digest to the sales channel: median speed to lead, leads over SLA, conversion by tier. What gets posted publicly gets fixed.
Measuring success
One number rules this playbook: median minutes from form submit to first rep touch. Everything else is diagnosis.
| Metric | Where to measure | Target | You know it is solved when |
|---|---|---|---|
| Median speed to lead | Clay SLA view + CRM first-activity timestamp | Under 5 minutes for hot tier | The 42-hour average becomes a war story |
| Lead-to-opportunity conversion | CRM funnel report by tier, before vs after | Meaningful lift on hot tier within one quarter | Marketing stops arguing about lead quality and starts arguing about volume |
| Routing accuracy | Reassignment count in CRM | Under 2% of leads reassigned | Territory disputes leave the pipeline meeting agenda |
| Enrichment latency | Clay stage timestamps | Under 60 seconds submit to alert | Reps trust the alert enough to act on it alone |
Staffing the workflow
Growth plan is non-negotiable here; webhooks and HTTP API carry the whole flow. The build is a focused sprint.
| Phase | Hours | Who |
|---|---|---|
| Build: webhook, waterfall, scoring, routing, alerts | 20 to 30 hours | GTM engineer |
| Rollout: SLA baseline, rep training, routing sign-off | 6 to 8 hours | GTM engineer + sales leadership |
| Maintenance | 3 to 4 hours per month | GTM engineer |
Maintenance and monitoring
Workflows drift as your GTM strategy, ICP and stack change. Keep this one honest with the following cadence.
- Watch the SLA view daily for the first month, then weekly; any drift over 10 minutes median is a pipeline break, not a rep problem, until proven otherwise.
- Re-validate scoring weights quarterly against actual conversion by tier; reweight when the data disagrees with the opinions.
- Keep the routing lookup current the same week territories change; a stale routing table is how hot leads die quietly.
- Test the webhook after every form or marketing-automation change; forms fail silently and Clay cannot enrich what never arrives.
- Alert on enrichment latency over 5 minutes; a slow provider in the chain should be swapped, not tolerated.
Related
Want this running in your stack?
I build Clay-powered data orchestration systems for growth-stage GTM teams: this playbook and the four beside it, tuned to your ICP, CRM and motion.