Home › Blog › How Many Cold Email Domains Do I Need for 300 Emails per Day?
Working backward from daily volume shouldn't produce five different answers, the math is fixed once you lock two numbers: sends per inbox and inboxes per domain. Here's the formula, worked examples for 100, 300, 500 and 1,000 sends/day, and the rotation buffer that most calculators forget.

300 ÷ 30 sends/inbox = 10-11 inboxes ÷ 2-3 per domain = 4-5 domains. Add ~25% warming reserve → 5-6 domains, 12-14 inboxes. Microsoft-heavy list? Use 15-20/inbox and double the fleet. Run your own numbers in the Inbox Planner, same formula, interactive.
inboxes = daily_sends ÷ per_inbox_cap (30 Google-targeted · 15-20 Microsoft-targeted) domains = inboxes ÷ inboxes_per_domain (2-3, see the ratio guide) reserve = +20-30% capacity warming (rotation + retirement buffer)
Every disagreement you've read about domain counts is a disagreement about the two input constants, not the arithmetic. We covered why 2-3 inboxes per domain is the right middle and why ~30/day per inbox keeps you out of bulk-pattern territory. Lock those and the answer stops being controversial.
Split fleets adjust per segment: if your list segments 60% Google / 40% Microsoft (check yours with the ESP Segmenter), the Microsoft share runs at half the per-inbox cap, a 300/day mixed operation lands closer to 7-8 domains than 5.
Calculators that stop at "4-5 domains" assume nothing ever goes wrong. Real fleets rest inboxes on cycles, occasionally retire a domain, and never want a warmup delay standing between them and Monday's sends. That's the 20-30% reserve: capacity that's warming while the active pool sends, promoted when needed. The full active/resting/warming structure is in the rotation system guide, at 300/day and above, it's the difference between an incident and an outage.
Using safe operating numbers, ~30 sends/inbox/day and 2-3 inboxes/domain, 300/day needs 10-11 active inboxes across 4-5 domains. Add a rotation/reserve margin of ~25% (one more domain warming) and the practical answer is 5-6 domains, 12-14 inboxes total. Halve per-inbox caps for Microsoft-heavy targeting and the domain count roughly doubles.
Inboxes = daily target ÷ per-inbox cap (use 30 for Google-targeted, 15-20 for Microsoft-targeted). Domains = inboxes ÷ inboxes-per-domain (use 2-3). Then add 20-30% reserve capacity warming so retirements and rest cycles never pause campaigns. Every serious calculator is those three lines with different defaults.
Physically yes, two domains with three inboxes each at 50 sends/inbox gets you there. But 50/day/inbox is deep in bulk-pattern territory and the whole 300 rides on two domain reputations. You'd be trading ~$40/year of domain cost against the survivability of your entire channel. Volume discipline is the one corner never worth cutting.
Yes, the per-inbox cap is total outbound messages, not new prospects. A 4-touch sequence means ~300 sends/day supports roughly 75-100 NEW prospects/day at steady state, depending on your reply and drop-off rates. Size infrastructure on total sends, plan pipeline on new-prospect capacity.
From scratch: 2-4 weeks of warmup before real volume, then 3-4 more weeks ramping to full capacity, call it 6-8 weeks. Prewarmed domains and inboxes collapse the first phase to day one, which is exactly why they exist.
Prewarmed Inboxes So You Can Send Cold Emails Today
Get Prewarmed & Fresh InboxesGoogle, Microsoft 365 and Azure inboxes with free prewarmed domains and DNS configured before you log in. Prewarmed inboxes send the day they land; every order is delivered within 48 to 72 hours.
Get Prewarmed & Fresh Inboxes