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 landed in the inbox

Decision-makers replying with role lists, credentials and pricing questions.

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

Worth noticing: the opener quotes the clinic's own accreditations — the engine read what they do. The ask is one word. Sent 8:37, answered 9:37.

Asked prices for two roles · Sep 8
Redacted email reply asking what we charge for two provider roles
Asked for specific credentials · Sep 16
Redacted email reply asking for candidates with specific clinical credentials
Asked us to staff their team · Sep 15
Redacted email reply asking us to find licensed clinicians for their team
Asked for per-diem help · Sep 11
Redacted email reply asking for per-diem clinical help
Described the role they need · Sep 23
Redacted email reply describing a role they need to hire for

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

The run, straight from the sending tool

Batch dashboards, untouched except for redaction.

One batch: sends, replies and the step table
Sending-tool analytics for one batch: sent volume and reply trend, with the step table showing reply rates
A later batch: the engine kept running
Sending-tool analytics for a later batch: sent volume and reply trend over four weeks
The bounce tab — verification doing its job
Sending-tool bounce tab for one batch: a small number of bounces against the full sent volume

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.