Published May 28, 2026 — 14 min read
Bottom line: Most people think scaling cold email means buying more sending accounts. That works until it doesn't. When you go from 500 to 5,000 emails a day, the infrastructure that worked at low volume breaks. I have rebuilt my sending setup three times in four years. Here is what I learned about building infrastructure that scales without destroying your sender reputation.
In late 2023, I had a campaign that was performing well. Open rates around 35%, reply rates averaging 8%. I was sending about 200 emails a day from two domains and two inboxes. The numbers looked good, so I decided to scale up.
My thinking was simple: more emails equals more replies equals more customers. I increased volume from 200 to 1,000 per day on the same two domains. I did not add new inboxes. I did not adjust warmup. I just cranked the dial.
Within four days, both domains were blacklisted by Microsoft. Gmail followed a week later. Open rates cratered to 2%. I had to trash six sending domains that had been building reputation for months and start over from zero. The campaign that was working perfectly at 200/day was completely dead at 1,000/day because the infrastructure was not designed for that volume.
That is the core problem with scaling cold email. It is not a linear problem. You cannot just multiply your volume by 5 and expect the same deliverability. The infrastructure has to be rebuilt at each scale threshold.
From my experience and conversations with other operators, cold email infrastructure breaks down at three volume thresholds:
| Scale Level | Daily Volume | Infrastructure | Typical Monthly Cost |
|---|---|---|---|
| Starter | 50-300 | 1-2 domains, 2-3 inboxes, Google Workspace | $50-100 |
| Growth | 300-2,000 | 5-10 domains, 3 inboxes per domain, dedicated warmup | $200-500 |
| Scale | 2,000-10,000+ | 15+ domains, 3-5 inboxes/domain, dedicated IPs, custom tracking | $800-2,000+ |
Note: These numbers are for campaigns targeting B2B prospects using individual email addresses. Sending to role-based or catch-all addresses will result in higher bounce rates and lower thresholds.
Every cold email operator knows they need sending domains. But most treat domains as interchangeable and disposable. That is a mistake. Domain setup determines your deliverability before you send a single email.
The rule of thumb I use: no more than 30-40 emails per day per inbox, and no more than 100-150 per day per domain. Here is why:
For scaling, plan your domains like this:
Do not buy domains like send-mail-1.com, send-mail-2.com. Email providers can detect these patterns. Instead, buy domains that look like they could belong to real businesses:
At the Growth and Scale levels, you cannot manually manage inboxes. You need a sending tool that handles rotation automatically. But the tool is only as good as the rotation logic.
Here is how I calculate inbox requirements:
Daily volume target / (emails per inbox per day) = inboxes needed
Inboxes needed / inboxes per domain = domains needed
Example: 5,000 / 35 = 143 inboxes / 4 inboxes per domain = 36 domains
Key rotation rules I follow:
Every new domain and inbox needs warmup. No exceptions. I have seen people register a domain on Monday, set up DNS on Tuesday, and start sending 100 cold emails on Wednesday. That domain is dead within a week.
I use a 4-week ramp for every new domain:
| Week | Daily Volume/Inbox | Daily Volume/Domain | Activity |
|---|---|---|---|
| 1 | 5-10 | 15-30 | Warmup tool only. No cold emails yet. |
| 2 | 10-20 | 30-60 | Warmup + start sending 5-10 real cold emails/day |
| 3 | 20-30 | 60-90 | 50% warmup, 50% real emails |
| 4 | 30-40 | 90-120 | Full cold email volume, minimal warmup |
Tools I have used for warmup: Warmbox, Mailwarm, and Instantly's built-in warmup feature. All three work. The tool matters less than the discipline of sticking to the schedule. Skip a week and you set yourself back two weeks.
This is the most tedious part of scaling infrastructure, and the part most people skip or do wrong. Every single domain needs proper DNS records. If even one domain in your rotation has misconfigured authentication, it can contaminate the reputation of your entire sending pool.
SPF tells receiving servers which IPs are allowed to send email from your domain. For Google Workspace, the record is straightforward:
If you are using a dedicated sending service like SendGrid for some domains, add their include as well:
DKIM adds a cryptographic signature to every outgoing email. Receiving servers check this signature against your public key published in DNS. If they match, the email is authenticated. Google Workspace generates the DKIM key; you add it as a TXT record. Most ESPs have a one-click DKIM setup now, but you still need to verify it is active for every domain.
DMARC ties SPF and DKIM together and tells receiving servers what to do when authentication fails. For cold email domains, start with a monitoring-only policy before moving to enforcement:
After 2-4 weeks of monitoring and confirming no legitimate authentication failures, switch to quarantine or reject:
This is a common oversight. Most cold email tools track opens and clicks by embedding their own tracking domain in your emails. When 40 different domains all use the same tracking domain, it creates a pattern that spam filters recognize. Set up a custom tracking domain for each sending domain, or at minimum, use 3-4 different tracking domains across your pool.
At scale, you cannot manually check if your emails are landing in inbox. You need automated monitoring. Here is what I track across every domain and inbox:
| Metric | Healthy Range | Warning | Critical |
|---|---|---|---|
| Bounce rate | < 3% | 3-7% | > 7% |
| Spam complaint rate | < 0.1% | 0.1-0.3% | > 0.3% |
| Open rate (per campaign) | > 25% | 15-25% | < 15% |
| Inbox placement rate | > 85% | 70-85% | < 70% |
| Blacklist status | Clean | Listed on 1-2 minor lists | Listed on Spamhaus/Barracuda |
Tools I use for monitoring: GlockApps for inbox placement testing, MXToolbox for blacklist checks, and Google Postmaster Tools for domain-level reputation data. For domains on Google Workspace, Postmaster Tools is free and gives you the actual spam rate Google is calculating, not estimates.
At scale, domains will get burned. It is not a question of if, but when. Your infrastructure should be built to absorb domain losses without interrupting campaigns. Here is my recovery protocol:
Here is a realistic cost estimate for running cold email infrastructure at scale, based on what I actually spend:
| Item | Growth (2,000/day) | Scale (5,000/day) | Notes |
|---|---|---|---|
| Domains | 15 x $12/yr = $180/yr | 40 x $12/yr = $480/yr | Buy in batches, look for promos |
| Inboxes (Google Workspace) | 45 x $6/mo = $270/mo | 120 x $6/mo = $720/mo | Use Business Starter plan |
| Sending tool | $100-200/mo | $300-600/mo | Instantly/Smartlead scale pricing |
| Verification tool | $50-100/mo | $150-300/mo | Bulk verification pricing |
| Warmup tool | $50-100/mo | $100-200/mo | Warmbox/Mailwarm |
| Total monthly | ~$500-700/mo | ~$1,300-1,900/mo | Does not include list costs |
The domain and inbox costs are the base layer. You pay these whether you send 10 emails or 10,000. The sending tool and verification tool costs scale with volume. The key insight: infrastructure cost per email drops significantly as you scale. At 2,000 emails/day, you are paying roughly $0.01 per email in infrastructure. At 5,000/day, that drops to about $0.008 per email.
I will keep this section short because these are the mistakes that cost real money:
After four years of running cold email campaigns at various volumes, I can tell you this: infrastructure is the easy part. You can buy domains and set up inboxes. The hard part at scale is list quality.
When you are sending 200 emails a day, a 5% bounce rate is annoying but survivable. When you are sending 10,000 emails a day, a 5% bounce rate means 500 hard bounces hitting your sender reputation every single day. No amount of infrastructure can compensate for bad data.
The infrastructure setup I described works because it assumes you are sending to verified, targeted contacts. If your list has a 15% bounce rate, none of this matters. Your domains will burn regardless of how many inboxes you rotate through. Infrastructure scales deliverability. It does not fix bad targeting.
Need verified contacts to fuel your scaled infrastructure? B2BRepurpose provides SMTP-verified Shopify store owner email lists at $29 per 1,000 contacts. Every email is verified within 30 days of delivery, keeping your bounce rate under 3%. See available lists and pricing here.