Turn a monthly prospect target into inboxes, domains and a ramp schedule with every formula visible. No signup, runs in your browser.
Unique people entering the sequence each month.
Emails per prospect, including follow-ups.
Business days is 20 to 22 in most months.
Your operating assumption, not a verified safe limit.
Extra inboxes held back for pauses and rotation.
2 to 3 keeps domain risk spread out.
0 means infrastructure is already warmed.
First sending day of the plan.
The upper range adds resilience headroom; it is not a purchase requirement. The full-capacity date is a plan date computed from your inputs, not verified sender health. This tool does not test or guarantee inbox placement.
| Week | Share of campaign cap | Approx. sends/day (all inboxes) |
|---|---|---|
| 1 | 25% | 94 |
| 2 | 50% | 188 |
| 3 | 75% | 281 |
| 4+ | 100% | 375 |
Same formulas, same settings as your plan above, only the monthly prospect count changes.
| Monthly prospects | Total sends | Daily demand | Active inboxes | Domains |
|---|---|---|---|---|
| 500 | 1,500 | 75 | 4 | 2 |
| 2,000 | 6,000 | 300 | 15 | 5 |
| 5,000 | 15,000 | 750 | 36 | 12 |
These boxes reflect what you report about your setup; nothing is verified here. For a live check of your actual DNS records, run the free email deliverability test.
0 of 8 items reported ready.
Every number on this page comes from six visible formulas, in order. There is no hidden model and no scoring: change an input and the plan recomputes deterministically.
The per-inbox daily cap is your own operating assumption. The planner will not certify any single number as a safe limit, because no such universal limit exists: what a given inbox sustains depends on list quality, engagement and sender history. For the full reasoning behind each step, read the guide on how to plan cold email inbox capacity.
The inbox and domain counts above describe steady state: what your infrastructure handles once it is established. The ramp schedule describes how you get there. New inboxes start at a fraction of their planned campaign cap (25, 50 and 75 percent over the default three weeks) and only then reach 100 percent, while automated warm-up keeps positive engagement flowing in the background. Mixing the two up, by treating week-one capacity as steady-state capacity, is the most common way new senders overload fresh domains.
Plans built at exactly 100 percent utilization break the first time anything goes wrong: an inbox gets paused, a domain needs a rest, a mailbox provider throttles a sender. Reserve inboxes, 20 percent by default here, absorb those events without cutting your deliverable volume. Reserve capacity also matters less if your list is clean in the first place: fewer bounces means fewer paused senders, so run your list through the pre-send cleaning process and segment it properly before the volume plan ever executes.
The readiness checklist above is self-reported: it records what you believe about your SPF, DKIM, DMARC and process setup, and this page does not query DNS to confirm any of it. Before the first sending day, verify the technical items with the live deliverability test, then run the whole campaign through the campaign readiness checker to catch gaps beyond DNS: sequencing, list hygiene, monitoring and opt-out handling.
Customer reviews
Don't take our word for it