Internal product
A cold-outreach engine we ran on our own pipeline first
Contact sourcing from Apollo, verification, warmed secondary sending domains, sequenced copy, reply triage, and weekly deliverability reporting. We ran it at scale on our own program through the second half of 2025, then for a partner under their brand, as a pilot for a client, and on hourly contracts.
Internal product
Built and operated by us, not sold as a product. Happy to demo it live and explain the decisions inside it.
- Headline figure
- 247 qualified leads
- Status
- Delivered
- Practice
- Automate · Data · Growth
- Sources
- 3 figures
from about 3.6 million emails sent to lists built in Apollo, on our own program: 79 in July, 71 in August, 58 in September, and 39 in October. That ratio is why the sequence, verification, and deliverability playbook exists, July to October 2025
Internal product
Outbound sales operations
document on record, dashboard export, operator statement
The problem.
Founder-led firms need qualified conversations from cold channels without burning their primary domain, and most outbound tooling is sold on reply rates nobody can reproduce. We ran the engine on our own program first. The figures on this page come from that run and from the domains we send from today.
What was built.
- Contact sourcing from Apollo, then verification with a commercial verifier and later our own Email Verifier
- Secondary sending domains with SPF, DKIM, and DMARC, warmed before use, so the primary domain never carries cold mail
- Sequenced, persona-segmented copy: nine templates tested against the one five-step sequence that won
- Reply triage and marketing-qualified-lead hand-off, with weekly deliverability reporting
- The same engine, run as a pilot for a hotel-data client on an 8,869-contact list that passed verification with zero flags, and for a partner under their brand
- Own program, July to October 2025: about 225,000 unique recipients a month with four touches each, roughly 900,000 emails a month, sent through five Salesforce Starter accounts and one third-party sending app; the sequence that won offered a free custom AI agent over five steps
- An email-infrastructure review delivered to a partner team on 19 February 2026: Instantly on Google Workspace, ideal-customer profile, copy framework, verification, and reseller economics
- Our own 2026 rebuild: ten mailboxes across five domains on Hostinger with Cloudflare name servers, an Apollo Context Center profile, a 42-combination offer-by-segment grid, sequences staged inactive, and a weekly deliverability report per domain
- Two hourly contracts with one client, February to May 2025: Apollo-based email marketing and AI-assisted scraping of website addresses and contacts
Timeline.
Partner program agreed under NDA: the engine to run under the partner's brand, on their targets
Our own program: about 3.6 million emails over four months, 247 marketing-qualified leads, one winning sequence out of ten
Partner campaign operating under their brand: email templates reviewed, a response-time process and a rate card in place
Pilot for the hotel-data client, capped at 2,000 sends a day: a 13,000-row list cut to 8,869 contacts with zero verification flags, two domains warming, 15 sending seats; first campaign live 20 March
Our own 2026 fleet: ten mailboxes bought and five domains connected, name servers on Cloudflare
Weekly deliverability report on one secondary domain: DKIM 100%, SPF 96.3%, DMARC pass on 109 messages
What this case claims, and what it does not.
On the record
- Our own second-half-2025 program sent about 3.6 million emails from Apollo-sourced lists and produced 247 marketing-qualified leads
- Built a verified 8,869-contact dataset with zero verification flags for a client pilot
- Deliverability operations with DKIM, SPF, and DMARC monitoring across secondary domains
Withheld, and why
Figures that exist internally and are not on this page, with the reason.
- Lead counts as revenue or closed deals
- A marketing-qualified lead is a conversation, not a customer. No count here is a revenue figure, and none is presented as one.
- The partner campaign's numbers
- It produced qualified leads and no closed deals. The leads were handed off and the closing was not ours, so neither number is a result we would publish.
- Per-campaign reply-rate benchmarks
- They exist per sequence and are not yet in an exportable form with their windows, so nothing is published beyond the program total.
- The partner's or the client's name
- Not recorded as permitted.
Elsewhere on the site
Read next
Where to next
Have a problem in this shape?
Send a short description. The form opens with this case already named, so you only add the part that is yours. We will tell you whether it is worth building at all.