Cold email at scale, without burning the domains
Cold outreach fails in two directions: too little and nothing converts, too much from too few inboxes and every future email lands in spam. This system bounds the second failure structurally, because nothing in a normal sending setup enforces a ceiling.
LIVE · 7 OF 7 WORKFLOWS ACTIVE · QUOTA ENFORCED AT ASSIGNMENT
- Sector
- B2B lead generation
- Basis
- Own build, running live
- Stack
- n8n · Sheets · multiple SMTP accounts · LLM research · Discord
- Surface
- 7 interlocking workflows
- Status
- All seven running live
The problem: sending volume that burns the domains
Most teams discover the deliverability failure only after it has already happened: mailboxes throttled, domain reputation collapsed, and every future email in spam, including the ones people wanted. By then the damage is to infrastructure, not to a campaign, and it takes months to undo.
The approach
Seven interlocking n8n workflows cover the full pipeline: prospect sourcing, inbox assignment, scheduled first contact, second and third follow-ups, email management and reply handling. The deliverability architecture is the real product:
-
Daily inbox assignment with a hard quota
A scheduled workflow takes the waiting list, caps the batch, pulls the active inboxes, and distributes leads evenly before writing each lead back with its assigned sender. No inbox exceeds its daily volume, because the ceiling is enforced at assignment time rather than hoped for at send time.
COLD EMAIL / N8N / INBOX ASSIGNMENT LIVE
FIG. 01 The quota lives here: the batch is capped and distributed across active inboxes before anything sends. -
One lead, one inbox, for the whole sequence
A prospect's first email and every follow-up come from the same address. Threads stay coherent and do not look like a rotating machine.
-
Throttled sending, not blasting
The sender runs on a short timer, processes the pending queue, then explicitly waits for the next execution. Volume is spread across the day by design.
COLD EMAIL / N8N / SCHEDULED SENDER LIVE
FIG. 02 The sender: research pulled per prospect, parsed into fields, built into a message, sent throttled. -
Follow-ups timed in business days
Leads are selected by business days since the previous touch, so a sequence does not fire over a weekend and stack three emails into a Monday morning.
COLD EMAIL / N8N / SECOND FOLLOW-UP LIVE
FIG. 03 Follow-up selection by business days since the last touch, keyed to the same assigned sender. -
A reply stops the sequence
A dedicated response-management workflow watches for engagement, so someone who answers stops receiving automated follow-ups. The difference between a system that starts conversations and one that annoys people into blocking you.
Personalization runs on live research rather than mail-merge tokens: the sender pulls research on each prospect, parses it into structured fields, and builds the message from those fields, so the opening line references something real about the company.
The system
How it fails safely
| Failure | What happens instead |
|---|---|
| Mid-run crash | Lead state is tracked explicitly through the pipeline, so a failure resumes rather than restarts. No double-sends. |
| Volume spike | Impossible by design: the quota is enforced at assignment, and the sender throttles across the day. |
| Prospect replies mid-sequence | The response workflow stops their follow-ups automatically. |
| Lead pool runs dry | The assignment workflow pings the team, so an empty pipeline surfaces immediately instead of looking like a quiet day. |
Result
- Full outreach pipeline automated from sourcing through reply handling, running as seven live workflows.
- Sending volume bounded per inbox per day, enforced structurally rather than monitored manually.
- Personalization based on real research per prospect instead of merge fields.
- Sequences stop automatically on reply, and operational alerting surfaces an empty lead pool the moment it happens.
Related, but a different ceiling: the sponsor sourcing pipeline bounds API spend while building a prospect list. This system bounds sending volume while working one.
Built by Hisham Hanawi. This is an operations automation build.
Outreach that protects its own infrastructure.
100% JOB SUCCESS · TOP RATED PLUS · 583 HOURS / 6 ENGAGEMENTS
Source: Upwork profile, verified 2026-08