automation 02
Lead Generation Engine
Ten workflows on a Postgres backbone. Finds companies actively running ads, scores them on two independent axes, finds and verifies decision-makers, routes them through per-country compliance, and dispatches through warmed infrastructure with a circuit breaker on the way out.
- Install
- Install from $4K
- Timeline
- Two weeks to install, then about three weeks of domain warmup before the first send
- Runs on
- Your own n8n
- 01
134
nodes
- 02
10
workflows
- 03
14
tables
- 04
26
SQL statements
Everyone sending cold email is competing for the same attention with the same template. The only durable edge is knowing something specific and true about the company before you write the first line.
how it runs
the workflows
- 0
Orchestrator
Campaign intake, daily tick, and the readiness gate that refuses to send from a domain that has not finished warming.
- 1
Discovery
Maps and SERP harvest, then a Claude pass against the written ICP to drop the companies that merely match the keyword.
- 2
Signals
Ad harvest and a two-by-two score on budget and need, kept as independent axes because a company with money and no problem is a different prospect from one with a problem and no money.
- 3
Enrichment
Apollo to Findymail waterfall with a verification gate. Unverified addresses do not proceed.
- 4
Compliance
US CAN-SPAM and UK PECR routing with suppression handling, plus cross-client dedupe so two campaigns cannot both hit the same inbox.
- 5
Personalisation
An opener grounded in the prospect's own live ads, then a specificity critic that rejects anything that would read as a template, then approval.
- 6
Dispatch
Smartlead dispatch with a quota re-check at send time rather than at queue time.
- 7
Events
Reply and bounce webhook feeding a circuit breaker that pulls a campaign automatically when bounce rates move.
- 8
Reporting
Weekly client report and sending-infrastructure health.
- E
Error handler
Failure logging and alerts.
how it holds up
01
Four gates protect the infrastructure
Domains are shared across clients, so one client's bad targeting can damage deliverability for everyone. The readiness gate, the verification gate, the cross-client dedupe and the circuit breaker exist for that reason and none of them are optional.
02
Grounded openers, not spun ones
The first line references something the prospect is actually running right now. A critic pass rejects anything generic enough to have been sent to anyone else.
03
Two axes, not one score
Budget and need are scored separately and kept separate. Collapsing them into a single number hides the distinction that decides how you approach the account.
what it will not do
You cannot send for about three weeks after onboarding. New domains need roughly fourteen days of warmup and the readiness gate will refuse until then. Price and pitch with that ramp built in.
Deliverability is a shared resource. Targeting that generates complaints is caught by the circuit breaker, but prevention is a client conversation, not a setting.
It does not replace a salesperson. It fills a calendar with conversations that have a reason to happen.
you supply
- n8n, cloud or self-hosted
- Postgres, Supabase is the least friction
- Apollo and Findymail accounts
- Smartlead or equivalent sending infrastructure
- Anthropic API key
running cost
Dominated by enrichment credits and sending seats rather than model calls. Sized per campaign.
Billed by your own providers, not by us. There is no platform fee and no seat count.
InstallLead?
Install from $4K, two weeks to install, then about three weeks of domain warmup before the first send. Tell us about your setup and we will confirm it fits before taking anything.