How many domains and inboxes do you need for cold email? For most teams the honest answer is smaller than the internet suggests: 2 to 3 inboxes per secondary domain, 20 to 50 sends per inbox per day, and roughly one new domain for every 120 daily sends you want to add. This guide walks through the consensus math, flags where published advice disagrees, prices the whole stack, and shows how the requirement scales tier by tier without ever touching your company’s real domain.
These numbers are cross-checked against the infrastructure vendors who answer this question for a living, but they also match what we run ourselves. Our parent agency, Referral Program Pros, has booked more than 7,000 meetings across 4,000+ outbound campaigns, and the most common infrastructure mistake in all that campaign data was not too little capacity but too much concentration: a dozen inboxes piled onto one domain, all burned together by a single bad campaign. GTM Bud is built on that agency’s playbook, and the domain architecture below is the one it provisions by default.
How many domains and inboxes do you need for cold email?
Most teams need 1 secondary domain and 2 to 3 inboxes to start, and roughly 1 domain per 100 to 120 daily sends once they scale. The math rests on three consensus numbers: a warmed inbox safely sends 20 to 50 cold emails per day, a domain carries 2 to 3 inboxes, and every sending domain is a lookalike secondary domain rather than your main company domain. Work backwards from volume: 150 sends per day needs 4 inboxes on 2 domains, 500 per day needs 13 inboxes on 5 domains, and 1,000 per day needs 25 inboxes on 9 domains. Those ratios match what the vendors who answer this question for a living publish, including Scaledmail, Litemail, and Vendisys, which all put the ceiling at 2 to 3 inboxes per domain and plan around roughly 40 sends per inbox.
Notice that the domain count is derived, not chosen. You decide a daily volume, the per-inbox and per-domain ceilings do the rest, and the only real judgment call left is which ceiling you trust. The send-side half of that equation, including the ramp schedule that gets a new inbox to full volume, is covered in our guide to how many cold emails per day are safe. This article covers the asset side: how many domains and inboxes to buy, what they cost, and how to arrange them.
The three rules the math is built on
Never send from your main domain
A secondary domain is a lookalike domain registered solely for outbound, so that any reputation damage lands on a disposable asset instead of the domain your invoices, contracts, and customer replies depend on. Vendisys’s scaling guide is blunt about this: never send cold outbound from your primary corporate domain, because a flagged sending domain should be a contained loss, and a flagged primary domain breaks the mail your business actually runs on. EmailBison’s secondary-domain guide recommends lookalike patterns close to your brand, such as try-yourbrand.com, get-yourbrand.com, or yourbrand-hq.com, on trusted TLDs like .com, .io, or .co. Point each one at your main site with a redirect so a curious prospect who types it into a browser lands somewhere real. And remember that every domain needs its own authentication records, a setup we walk through in our SPF, DKIM, and DMARC guide.
Cap each domain at 2 to 3 inboxes
Two to three inboxes per domain is the most consistent number in the entire niche. Scaledmail’s 2026 answer runs 2 inboxes per domain on Google Workspace and 2 to 3 on self-managed Microsoft 365, and Litemail’s 2026 guide draws the same line, warning that more than three inboxes sharing a domain concentrates risk because a domain flag stops all of them at once. The reasoning is as much camouflage as containment: two or three working mailboxes on a domain looks like a normal small business, while ten looks like exactly what it is.
Plan 20 to 50 sends per inbox, and treat 40 as the working number
This is the one figure where published sources genuinely disagree, so treat it as a range with a conservative default. Litemail advises staying at 30 to 50 emails per inbox per day while calling 20 to 30 the safe cold ceiling on both Google Workspace and Microsoft 365. Vendisys plans its sizing around a 40-per-inbox ceiling. At the aggressive end, howmanydomainsforcoldmail.com, a site dedicated entirely to this question, allows 50 to 100 per mailbox and divides daily volume by 75. We side with the conservative majority: 20 to 50 per warmed inbox, 40 as the planning number, and 100 to 150 per domain across all its mailboxes, the same figures our agency campaigns run on. A brand new inbox starts near zero either way and earns that ceiling over several weeks, a process covered in our email warmup guide.
Every published formula disagrees on the per-inbox number and agrees on the shape: scale horizontally. An extra inbox costs a few dollars a month. A rebuilt reputation costs weeks.
The domain and inbox matrix by volume tier
Here is the full requirement at each common volume tier, using the conservative consensus ratios of 40 sends per inbox and 3 inboxes per domain:
| Daily cold sends | Warmed inboxes (at 40 per day) | Secondary domains (2 to 3 inboxes each) | Approximate monthly infrastructure cost |
|---|---|---|---|
| 50 | 2 | 1 | ~$15 |
| 150 | 4 | 2 | ~$30 |
| 250 | 7 | 3 | ~$52 |
| 500 | 13 | 5 | ~$96 |
| 1,000 | 25 | 9 | ~$184 |
Cost column assumes Google Workspace Business Starter at $7 per inbox per month on an annual plan and domains amortized at $12 per year. If you would rather size from a meetings goal than a send count, Vendisys publishes the same math worked backwards: a 20-meeting-per-month program needs roughly 5 inboxes across 2 to 3 sending domains, while a 60-meeting-per-month program lands around 540 sends per day, which is about 14 inboxes across 5 to 6 domains. Both framings agree with the table above.
The table also shows where the real work lives. At 500 sends per day you are not managing a campaign, you are managing 13 mailboxes and 5 domains, each with its own authentication, warmup, rotation schedule, and reputation to watch. The platforms that automate that provisioning and monitoring are compared in our roundup of cold email infrastructure tools.
What does cold email infrastructure cost per month?
Cold email infrastructure costs far less than most founders expect: plan on roughly $7 to $8.40 per inbox per month and $10 to $15 per domain per year. Google Workspace Business Starter runs $7 per user per month on an annual plan, or $8.40 month to month, per EmailToolTester’s 2026 pricing breakdown, and howmanydomainsforcoldmail.com puts secondary domains at $10 to $15 each per year, with Cloudflare Registrar selling .com domains at $9.15 in EmailBison’s guide. At those rates, a 500-send-per-day setup of 13 inboxes across 5 domains costs about $96 per month, and even a 1,000-send operation stays under $200 per month in raw infrastructure. The monthly spend, in other words, is not the hard part. The hard part is provisioning, authenticating, warming, and monitoring every one of those assets, which is where the real cost hides.
Watch the renewal line when you register, because introductory domain pricing and renewal pricing can differ meaningfully between registrars. And budget time, not just money: every new domain needs DNS records published, every inbox needs two to three weeks of warmup before it sends a real campaign, and the whole fleet needs weekly reputation checks. For an early-stage team, that operations tax is usually the deciding factor between building this stack and using a managed service, a tradeoff we see constantly in outbound email for startups.
Should you split your inboxes between Google and Microsoft?
A 60/40 Google-to-Microsoft split is the most commonly recommended inbox pool for mixed B2B lists. Both Litemail’s Google Workspace versus Microsoft 365 comparison and Puzzle Inbox’s 2026 provider analysis land on the same default: roughly 60 percent of your inboxes on Google Workspace and 40 percent on Microsoft 365. The logic is recipient matching. Per Puzzle Inbox’s estimates, around 60 percent of B2B contacts sit on Gmail or Google-hosted business domains, another 30 to 35 percent on Outlook or Microsoft 365, and the rest elsewhere, so a mixed pool mirrors the mailboxes you are landing in. The split also buys resilience: when Google tightened sender requirements in 2024, Litemail notes, agencies running mixed pools kept sending through Microsoft inboxes while their Workspace settings caught up. If your list skews hard toward one provider, skew the pool the same way.
Provider mix is a second-order optimization, though. Authentication, list quality, and volume discipline decide the bulk of your inbox placement, and the full picture of how receivers score you is in our cold email deliverability guide. Get those right on an all-Google pool and you will beat a perfectly balanced pool with a dirty list every time.
Why GTM Bud users skip the domain spreadsheet
Everything above eventually becomes a spreadsheet: domains, registrars, renewal dates, inboxes, warmup start dates, per-inbox ramp stages, and weekly reputation checks, multiplied by every row you add as you scale. That spreadsheet is exactly the work GTM Bud was built to absorb. As a done-for-you outbound platform, it handles the research, the copy, the sending, and the follow-ups across both email and LinkedIn, with sending infrastructure provisioned and volume-managed inside the ratios in this article, for a flat monthly rate per connected sending account. You choose the targets and approve the campaigns; the domain math runs underneath without your involvement.
The reason we can operate that way is the same agency playbook behind these numbers. Referral Program Pros ran this architecture across 4,000+ campaigns before GTM Bud productized it, which is why GTM Bud carries a reply-rate guarantee of 5 percent positive replies on LinkedIn or 1.5 percent on email, with a full refund if a campaign misses it. Infrastructure sized correctly is what makes a guarantee like that possible to offer.
Frequently asked questions about cold email domains and inboxes
Can I run all my sending domains inside one Google Workspace account?
Technically yes, since Workspace supports secondary domains under one account, but most infrastructure guides advise against it. EmailBison recommends an independent Workspace account per sending domain, so an account-level suspension on one domain cannot take the rest down with it. The tradeoff is more admin overhead per account. If you stay under one account for simplicity, keep total volume conservative, because you have stacked a second layer of concentrated risk on top of domain reputation.
Should I buy aged domains instead of registering new ones?
Usually no. An aged domain only helps if its history is clean, and you rarely get to verify that before buying. A domain that previously sent spam or sat on a blocklist starts you below zero, which is worse than starting fresh. A newly registered domain with correct authentication and two to three weeks of warmup is predictable, cheap, and fully under your control. If you do buy aged, check blocklist status and archived usage first, then warm it exactly like a new domain.
What TLD should cold email sending domains use?
Stick to .com wherever the name is available. In placement tests published by Litemail, .com domains paired with pre-warmed inboxes averaged 92 to 94 percent inbox placement, and .com remains the least suspicious-looking TLD to filters and recipients alike. Established alternatives like .io and .co are workable second choices. Avoid cheap novelty TLDs, which are heavily used by spammers and inherit that neighborhood’s reputation before you send a single message.
Do agencies need separate sending domains for each client?
Yes. Reputation must be isolated per client, so one client with a bad list or an aggressive offer cannot damage every other campaign you run. EmailBison puts the working range at 3 to 10 lookalike domains per client, sized to each client’s volume tier. That multiplies the provisioning work fast, which is why teams running cold email for agencies either dedicate real operations time to infrastructure or use a platform that provisions per-client domains automatically.
When should you retire a cold email sending domain?
Retire a domain when its metrics stay degraded after you have cut volume, fixed the list, and let it rest, because a reputation that does not recover in weeks rarely recovers at all. At the 10 to 15 dollars per year that howmanydomainsforcoldmail.com prices secondary domains at, they are consumables, not assets. Keep a small bench of registered, authenticated, and warming domains at all times so a retirement never interrupts your sending schedule.
Right-size the stack once, then go book meetings
The answer to how many domains and inboxes for cold email is arithmetic, not folklore: 2 to 3 inboxes per secondary domain, 20 to 50 sends per warmed inbox with 40 as the planning number, and a domain count that falls out of your daily volume target. Start with one domain and two inboxes, prove the campaign works, then add domains in the ratios above instead of pushing any single asset harder. The infrastructure is cheap; the discipline is the asset.
If you would rather never open the domain spreadsheet at all, connect a sending account to our cold email automation tool and let it run the provisioning, warmup, and volume management on the same playbook that booked 7,000+ meetings, with a 7-day trial to see the difference before you commit.