Why Infrastructure Matters
You can spend weeks perfecting your cold email copy. You can craft the perfect subject line, nail the value proposition, and include a compelling call-to-action. But if your infrastructure is set up wrong, none of it matters because your emails won’t reach the inbox.
Think about it like building a restaurant. You could have the world’s best chef and an incredible menu, but if your kitchen is too small to handle more than ten orders per night, you’ll never scale. Email infrastructure is your kitchen. It determines how much volume you can handle and whether you can maintain quality at scale.
The most common infrastructure failures we see all follow a similar pattern. Someone sets up a single domain, creates one or two email accounts, and starts blasting hundreds of emails per day. Within weeks, their domain reputation is destroyed. Gmail starts sending everything to spam. Their email provider starts flagging suspicious activity. And suddenly, their entire cold email operation grinds to a halt.
Other times, we see operations where one mailbox gets hammered with sends while other accounts sit idle. The overused account gets flagged, which affects the entire domain, and the reputation damage spreads. Or companies try to scale too quickly, adding massive volume before their infrastructure is ready, which triggers spam filters across the board.
The goal of proper infrastructure is simple: support the volume you need while protecting your deliverability. This means spreading your sends across multiple domains and mailboxes, keeping volume per account at safe levels, and building redundancy so one issue doesn’t take down your entire operation.
Understanding the Infrastructure Formula
At its core, email infrastructure is about math. Your daily email capacity equals the number of domains you have, multiplied by the number of mailboxes per domain, multiplied by the safe sending limit per mailbox.
Let’s say you want to send 450 emails per day. You could set up three domains, create three mailboxes on each domain, and send 50 emails from each mailbox. That gives you three times three times fifty, which equals 450 daily emails. The math is straightforward, but the execution requires careful planning.
The reason we keep emails per mailbox at 50 per day is based on years of testing and industry best practices. Send more than that from a single account, and spam filters start to notice. Email providers like Gmail and Outlook track sending patterns, and when a new account suddenly starts pumping out 100 or 200 emails daily, it looks like spam. The algorithms don’t care that you’re doing legitimate outreach. They see behavior that matches spam patterns, and they act accordingly.
Similarly, we recommend keeping total volume per domain under 150 emails per day. Domains share reputation, so if you have multiple mailboxes on one domain all sending aggressively, the entire domain’s reputation suffers. By keeping domain-level volume reasonable, you maintain a healthy sender reputation that protects all the accounts using that domain.
Here’s a practical planning table based on your target volume:
| Target Volume | Domains | Mailboxes | Total Accounts |
|---|---|---|---|
| 100/day | 1 | 2-3 | 2-3 |
| 300/day | 2-3 | 6-9 | 6-9 |
| 500/day | 4-5 | 12-15 | 12-15 |
| 1,000/day | 7-10 | 21-30 | 21-30 |
| 5,000/day | 35-50 | 100+ | 100+ |
Notice how the infrastructure requirements scale non-linearly. To go from 100 to 300 emails per day, you don’t just triple your setup. You need to carefully distribute volume across more infrastructure to maintain deliverability.
Building Your Infrastructure Step by Step
Domain Strategy
Your domain strategy is the foundation of everything. You need to purchase one domain for every 100 to 150 daily emails you plan to send. These domains should be related to your brand but distinct from your primary company domain.
Let’s say your company is Acme Corp and your main website is acmecorp.com. You’ll want to buy additional domains like getacme.com, tryacme.com, acmehq.com, meetacme.com, or hiacme.com. These variations feel legitimate because they’re clearly connected to your brand, but they protect your primary domain from any deliverability issues with cold email.
Purchase these domains from reputable registrars like Namecheap, GoDaddy, or Google Domains. After purchase, let them age for at least two weeks before setting up email. Brand new domains have zero reputation, and email providers are more suspicious of them. A couple weeks of aging won’t solve everything, but it helps establish that the domain has been around for at least a little while.
The timeline from domain purchase to active sending typically looks like this: purchase the domain, wait two weeks for aging, set up DNS records, begin warmup, and then start sending. You’re looking at about six to eight weeks from purchase to full capacity, which is why you need to plan infrastructure expansion well in advance.
Email Hosting Setup
Once your domains are ready, you need to choose an email hosting provider. The two most common options are Google Workspace and Microsoft 365.
Google Workspace is the most popular choice for cold email. It has excellent deliverability reputation because Gmail is such a dominant email provider. Most cold email tools integrate smoothly with Google. The interface is familiar if you’ve used Gmail. The main downside is cost, which runs six to twelve dollars per user per month, and Google can be strict with limits when accounts are brand new.
Microsoft 365 also works well for cold email. It offers good deliverability, strong security features, and is particularly suitable for enterprise companies already using Microsoft tools. The costs are similar to Google, running six to twelve dollars per user per month. However, Microsoft tends to have stricter sending limits, and fewer cold email platforms integrate as smoothly compared to Google.
For very high volume operations sending 5,000 or more emails daily, some companies use dedicated SMTP services like SendGrid, Amazon SES, or Mailgun. These require more technical setup and careful management, but they can handle massive scale. We generally recommend starting with Google Workspace or Microsoft 365 and only moving to dedicated SMTP if you absolutely need it.
Setting up email hosting involves adding your domain to the platform, verifying domain ownership, configuring MX records so email routes correctly, creating user accounts, and setting up authentication. Most email providers have step-by-step guides for this process.
Mailbox Structure
For each domain, you’ll create two to five email accounts. These should use real first names like john@getyourcompany.com, sarah@getyourcompany.com, and mike@getyourcompany.com. Avoid generic addresses like info, sales, or admin, which look less personal and often have worse deliverability.
Vary the names across domains. If you use John on one domain, use different names on your other domains. This makes your infrastructure look more natural and distributed.
Complete the profiles for each account. Add profile photos of real people (you can use stock photos or AI-generated faces, but make them look professional). Create email signatures with names, titles, and contact information. The more these accounts look like real people actually using them, the better.
Authentication Setup
Every domain needs three key authentication records: SPF, DKIM, and DMARC. These tell receiving email servers that your emails are legitimate and authorized.
SPF (Sender Policy Framework) specifies which mail servers are allowed to send email from your domain. For Google Workspace, your SPF record will include Google’s mail servers. For Microsoft 365, it will include Microsoft’s servers.
DKIM (DomainKeys Identified Mail) adds a digital signature to your emails that proves they actually came from your domain and weren’t modified in transit. Your email provider generates a DKIM key, and you add it to your DNS records.
DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receiving servers what to do if an email fails SPF or DKIM checks. It also provides reporting so you can monitor authentication issues.
Setting up these records involves logging into your domain registrar or DNS provider, adding the records your email hosting provider gives you, and then verifying everything is configured correctly using a tool like MXToolbox. Every domain needs all three records properly configured before you start sending.
Warmup Process
Every single mailbox needs to go through a warmup period. Warmup involves gradually increasing sending volume while maintaining positive engagement signals. This builds reputation with email providers so your cold emails land in the inbox instead of spam.
The warmup schedule typically runs about four weeks. In week one, you send ten to twenty warmup emails per day and zero cold emails. These warmup emails are automated exchanges with other accounts in a warmup network, where emails are opened, marked as important, and replied to. This creates positive engagement signals.
In week two, you increase warmup volume to twenty to thirty emails per day, still with no cold sending. Week three bumps warmup to thirty to forty per day while you can start sending ten to twenty cold emails. By week four and beyond, you maintain thirty to forty warmup emails daily while sending your full cold email volume of thirty to fifty per day.
Tools like Instantly, Lemwarm, and Warmbox handle this process automatically. They connect accounts in a warmup network where everyone’s accounts exchange positive engagement signals. The costs typically run thirty to fifty dollars per inbox per month during the initial warmup phase, though some platforms include warmup in their base pricing.
Never skip warmup. We’ve seen companies burn through thousands of dollars in infrastructure by rushing new accounts into full volume. The email providers notice, and once an account is flagged as spam, it’s extremely difficult to recover.
Connecting to Your Sending Platform
Once your mailboxes are warmed up, you connect them to your cold email platform. Popular options include Instantly, Lemlist, Apollo, and Smartlead, with pricing typically ranging from thirty-seven to ninety-nine dollars per month.
When connecting accounts, you set sending limits at the account level. Configure each account for a maximum of fifty emails per day. Set up rotation so sends distribute evenly across all accounts. Configure timing to send only during business hours, with delays between emails to mimic human sending patterns.
Most platforms offer test sends that show where your emails land: inbox, spam, or promotional tabs. Run these tests before launching campaigns to verify your infrastructure is working correctly.
Email Rotation Strategies
Rotation is critical for distributing volume and protecting deliverability. Without rotation, you end up with uneven usage where some accounts hit limits while others sit idle. The overused accounts burn out while the idle accounts represent wasted capacity.
The most common rotation strategy is round-robin, where emails cycle through accounts sequentially. Email one goes to account A, email two to account B, email three to account C, email four back to account A, and so on. This ensures perfectly even distribution.
Random rotation assigns each email to a random available account. This works well and looks more natural than strict round-robin, though distribution may be slightly less even over small sample sizes.
Weighted rotation assigns different percentages to different accounts based on their reputation strength. Maybe account A with the strongest reputation gets forty percent of sends, account B with medium reputation gets thirty-five percent, and newer account C gets twenty-five percent. As newer accounts build reputation, you can rebalance the weights.
Most cold email platforms handle rotation automatically. You just need to configure maximum emails per account per day, set delays between sends (typically thirty to sixty seconds), restrict sending to business hours, and enable account health checks that pause accounts showing issues.
Monitoring Your Infrastructure
Daily monitoring should check that warmup is running on all accounts, no accounts are showing errors or blocks, and sends are distributed evenly across accounts. These quick checks catch issues before they become major problems.
Weekly checks include reviewing Google Postmaster reputation scores for each domain, running blacklist checks on all domains and IP addresses, monitoring bounce rates per account (which should stay below two percent), and assessing overall deliverability metrics.
Monthly reviews analyze cost per email, compare capacity versus actual usage to identify expansion needs, evaluate account health across your entire infrastructure, and identify optimization opportunities.
Warning signs requiring immediate attention include account suspensions, blacklist listings, sudden bounce rate spikes, or reputation score drops. Investigate immediately if you notice open rates declining, reply rates dropping, uneven account usage, or warmup issues.
Scaling Your Infrastructure
You know it’s time to add capacity when accounts regularly hit eighty percent or more of their sending limits, you need to increase volume for business reasons, or accounts are showing strain with declining open rates.
The scaling process starts with purchasing a new domain. Wait two weeks for the domain to age. Set up email hosting and configure authentication. Create mailboxes and begin warmup, which takes at least three weeks. Only then can you add the new accounts to your rotation and gradually increase volume.
This means you need five to six weeks from deciding to scale until new infrastructure is at full capacity. Plan expansions well in advance based on your growth projections.
Infrastructure costs scale with volume, but cost per email decreases as you grow:
| Scale | Monthly Cost | Per Email |
|---|---|---|
| 1,000/mo | $100-150 | $0.10-0.15 |
| 5,000/mo | $300-500 | $0.06-0.10 |
| 20,000/mo | $800-1,200 | $0.04-0.06 |
| 50,000+/mo | $2,000+ | $0.03-0.04 |
Fixed costs like sending platform subscriptions get spread across more emails, while variable costs like email hosting scale proportionally. The result is improving unit economics as you grow.
Common Infrastructure Mistakes
The biggest mistake is single point of failure infrastructure: one domain with one or two accounts. When something goes wrong, and eventually something will, your entire operation stops. Always build redundancy with multiple domains and multiple accounts per domain.
Maxing out limits is another common error. Running accounts at their absolute maximum triggers spam filters and degrades deliverability. Operate at eighty percent of capacity maximum and maintain buffer capacity for safety.
Skipping warmup is tempting because it feels like you can get to results faster. But new accounts that immediately jump to full volume get flagged as spam almost immediately. The few weeks you save on warmup costs you months of burned infrastructure and damaged reputation.
Not monitoring infrastructure means issues go unnoticed for days or weeks, causing massive reputation damage. Set up daily checks and alerts so you catch problems immediately.
Poor rotation where one account handles most sends creates uneven reputation and leads to burned accounts. Use automated rotation with balanced distribution to spread volume evenly.
Key Takeaways
Proper email infrastructure is the foundation that enables cold email at scale. Without it, even the best messaging and targeting won’t deliver results because your emails won’t reach the inbox.
Use one domain per 100 to 150 daily emails maximum to distribute risk and maintain healthy domain reputation. Create two to three mailboxes per domain, with each mailbox sending a maximum of fifty emails per day. Rotate sends across all mailboxes automatically to balance load and protect deliverability.
Warm up every new domain and mailbox before sending cold email. This gradual ramping builds reputation with email providers and prevents immediate spam flagging. Budget fifty to one hundred fifty dollars per 1,000 monthly emails for domains, hosting, warmup, and sending platforms. While infrastructure costs money, it’s essential for sustainable cold email.
Infrastructure isn’t the glamorous part of cold email. It doesn’t involve clever copywriting or creative targeting strategies. But it’s absolutely foundational. Companies that invest in proper infrastructure see consistent deliverability, sustainable scaling, and long-term success. Companies that skip infrastructure end up burning through domains and wondering why their campaigns don’t work.
Need Infrastructure Help?
We’ve built and managed cold email infrastructure for clients sending more than 100,000 emails monthly with consistently strong deliverability. We understand the nuances of domain selection, the timing of warmup schedules, the configuration of rotation strategies, and the monitoring needed to catch issues early.
If you need help setting up your infrastructure from scratch or scaling your existing operation, we’d love to talk. Book a call with our team to discuss your specific situation and get a custom infrastructure plan.