Lead Qualification
A form fills at 6:40pm on a Friday. Inside a minute this agent has read it, scored it against your criteria, pulled the relevant detail out of your own material, and written a reply that answers the question they actually asked — not an acknowledgement. It pings you, you read it, you click send. Then it keeps the thread alive: a bump on day one, something useful on day three, a re-engagement on day seven, a close-out on day fourteen. Weak leads get a drafted, polite no. Nothing goes out until a person clicks send.
Yours outright — no required subscription.
Every agent is built for your business — your systems, your approval chain, your way of working. We scope it on the call.
If this sounds too technical, don't worry. We take care of everything for you.
- Private VPS deployment. This agent runs on a server that belongs to you, not a shared cloud tenant. Your inbound leads, your criteria, and everything it writes about them stay on your box.
- A technician agent alongside it. Every hire ships as a pair: the Lead Qualification Agent doing the scoring, drafting, and following up, and a VPS-technician agent that lives on the same box and keeps it healthy — patched, backed up, monitored. You're not hiring one thing, you're hiring a small team of two.
- Your criteria and your answers, written down. Two documents, both out of the owner's head: what makes a lead worth a call — budget bands, service area, timelines, who has to be able to sign — and the material it answers from, meaning your pricing, your case studies, and the questions every prospect asks. When a lead is scored wrong you point at the line that did it. When a reply reads generic, you fix the source it read.
- Your highest-volume lead channel, wired in. We start with the one channel most of your leads actually arrive in — the website form, a shared mailbox, a lead-source notification, texts — connected directly where there's a native connector and through Zapier where there isn't, so nothing has to be forwarded by hand.
- A five-touch follow-up cadence. Minute zero, day one, day three, day seven, day fourteen — each one drafted in context, each one stopping the moment the prospect replies. It is the sequence everybody intends to run and nobody runs.
- Security hardening. Private VPN, firewall, and encryption configured on your server before a single lead runs through it.
- 14 days of priority support after launch, to tune the criteria and the cadence against the real mix your channel actually catches.
- You own everything — the server, the agent, the code it runs on.
Not sure it fits? Check fit in 90 seconds in the free assessment chat.
Who this is for
- You're buying shared leads, and the first company to call back usually wins the job. The notification hits your phone while you're on a roof, and you either answer at 7pm from the truck or you don't.
- Leads arrive at 1am, on Saturdays, and during the two hours you're in a meeting. Nobody is awake to answer them, and by Monday the good ones have signed with somebody faster.
- You follow up once, maybe twice. The deals live in the third and fourth touch, and that is the part that stops happening the moment the week gets busy.
- You're a 25-person shop where info@ forwards to three people, so each one assumes another has it. Forty inquiries last month, four worth a call, and nobody has sent a decline in about a year.
- You have one inquiry form doing two jobs. It catches a 200-door retailer and a dropshipper who wants a discount on a single unit, and whoever answers pastes the same paragraph into both.
How it earns trust
The failure mode of AI on inbound isn't a lead scored wrong — every system scores some wrong. It's that a fast, confident, wrong reply looks exactly like a right one on the way out, and the prospect it mishandled never calls to complain. This one is built on the opposite bet: every draft arrives with the message it answers and the reasoning behind its score.
Read the bottom ten every Friday
Sort the queue by lowest score and read the ten it liked least. The leads it wanted to decline are exactly where a miss hides, and those declines are still sitting there unsent — so catching one takes a minute, and it costs you nothing but the minute.
The first month is the evidence
You approve every draft for a month before anything is loosened. That is not a formality — it's the record you decide on. If its wording, its scoring, or its day-three pick isn't right yet, you found out while every message was still passing under your eyes.
A stamped record on your server
The raw inbound text exactly as it arrived, which of your criteria it hit and which it missed, the score and the reasoning behind it, every draft including which touch of the cadence it was, and who edited or sent it. Because it appends and never overwrites, you can tell its work apart from your team's after the fact.
None of this asks you to trust the score — it makes the score cheap to check, which is the part that's usually impossible.
Pairs well with
These share a workflow with this role. Tick any to add them to your setup.
By the time I call them back, they've already hired somebody.
That is the whole point of this one. A lead that arrives at 6:40pm Friday is scored and has a reply drafted about a minute later, not Monday morning — and the reply names what they asked about, because it is written from your material rather than from a template. A person still clicks send, so for the first month your response time is really how fast you check your phone. That is also the month that earns the right to loosen it.
Won't a one-minute reply just be a generic one?
Fast and generic loses to fast and relevant, so the draft is written against the specific message and whatever your material says about it — your pricing bands, the case study that matches their situation, the answer you have given forty times. There are hard limits on what it may say: it can attach your scheduling link, but it will never quote a price, commit to a start date, or promise scope. Those stay yours.
I know I should follow up five times. I never do.
It drafts all five: the first reply, a short bump on day one so it doesn't get buried, something genuinely useful on day three — a case study or a tip from your own material, matched to what they came in about — a re-engagement on day seven, and a close-out on day fourteen that asks plainly whether this is dead. A reply from them stops the sequence. Each touch is a draft you approve, so the cadence runs whether or not you remember it.
Do I have to approve every message forever?
For the first month, yes, and that is deliberate — a month of reading its drafts is how you find out where it is wrong while nothing is at stake. As long as you're in the loop you are also the bottleneck: a lead at 1am waits for you. After a month most owners let it answer the clear-cut leads on its own and stay in the loop for the ones that need a human. You own the server and the code, so that switch is yours to set and to reverse.
Half of what comes through that form isn't a real person.
That first pass is the cheapest thing it does — bots, dev-shop and SEO pitches, recruiters, students asking for portfolio feedback, all sorted out of the way with a reason attached. What it won't do is delete or archive them. A 2-out-of-10 stays in the queue with its reasoning next to it. Nothing disappears because it scored badly, so a miss costs you a click, not a customer.
I know I should tell people no. I just never get around to it.
It writes the no for you. What it will not do is send it. Every reply, and the polite decline especially, sits in a queue until a person reads it and clicks send — a no goes out under your name only after someone with your name has looked at it. Declines are the highest-risk copy it drafts, which is exactly why they stay drafts even after you loosen the rest.
Our CRM is a graveyard — nobody logs anything.
It writes the entry every time — contact, company, deal, source, stage, and which touch of the cadence they're on — which is the step that gets skipped and the reason Monday's pipeline number is wrong. It only ever appends. It won't merge duplicates, reassign an owner, move a deal stage, or overwrite a record that's already there. Your routing and your approval chain stay yours: it adds a step, it never removes one.
What's covered under the $1,997 setup, and what isn't?
One company, one lead channel, one system of record, one approval chain. A second and third channel are usually straightforward once the first is running, but they get scoped rather than assumed — as do multiple brands with genuinely different qualifying criteria. Typically live in about seven days from kickoff, with 14 days of priority support after launch.
Hiring more than one? A department on tap — the subscription puts a build team behind every request, agent after agent.