1. Deliverability Is the Product
In B2B email outreach, the best copy in the world is worthless if it lands in spam. Technical infrastructure — authentication, warmup, list hygiene, sending patterns — determines whether your campaign lives or dies before a single prospect reads a word. Treat deliverability as the product and copy as the packaging.
The High-Deliverability Stack:
- Authentication: Valid SPF, DKIM, and DMARC (progressing to p=quarantine) on every sending domain.
- Domain separation: Cold outreach runs on secondary domains; the primary brand domain never touches cold volume.
- Warmup discipline: 14-21 day ramp with engagement simulation before real campaigns begin.
- List hygiene: Every address verified; bounce rates held under 2%.
2. Domain Architecture for Scale
A serious B2B outreach operation runs multiple secondary domains (2-4), each with 2-3 mailboxes, each mailbox capped at 20-30 sends per day. This architecture does two things: it multiplies daily capacity into the hundreds while keeping per-mailbox volume human, and it contains reputation damage — if one mailbox burns, the rest of the operation is untouched.
Choose secondary domains that are clearly affiliated but distinct (getourex.com style variants, never deceptive lookalikes of other brands). Set up Google Workspace or Microsoft 365 mailboxes — not cheap bulk SMTP — because mailbox providers trust their own ecosystem's sending patterns.
3. Authentication Deep Dive: SPF, DKIM, DMARC, BIMI
SPF and DKIM
SPF authorizes your sending servers; DKIM cryptographically signs every message. Both are table stakes — missing either means instant spam-foldering at Gmail and Outlook.
DMARC Policy Progression
Start at p=none with aggregate reporting to a monitored mailbox. Review the reports weekly to confirm only your legitimate senders appear. Once clean, move to p=quarantine. In 2026, bulk senders without enforced DMARC face systematic rejection.
BIMI (Bonus Trust Signal)
Brand Indicators for Message Identification displays your logo in the inbox. It requires enforced DMARC and a verified trademark, but the visual trust lift on open rates makes it worth pursuing for long-term programs.
4. Warmup Protocols That Actually Work
Warmup is not "send a few emails and wait." It is a structured 14-21 day program: start at 5-10 emails daily through a warmup network that opens, replies, marks as important, and rescues messages from spam. Increase volume ~20% every few days. Mix in real human-style replies. Never launch a campaign from a mailbox younger than three weeks, and re-warm any mailbox idle for more than a month.
5. List Building and Verification Systems
Build lists from signal-rich sources: funding announcements, hiring posts, technology installs, conference attendee lists. Then verify every address with a dedicated verification tool before it enters a sequence. The math is unforgiving — a 5% bounce rate on a 10,000-contact list means 500 bounces, enough to crater a mailbox's reputation for weeks.
Segment ruthlessly. Separate campaigns by persona, industry, and trigger signal so messaging stays relevant and engagement rates stay high — engagement is itself a deliverability signal that mailbox providers reward.
6. Sending Patterns That Look Human
Automation platforms make it easy to look like a bot. Counter it: randomize send times across the workday, throttle to natural cadences, vary subject lines across batches, and keep HTML minimal — plain-text-style emails with one link outperform designed templates on both deliverability and reply rates. Rotate sending across mailboxes so no single identity carries suspicious volume.
7. Monitoring, Seed Testing, and Repair
Run weekly seed tests: send to test inboxes across Gmail, Outlook, and Yahoo and check placement. Monitor Google Postmaster Tools and Microsoft SNDS for domain reputation, spam rate, and authentication failures. If placement drops, pause the affected mailbox immediately, diagnose (check blocklists, complaint rates, authentication), fix, re-warm, and only then resume. Never "push through" a deliverability problem — it compounds.
8. Compliance: The Legal Layer
Technical systems mean nothing if the operation is illegal. In the US, CAN-SPAM requires accurate headers, honest subject lines, a physical address, and prompt opt-out honoring. For EU prospects, GDPR requires a legitimate-interest assessment and easy objection. Canada's CASL is stricter still, generally requiring express consent. Build compliance into the system: one-click unsubscribe in every sequence, suppression lists honored globally, and documented legitimate-interest reasoning for B2B prospecting.
9. Google Workspace vs Microsoft 365: Provider Differences
The two major mailbox ecosystems behave differently under cold outreach load. Google Workspace enforces strict daily sending limits (around 2,000/day theoretical, but cold outreach should stay far below) and its spam filtering is aggressive toward new domains — warmup matters more here. Microsoft 365 (Outlook) has lower hard limits but is more sensitive to complaint rates; a single spam-complaint spike can throttle a mailbox for days. Our practice: run both ecosystems in parallel, keep per-mailbox volume conservative on each, and never assume a configuration that works on Google transfers unchanged to Microsoft.
10. Scaling to 10,000+ Sends Per Month Safely
Scaling is a multiplication problem, not an intensification one. To reach 10,000 monthly sends at 25 sends/mailbox/day over 20 working days, you need 20 mailboxes across 7-10 domains. Stagger domain registration (never register ten domains on the same day), warm each mailbox on its own 21-day schedule, and distribute campaigns so no domain carries more than 15% of total volume. Add a dedicated deliverability owner once you pass 5,000 monthly sends — at that scale, monitoring and rapid response are a full-time function.
11. Disaster Recovery: When a Domain Burns
Even good operations lose a domain occasionally. Have a runbook ready: immediately pause all sending from the affected domain, shift its campaigns to healthy standby domains (maintain 20% spare capacity for exactly this), diagnose the cause via Postmaster Tools and seed tests, and either rehabilitate through re-warmup or retire the domain permanently. Never try to "send through" a reputation problem — every additional send deepens the hole.
12. Team Roles for a Serious Outreach Operation
Deliverability at scale is a team sport. The minimum viable team: a deliverability owner monitoring reputation and placement daily, a list builder prospecting and verifying contacts, and a copywriter writing and testing sequences. Above 20,000 monthly sends, add a dedicated data analyst running the testing program and attribution model. The most common failure mode we see is assigning all of this to one generalist — each function requires different skills, and neglecting any one of them silently degrades the whole system.
13. Choosing an Outreach Platform
Evaluate platforms on deliverability tooling first, features second. Must-haves: per-mailbox sending limits and throttling, automatic bounce handling with suppression lists, seed testing or inbox placement reports, and clean integrations with your CRM. Nice-to-haves: AI writing assistance, advanced analytics, multichannel sequences. Avoid platforms that encourage high-volume sending from single mailboxes — their incentives are misaligned with your deliverability.
FAQ
How many emails can one mailbox safely send daily?
20-30 cold emails per day on a fully warmed mailbox. Scale by adding mailboxes and domains, never by overloading one identity.
How long does warmup really take?
14-21 days minimum for a new mailbox, with gradual ramping and engagement simulation. There are no shortcuts that do not eventually cost more.
What bounce rate is acceptable?
Under 2%. Anything above 3% sustained will damage sender reputation — verify lists before sending, always.
Can we do cold outreach from our main domain?
You should not. Cold outreach carries inherent complaint risk; secondary domains isolate that risk away from the domain your customers and transactional email depend on.

