The most common outbound mistake I see in 2026 is not bad copy. It is burning your main domain on cold email before understanding how inbox routing actually works.
Here are the five things that decide deliverability — in the order they matter.
1. Satellite domain architecture {#satellite-domains}
Never send cold email from your primary company domain (yourcompany.com). The risk is permanent: one spam complaint threshold, one blacklist event, and your transactional email — receipts, onboarding flows, password resets — goes with it.
The pattern that works:
- Buy 2–3 satellite domains:
yourbrand-sales.com,yourbrand-team.com,outrch-yourbrand.com - Configure email on each satellite domain, not the primary
- Keep the primary domain for product email only
Cold email goes out from satellites. If a satellite gets blacklisted: retire it, buy a new one, restart warm-up. Your main domain survives.
2. SPF, DKIM, DMARC — in that order {#spf-dkim-dmarc}
These three DNS records are not optional. They are the handshake between your sending infrastructure and the receiving server that tells it “this email is legitimate.”
SPF (Sender Policy Framework): declares which servers are allowed to send email from your domain.
v=spf1 include:_spf.google.com ~allAdd this to DNS for every satellite domain. If you’re using Google Workspace, Instantly, or Smartlead, they will tell you the exact string.
DKIM (DomainKeys Identified Mail): cryptographically signs every outbound email. Receiving servers verify the signature. No DKIM = significantly higher spam probability.
DMARC (Domain-based Message Authentication, Reporting and Conformance): tells receiving servers what to do when SPF or DKIM fails. Start permissive:
v=DMARC1; p=none; rua=mailto:[email protected]Then tighten to p=quarantine after 30 days of clean reports.
All three must be set correctly before you send a single email. Many tools will check them for you (MXToolbox, Mail-Tester).
3. Warm-up cadence {#warm-up}
A fresh domain and inbox has zero reputation. Sending 500 emails on day one will land in spam and get the domain flagged.
The standard warm-up sequence:
| Week | Daily volume per inbox |
|---|---|
| 1–2 | 5–10 |
| 3–4 | 10–20 |
| 5–6 | 20–30 |
| 7+ | 30–50 (max per inbox) |
Use a warm-up tool (Instantly, Smartlead, Lemwarm) that automatically sends and “rescues” warm-up emails between a network of real inboxes. This builds positive signals: emails opened, replied to, not marked as spam.
Do not skip this. Do not rush this. Six weeks is not optional; it is the minimum.
4. Inbox rotation {#inbox-rotation}
For every satellite domain, set up 3–4 mailboxes ([email protected], [email protected], [email protected]). Your sending tool rotates sends across all inboxes.
Why: a single inbox hitting 50 emails/day triggers volume flags. Three inboxes at 20 emails/day each do not.
The math: 3 satellite domains × 4 inboxes each × 20 emails/day = 240 touches/day. That’s a real outbound motion from a standing start, without touching your primary domain.
5. Content signals {#content-signals}
Technical settings handle delivery to the inbox. Content signals handle whether the human opens it or marks it as spam.
The things that spike spam rates:
- Spammy words in subject lines: “free”, “guarantee”, “no obligation”, “limited time offer” — these are scored by filters
- Image-heavy emails: text-to-image ratio matters. Cold email should be text-only or nearly so
- Links in the first email: every link is a signal. Consider sending the first email link-free
- Personalization tokens that don’t resolve:
Hi {FirstName}in the inbox means your data has blanks. Fix the data before sending
What happens when you skip all of this {#skip}
You send from your main domain. You skip warm-up. You use a template with three links and an image. You send 500 emails on day one.
Within a week: open rates collapse, the domain hits a Spamhaus listing, your support team starts getting tickets about password reset emails going to spam.
This is not hypothetical. It happens every month. It takes six to twelve months to recover a domain reputation, and some domains never fully recover.
What to do next {#next}
The AI Outbound / GTM Engineering engagement covers all of this: satellite domain purchase and configuration, SPF/DKIM/DMARC setup, warm-up plan execution, inbox rotation, and a piloted campaign with real deliverability metrics reported at the end.
Six weeks to a working outbound infrastructure. With a pilot report that tells you whether to scale, adjust, or stop.