October 1, 2026 · LeadButton
How Many Domains and Inboxes for Cold Email? About 1 Inbox per 25 Sends a Day, and 3 Inboxes per Domain
One inbox per 25 cold sends a day, and no more than 3 inboxes per sending domain. At 500 emails a day that is 20 inboxes across 7 domains, roughly $146 a month in licenses and registrations. Nobody’s platform limit forces those numbers.
The ceilings Google and Microsoft publish are 20 to 80 times higher than the rate any cold program should run at, so the real constraint is reputation, not policy. This piece sits in our cold email deliverability hub and does four things: lays five vendors’ published per-inbox numbers side by side, explains why they differ by a factor of 33, gives the inbox and domain count at five volumes with the monthly cost, and names the documented platform limits you are nowhere near. Every external figure is linked and dated at the end.
How many cold emails can one inbox send per day?
Twenty-five is the planning number. Published recommendations from the companies that sell cold email software and inbox provisioning run from 3 a day to 100 a day, and 25 sits inside the band where four of the five agree. Treat it as the figure you build the spreadsheet on, then let your own bounce and complaint data move it.
Here is what each company publishes on its own site.
| Source | Cold sends per inbox per day | Inboxes per domain | Date on the page |
|---|---|---|---|
| PuzzleInbox | 15 on Google Workspace, 3 on Outlook 365 | Maximum 3 | 21 March 2026 |
| ScaledMail | 15 to 25 on Google Workspace and self-managed Microsoft 365, 5 to 10 on SMTP | 2 on Google Workspace, 2 to 3 on self-managed Microsoft 365, up to 25 on inboxes it provisions itself | 18 January 2026 |
| Instantly | 30, described as the point past which “spam risk” rises “exponentially” | Not stated. Advises rotating across 10 warmed inboxes to reach 300 a day | 25 November 2025, updated 29 September 2026 |
| Smartlead | 50 or fewer, with any one domain held under about 500 a day | Not stated. Says 8 mailboxes at 50 is safer than 1 at 400 | 25 September 2026 |
| MailReach | About 100 once warmed | 1 is “the ideal scenario” | Updated 11 February 2026 |
That last figure is the one to sit with. The argument is over whether the ceiling is 30 or 100, and the typical mailbox in the wild is sending 14.
Why do the published numbers differ by a factor of 33?
Because they are not answering the same question, and because the per-inbox number is meaningless without the inboxes-per-domain number beside it. Multiply the two and the disagreement mostly disappears.
MailReach’s 100 a day assumes one address on the domain, so its per-domain capacity is 100. Instantly’s 30 across 3 inboxes is 90. PuzzleInbox’s 15 across its maximum of 3 is 45. ScaledMail’s 25 across 2 is 50. Converted to per-domain-per-day, five sources that look 33 times apart land between 45 and 100. The spread is a disagreement about how many mailboxes a domain can carry before it looks like a sending farm, not about how much mail a domain can carry.
One row needs reading carefully. ScaledMail’s “up to 25 inboxes per domain” applies only to Microsoft 365 tenants it provisions and runs itself; for mail you set up yourself it publishes 2 to 3, the same as everyone else. A vendor’s best case for its own stack is not a planning number for yours.
This is the same pattern as the warmup literature, where published schedules run from 14 days to 8 weeks because each vendor is timing a different finish line. Before adopting anyone’s figure, check what it is counting.
How many domains and inboxes do you need at your volume?
Divide the daily target by 25 for inboxes, divide inboxes by 3 for domains, round up both times. At Microsoft 365 Business Basic and a .com registration, the hardware side of a cold email program costs less than most teams assume.
| Emails per day | Per month, at 22 business days | Inboxes | Domains | Licenses and domains per month |
|---|---|---|---|---|
| 100 | 2,200 | 4 | 2 | $29.84 |
| 250 | 5,500 | 10 | 4 | $73.68 |
| 500 | 11,000 | 20 | 7 | $146.44 |
| 1,000 | 22,000 | 40 | 14 | $292.88 |
| 2,000 | 44,000 | 80 | 27 | $584.84 |
Two things fall out of that table. The first is that infrastructure is not the expensive part of outbound; 1,000 emails a day costs under $300 a month in licenses and domains. The second is that the inbox count is the number that scales linearly and the domain count is the number that gets operationally awkward. Twenty-seven domains means 27 sets of SPF, DKIM and DMARC records, 27 registrations to renew, and 27 reputations to watch. That is the real cost of volume, and it is paid in attention rather than dollars.
Decide the volume from the pipeline you need, not from the capacity you can afford. Our own reading of the published figures found that answers on how many emails produce one meeting range from 33 to 6,275, so the honest way to size infrastructure is to pick a conservative figure from that range, work out the sends it implies, then buy the inboxes.
What do Google and Microsoft actually allow?
Far more than you should use. These are the documented ceilings, and the useful observation is the gap: a paid Google Workspace mailbox is allowed 2,000 messages a day, which is 80 times the 25 a day a cold mailbox should run at. The platform is never the constraint.
| Limit | Number | Source |
|---|---|---|
| Google Workspace, paid account | 2,000 messages per day per user | Google Workspace Admin Help |
| Google Workspace, trial account | 500 messages per day | Same page |
| Google Workspace, total recipients | 10,000 per day per user | Same page |
| Google Workspace, recipients per message over SMTP, POP or IMAP | 100 | Same page. Most sequencers send this way |
| Exchange Online, per user | 10,000 recipients per day and 30 messages per minute, both hard limits that cannot be raised | Microsoft Learn |
| Exchange Online, tenant external recipient rate limit | 5,000 external recipients per day on a trial tenant, scaling with license count on paid tenants | Same page. The paid tiers are not published; admins read their own figure in the Exchange admin center |
| Exchange Online, unconfigured onmicrosoft.com domain | 100 external recipients per 24 hours for the whole organization | Same page |
| Gmail spam complaint rate | Below 0.10%, never reaching 0.30% | Google, Email sender guidelines |
The rows that actually bite are the last two. A tenant running on its default onmicrosoft.com domain is capped at 100 external recipients a day across the entire organization, which is why a new Microsoft tenant appears broken before anyone has configured a custom domain. And the only ceiling that ends programs is the complaint rate, which has nothing to do with how many inboxes you own.
What changes at 5,000 a day?
Both consumer mail providers draw a line at 5,000 messages a day, and both count it per sending domain rather than per mailbox. Since 1 February 2024, anyone sending more than 5,000 messages a day to personal Gmail accounts must have SPF and DKIM and DMARC in place and must support one-click unsubscribe on marketing mail. Since 5 May 2025, Microsoft applies the same threshold to Outlook.com, Hotmail.com and Live.com, requiring SPF, DKIM and DMARC at a minimum of p=none, and rejecting non-compliant mail outright with 550 5.7.15 rather than filing it in Junk.
Spreading 2,000 sends a day across 27 domains keeps each domain far under either threshold, and that is a real consequence of the architecture rather than a trick. It is also not a reason to skip any of it. SPF, DKIM and DMARC cost an afternoon, the complaint-rate thresholds apply at every volume, and a program that only passes authentication because it stayed small is one list purchase away from failing.
What makes the inbox count irrelevant?
Five things, each of which wastes the whole investment:
- DNS that does not pass. SPF, DKIM and DMARC have to be correct on every domain before the first send, verified by reading the headers on a seed message rather than trusting a setup wizard.
- No ramp. A new mailbox set to 25 a day on day one sends 25 on day one, which is exactly the volume spike Google’s guidelines tell senders to avoid.
- A list that generates complaints. Every inbox on a domain shares its reputation, so the causes that put cold email in spam scale with the inbox count instead of being diluted by it.
- Cold mail from the company’s primary domain. The domain that carries invoices and contracts should never carry prospecting, which is what makes a strict DMARC policy on it possible.
- Inboxes stacked beyond 3 to a domain to save on registrations. Saving $0.92 a month on a domain to put 10 mailboxes on one host is the cheapest way to lose all 10.
How LeadButton handles this
We buy and configure the sending domains, hold inboxes to 3 per domain and roughly 25 cold sends each per day, ramp every new mailbox over three to four weeks, and keep the client’s primary domain out of the sending pool entirely. The infrastructure is part of the retainer rather than a setup fee: Launch is $1,500 a month for managed email outreach, Growth is $3,500 a month for email plus LinkedIn, and Scale is quoted for programs that need more volume or more markets than Growth covers. The tiers are set out on the LeadButton pricing page.
The number that matters in a proposal is not how many inboxes someone will run. It is how many sends a day they plan per inbox, and how many inboxes per domain. If an agency will not say, you are buying a sending farm.
Sources
- Google Workspace Admin Help, Gmail sending limits in Google Workspace, checked 1 October 2026. Source for 2,000 messages a day on paid accounts, 500 on trial accounts, 10,000 recipients a day, 100 recipients per message over SMTP, POP and IMAP, and the rolling 24-hour window.
- Google, Email sender guidelines, checked 1 October 2026. Source for the 5,000 messages a day bulk sender threshold effective 1 February 2024, the SPF, DKIM and DMARC requirement, one-click unsubscribe, and the 0.10% and 0.30% spam rate thresholds.
- Microsoft Learn, Exchange Online limits, checked 1 October 2026. Source for 10,000 recipients a day, 30 messages a minute, the 5,000 external recipient trial tenant limit, the statement that the paid tenant figure scales with license count and is read in the Exchange admin center, and the 100 external recipient cap on unconfigured onmicrosoft.com domains.
- dmarcian, Microsoft enforces SPF, DKIM and DMARC, updated 2 May 2025, checked 1 October 2026. Source for Microsoft’s 5,000 a day high-volume sender threshold, the 5 May 2025 enforcement date, the p=none minimum and the 550 5.7.15 rejection. Microsoft’s own announcement would not render its body to our fetcher.
- PuzzleInbox, How many inboxes for cold email, 21 March 2026, checked 1 October 2026. Source for 15 cold sends a day on Google Workspace, 3 on Outlook 365 and a maximum of 3 inboxes per domain. PuzzleInbox sells cold email infrastructure.
- ScaledMail, How many inboxes per domain for cold email, 18 January 2026, checked 1 October 2026. Source for 15 to 25 cold sends per inbox, 2 inboxes per domain on Google Workspace, 2 to 3 on self-managed Microsoft 365 and up to 25 on tenants it provisions. ScaledMail sells provisioned inboxes.
- Instantly, Agency guide to unlimited sending accounts, 25 November 2025, updated 29 September 2026, checked 1 October 2026. Source for the 30 campaign emails per inbox per day cap and the 10 inboxes for 300 a day example. Instantly sells a cold email platform.
- Smartlead, How many cold emails should you send per day per domain, 25 September 2026, checked 1 October 2026. Source for 50 or fewer per mailbox, under about 500 per domain per day, the 8 mailboxes versus 1 comparison and the median of 14 cold emails a day per mailbox on its platform. Smartlead sells a cold email platform.
- MailReach, How many cold emails to send per day, updated 11 February 2026, checked 1 October 2026. Source for roughly 100 cold emails a day per inbox and the one address per domain ideal. MailReach sells warmup software.
- Microsoft 365 business plan comparison, checked 1 October 2026. Source for Business Basic at $7.00 per user per month on an annual subscription.
- Porkbun domain pricing, checked 1 October 2026. Source for the .com registration and renewal price of $11.08 a year.
- Cloudflare Registrar, checked 1 October 2026. Source for at-cost pricing with no markup over the registry and ICANN fee.
Leave a Reply