How many cold emails to send per day (from 5 million real sends)

I sent over 5 million cold emails in the past 12 months. So when someone asks how many cold emails to send per day, I don't guess. The answer is 20 to 30 per inbox per day, and the ceiling is 50. Everything past that is where deliverability goes to die.

That answer feels small. It's supposed to. The per-inbox cap is not where volume comes from. Volume comes from infrastructure: more inboxes across more domains, each one held at a boring, human-looking number and ramped up on a schedule.

Most articles on this question are written by companies that sell warmup tools, so the advice always ends in the same place. (buy more warmup. shocking.) I run the sending, not the tooling, so this is the version with the numbers we actually hold.

How many cold emails to send per day, in 3 numbers

If you only take one section from this post, take this one:

1. 20 to 30 cold emails per inbox, per day. Hard ceiling of 50.
2. Inboxes per domain depends on your provider. 2 to 3 on Google. Up to 100 on Microsoft, where the standard build is one domain to one tenant to 100 mailboxes.
3. Per-domain volume follows from that, not from a universal number: 40 to 90 cold sends a day on a Google domain, and on Microsoft the mailbox count is the constraint rather than the domain.

Need 1,000 sends a day? That's roughly 40 inboxes either way, not one inbox working overtime. On Google that means 15 to 20 domains. On Microsoft it can be a single tenant using 40 of its 100 mailboxes. A mature campaign on our side runs around 10,000 emails a day, and every single inbox inside it still obeys the small numbers above.

The official provider limits are a trap

Google Workspace technically lets one account send 2,000 emails a day. Microsoft 365 allows up to 10,000 recipients per mailbox per day. Cold email tools will happily let you schedule against those caps.

Do not confuse a ceiling with a budget.

Those limits exist for regular business mail: invoices, newsletters people opted into, internal threads. Spam filters act on behavior long before you touch an official cap. An inbox that jumps from zero to 500 cold sends looks exactly like what it is, and both providers have spent the last two years getting much better at ending it.

Google's email sender guidelines now treat anyone sending 5,000+ messages a day to Gmail as a bulk sender: mandatory SPF, DKIM and DMARC, one-click unsubscribe, and a spam complaint rate under 0.3% (under 0.1% if you want to sleep at night). Microsoft stacked tenant-wide external recipient limits on top of the per-mailbox cap. The direction is obvious. The free-volume era is over, and honestly, good. It's the reason doing this properly still works at all.

How many cold emails per day per inbox, and why

20 to 30. Here's the mechanism, because the number is useless without it.

A real human at a real company sends a few dozen external emails a day, gets replies, sits in threads. That's the pattern the filters consider normal. Keep an inbox inside that shape, with warmup replies still trickling through, and it stays boring. Boring is the goal.

Push the same inbox to 80 or 100 a day and 2 things break:

• The send-to-reply ratio stops looking human. Nobody sends 100 cold messages and gets 2 replies without tripping a pattern detector.
• One bad day compounds. At 30 a day, a bounced batch is a blip. At 100 a day, the same list problem torches the domain, and recovery takes weeks, not days.

We run a 60/40 split of Microsoft and Google inboxes across the whole infrastructure, and the cap is the same on both sides. The filters differ; the safe human range doesn't.

How many emails per day per domain

Here is where nearly every guide gets it wrong, including ours until we corrected it. How many emails you can send per inbox per day is provider-independent: 20 to 30, on Google and Microsoft alike. How many you can send per domain is not. It depends entirely on which provider that domain sits on, and the two are nothing alike.

• Google: 2 to 3 mailboxes per domain.Stack more and you concentrate the risk, because everything rides on that one domain's reputation. At 20 to 30 per inbox, a fully ramped Google domain carries 40 to 90 cold sends a day. That is the number people usually quote as universal. It is not universal. It is Google.
• Microsoft: up to 100 mailboxes per domain. The standard build is one domain to one tenant to 100 mailboxes, and the tenant is billed flat regardless of how many of those slots you fill. On this side the domain stops being the unit you plan around. The mailbox count is the constraint.

So the useful way to size an outbound system is inboxes first, domains second. Work out how many inboxes your target volume needs, then let the provider decide how many domains that becomes:

• 1,000 sends a day is roughly 40 inboxes. On Google that is 15 to 20 domains. On Microsoft it can be a single tenant with 40 of its 100 slots in use.
• 10,000 sends a day is roughly 400 inboxes. On Google that is 130 to 200 domains, which is a genuine operational burden. On Microsoft the same volume needs far fewer domains to administer.

That gap is most of the reason our infrastructure runs 60/40 rather than all-in on either one. Google domains cost more to operate at volume; Microsoft tenants concentrate more of the operation behind fewer names. Running both means a bad week on one platform never takes the whole pipeline with it. The full breakdown of what that costs and how it gets built lives in cold email infrastructure.

How to ramp a new domain from zero to full volume

A cold email ramp up schedule for a new domain is not optional, and it starts before the first cold send:

1. Day 0: buy the domain, set up SPF, DKIM and DMARC, redirect it to your main site.
2. Days 1 to 14: automated warmup only. Zero cold sends. Fourteen days is the minimum; three weeks is safer.
3. Then ramp, per inbox, on this schedule:

One rule overrides the whole table: if deliverability slips, NEVER add more emails (we run plain text with no open tracking, so the signals are bounces, spam complaints, and inbox placement, not opens). Volume is earned. If bounces climb or complaints rise in week 2, you fix the list or the setup. You do not push to week 3 because the calendar says so.

From domain purchase to full volume is about six weeks. Anyone promising full volume in one week is about to teach you an expensive lesson with your own domains.

How many cold emails can you send without going to spam?

Wrong shape of question, and I say that kindly, because the honest answer is more useful: there is no single number. Spam placement is triggered by behavior, and 3 behaviors do almost all the damage:

1. Volume spikes.Thirty a day for two weeks, then 300 on a Monday because pipeline looked thin. Filters key on deviation from your own baseline more than on any absolute number. Spikes are the fastest way I've watched senders erase months of reputation in one afternoon.
2. List quality. A dirty list pushes bounces over 2%, and bounce rate feeds sender reputation directly. A clean, verified list at 10,000 sends a day is safer than a scraped one at 500.
3. Broken authentication.If SPF, DKIM and DMARC aren't aligned, nothing else in this post matters. You're filtered before a human ever sees subject line one.

Get those three right and hold the per-inbox caps, and total volume scales with infrastructure, not risk. That's how you reach hundreds of thousands of prospects a month without landing in spam: never by making any single inbox work harder.

Deliverability only gets you into the inbox, though. What happens next is decided by the list and the offer, and that's a different post: here's what cold email reply rates actually look like across real campaigns.

What 10,000 cold emails a day actually looks like

I quoted the 10,000-a-day campaign earlier. Here's what sits underneath it, because "we send at scale" sounds impressive right up until you see the spreadsheet:

• → Roughly 400 inboxes, each capped at 20 to 30 cold sends a day.
• → 130 to 200 sending domains, each carrying 2 to 3 inboxes.
• → A 60/40 split of Microsoft and Google inboxes, because your buyers live on both, and when one ecosystem has a rough week the other keeps the pipeline alive.
• → Zero cold sends from the primary domain. Ever. The main domain is for real conversations with real prospects.

Domains age, inboxes get flagged, pieces get rotated and rebought on a cycle. It's a bit of a pain, but that's the job. This unglamorous inventory management is a solid chunk of what GTM engineering actually is once you strip the shine off the job title.

Work the math backwards from booked calls

The better question was never how many you can send. It's how many you need.

Here's the math we run before sizing any campaign. On a tight, intent-based list, 500 to 1,000 right-fit companies convert to 25 to 50 qualified calls, roughly a 5% rate. So if you need 25 calls a month, you need about 500 genuinely right companies a month, times 3 to 4 emails per company across a sequence. That's 1,500 to 2,000 sends: two or three domains' worth of daily capacity. Most founders massively oversize the infrastructure and undersize the list.

The 5% holds on intent: companies hiring for the role you replace, spending on ads, actively posting. On a broad scraped list it falls off a cliff, and no amount of daily volume brings it back. Our infrastructure booked 3,000+ sales calls for clients in the past year, and a vast majority came from prospects showing intent, not from turning the volume dial.

And here's what the tool vendors will never admit: even our own outbound has months where we book 5 calls from email alone. That's not a broken system. That's cold email doing the only job it does now, opening the top of the funnel. Judge the channel by qualified pipeline over quarters, not by any single week's send count.

tl;dr: 20 to 30 per inbox per day, 2 to 3 inboxes per domain, 14+ days of warmup, a 4-week ramp, and scale with more domains, never with a bigger daily limit.

Frequently asked questions

PS - one client closed a $250k deal off a 50-word email. The email was plain. The infrastructure underneath it was not.

If you'd rather skip six weeks of domain shopping and inbox babysitting, that's fair. Building and running this machine for B2B service businesses is what we do all day as a growth partner. If you want to see what the sends-to-calls math looks like for your market, book a calland we'll walk through it with real numbers. More field notes like this one live on the blog index.