Inbound Lead Routing for a Small Team
Outbound gets the airtime. Inbound, when it exists at all, often sits in a shared inbox or a CRM notification nobody owns. Fivos Aresti has listed "inbound orchestration" among core builds. Another operator frame, in an Era 1 systems list, treats automated inbound follow-up as a standard early system. And a fair challenge still circulates: why aren't B2B companies putting effort on inbounds?
Pramod Kumar, co-founder of Kingdom of Kumar. On X
·
My answer: because outbound is more visible, and because inbound feels like it should "just work" once the form exists. It does not. Routing is how a raised hand becomes a same-day human conversation, or how it becomes a lead that went cold while you were building a sequence.
This is a small-team routing system. Speed is in Lead response time for B2B. The demo-request path is in A demo-request follow-up process. Queue order is in Lead scoring for early-stage SaaS. The wider work is on GTM engineer and GTM engineering. If the product is not ready to sell, take the App Launch Score — a well-routed demo for a product that is not ready is still a bad first meeting.
"Inbound orchestration" as a core build
You do not need a platform to orchestrate inbound at seed. You need a path with an owner.
When a form is submitted, a chat is left, a "contact us" mail arrives, or a demo is requested, four things must happen:
- 1The record is captured in a place the team actually looks — CRM or a serious sheet — with the source and the time
- 2Duplicates, customers, and open deals are recognised, so you do not treat a current customer like a stranger
- 3A person is assigned, by a rule, not by who happened to see the Slack ping
- 4The person is notified in a way they honour, and the first human response has a time limit you have written down
"Automated" can mean a mail that confirms you received the request, and a task created for the owner. It should not mean a long nurture sequence that delays a human when someone asked to talk.
"Why aren't B2B companies putting effort on inbounds?"
Often because the volume feels too low to "deserve a system," or because the inbound is messy — students, competitors, job seekers, people who wanted a pricing PDF. Low volume is an argument for a *simple* system, not for no system. Messy inbound is an argument for a fit check in the first minutes, not for ignoring the form.
I would rather a founder have a ten-minute daily inbound ritual, even at two requests a week, than a sophisticated router that nobody watches. The companies that look like they "don't care about inbound" are often the ones whose outbound ambition outran the basic courtesy of answering people who already raised a hand.
A routing rule you can write today
- Demo or "talk to sales": assigned to the founder or AE on a stated rotation, immediately. First human reply the same day, faster if you can. See the response-time piece for the habit, not for invented benchmarks.
- Contact form with a clear buying question: same as above.
- Content download or waitlist: a short, honest email, then a human follow-up if they fit, not a ten-step drip that hides the ask.
- Existing customer: route to whoever owns the account, not to the outbound queue.
- Existing open opportunity: notify the owner; do not open a second thread.
- Clear mismatch (wrong country you do not serve, student using a personal mail for a homework question, job applicant in the demo form): a polite close or a redirect, and a tag so you can see how much of the inbound is this.
Write the rotation in a sentence: "This week, Pramod owns inbound replies; next week, ___." If there is only you, say that, and block the time.
What to automate, and what not to
Automate the capture, the owner assignment, the internal notice, and a simple confirmation to the person who submitted the form. Automate the never-contact check if you can do it reliably.
Do not automate a pitch sequence that runs before a human has looked. Do not auto-qualify with a long form if a short form plus a conversation would tell you more. Do not let a chatbot promise a callback time you will not keep.
If you use a model to draft the first reply, approve it the same way you would an outbound first line when it states facts. For a plain "thanks, here are two times," a saved snippet is often better than a model.
A daily ritual, even when volume is low
Morning and late afternoon: open the inbound view, not only Slack. Clear every new row. If a row is older than your written time limit, treat that as an incident, not as "we'll get to it." On Friday, count inbound, time to first human reply, misses, and mismatches. If mismatches dominate, fix the page or the form, not the router.
This ritual is part of GTM engineering as much as a Clay table is. It is less photographed.
A form that makes routing easier
You do not need twenty fields. You need a few that change the route: work email, company, what they want (demo, support, pricing, other), and maybe a role. If your form cannot tell a support request from a demo request, the router will fail in the first minute, and a salesperson will get a password-reset.
Put a note on the thank-you page about when a human will reply, and then keep that promise. A vague "we'll be in touch" is how people follow up on a second channel while you are still organising the first.
If the same person submits twice, the second submission should bump the existing record, not create a twin that two people answer. That sounds obvious, and it is one of the common misses in a small CRM that was never given a unique key.
When volume grows, change the rule, not the courtesy
If inbound goes from two a week to two a day, add a clearer rotation, a shared view, and a backup owner for leave days. Do not add a long qualification bot as your first response to growth. The first response is still a human, or a short confirmation plus a human. You can tighten the form, and you can send mismatches to a kinder close, but "scale" that starts with ignoring the people who already raised a hand is the habit this article is against.
FAQ
What if inbound and outbound compete for the same hour?
Inbound wins the first look, then you return to the outbound cap. People who already asked should not wait behind a cold batch.
Do I need a routing product?
Not at small volume. A CRM assignment rule, or even a sheet plus a calendar block, is enough until it starts failing. Buy a tool when you can name the failure.
Can Kingdom of Kumar set this up?
We build and run a scoped system on Grok and Claude for $500 a month, three-month minimum. You own it, and you approve what goes out. We can include inbound routing and the daily habit in that system. We will not hide a dropped demo request behind a chatbot. You still need a named human. This is not a $135,000 RevOps hire.