- Oct 16, 2026
- 3 min read
Keep Outbound Away From Your Inbound Engine
My sites already had an inbound engine: same-origin forms, double opt-in, retention enforced by code, a weekly digest, follow-up emails only to people who asked for them (from five lead silos to one hub). Then I wanted to learn outbound: lead lists, enrichment, cold email.
The first design question wasn’t technical. It was: what must outbound never touch?
Four separations
| Inbound (opt-in) | Outbound (cold) | |
|---|---|---|
| Brand | The main business | A separate trading name |
| Domain | The main domain and its subdomains | A separate domain bought for sending |
| Sender | The transactional provider that sends confirmations and receipts | A cold-email tool with mailbox rotation and warm-up |
| Data | The lead inbox: people who contacted us or opted in | Files per batch, deleted after 90 days |
1. Domain: protect your reputation where it pays
Mailbox providers judge every sending domain by complaints and bounces. Cold email collects some of both, even when it’s done well. If the domain that sends your double-opt-in confirmations gets a reputation hit, your real subscribers stop receiving them.
A separate domain with its own SPF, DKIM and a strict DMARC policy keeps the two reputations apart.
2. Sender: read your provider’s terms
Transactional email providers forbid sending to scraped or purchased lists. A suspended account doesn’t just stop the campaign: it stops every confirmation, password reset and report your business sends. Cold email goes through a tool built for it, with inboxes on the separate domain.
3. Data: the lead inbox stays opt-in only
It would be easy to add prospects to the existing lead store as a new “kind”. I decided against it:
- Consent becomes muddy. Everyone in the inbox today contacted me or opted in. Mixing in people who never asked complicates retention, erasure requests and every count in the weekly digest.
- Different lifetimes. Prospects who don’t reply are deleted after 90 days; enquiries are kept for the period the privacy page promises.
So prospects live in per-batch files on the machine that runs the batch, excluded from git, deleted on a schedule. Someone enters the inbound engine only by their own action: replying, then booking or filling in a form.
4. Brand: separation isn’t anonymity
A separate brand protects the main one from association with cold outreach. It does not hide who’s behind it, and it shouldn’t:
- UK and US rules require the sender’s identity to be truthful.
- Data protection requires the privacy notice to name the data controller: a real person or company.
So the outbound site names its controller, and emails go out in the name of a real person who agreed to send them.
The checklist I keep
- Separate domain; SPF, DKIM, DMARC verified with
digbefore the first send - Separate sending tool; warm-up running for 2–3 weeks
- Never the transactional provider; never the main domain
- Prospects never written to the lead inbox
- Per-batch files gitignored, deleted after 90 days
- A site on the outbound domain whose claims are true (real client stories only, no placeholder testimonials)
- Privacy notice naming the real controller
- A legitimate-interest assessment on file
- One finding per email, no tracking, an easy “reply no”
Takeaways
- Decide what outbound must never touch before building it.
- Reputations are per domain: give cold email its own.
- Opt-in data stays opt-in. Prospects become leads only by their own action.
- A separate brand is a firewall for reputation, not a disguise.