Case studies · 01 · Lead Engine

The First Run

The engine's first client campaign: a healthcare-staffing firm that wanted to reach clinic and facility decision-makers across New York. Everything below is real and redacted — the client and their prospects are never named.

What the engine did

01Took a short brief: who to reach, where, and what the client offers

02Built the list fresh at launch from live maps and directories

03Filtered out anything that didn't match the brief

04Verified every address before a single send

05Wrote a personal first line for each business — read by a human before it went out

06Sent in paced batches from warmed domains the client never had to risk

What the client received

The deliverables, plainly — the same set every Lead Engine client gets.

A verified lead list, built fresh for the brief — every address checked before sending
A personalized opener for every business, written one by one and read by a human
Warmed sending domains and inboxes, set up and run for them — their own domain untouched
Every interested reply routed straight to their inbox
A live lead sheet — who was found, contacted, and replied — updated as the campaign ran
A weekly read of what went out, who answered, and what to change next

The run, straight from the sending tool

Batch dashboards, untouched except for redaction. Sent volume, the reply curves, and the bounce tab — the number we watch first, because deliverability is what keeps every later email landing in inboxes.

Sending-tool analytics for one batch: sent volume and reply trend, with the step table showing reply rates — One batch: sends, replies and the step table

Sending-tool analytics for a later batch: sent volume and reply trend over four weeks — A later batch: the engine kept running

Sending-tool bounce tab for one batch: a small number of bounces against the full sent volume — The bounce tab — verification doing its job

What landed in the inbox

Decision-makers replying with role lists, credentials and pricing questions. The first card keeps the personalized opener that earned the reply.

Redacted email reply asking for pricing on five clinical roles, with the personalized opener that started the thread quoted beneath — Asked for pricing on 5 roles · Sep 3

Worth noticing in the first card: the opener references the clinic's own accreditations — the engine read what they do and wrote a line only they could receive — and the ask is one word (“reply ‘sure’”). The email went out at 8:37; the reply, with five roles listed, landed at 9:37.

Redacted email reply asking what we charge for two provider roles — Asked prices for two roles · Sep 8

Redacted email reply asking for candidates with specific clinical credentials — Asked for specific credentials · Sep 16

Redacted email reply asking us to find licensed clinicians for their team — Asked us to staff their team · Sep 15

Redacted email reply asking for per-diem clinical help — Asked for per-diem help · Sep 11

Redacted email reply describing a role they need to hire for — Described the role they need · Sep 23

What this run proves — and what it doesn't

It proves the machine: fresh lists, verified addresses, personal openers that real decision-makers answered, and bounce numbers low enough to keep sending. It doesn't promise your results — replies depend on your offer and your market too, which is why our guarantee covers the delivery, and why month 1 is a test we read with you.

See how the engine works Get 5 sample leads — free Next: The Engine That Sold Itself