The path, step by step
You add a company
"Acme Corp, Jane Lindqvist" is enough. No email address required, no enrichment subscription, no spreadsheet gymnastics. Paste a list of company names and let the engine take it from there.
It finds the right person
The discovery pipeline searches, reads the company website, cross-checks data providers, and verifies the email address before a single word is sent to it. Unverifiable addresses never get mailed.
It does the homework
The company gets read before it gets written to. The first line of the intro comes from research on that specific business, not from a mail-merge template.
A considered intro goes out
One email, to one person, sent from your own Gmail, inside your working hours, minutes apart from the last one. The way you would send it yourself. Prefer sign-off on every word? Approval mode queues each draft for you first.
Patient follow-ups
No reply? It waits the interval you chose, then nudges politely. It never crowds, and it stops the moment the person writes back.
Every reply is read
A five-step matcher files each inbound to the right conversation on hard evidence (headers, thread IDs, quoted text), never on a hunch. Claude then reads it, scores how interested the person really is, and picks one of sixteen specialist playbooks: out-of-office waits it out, "talk to my colleague" follows the referral, a bounce is quarantined, and anything unclear goes to a human.
Hot leads are handed to you
When interest crosses the threshold you get an instant alert with the thread, the intent score, and what the person cares about. Automation stops; the human conversation starts. Everything the AI learned travels with the lead, so you start informed, not cold.
What is running underneath
A warm-up ramp that protects your name
A new mailbox starts at about five emails a day and earns its way up to about fifty over weeks. Gmail never sees a cold mailbox behave suspiciously, and daily SPF/DKIM/DMARC and blocklist checks catch trouble before it compounds.
A kill switch you never have to pull
Bounce and spam-complaint rates are watched continuously. A spike pauses all sending automatically and keeps it paused until a human reviews it.
A ledger where nothing fires twice
Every action becomes a ticket with a unique receipt before it can run. If a worker crashes mid-task the ticket retries safely: nothing sends twice, nothing is silently lost, and a permanent opt-out is checked before every single send.
A night manager doing the rounds
Every few minutes the Steward sweeps the queues an operator would otherwise hand-triage: it parks out-of-office replies until the return date, quarantines confirmed bounces, reschedules drifted follow-ups, and leaves anything ambiguous in your morning digest with its reasoning attached.