Email InfrastructureFeatured

    Why We Maintain 3x Sending Capacity for Every Client Campaign

    Most agencies set up exactly the sending capacity they need. Then one domain gets flagged and the entire campaign dies. Here's the infrastructure standard that keeps us in the inbox 99% of the time.

    Cold email infrastructure and deliverability SOP infographic showing 3x sending capacity rules, domain caps, and health monitoring
    October 23, 20257 min read
    Share:
    The short answer

    Maintaining 3x sending capacity means setting up infrastructure to send three times your required monthly volume. For a campaign needing 9,000 emails per month, you build capacity for 27,000. This overcapacity allows aggressive domain rotation when health scores drop below 99%, prevents volume loss during infrastructure maintenance, and enables conservative sending limits of 40 emails per domain per day—ensuring 99% inbox placement without campaign interruptions.

    Key takeaways

    • The standard infrastructure uses 2 inboxes per domain with 20 emails per inbox per day, capping each domain at 40 total emails daily.
    • With 3x capacity, underperforming domains can be immediately replaced when health scores drop below 99% without reducing campaign send volume.
    • Conservative sending limits of 40 emails per domain per day prevent spam flags that make offer testing and optimization impossible.
    • For large TAMs of 20,000-40,000+ contacts, sending from generic domains for three weeks while branded domains warm up delivers immediate results.
    • Domains are recycled every 60 days as standard maintenance practice to sustain long-term deliverability.

    Reviewed and updated October 23, 2025

    Why We Maintain 3x Sending Capacity for Every Client Campaign

    Most agencies treat sending capacity like a math problem.

    "We need to reach 18,000 contacts in 60 days, so we'll set up exactly that capacity."

    Then one domain gets flagged.

    Suddenly they can't send at full volume. Deliverability tanks across the entire campaign.

    We do the opposite.

    We maintain 3x sending capacity for every single client.

    Why this works.

    The Math Behind 3x Capacity

    If a client has 18,000 contacts, we need to send 9,000 emails per month to reach everyone in 60 days.

    Most agencies would set up capacity for exactly 9,000 per month.

    We set up capacity for 27,000 per month instead.

    That feels excessive. Wasteful, even.

    But this overcapacity gives us three massive advantages.

    Advantage 1: Aggressive Domain Rotation

    If any domain drops below 99% health score on our monitoring tools, we replace it immediately.

    Most agencies can't afford to do this.

    They're running at capacity. If they pull a domain, they lose volume. Their campaigns slow down. Prospects get contacted late. Meetings drop.

    We never have this problem.

    With 3x capacity, we can pull underperforming domains without sacrificing send volume. The remaining domains pick up the slack while we swap in fresh ones.

    Advantage 2: Volume Never Suffers

    Even when rotating out underperforming domains, we maintain full send capacity across all campaigns.

    There's no "slow week" while we fix infrastructure issues.

    No explaining to clients why their campaign volume dropped.

    No scrambling to catch up later.

    We built enough buffer that infrastructure maintenance is invisible to campaign performance.

    Advantage 3: Conservative Sending Limits

    We cap at 40 emails per domain per day.

    Most competitors push 60-80+ trying to extract maximum value from each domain.

    They're playing a dangerous game.

    When you push domains that hard, you risk flagging the entire infrastructure. And once you're in spam, you can't evaluate anything else.

    You can't test if your offer works.

    You can't see if your angle resonates.

    You can't optimize your lead magnet.

    You're guessing in the dark.

    The Infrastructure Breakdown

    Exactly how we structure sending capacity:

    Per Domain:

    • 2 inboxes per domain
    • 20 emails per day per inbox
    • 40 total emails per domain per day

    Platform-Specific Limits:

    For Instantly:

    • 8 emails per day per inbox
    • 5 inboxes per domain by default
    • 40 emails per domain per day total

    For ZapMail:

    • 2 inboxes per domain
    • 20 emails per day per inbox
    • 40 emails per domain per day total

    The limits are conservative. But that's the entire point.

    Domain Sourcing Strategy

    We default to ZapMail for domains and inboxes, especially for clients with smaller TAMs.

    For larger TAMs (20k-40k+ contacts), we have an exception:

    We purchase generic domains from Instantly to get quick wins. Send from generic domains for the first three weeks while branded domains warm up. After three weeks, switch to warmed-up branded domains.

    This strategy could eventually apply to all clients since we recycle domains every 60 days anyway.

    For a 20k TAM:

    • Month 1: First 10k contacts via generic domains
    • Month 2: Second 10k contacts via on-brand domains
    • Month 3: Continue with on-brand domains

    It delivers immediate results while improving performance after three weeks.

    Why Infrastructure Comes First

    The agencies that push volume without proper infrastructure end up in spam within weeks.

    Then they blame the offer. The list. The market.

    Meanwhile, we're landing in primary inbox and booking meetings.

    When you're in spam, everything else is irrelevant.

    Your perfect copy doesn't matter if no one sees it.

    Your compelling offer is worthless if it hits the spam folder.

    Your ideal customer profile means nothing if your emails never arrive.

    Infrastructure isn't sexy.

    But it's the difference between a campaign that works and one that dies in spam folders.

    The Real Cost of Poor Infrastructure

    Most founders and agencies don't calculate the full cost of deliverability issues.

    They see the money spent on domains and think they're saving by running leaner.

    But consider what you lose when deliverability drops:

    • Weeks of wasted effort building campaigns
    • Prospect lists that become unusable (you can't re-contact them after landing in spam)
    • Team time spent troubleshooting instead of optimizing
    • Client trust when results disappear
    • The opportunity cost of meetings you never booked

    A domain costs $10. A meeting is worth thousands.

    The math isn't complicated.

    Monitoring and Maintenance

    The 3x capacity model only works if you monitor aggressively.

    We track health scores across all domains daily.

    The moment one drops below 99%, we investigate. If it doesn't recover immediately, we rotate it out.

    Most agencies notice deliverability issues after they've already lost weeks of campaign performance.

    We catch them before they impact results.

    The Standard Going Forward

    This is now our standard for all client campaigns:

    Always maintain 3x sending capacity to ensure deliverability is never an issue and we can rotate domains monthly.

    Cap sends at 40 emails per domain per day at all times.

    No exceptions. No pushing limits to squeeze out extra volume.

    The ROI on conservative sending is undeniable.

    What This Means for Results

    When we tell prospects we maintain 99% inbox placement, they're skeptical.

    Everyone claims high deliverability.

    But most agencies are guessing. They're not monitoring properly. They're pushing domains too hard. They're reacting to problems instead of preventing them.

    The 3x capacity model is expensive upfront.

    But it's the only way to guarantee consistent performance at scale.

    Your campaigns work or they don't. There's no middle ground when you're in spam.

    What's your approach to maintaining deliverability at scale?

    Questions

    Frequently asked questions.

    Frequently asked questions
    Why maintain 3x sending capacity instead of exactly what you need?
    Three times capacity allows you to immediately replace flagged domains without losing send volume, maintain conservative daily limits that protect deliverability, and perform infrastructure maintenance invisibly to clients. When running at exact capacity, pulling even one underperforming domain forces you to slow campaigns, contact prospects late, and lose meetings.
    How many emails should you send per domain per day for cold email?
    Cap at 40 emails per domain per day maximum, structured as 2 inboxes sending 20 emails each. Most competitors push 60-80+ emails per domain to maximize value, but this risks flagging your entire infrastructure. Once you're in spam, you cannot test offers, messaging, or lead magnets because no one sees your emails.
    What is the domain rotation strategy for large contact lists?
    For TAMs of 20,000-40,000+ contacts, send from generic domains during the first three weeks while branded domains warm up. Month one targets the first 10,000 contacts via generic domains, then switch to warmed branded domains for the second 10,000 contacts in month two. This delivers immediate results while improving performance after the three-week mark.
    When should you replace a sending domain in cold email campaigns?
    Replace domains immediately when health scores drop below 99% on monitoring tools. With 3x sending capacity, remaining domains pick up the slack during replacement without affecting campaign volume. Most agencies notice deliverability problems only after losing weeks of performance, but daily monitoring catches issues before they impact results.
    Email DeliverabilityCold EmailInfrastructureB2B SalesEmail Marketing
    Byline

    About the author.

    Tim Carden

    Tim Carden is CMO / CTO at RevenueFlow, which builds and operates outbound revenue engines for B2B companies. Studied at McGill University.

    Tim Carden · CMO / CTO

    Connect on LinkedIn →
    Your next move

    Ready to scale your outreach?

    We build GTM engines that book real meetings. See the receipts.