Never send cold email from your main domain

It feels natural: you're the founder, your email is [email protected], so that's where the outreach comes from. It's also how startups quietly break their own product. Cold email at any real volume accumulates spam complaints — even good campaigns run 0.1–0.3% — and the domain that absorbs those complaints is the same one your password resets, invoices, and investor updates depend on.

What actually breaks when your main domain gets flagged

Gmail and Outlook score sender reputation at the domain level. When cold-email complaints drag that score down, the damage isn't contained to your campaigns:

• Product email dies first. Sign-up confirmations, password resets, and receipts start landing in spam — users think your product is broken.
• Normal correspondence gets flagged. Your team's 1:1 emails to customers and investors pick up warning banners.
• Recovery is slow. Domain reputation rebuilds on the scale of weeks to months, and there is no support line to appeal to. One bad month of outreach can cost a quarter.

The rule serious senders live by: the domain that runs your business never sends cold email. No exceptions, no "just this one campaign."

Isn't a subdomain enough? (mail.yourcompany.com)

Subdomains are the right tool for opted-in streams — transactional mail on mail., newsletters on news. — because they separate those streams' reputations from each other. But for cold outreach they're a half-measure:

• Gmail's reputation systems increasingly roll up to the organizational domain — a burned subdomain stains the root it hangs from.
• DMARC alignment ties the subdomain to the org domain by default.
• Filters treat the org domain as the unit of trust; a subdomain is the same blast radius behind a thinner wall.

The standard: cousin domains

The setup used by effectively every experienced outbound team:

Each cousin domain gets: its own Google Workspace (about $7/user/month), SPF + DKIM + DMARC configured from day one, and a root that 301-redirects to your real site — so a prospect who types the domain lands somewhere legitimate. Sending as a real human ([email protected]) is completely standard; the human name is what earns the reply, and it survives the domain change.

The mailbox math for real volume

A warmed mailbox safely sends 50–100 cold emails a day, forever — that's the ceiling reputation physics allows (full numbers in how many cold emails per day). So volume is a horizontal problem, not a vertical one:

Two more constraints worth knowing. Gmail and Yahoo's bulk-sender rules kick in hard at 5,000+ emails/day to their users from one domain — one-click unsubscribe, DMARC enforcement, and a spam rate under 0.3% that cold email structurally struggles to meet. And brand-new domains have no history, which filters read as guilt: buy your cousin domains early and let them age at least 30 days with a page live before the first send.

Do you even need tens of thousands?

Honest question before you build the mailbox farm: volume is usually a substitute for targeting. Two thousand sends to a sharply defined ICP with per-contact personalization and follow-ups that actually happen will out-produce twenty thousand sprayed emails — on replies, on meetings, and on what it does to your sender reputation. Scale the list quality first, the mailbox count second.

The checklist version

1. Buy 2–3 cousin domains today (they age while you build).
2. Workspace + SPF/DKIM/DMARC on each; root redirects to your real site.
3. 1–3 human-named mailboxes per domain; warm up 2–4 weeks.
4. Hold 50–100/day per mailbox; add mailboxes, not volume.
5. Watch bounces (<2%) and reply-rate trend weekly — the rest of the hygiene list is in the 12-point deliverability checklist.
6. Cold conversations that turn warm can move to your real domain — risk lives in the cold sends, not the replies.