All Posts
Infrastructure

Cold Email Infrastructure Planning: How to Architect Your Setup Before Day One

SoniSoni
9 min read

Cold Email Infrastructure Planning: Architect Your Stack Before You Build It

Most cold email infrastructure problems aren't caused by using the wrong tools — they're caused by not planning architecture before building. The team buys mailboxes, connects a sequencer, skips the warmup, and wonders why campaigns don't work.

Infrastructure planning takes 90 minutes. Not doing it costs weeks of recovery.


What Cold Email Infrastructure Planning Covers

A proper cold email infrastructure plan answers six questions before you register a single domain:

  1. Scale: How many mailboxes do I need now, in 6 months, and in 12 months?
  2. Isolation: How will I prevent one campaign or client from affecting others?
  3. Provisioning: How will I add new mailboxes and domains efficiently as I scale?
  4. Warmup: How will I warm new mailboxes without delaying campaigns?
  5. Monitoring: How will I detect and respond to deliverability degradation?
  6. Compliance: What legal requirements apply to my sending (CAN-SPAM, GDPR, CASL)?

Answering these upfront determines your tooling choices, cost structure, team ownership, and operating procedures.


Step 1: Capacity Planning

Infrastructure capacity is not just "how many mailboxes today" — it's the growth trajectory you're planning for.

Mailbox calculator:

VariableYour Numbers
Active campaigns per month___
Contacts targeted per campaign___
Emails per contact (sequence length)___
Emails per mailbox per day (max 50)___
Sending days per month___

Formula:

Monthly emails needed = Active campaigns × Contacts × Sequence length
Mailboxes required = Monthly emails ÷ (50 emails/mailbox/day × 22 sending days)

Example calculation:

  • 5 campaigns × 200 contacts × 4-email sequence = 4,000 monthly emails
  • 4,000 ÷ (50 × 22) = 3.6 mailboxes → round up to 5 mailboxes

Agency planning: Calculate per client, then sum across your client portfolio. Add 20% buffer for warmup rotations and pauses.

Plan for your 12-month projection, not your current state. Infrastructure built for 10 mailboxes and then scaled to 100 often has architectural debt (shared DNS accounts, mixed-client workspaces, manual monitoring) that becomes expensive to fix at scale.

30–50 emails/dayper mailbox — the maximum safe cold email volume. Any more and you risk triggering inbox provider volume filters, regardless of how well-warmed the mailbox is.

Step 2: Domain Architecture Planning

Domain planning prevents the most common infrastructure failure: single-domain dependence that turns one incident into an entire campaign shutdown.

Rule: Never more than 3 mailboxes per domain. Never your primary business domain for cold email.

Naming strategy for sending domains:

  • Primary domain: yourcompany.com (transactional + marketing only, never cold)
  • Sending domain variations: getyourcompany.com, yourcompanyhq.com, yourcompanyteam.com, tryyourcompany.com

Agency domain strategy: Each client needs their own domain group — completely separate from other clients' domains. Never share a domain across clients.

Domain rotation planning: After 6–12 months of active sending, domains accumulate reputation history (both positive and negative). Plan for domain rotation: retire high-history domains, introduce fresh domains with proper warmup.

Campaign StageDomains NeededMailboxes per Domain
Single campaign (solo)2–3 sending domains2–3 each
5-client agency15–25 sending domains2–3 each
20-client agency60–100 sending domains2–3 each

Step 3: IP Architecture Planning

IP architecture is the most consequential infrastructure decision you'll make. Insufficient isolation here causes problems that propagate through everything above it.

The isolation decision:

OptionArchitectureUse CaseRisk
Shared IP pool100+ users share IPsLowest costAny neighbor's spam issues affect you
Dedicated serverYour mailboxes share one server's IPsBetter than shared poolInternal incidents affect all mailboxes
Per-mailbox isolation1 dedicated IP per 3 mailboxesFull professional useHighest cost, but lowest risk

Plan for per-mailbox isolation (1 IP per 3 mailboxes) unless you have a compelling cost reason not to. The deliverability premium is 20–30 points of inbox placement — the ROI is overwhelmingly positive.


Step 4: DNS Management Planning

DNS management at scale is a significant operational overhead if not automated.

Manual DNS management costs:

  • 20 minutes per new domain (SPF + DKIM + DMARC entry + verification)
  • Error rate: ~30% (at least one record needs correction on first attempt)
  • At 10 domains/month: ~300 minutes + 90 minutes rework = 6.5 hours/month on DNS alone

Automated DNS planning:

  • Choose a registrar with API access (Cloudflare, Namecheap)
  • Use a managed infrastructure platform that auto-configures DNS, or
  • Build or buy DNS automation scripts if you're a technical team

DNS redundancy planning:

  • Document all DNS configurations in a central system
  • Set up automated monitoring for DNS changes (unauthorized changes can break everything)
  • Configure DNS TTL appropriately (300–3600 seconds for cold email sending domains)

Step 5: Warmup Capacity Planning

Warmup planning aligns your production campaign calendar with your mailbox readiness.

Key constraint: Every new mailbox needs 14–28 days of warmup before production sending. Plan campaign launches around this timeline.

Warmup capacity table:

New mailboxes per monthSimultaneous (bulk) warmup?Time to production readiness
1–10 mailboxesOptional14–28 days (same for all)
10–50 mailboxesRecommended14–28 days if bulk; 6–12 weeks if sequential
50+ mailboxesRequired14–28 days (bulk only)

Agency warmup planning:

  • New client onboarded on Monday
  • All 12 mailboxes in warmup simultaneously by Tuesday
  • Client campaigns start in 2–3 weeks
  • Set client expectations accordingly — don't promise immediate campaign starts
Pro Tip

Create a warmup calendar integrated with your client onboarding calendar. When a new client signs, immediately trigger the domain/mailbox provisioning so warmup begins the same day. By the time contracts are fully signed and kickoff calls happen, warmup may be 50% complete.


Step 6: Monitoring and Response Planning

Monitoring planning means defining what you monitor, how often, who is responsible, and what the response protocol is.

Monitoring inventory:

  • Per-mailbox inbox placement rate (who checks this, how often)
  • Domain-level spam complaint rate via Postmaster Tools (Google) + SNDS (Microsoft)
  • Blacklist monitoring for all sending IPs and domains
  • DNS authentication monitoring (SPF, DKIM, DMARC passing rate)
  • Warmup progress monitoring for all active warmup mailboxes
  • Bounce rate per campaign (sequencer-level)

Response protocol planning: Define in advance what happens when metrics breach thresholds:

Threshold BreachAutomatic ResponseManual Response
Mailbox inbox rate < 50%Auto-suspend mailboxReview cause; replace if needed
Domain spam rate > 0.10%Alert sentPause all sends from domain; investigate
IP blacklistedAlert sentSubmit delisting; migrate mailbox
DNS authentication failureAlert sentFix DNS record; verify within 1 hour
Bounce rate > 5%Alert sentPause campaign; clean list

Step 7: Compliance Planning

Cold email compliance requirements vary by geography and industry. Plan for compliance before sending, not after receiving a cease-and-desist.

CAN-SPAM (US):

  • Physical mailing address in every email
  • Clear identification as commercial email
  • Working unsubscribe mechanism
  • Honor unsubscribes within 10 business days

GDPR (EU recipients or EU companies sending globally):

  • Document lawful basis for processing prospect data
  • Mechanism for data erasure requests
  • DPA (Data Processing Agreement) with your infrastructure provider
  • No sending to EU prospects without documented legitimate interest basis

CASL (Canada):

  • Express or implied consent required
  • Implied consent = existing business relationship within last 24 months
  • Unsubscribe must work within 10 business days
  • Strict penalties (up to $10M CAD per violation)

Industry-specific:

  • Healthcare: Keep PHI out of emails; BAA with providers if any PHI is touched
  • Financial services: FINRA requirements around communication records
  • Education: FERPA considerations for sending to educational institutions

Step 8: Total Cost of Ownership Planning

Document expected costs across all layers before committing to an infrastructure model:

Cost LayerDIY MonthlyManaged Platform Monthly
Mailbox licensing (per 100 mailboxes)$600–$840Included
Domain registration (per 20 domains)$14Included
Warmup service$150–$300Included
Monitoring service$100–$200Included
DNS management time (10 hrs)$500–$1,500~$0 (automated)
VA / support$0–$500Included (dedicated VA)
Infrastructure management time$1,500–$3,000$150–$300
Total$2,864–$6,354$500–$1,500

Key Takeaways

  • Infrastructure planning takes 90 minutes and prevents weeks of recovery from avoidable failures
  • Capacity planning must project 12 months forward, not just current state
  • Domain architecture: 3–5 sending domains per client/campaign; never your primary domain; never more than 3 mailboxes per domain
  • Plan for per-mailbox IP isolation (1:3 ratio) from the start — retrofitting isolation later is expensive
  • Automate DNS management — manual DNS at 20+ domains is a full-time job
  • Bulk warmup planning: new mailboxes should start warmup the same day as onboarding, calendar campaigns 2–3 weeks later
  • Define monitoring thresholds and response protocols before incidents happen — real-time response is too late

For the implementation guide, see How to Set Up a Scalable Cold Email Infrastructure. For compliance specifics, see Cold Email Infrastructure Compliance for US Outreach.

coldBirds is the managed infrastructure platform that executes this entire plan for you: auto-provision, auto-DNS, bulk warmup, 6-hour monitoring, and a dedicated VA who manages the dashboard.

Start Free with 20 Isolated Mailboxes →

The hardest mistakes to fix are the architectural ones. coldBirds' 1:1:1:3 isolation model was designed from the ground up so every mailbox starts with the right architecture.

Start Free with 20 Isolated Mailboxes →
Soni

Soni

Founder, coldBirds

Founder of coldBirds. Building cold email infrastructure that protects deliverability on autopilot.