Capacity math

How Many Domains and Inboxes Do You Need for Cold Email? (The Real Math)

By Toukir AhmedPublished July 13, 2026Read 3 min

"How much infrastructure do I need?" has an actual formula, not a vibe. You work backwards from daily volume — and you always build headroom, because domains get burned and rotated. This is the same math I use to spec fleets sending 100k+ per day.

The formula

Inboxes needed = daily target ÷ safe per-inbox volume (15–30/day)
Domains needed = inboxes ÷ 2–3 per domain — then add 20–30% headroom for rotation and warmup pipeline.
worked examples — daily target → infrastructure
500 / day25 in · 10 dom
2,000 / day100 in · 40 dom
6,000 / day300 in · 110 dom
10,000 / day500 in · 180 dom
assumes ~20/day per inbox, 2–3 inboxes per domain, ~25% headroom included

Why per-inbox volume stays low

A Google Workspace account can technically relay thousands of messages a day — but cold email isn't judged on technical limits, it's judged on engagement signals from strangers. At 15–30/day per inbox, each address looks like a normal professional. At 80/day it looks like a machine, and machines get filtered. The provider-by-provider details are in cold email sending limits.

Why 2–3 inboxes per domain

The domain is the reputation unit. Stack 10 inboxes on one domain and a single reputation dip takes out 10 inboxes of capacity at once. Spread the same 10 inboxes over 4 domains and a hit costs you a quarter of that — and you can rotate the burned domain out without touching the rest.

Build in rotation headroom

Fleets are living systems. At any moment some domains are warming, some are prime, some are cooling down. If your math says 100 domains, buy and warm ~125 — the spare capacity is what lets you swap instantly instead of pausing campaigns for three weeks while replacements warm. Naming and DNS for large fleets: domain setup at scale.

Mixed ESP fleets

At larger scale, split infrastructure across Google Workspace and Microsoft 365 — partly for provider-diversity resilience, and partly because matching sender ESP to recipient ESP measurably helps placement. A common split I run: Google-heavy for Gmail-dominated TAMs (startups, agencies), Microsoft pools for enterprise-heavy lists.

15–30emails / inbox / day
2–3inboxes / domain
+25%rotation headroom
100%domains authenticated
You have the number — now register them

Take the domain count from the formula above and buy the batch together so the fleet ages together. Namecheap does bulk registration with free WHOIS privacy, which keeps the WHOIS data consistent across all of them — one fewer fingerprint shared by fifty names.

Bulk-register on Namecheap →Affiliate link — it costs you nothing and helps keep this site free.

Do the maths with your own numbers

The domain & inbox planner turns a daily target into inboxes, domains, cost and a purchase-to-launch calendar at the ratios above. The sequence planner then shows what a multi-step cadence does to that daily volume once follow-ups stack.

Frequently asked questions

How many inboxes should I put on one cold email domain?

Two to three inboxes per domain is the standard I run at fleet scale. More inboxes on one domain concentrates risk: if the domain's reputation dips, every inbox on it dips together, and recovery is slower.

How many cold emails can one inbox safely send per day?

After full warmup, 15–30 cold emails per day per inbox is the sustainable range I use. Providers technically allow far more, but cold email is judged by recipient engagement, and pushing 50+ per inbox reliably degrades placement within weeks.

Is it better to add more domains or more inboxes to scale?

More domains. Domains are the reputation unit — spreading volume across more domains with 2–3 inboxes each keeps any single reputation hit small and lets you rotate burned domains out without denting total capacity.

Keep reading

Back to top