A sales team we work with at Beanstalk spent three months writing and rewriting cold email copy. They A/B tested subject lines, personalized every opener, even hired a copywriter. Reply rate sat at 0.4%.
Turns out 60% of their emails were landing in spam. They were sending from their primary domain, had no DKIM record, and skipped warmup entirely.
We fixed their infrastructure in a week. Same copy, same list. Reply rate jumped to 3.2%.
What Is Cold Email Infrastructure?
Cold email infrastructure is everything that sits between you clicking "send" and your email actually hitting someone's inbox. It's the technical foundation your outbound runs on.
The full stack:
- Secondary domains: Dedicated domains you send cold email from, separate from your primary company domain
- Mailboxes: Email accounts on those domains (Google Workspace, Microsoft 365, or SMTP)
- DNS authentication: SPF, DKIM, and DMARC records that prove your emails are legitimate
- Email warmup: The process of gradually building sender reputation before you start cold outreach
- Sending tool (sequencer): The platform that connects to your mailboxes and sends your campaigns
Miss any one of these, and your deliverability suffers. Get them all right, and you've got a foundation that can scale to thousands of emails per day without burning domains.
Why Infrastructure Matters More Than Copy
Here's the thing most people get backwards. They spend weeks perfecting their email copy and 20 minutes on infrastructure setup.
The best cold email ever written still lands in spam if the infrastructure behind it is broken.
According to Validity's 2025 benchmark report, the global average inbox placement rate sits around 84%. Roughly one in six emails never gets seen. For cold outreach, where you have zero prior relationship with the recipient, that number gets much worse if your infrastructure isn't dialed in.
Domains without proper SPF, DKIM, and DMARC records see 52% lower inbox placement. Accounts that skip warmup land in the inbox 61% of the time compared to 94% for properly warmed accounts.
Infrastructure is the multiplier. Your copy, your targeting, your offer. None of it gets through if Gmail and Outlook are routing you straight to spam.
The 5 Components of Cold Email Infrastructure
1. Secondary Domains
Non-negotiable: never send cold email from your primary company domain.
If your company is acme.com, you buy secondary domains like getacme.com, tryacme.com, or acmehq.com. Close enough to look legitimate to recipients. Separate enough to keep your main domain insulated.
When you're sending cold email at volume, spam complaints are always a risk. If those complaints hit your primary domain, you torpedo deliverability for your entire company. Marketing emails, transactional emails, client communication. One bad week of cold outreach could mean your invoices start landing in spam.
Buy your secondary domains from a registrar like Porkbun, Namecheap, or GoDaddy. Plan for 2-3 mailboxes per domain to start, and keep each domain's total daily volume low.
How many domains do you need? Depends on your target daily volume. A good rule of thumb: plan for 30-50 cold emails per domain per day across all mailboxes on that domain. If you want to send 500 cold emails per day, you need roughly 10-15 domains.
2. Mailbox Providers
Three main options for the actual email accounts on your secondary domains:
Google Workspace
- Best inbox placement for Gmail recipients
- Familiar interface for most sales teams
- Safe cold sending limit: 15-25 emails per inbox per day in 2026
- Higher cost at scale ($7.20/user/month)
Microsoft 365
- Strong for reaching Outlook/Microsoft recipients
- Higher technical sending limit (10,000/day) but safe cold limit is still 30-50/day
- Good option if your target market is enterprise (most run Outlook)
- Slightly cheaper than Google at scale
SMTP / Custom Servers
- Highest volume potential
- Full control over IP reputation
- Requires more technical expertise
- Best for teams sending 5,000+ emails per day who need dedicated IPs
Most teams start with a mix of Google Workspace and Microsoft 365. The split gives you coverage across both ecosystems. Some operators swear by matching provider to recipient (Google to Google, Microsoft to Microsoft), but we've actually seen that backfire. It gives ESPs visibility into both the sending and receiving side, which makes fingerprinting easier.
3. DNS Authentication
DNS authentication is the set of records that tell receiving email servers "yes, this email actually came from who it says it came from." In 2026, Gmail, Yahoo, and Microsoft all require these for bulk senders. Three records matter:
SPF (Sender Policy Framework)
SPF tells receiving servers which mail servers are authorized to send email on behalf of your domain. It's a TXT record in your domain's DNS that lists approved sending IPs.
Example: v=spf1 include:_spf.google.com ~all
DKIM (DomainKeys Identified Mail)
DKIM adds a digital signature to your emails that proves they haven't been tampered with in transit. Your email provider generates a public/private key pair. The private key signs outgoing messages, and the public key (published in DNS) lets recipients verify the signature.
DMARC (Domain-based Message Authentication, Reporting & Conformance)
DMARC ties SPF and DKIM together and tells receiving servers what to do when authentication fails. It also sends you reports on authentication results.
Start with: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
The p=none policy means "monitor but don't reject." Useful when you're first setting up. Once you've confirmed everything is working, move to p=quarantine or p=reject.
The setup process: Log into your domain registrar, go to DNS settings, and add these three TXT records. Google Workspace and Microsoft 365 both provide the exact records you need during setup. If you're using a Gmail generator approach, your DNS still needs to be configured correctly on each domain.
4. Email Warmup
A brand-new mailbox has zero sender reputation. If you start blasting 50 cold emails from it on day one, inbox providers flag it immediately.
Warmup is the process of gradually building that reputation by sending and receiving emails that mimic real human conversation. Warmup tools connect your mailbox to a network of other mailboxes and exchange emails that get opened, replied to, and pulled out of spam. All signals that tell Gmail and Microsoft "this is a real person sending real emails."
How long does warmup take? Two to three weeks minimum before you start any cold sending. Four weeks if you want to be safe.
What does a warmup schedule look like?
- Week 1: 5-10 warmup emails per day
- Week 2: 15-25 warmup emails per day
- Week 3: 30-40 warmup emails per day, start light cold outreach (5-10 per day)
- Week 4+: Maintain warmup at 2:1 ratio (twice as many warmup emails as cold emails)
That 2:1 warmup-to-cold ratio matters more now than it used to. ESPs are tracking whether recipients engage meaningfully with your emails. Replies, forwards, saves. Warmup generates high-engagement signals that cover for the naturally lower engagement of cold sends.
Warmup tools vs managed services: Tools like Instantly, Mailreach, and Mailivery handle warmup automatically. Managed infrastructure services include warmup as part of the package so you don't have to think about it.
5. Sending Tool / Sequencer
The sequencer is where you actually build and launch campaigns. It connects to your mailboxes (usually via IMAP/SMTP or OAuth), schedules your sends, manages follow-up sequences, and tracks replies.
Popular sequencers in 2026 include Instantly, Smartlead, EmailBison, and Plus. These are the orchestration layer that sits on top of your infrastructure. They're separate from infrastructure itself.
Your sequencer doesn't provide mailboxes or domains. It uses the ones you bring. Think of the sequencer as the driver, and your infrastructure (domains, mailboxes, DNS, warmup) as the car. You need both, but you need the car first.
When choosing a sequencer, look for inbox rotation (spreads sends across mailboxes automatically), warmup integration, and campaign analytics that show you inbox placement, not open rates.
How to Set Up Cold Email Infrastructure From Scratch
Here's the step-by-step if you're starting from zero:
Step 1: Buy secondary domains (Day 1)
Purchase 3-5 domains that are variations of your brand name. Use .com, .co, .io, or .net extensions. Avoid cheap TLDs like .xyz or .info. They carry spam stigma.
Step 2: Set up mailboxes (Day 1-2)
Create 2-3 email accounts per domain on Google Workspace or Microsoft 365. Use real-sounding names (sarah@, mike@, james@). Skip noreply@ or sales@.
Step 3: Configure DNS (Day 2)
Add SPF, DKIM, and DMARC records for every domain. Verify them using a tool like MXToolbox or the built-in diagnostics in your email provider's admin console.
Step 4: Start warmup (Day 2)
Connect all mailboxes to a warmup tool. Let them run for at least 14 days before sending any cold email.
Step 5: Connect to your sequencer (Day 14+)
Once warmup metrics look healthy (90%+ inbox placement), connect your mailboxes to your sequencer. Start with 5-10 cold emails per inbox per day and ramp up slowly.
Step 6: Monitor and adjust (Ongoing)
Watch your deliverability metrics. Bounce rate should stay under 2%. Spam complaints under 0.3%. If inbox placement drops below 90%, pause cold sending and let warmup rebuild reputation.
Total timeline from purchase to first campaign: roughly 3 weeks. Faster if you've done it before. Slower if you're finding email addresses and building lists at the same time.
Common Infrastructure Mistakes That Kill Deliverability
After managing infrastructure for thousands of inboxes, these are the mistakes we see over and over:
Sending from your primary domain. We covered this, but it still happens constantly. One burned primary domain can take months to recover. Sometimes it doesn't recover at all.
Skipping warmup. The data is clear: 61% inbox placement without warmup vs 94% with it. There is no shortcut here.
Too many emails per inbox. The days of blasting 50-100 cold emails from a single mailbox are done. In 2026, 10-20 cold emails per inbox per day is the sweet spot. Push past that and you're asking for trouble.
Wrong or missing DNS records. 77% of deliverability issues stem from bad domain health. If your SPF record has a typo or your DKIM isn't aligned, nothing else you do matters. Check your records twice.
Too many mailboxes per domain. Stacking 5+ mailboxes on a single domain increases your blast radius. When that domain gets flagged, you lose all of them at once. Spread your risk across more domains with fewer mailboxes each.
No monitoring. Infrastructure isn't set-and-forget. Domains degrade. Warmup pools go stale. Email providers change their algorithms. If you're not checking deliverability weekly, you're flying blind.
ESP matching (Google-to-Google sending). Some people think matching your sending provider to the recipient's provider helps deliverability. It can actually backfire. The ESP has visibility into both sides of the conversation, making it easier to identify and fingerprint cold campaigns.
DIY vs Managed Infrastructure
You have two paths for building cold email infrastructure:
DIY Setup
| Item | Cost | Time |
|---|---|---|
| Domains (5) | ~$50-75/year | 30 min |
| Google Workspace (10 mailboxes) | ~$72/month | 2-3 hours |
| DNS configuration | Free | 1-2 hours |
| Warmup tool | $30-50/month | 30 min setup, ongoing monitoring |
| Sequencer | $50-200/month | 1-2 hours |
| Total | ~$150-320/month + time | 6-10 hours setup + weekly maintenance |
DIY works if you have the technical knowledge and time. The real cost is the hours spent buying domains, configuring DNS records, monitoring warmup, troubleshooting deliverability issues, and replacing burned inboxes. For a team running 10-20 inboxes, that's manageable. At 50+, it becomes a part-time job.
Managed Infrastructure
Managed providers handle the entire stack: domain acquisition, mailbox provisioning, DNS configuration, warmup, and ongoing monitoring. You get inboxes that are ready to connect to your sequencer.
| Item | Cost | Time |
|---|---|---|
| Managed mailboxes (10) | Varies by provider | Minutes to order |
| DNS configuration | Included | Done for you |
| Warmup | Included | Done for you |
| Monitoring | Included | Done for you |
| Total | Provider-dependent | Near-zero setup time |
The trade-off is straightforward: managed costs more per mailbox but saves significant time, especially at scale. Teams running 50+ inboxes almost always end up going managed because the operational overhead of DIY becomes untenable.
At ScaledMail, we provision pre-warmed mailboxes with DNS fully configured. Google, Microsoft, and SMTP types. You can see the pricing breakdown here. Regardless of which provider you choose, the question is the same: is your time better spent configuring SPF records, or writing campaigns and closing deals?
Book a Call
How to Scale From 100 to 10,000 Emails Per Day
Scaling cold email is an infrastructure math problem. Here's the playbook at each level:
100-500 emails/day (Getting Started)
- 3-5 secondary domains
- 2-3 mailboxes per domain (6-15 total)
- 10-20 cold emails per inbox per day
- One sequencer, basic warmup tool
- Time investment: a few hours per week monitoring
500-2,000 emails/day (Growth Stage)
- 10-20 secondary domains
- 2-3 mailboxes per domain (20-60 total)
- Mix of Google Workspace and Microsoft 365
- Dedicated warmup monitoring
- Start rotating domains. Retire any showing deliverability dips.
- Time investment: significant. Consider managed infrastructure.
2,000-5,000 emails/day (Scale Stage)
- 40-100+ domains
- 80-200+ mailboxes
- Consider adding SMTP/dedicated IP for a portion of volume
- Domain health monitoring becomes critical. Check weekly.
- Need a system for replacing burned domains and mailboxes
- DIY is barely feasible here. Managed infrastructure pays for itself in time saved.
5,000-10,000 emails/day (Volume Operations)
- 100-200+ domains
- 200-500+ mailboxes
- Mixed provider strategy (Google + Microsoft + SMTP)
- Automated domain rotation and replacement
- Dedicated person or team managing infrastructure
- At this level, you're either using a managed provider or you've built a dedicated ops function
The math is simple. If you're sending 10-20 cold emails per inbox per day (the safe range in 2026), you need 500-1,000 inboxes to hit 10,000 emails/day. Those inboxes sit across 200-300+ domains, each needing DNS configured, warmup running, and regular monitoring.
At scale, the DIY vs managed question answers itself. The cost of managed infrastructure is a fraction of the cost of hiring someone to manage all of it manually.
Frequently Asked Questions
How much does cold email infrastructure cost?
DIY infrastructure for a small setup (5 domains, 10-15 mailboxes) runs $150-320/month including domains, email hosting, warmup tools, and a sequencer. Managed infrastructure costs more per mailbox but eliminates setup time and ongoing maintenance. At scale (50+ mailboxes), managed providers often cost less per-email than DIY when you factor in the labor.
How long does it take to set up cold email infrastructure?
DIY setup takes 6-10 hours for initial configuration, plus 2-3 weeks of warmup before you can send your first campaign. Managed providers can have you sending within days, since they maintain pre-warmed mailbox inventories.
Can I use my regular email for cold outreach?
You can, but you shouldn't. Sending cold email from your primary domain puts your entire email reputation at risk. If your domain gets flagged for spam, your marketing emails, client emails, and transactional emails all suffer. Always use secondary domains for cold outreach.
How many cold emails can I send per mailbox per day?
In 2026, the safe range is 10-20 cold emails per inbox per day for Google Workspace and Microsoft 365. Some operators push to 30-50, but data from millions of emails shows that accounts exceeding 150/day see 43% higher spam rates. Conservative volume with more inboxes beats aggressive volume with fewer inboxes.
Do I need both Google Workspace and Microsoft 365?
Not necessarily, but using both gives you better coverage. Google Workspace tends to deliver better to Gmail inboxes, and Microsoft 365 has advantages for Outlook recipients. A mixed approach also diversifies your risk. If one provider tightens enforcement, you're not fully exposed.
What's the difference between a sequencer and cold email infrastructure?
Infrastructure is the foundation: domains, mailboxes, DNS records, and warmup. A sequencer is the software that connects to that infrastructure to send and manage campaigns. You need infrastructure before you need a sequencer. Think of infrastructure as the car and the sequencer as the driver.
