TL;DR
"How many domains and mailboxes do I need?" is the first real question of any cold email build — and the one most people get wrong. They either cram 20 inboxes onto one domain and torch its reputation, or they buy a single Google Workspace seat and wonder why 500 emails a day lands them in spam. The right answer is a short calculation, and this post walks you through it end to end: the math, the naming and warmup rules, the provider caps you must respect, and what it actually costs.
Sourcing note: the provider rules and thresholds here are VERIFIED against Google, Yahoo, and Microsoft's own announcements. The architecture ratios — sends per mailbox, mailboxes per domain, warmup timelines, and pricing — are practitioner and vendor guidance that varies by source; we flag those as (directional) and commit to conservative working numbers rather than presenting any single figure as settled.
Divide your target daily send volume by a safe per-mailbox rate (~20/day), then divide the mailbox count by 2–3 mailboxes per domain, then add a 20–30% buffer for warmup and rotation. For 1,000 emails a day that lands around 50–60 mailboxes spread across roughly 30 domains; for 500 a day, about 25 mailboxes across ~16 domains. You send from secondary domains — never your primary company domain — redirect them to your main site, warm each new domain for two to four weeks, and keep each domain well under 5,000 sends a day so you sit below the Google/Yahoo bulk-sender threshold.
Cold outreach carries reputation risk. One bad week — a spike in spam complaints, a blocklist listing — can start routing your invoices, contracts, and inbound sales replies to spam if that reputation is attached to your main company domain. So you isolate the risk: register standalone secondary sending domains that exist only to send cold email, and 301-redirect them to your main website so clicks and brand checks still resolve (directional). Many teams also route link tracking through a separate custom tracking domain so the primary never appears in the send path at all. The rule is simple: your money domain never touches cold traffic.
Everything downstream flows from three inputs. Here's the chain:
target daily sends ÷ safe sends-per-mailbox = mailboxes
mailboxes ÷ mailboxes-per-domain = domains
+ 20–30% buffer for warmup and rotation
Plug in conservative numbers — ~20 sends per mailbox per day and 2 mailboxes per domain (directional) — and the 1,000-emails-a-day build looks like this:
Scale it up or down and the ratios hold. Here's the reference build across common volume targets:
| Target sends/day | Mailboxes (~20/day each) | Domains (2/domain + buffer) | Est. mailbox cost/mo (reseller ~$3) | Warmup lead time |
|---|---|---|---|---|
| 100 | ~5 | ~3 | ~$15 | 2–3 weeks |
| 250 | ~13 | ~8 | ~$40 | 3–4 weeks |
| 500 | ~25 | ~16 | ~$75 | 3–4 weeks |
| 1,000 | ~50–60 | ~30 | ~$150–180 | 4 weeks |
| 2,500 | ~125 | ~75 | ~$375 | 6–8 weeks |
All figures directional (practitioner formulas + reseller pricing). Add ~$25–40/mo for domains and $50–200/mo for a sending platform. Sends-per-mailbox held conservative at 20/day; some Microsoft 365 operators run higher.
The number that varies most is sends-per-mailbox-per-day. Sources put it anywhere from 10–25 (Google Workspace) to 30–50 (Microsoft 365). Don't chase the high end — reputation, not the platform cap, is what limits you. Start at 20/day per mailbox, watch your complaint and bounce rates, and only nudge upward if the data stays clean.
Once you know how many domains you need, buy them right:
getacme.com, tryacme.com, acmehq.com — so replies still feel legitimate and on-brand.You have three provisioning paths, and most serious builds mix them:
Two different things warm up, and both matter. Domain warmup builds the sending domain's reputation; mailbox warmup builds each individual account's sending history. Ramp both:
For the tooling side of this — warmup pools, deliverability monitors, and whether warmup services still work in 2026 — see our guide to the best email warmup & deliverability tools.
This is the VERIFIED backbone every build has to respect:
550 5.7.515 Access denied. Microsoft switched from junk-foldering to outright rejection in late April 2025.Why the multi-domain architecture is a feature, not just overhead: spreading volume across ~30 domains keeps each one structurally below the 5,000/day bulk-sender trigger and isolates reputation risk. You get compliance and resilience from the same design. The authentication itself (SPF, DKIM, DMARC records per domain) is non-negotiable — see our step-by-step SPF, DKIM & DMARC setup guide.
Using the ~1,000-sends/day build (~30 domains, ~60 mailboxes), all figures (directional):
All-in, a ~1,000-sends/day operation runs roughly $260–600/month, driven mostly by how you source inboxes. One warning: don't confuse "1,000 sends/day" with "1,000 inboxes" — you only need ~60 inboxes for 1,000 daily sends, and cost calculators quoting four-figure monthly totals are almost always pricing a 1,000-inbox operation. To translate this infrastructure spend into a true cost per booked meeting, see what cold email really costs in 2026.
Divide your daily send target by ~20 emails per mailbox, then by 2 mailboxes per domain, and add a 20–30% buffer. For 1,000 emails/day that's roughly 30 domains; for 500/day, about 16. You scale by adding domains, not by adding inboxes to existing ones.
Two to three — two for Google Workspace, two to three for self-managed Microsoft 365. Piling more inboxes onto a single domain concentrates reputation risk, which is the opposite of what the architecture is for.
Keep it around 20 per inbox per day. Community estimates range from 10–25 for Google Workspace up to 30–50 for Microsoft 365, but the platform cap (~2,000/day on Google Workspace) is far higher than what's safe — reputation, not the cap, is the real limit.
No. Use secondary sending domains and redirect them to your main site. A reputation hit on your primary domain can push your invoices, contracts, and inbound sales replies into spam — a risk that is never worth taking.
Two to four weeks for a new domain, and treat 30 days as the safe floor since Google flags very young domains. Start at 5–10 sends/day and ramp by about 5/day up to 25–30. High-volume senders should plan 6–8 weeks.
Google/Yahoo (since Feb 1, 2024) and Microsoft Outlook.com (since May 5, 2025) require SPF, DKIM, and DMARC for senders above 5,000/day, plus one-click unsubscribe and a spam-complaint rate under 0.3% (aim for 0.1%). Fail Microsoft's authentication check and you get a 550 5.7.515 rejection.
Building your sending infrastructure from scratch? Start with the full cold email infrastructure guide and the SPF/DKIM/DMARC setup walkthrough — or talk to our team and we'll architect and warm the whole thing for you.
By the GenFlows GTM engineering team. We build and run cold email infrastructure for B2B outbound programs. Architecture ratios and pricing marked directional vary by source — treat them as planning guidance, not guarantees. Last updated July 2026.