For scaled outbound, five campaign sends per inbox per day is the better capacity-planning number. It spreads outbound volume across more domains and limits how much of the total sending operation depends on any one of them.A
For scaled outbound, five campaign sends per inbox per day is the better capacity-planning number. It spreads outbound volume across more domains and limits how much of the total sending operation depends on any one of them.
The alternative prioritizes the lowest initial infrastructure count. Buy fewer domains, operate fewer inboxes, and ask each inbox to produce more volume. That works until a domain develops reputation problems, gets blocked, or needs to be removed from production. The more campaign capacity concentrated on that domain, the more of the sending operation disappears with it.
Planning around five makes the wiser infrastructure investment at the beginning. It creates a wider base, reduces campaign exposure per inbox and domain, and gives the portfolio a better chance to remain productive longer when individual domains develop problems.
Consider a program that needs 300 campaign sends per day and uses ten campaign inboxes per domain. At five per inbox, it needs 60 inboxes across six domains. Each domain carries 50 daily slots. At 30 per inbox, the same 300-send target can be concentrated in ten inboxes on one domain.
If one domain has to be removed from production, the wider design loses 50 of its 300 daily slots, or about 16.7%. The concentrated design loses all 300. Replacing that capacity takes longer than registering another domain. The replacement must be configured, authenticated, connected, ramped, and monitored before it can carry production traffic with confidence.
This is why per-inbox volume cannot be separated from domain concentration. A setting that looks efficient at the mailbox level can create a fragile portfolio when too much output depends on a small number of domains.
The number 30 appears frequently in sequencer settings and outbound discussions, but it is not a safe allowance published by Gmail, Microsoft, or Yahoo.
Instantly's current account-limit documentation uses 30 campaign emails per account per day as an opening example. Farther down the same page, it explicitly recommends 30 campaign emails per day for non-AirMail mailboxes and calculates its recommended campaign limit as the number of accounts multiplied by 30. A separate Instantly bounce article calls 30 cold emails plus 10 warm-up emails per account per day a suggested safe limit.
Receiver documentation does not validate either number. Google's email sender guidelines focus on consistent pacing, gradual volume increases, spam rates, bounces, deferrals, and domain and IP reputation. Microsoft says its filtering considers the sending IP, domain, authentication, list accuracy, complaint rates, content, and other factors. Its sender guidance identifies junk-email complaints as a principal factor in sender reputation.
Those are Instantly's operating recommendations, not receiver-published safety thresholds. At 22 business days per month, five allows 110 campaign sends per inbox and 30 allows 660. If bounce and complaint rates remain unchanged, the higher send count produces more absolute failures and exposes more recipients before an operator can react. Reputation does not necessarily change at the same six-to-one rate, but the amount of campaign activity at risk is six times larger.
A lower per-inbox number requires more inboxes and domains to reach the same monthly target. That means making the infrastructure investment in domain capacity, mailbox capacity, DNS work, authentication, renewals, monitoring, and suppression management at the beginning.
That investment creates a smaller unit of capacity at risk. When one sending domain deteriorates or has to be taken offline, less of the total campaign capacity is removed. Healthy remaining domains can continue operating while the affected capacity is inspected, rested, repaired, or replaced.
The opposite design minimizes the initial domain count but concentrates more production capacity behind each domain. Losing one domain removes a larger share of daily output. The replacement has to recover more capacity, and the ramp period creates a larger shortfall.
For a program targeting two million campaign emails across 22 business days, the required average is about 90,909 campaign sends per business day. A base of 24,000 inboxes spreads that target across about 3.8 campaign sends per inbox per business day. At five, the same base provides 2.64 million theoretical monthly campaign slots, leaving room for unavailable inboxes, paused domains, and normal operational variation.
This capacity calculation is not an inbox-placement forecast. It identifies how much room remains when the program does not plan every asset near its nominal output.
More domains do not make a sender invisible to email security gateways. Receivers can evaluate domain, IP, authentication, content, and recipient-response signals together. Five also does not repair poor targeting, inaccurate data, misleading copy, or unwanted email.
Horizontal scale works when each domain is treated as a legitimate sending identity. The M3AAWG guidance on sending domains warns that lookalike or "cousin" domains can resemble phishing. Domains should be recognizable, properly authenticated, consistently operated, and connected to legitimate sender information.
The objective is not to cycle through disposable domains. It is to avoid placing an unnecessary share of production capacity behind any single domain.
Five covers campaign activity: first touches and automated follow-ups sent by the sequencer.
A genuine reply to a prospect does not reduce the five campaign-send allocation. It is still real mailbox traffic and should be included when reviewing total activity, but it is not another campaign touch. Warm-up messages are also outside the five campaign sends and still belong in total-load and pacing calculations.
The usual planning model uses approximately 22 business days per month. Sending on weekends changes monthly capacity and traffic patterns, but it does not change the concentration argument.
Five is a planning number, not a technical maximum. A mature program may choose a higher allocation when its list quality, recipient response, provider feedback, bounce patterns, complaint signals, and domain history support it.
That decision should include the cost of failure. Before increasing per-inbox volume, calculate how many daily and monthly campaign slots disappear if one domain is removed, how long replacement capacity takes to ramp, and how much unused capacity remains elsewhere in the portfolio.
A smaller initial infrastructure footprint concentrates more campaign output on every domain. Building the wider base at the beginning is the wiser investment for scaled outbound because one domain problem removes less of the operation and creates a smaller replacement gap.
Size domains and density to your sending target and see the capacity that holds.
Build My Sending Plan