All articles

Scaling

How Many Mailboxes Do You Need for Cold Email?

Divide target sends by the safe per-inbox limit. Azure is 2 to 3 a day, Google up to 15. Everything else follows from that.

Key takeaway: Divide your target daily sends by the safe per-inbox limit for your provider. Azure is 2 to 3 a day, Google is up to 15. Then divide inboxes by 2 to 3 to get domains. Never solve a volume problem by pushing existing inboxes harder.

The most common way people burn cold email infrastructure is deciding they need more volume and getting it from the inboxes they already have. It works for about three weeks, then placement collapses and they cannot work out why.

Volume comes from breadth. More inboxes, more domains, same conservative per-inbox limits. Here is how to size it.

The formula

Inboxes = daily sends ÷ safe per-inbox limit

Azure domains = inboxes ÷ 100    Google domains = inboxes ÷ 3

The safe per-inbox limit is not a preference, it is set by the provider:

  • Microsoft Azure: 2 to 3 emails per inbox per day
  • Google Workspace: up to 15 emails per inbox per day

Inboxes per domain is not one number, it is provider specific. An Azure tenant of 100 accounts runs on a single domain, which is why the .com is bundled into the per-inbox price. Google runs 3 inboxes per domain, so a Google estate needs far more domains than an Azure one of the same inbox count.

Worked examples

Daily sendsAzure inboxesAzure domainsGoogle inboxesGoogle domains
500200235~12
1,000400470~24
2,000800813545
6,0002,40024400~134

Azure needs roughly five times the inboxes but far fewer domains, because 100 accounts sit on one domain. Google needs fewer inboxes but many more domains, each bought separately. At €0.30 per inbox with the .com included, 400 Azure inboxes across 4 domains cost less than 70 Google inboxes across 24 domains you have to register yourself.

Warm-up changes the timeline, not the maths

New inboxes do not send at full volume on day one. The ramp differs by provider:

Azure

Days 1 to 14: 5 warm-up emails a day, increasing by 1 per day, target reply rate 65 percent. From day 15: 2 cold emails a day with warm-up maintained at 5, and 60 to 80 minutes between sends.

Google Workspace

Sending limit 15 a day, warm-up limit 20 a day increasing by 2, reply rate 35 percent, 20 minutes between sends.

These are not interchangeable. Applying Google's numbers to an Azure tenant is the fastest way to lose it.

Pre-warmed inboxes skip this. They have already had four weeks of warm-up and are sending within about six hours of arriving, which matters if you are replacing a set mid-campaign.

Sizing for growth, not for today

Order for the volume you want in two months, not the volume you need this week. Warm-up takes two weeks and provisioning takes 24 hours, so infrastructure ordered today is at full capacity in roughly a fortnight.

The other thing to plan for is decay. Sets do not last forever, and reputation drifts down over months. Running a rotation means a replacement set is ordered at week four and takes over at week six, so you always have a warmed set ready rather than scrambling when numbers dip.

A sanity check. If your plan involves any inbox sending more than 3 a day on Azure or more than 15 on Google, the plan is wrong. Add inboxes instead. Infrastructure is cheap; a burned domain and a burned list are not.

Want this done for you?

Our Build and Release service stands up your entire cold email infrastructure: domains, mailboxes, authentication, warm-up, and tracking, all authenticated and ready to send. You skip the weeks of setup and start with campaigns.

Book a call