The Short Answer
Divide your required daily sending volume by what one mailbox can safely send — 20–30 cold emails per day for a warmed account — then add a 25–30% buffer for rotation and recovery. Spread mailboxes across domains at 2–3 mailboxes per domain, never on your primary domain.
mailboxes = (daily volume ÷ 25) × 1.3 · domains = mailboxes ÷ 2.5
The rest of this article is where those numbers come from — and the failure modes you avoid by respecting them.
Why Not Just Send More From One Account?
Mailbox providers score sending behavior per account and per domain. A new or lightly-used account that jumps to hundreds of daily sends exhibits the volume signature of a compromised mailbox — which is exactly what filters are trained to catch. Three independent ceilings apply:
- Hard caps: Google Workspace allows 2,000 sends/day, Microsoft 365 allows 10,000 recipients/day — but these are technical limits for legitimate transactional mail, not safe cold-email volumes.
- Behavioral thresholds: reputation systems react to volume velocity. Sustained 20–30/day with engagement reads as human; 200/day does not.
- Blast-radius economics: when one account gets flagged, everything it sends is dead until recovery. Small per-account volume means any single flag costs you 25 sends/day, not 500.
This is why scale comes from rotating many small senders, not pushing one big one — the same architecture every serious outbound team converges on.
The Worked Example: 20 Meetings a Month
Work backwards through the funnel. Assume defensible mid-range rates — adjust with your own data once you have it:
| Step | Assumption | Result |
|---|---|---|
| Target meetings/month | — | 20 |
| Positive replies needed | ~50% of positives book | 40 |
| Total replies needed | ~30% of replies are positive | ~135 |
| Prospects contacted | 3% reply rate (multi-step sequence) | ~4,500 |
| Emails sent (3.5 touches avg) | sequence of 3–4 steps | ~15,750/mo |
| Daily volume | 21 sending days | ~750/day |
Now apply the formula: 750 ÷ 25 = 30 mailboxes; × 1.3 buffer = 39 mailboxes, call it 40. At 2–3 mailboxes per domain that's 14–20 domains. On DitLead's pre-warmed account pricing ($8/domain + $3/month per mailbox), that fleet costs roughly $120/month in mailboxes plus ~$130 one-time in domains — infrastructure for a pipeline target, priced like a software seat.
Capacity Cheat Sheet
| Daily cold emails | Mailboxes (with buffer) | Domains (2–3 boxes each) |
|---|---|---|
| 100 | 5–6 | 2–3 |
| 250 | 13 | 5–7 |
| 500 | 26 | 9–13 |
| 1,000 | 52 | 18–26 |
| 2,500 | 130 | 45–65 |
Run your own numbers with the mailbox calculator and sending capacity calculator.
The Three Rules That Keep a Fleet Healthy
- Never send cold from your primary domain. Use secondary domains so a reputation hit never touches the domain your invoices and signups depend on. (Full reasoning: why secondary domains are non-negotiable.)
- Keep warmup running forever. Reputation decays without positive engagement. Every DitLead mailbox stays on the 55,000+ inbox warmup network while campaigns run.
- Rotate and monitor. Health-score every mailbox, pause flagged ones automatically, and let rotation absorb the loss. A fleet with a 30% buffer doesn't miss quota when two accounts need a recovery week.
FAQs
Can I start with fewer and scale up?
Yes — that's the right way. Start at half your target fleet, watch placement and reply rates for two weeks, then add capacity. Adding warmed mailboxes takes a day; recovering a burned fleet takes weeks.
Why 2–3 mailboxes per domain and not more?
Domain reputation aggregates its mailboxes. Stack five senders on one domain and a single bad account drags down all five. Two to three keeps the blast radius small while amortizing the domain cost.
Do warmup emails count against the daily volume?
Yes. A mailbox sending 25 cold + 30 warmup emails is doing 55 sends that day. Budget total volume, not just campaign volume — DitLead's scheduler does this automatically.