The Challenge
Speed Without Compromise. That Was the Brief.
OutboundBin is a cold email agency that runs outreach campaigns at scale for clients. When they needed their largest infrastructure project built — 6,000 email accounts — they came to me on a contractual basis with a challenge that sounds simple but is anything but: build it fast and build it right.
In cold email infrastructure, speed and quality are usually in direct tension. The faster you move, the more corners get cut — DNS records get misconfigured, warm-up gets rushed, workspaces get set up sloppily. And at 6,000 accounts, a single error doesn't cost you one account. It costs you an entire workspace. That's potentially hundreds of accounts burning simultaneously.
The Core Tension
6,000 accounts. One month. Zero compromises on quality.
The deadline was fixed. The quality standard was non-negotiable. Most people would pick one. The challenge was proving you could have both — if your process was tight enough to execute at speed without introducing errors that compound at scale.
This wasn't just a technical challenge. It was a systems challenge. The only way to set up 6,000 accounts in 30 days without quality degradation is to have a setup process so repeatable, so well-documented and so error-resistant that you can execute it at high speed without needing to slow down and double-check every step.
The brief: 6,000 Google Workspace email accounts — fully configured with DNS (SPF, DKIM, DMARC), warmed up in Instantly.ai, 100% health score on every account, delivering 80%+ open rates from the first campaign. Deadline: 30 days.
The Flagship Project
6,000 Accounts — The One That Defined the Engagement
This was the largest and most demanding project in the OutboundBin engagement. Every process, every system and every quality check used across all three projects was first built and refined here. Getting this right wasn't just about one client — it was proof that cold email infrastructure at this scale was achievable without compromising deliverability.
Flagship Project — Completed in 30 Days
6,000Email accounts. 100% health score. Ready to send.
Set up across 1,500 domains and 150 Google Workspace admin accounts — every account individually configured, DNS-verified and warmed up in Instantly.ai before the first campaign email went out.
1,500Domains registered
150Workspace admin accounts
4/domainMailboxes per domain
3M/moSending capacity at full ramp
6,000 Accounts — Instantly.ai Dashboard (Health Score 100%)
The Process
How You Set Up 6,000 Accounts in 30 Days Without Breaking Anything
The only way speed and quality coexist at this scale is through an airtight repeatable process. Not rushing — systematising. Every step was templated, every checkpoint was documented, and every layer was verified before moving to the next. Here's exactly how it was done.
1
Domain Registration — 1,500 Domains via Namecheap
Registered 1,500 domains in bulk via Namecheap — the most efficient registrar for bulk domain management at this scale. All registered as .com for maximum deliverability trust signals. Namecheap's bulk management dashboard made it possible to handle 1,500 domains without switching between individual accounts.
Math: 1,500 domains × 4 email accounts each = 6,000 accounts. Domain naming followed a deliberate convention to keep reply management clean across the full setup.
2
Google Workspace Setup — 150 Admin Accounts
Created 150 Google Workspace admin accounts via a reseller account — saving the client approximately 50% on monthly subscription costs vs direct Google billing. Each admin account was structured to manage exactly 10 domains and 40 mailboxes, keeping the setup uniform and scalable across the entire project.
Structure: 150 admin accounts × 10 domains × 4 mailboxes = 6,000 accounts. Accounts split across multiple sender identities for campaign segmentation and centralised reply management.
3
DNS & Technical Records — Verified Individually
Manually configured SPF, DKIM, DMARC, custom tracking domain and domain redirections for every single domain — all 1,500 of them. Each record was verified individually for correct format and propagation before moving to the next domain. No automation shortcuts on DNS. At this scale, a misconfigured DMARC policy on a shared workspace can blacklist every account in that workspace simultaneously.
Why manual? Automated DNS tools miss edge cases. At 1,500 domains, even a 1% error rate means 15 broken workspaces. Manual verification takes longer but eliminates that risk entirely.
4
Instantly.ai Connection — OAuth for Maximum Stability
Connected all 6,000 accounts via OAuth rather than App Password — more stable connections, significantly less disconnection risk, and no interruptions to warm-up continuity. At 6,000 accounts, even a 2% disconnection rate means 120 accounts losing warm-up progress simultaneously. OAuth eliminates that risk.
Warm-up protocol: 25 max warm-up limit, increasing by 1 per day for a natural ramp. Cold sending started at 5 emails/day per account, increasing by 5 weekly up to 25 by week 5. This patience is what produces a 100% health score.
5
Reply Management — Centralised Master Inboxes
Configured master inbox forwarding so that all 6,000 accounts funnel replies into a manageable number of central inboxes. This allowed OutboundBin's team to manage thousands of daily replies without logging into hundreds of individual accounts — making the operational side of the infrastructure as clean as the technical side.
Capacity Built
What 6,000 Accounts Can Actually Send
Monthly Sending Capacity — 6,000-Account Setup
6,000Email accounts
×25Max emails/day per account
×20Working days per month
3,000,000
Maximum monthly email capacity at full ramp · Delivered 80%+ open rates from first campaigns
6,000Accounts fully configured
100%Health score across all accounts
80%+Open rate from day one
30Days to full completion
Also Completed for OutboundBin
Two Additional Projects — Same Standards, Different Scale
The 6,000-account project was the largest and most complex, but the OutboundBin engagement also included two additional infrastructure projects — each delivered to the same 100% health score standard, using the same systematised process refined during the flagship project.
Project 2
2,000Email accounts — second infrastructure build
500 domains · 50 Workspace admin accounts · 4 mailboxes each. 1M emails/month capacity at full ramp. Largest of the three additional projects — built using the same repeatable process, delivered on time with a 100% health score.
100% Health Score
Project 3
1,000Email accounts — third infrastructure build
250 domains · 25 Workspace admin accounts · 4 mailboxes each. 500K emails/month capacity at full ramp. Built using the same systematised process — completed on schedule with zero DNS errors.
100% Health Score
Project 4
600Email accounts — fourth infrastructure build
150 domains · 15 Workspace admin accounts · 4 mailboxes each. 300K emails/month capacity at full ramp. Delivered in under one week. First campaigns launched immediately with 80%+ open rates from day one.
100% Health Score
2,000 Accounts — Instantly.ai Dashboard (Health Score 100%)
1,000 Accounts — Instantly.ai Dashboard (Health Score 100%)
600 Accounts — Instantly.ai Dashboard (Health Score 100%)
Across all four projects, the total infrastructure delivered for OutboundBin was 9,600 email accounts, covering 2,400 domains across 240 Google Workspace admin accounts — all with a 100% health score and delivering 80%+ open rates immediately on launch.
Key Takeaways
What 6,000 Accounts in 30 Days Actually Teaches You
Speed and quality are not opposites — they're achieved through systematic process. Having a documented, repeatable setup workflow for each layer (domains → workspace → DNS → Instantly → warm-up) is what allowed 6,000 accounts to be configured in 30 days without a single DNS error or failed health check.
Architecture decisions made before you touch a single account determine whether the whole thing is manageable. 150 admin accounts × 10 domains × 4 mailboxes isn't a default — it's a deliberate structural choice. Change that ratio and you change how the entire system performs and how the team can operate it.
Manual DNS verification is non-negotiable at scale. Automated tools miss edge cases. At 1,500 domains, even a 1% error rate equals 15 misconfigured workspaces — potentially 60 broken accounts. Verifying every SPF, DKIM and DMARC record individually takes time, but it's what separates a 100% health score from an 85% one.
OAuth over App Password, always. More stable, less disconnection risk, no warm-up interruptions. At 6,000 accounts, a 2% disconnection rate means 120 accounts losing warm-up progress at once. OAuth eliminates that entire category of problem.
Slow warm-up protects everything else. Starting at 5 emails/day and increasing by 5 per week feels slow when you're staring at 6,000 accounts waiting to fire. But rushing warm-up is how you burn the domains you just spent 30 days configuring. The patience is what produces the 80%+ open rate on day one of campaigns.
A process built for 6,000 accounts scales down effortlessly. The 1,000-account and 600-account projects that followed used the same workflow — just fewer iterations. Once the system is right at large scale, smaller projects become fast and reliable by default.