How Cold Email Agencies Should Build Backup Infrastructure Before Disaster Hits
The agencies that handle deliverability crises without losing clients are the ones with backup infrastructure already in place. Here's how to build it.
Every cold email agency that operates at scale will eventually face a deliverability crisis. A domain gets burned, a batch of inboxes gets flagged, or an ESP changes their sending infrastructure and breaks something. How quickly you can recover depends almost entirely on whether you prepared in advance.
The case for pre-built backup infrastructure
Most agencies don't build backup capacity until after they've lost a client campaign. That's the wrong time to learn the lesson. The math is simple:
- A domain that burns and needs a fresh warmup costs you 4–6 weeks of campaign downtime
- A pre-warmed backup domain costs you the monthly account fee, sitting idle until needed
- One client campaign lost to preventable downtime costs far more than months of idle backup infrastructure
How much backup capacity to maintain
The standard guidance for cold email agencies:
- 25–30% backup: If you have 100 active inboxes across clients, maintain 25–30 warmed backup inboxes
- Per-client minimum: Each client's campaign should have at least one backup domain ready
- High-volume clients: Clients with 20+ active inboxes should have 30–40% backup capacity
Use the infrastructure calculator to determine the right numbers for your portfolio size.
Backup infrastructure requirements
Backup inboxes only work as emergency capacity if they're actually ready to deploy immediately. That means:
- Fully warmed: at least 21 days of warmup, ideally 30+
- Auth configured: SPF, DKIM, DMARC all verified and working
- Correctly limited: not currently sending at or near daily limits
- Tested: placement test passing before they're needed
- Documented: you know exactly which backup inbox is designated for which client
Building the backup pool
Option A: Maintain your own warmed domains
Buy extra domains, set them up correctly, warm them, and keep them in a low-volume maintenance state (2–3 sends per day from the warmup tool). This preserves the sending history without using the capacity. Cost: domain + hosting fees + warmup tool sends. Benefit: full control, immediate deployment.
Option B: Pre-warmed infrastructure from providers
Purchase pre-warmed inboxes from providers who maintain warmed infrastructure. This eliminates the warmup wait but has a higher upfront cost per inbox. Benefit: deploy same-day, no warmup management required. Best for agencies that need emergency capacity now or want to offload warmup management.
Option C: Hybrid
Maintain a small pool of your own warmed domains (for minor issues and client-specific replacements) plus a relationship with a pre-warmed provider (for major crises requiring fast deployment). This gives you coverage across the risk spectrum.
Maintaining backup infrastructure without degrading it
The failure mode of option A is letting backup infrastructure go stale. If you warm up backup inboxes and then don't send anything for 2–3 months, the sending history fades and they're effectively cold again. Maintain backup inboxes with:
- 2–3 warmup tool sends per day (keeps the history active)
- Monthly placement test to confirm they're still inbox-placing
- Quarterly rotation: retire the oldest backup inboxes and add fresh ones
Deploying backup infrastructure
When you need to deploy backup capacity:
- Run a placement test on backup inboxes before activating them
- Configure the ESP sequences with the backup inboxes
- Exclude any prospects who already received email from the failed inboxes
- Start at 50% of the backup inbox's daily limit for the first day
- Monitor bounce and placement closely for 48 hours
Agencies that use WarmInboxes for their backup pool get pre-warmed inboxes that can be deployed within hours and don't require ongoing warmup maintenance. This is the most operationally efficient approach for agencies managing large client portfolios where downtime is not acceptable.
Run the checks first
Before replacing anything, run a free inbox placement test. You might find the issue is DNS, not the domain — and save yourself a week of unnecessary work.