How much infrastructureyour send target really needs.
You don't hit 1,000 cold emails a day from one inbox — you hit it from a fleet of them, each sending a safe trickle. This planner turns your daily target into the exact count of inboxes and domains it takes to send it without torching your deliverability.
Your target
Cold emails you want to send each sending day.
How many you'll send from each inbox daily. Keep it 30-40 for cold.
Mailboxes you run on each sending domain. ~3 is the common ceiling.
Working days you actually send on (weekdays ≈ 22).
Infrastructure needed
Inboxes needed
25
Domains needed
9
Monthly send volume
22,000
Per-inbox monthly load
880
Sends each inbox carries per month.
The fleet, at a glance
Your per-inbox cap vs. the safe band
Sensitivity · the per-inbox cap
How the cap drives your inbox count
| Per-inbox cap | Inboxes needed | Domains needed |
|---|---|---|
| 20/day | 50 | 17 |
| 30/day | 34 | 12 |
| 40/day | 25 | 9 |
| 50/day | 20 | 7 |
Same 1,000/day target, four different caps. Pushing the cap higher shrinks your inbox count — and your safety margin. The 40/day row (highlighted) is the standard safe ceiling for cold; at it you'd run 25 inboxes.
Reference · safe-sending rule of thumb
| Inbox posture | Safe sends / inbox / day | Inboxes for your target |
|---|---|---|
| Fresh / just warmed | 20/day | 50 |
| Established, steady | 40/day | 25 |
| Aggressive | 50/day | 20 |
| Reckless | 80/day | 13 |
No provider publishes an official cold-send limit — these are operator consensus guardrails, not guarantees. The fresher the inbox, the lower you stay. Warm every new mailbox 2-4 weeks before sending at the cap.
Your move
I size the fleet so your sends land, not bounce.
1,000 cold emails/day needs 25 inboxes across 9 domains at 40/inbox/day.
Cold email at volume is an infrastructure game before it's a copy game — inboxes, domains, authentication, warm-up, and a list clean enough to deserve the send. Tell me the number you're chasing and I'll map the setup that hits it without burning your domains. Free, and yours to keep.
Plain English
Volume is a fleet problem, not an inbox problem.
There is one hard rule in cold email infrastructure: a single inbox can only send a small, safe number of cold messages a day before mailbox providers start treating it like a spammer. Push past that and you don't get warnings — you get the spam folder, then a blocklist, then a dead domain. So scale doesn't come from sending more per inbox. It comes from sending the same safe trickle across more inboxes.
That's the whole math of this tool. Pick the daily volume you want, pick the safe per-inbox cap you'll respect (30-40 a day for cold is the consensus ceiling), and it tells you how many inboxes that requires. Then, because stacking too many mailboxes on one domain is its own deliverability risk, it spreads those inboxes across domains at roughly three per domain and tells you how many domains to buy.
The output is a shopping list and a sanity check in one: inboxes needed, domains needed, the monthly volume you'll actually push, and the load each inbox carries. If the per-inbox number you typed is above the safe ceiling, the verdict says so — because the cheapest way to scale cold email is the one that doesn't get your sending burned.
The formula
Inboxes = ⌈target ÷ per-inbox cap⌉ · Domains = ⌈inboxes ÷ inboxes-per-domain⌉
Want 1,000/day at a safe 40/inbox? That's ⌈1000 ÷ 40⌉ = 25 inboxes. At 3 inboxes per domain you need ⌈25 ÷ 3⌉ = 9 domains. Over 22 sending days that's 22,000 emails a month, with each inbox carrying 880 sends a month — comfortably inside safe territory.
Safe sending, rule of thumb
No mailbox provider publishes an official cold-send limit, so these are the consensus guardrails experienced deliverability operators run by — treat them as ceilings, not targets. The fresher the inbox, the lower you stay.
| Inbox posture | Safe sends / inbox / day | What it signals |
|---|---|---|
| Fresh / just warmed | 20/day | New inbox out of warm-up. Stay conservative for the first month. |
| Established, steady | 40/day | The standard safe ceiling for an aged, authenticated inbox sending cold. |
| Aggressive | 50/day | The edge of safe. Only with great lists, tight copy, and live reply monitoring. |
| Reckless | 80/day | Above the safe ceiling. Spam folders, blocklists, and burned domains live here. |
Rule-of-thumb operator bands — not a published dataset. Providers don't publish cold-send limits; the fresher the inbox, the lower you stay. Warm every new mailbox 2-4 weeks before sending at the cap.
Your plan came back heavy. Where to look.
Per-inbox cap above ~50/day.
You're trading deliverability for a smaller invoice, and it's a bad trade. Drop the cap to 30-40, accept more inboxes, and keep your domains alive. A burned domain costs months, not dollars.
Domain count looks brutal.
It's the per-inbox cap doing the damage. Each 10-email cut to the cap adds inboxes and domains fast. Before you buy more domains, ask whether your target volume is real or aspirational — most teams over-plan send and under-plan list quality.
Inboxes pile up on few domains.
Stacking 10 mailboxes on one domain concentrates risk: one spam complaint can sink them all. Keep it near 3 per domain so a problem stays contained instead of cascading.
Brand-new infrastructure.
None of these inboxes can send at the cap on day one. Warm every mailbox for 2-4 weeks first, ramping from a handful of sends up to the cap. Plan the warm-up before you plan the campaign.
How to scale sends without burning
01Respect the 30-40 ceiling
For cold outreach, 30-40 sends per inbox per day is the safe band. Adding inboxes is cheap; recovering a blocklisted domain is not.
02Spread across domains
Run ~3 inboxes per sending domain. Spreading volume contains the blast radius if one mailbox draws complaints.
03Warm before you send
Every new inbox needs 2-4 weeks of warm-up, ramping sends gradually, before it touches a real campaign at full cap.
04Authenticate everything
SPF, DKIM, and DMARC on every sending domain. Without them, even a perfect cap lands you in spam.
05Use dedicated domains
Send cold from secondary domains (yourbrand-mail.com), never your primary. Protect the domain your customers email.
06Monitor reply and bounce rates
A bounce rate over ~3% or a complaint spike means pull back the cap immediately — the fleet only works if every inbox stays clean.
07Clean the list first
Verify addresses before sending. Bad lists burn inboxes faster than high volume ever will; capacity can't outrun a dirty list.
08Stagger sends across the day
Drip the daily cap over working hours, not in one blast. Human-looking cadence keeps inboxes off provider radar.
The vocabulary
- Inbox (mailbox)
- A single sending email address. The unit of cold-email capacity: each one has a safe daily ceiling.
- Sending domain
- The domain your inboxes send from. Usually a secondary domain bought to protect your primary.
- Per-inbox cap
- The number of cold emails one inbox sends per day before deliverability risk climbs. 30-40 for cold.
- Warm-up
- The 2-4 week ramp that builds a new inbox's reputation before it sends real campaigns at full volume.
- Deliverability
- Whether your email reaches the inbox instead of spam. The thing per-inbox caps exist to protect.
- Authentication
- SPF, DKIM, and DMARC records that prove your mail is legitimate. Required on every sending domain.
Sending capacity questions, straight answers
30-40 a day is the safe ceiling for cold outreach from an established, authenticated inbox. There's no official provider limit, but past roughly 40-50 cold sends a day from a single mailbox, deliverability risk climbs sharply. To send more, add inboxes — don't push one harder.
Keep going
A calculator tells you what. A call tells you what to do about it.
Send me the account behind these numbers. I'll tell you straight where the money's leaking and what I'd fix first — free, and you keep it whether you hire me or not.