---
title: "5,000 cold emails a day, agency setup | Cold Email Infrastructure Recipe"
description: "Agency scale across two pools, where the domain count becomes the thing you manage."
url: https://warminboxes.com/recipes/5000-emails-a-day
breadcrumb: "Home > Infrastructure recipes > 5,000 cold emails a day, agency setup"
---
Infrastructure recipe

# 5,000 cold emails a day, agency setup

Agency scale across two pools, where the domain count becomes the thing you manage.

**5,000 sends a day needs 1,200 inboxes across 77 domains, costing $2,290 a month** — prewarmed, sized for a list that is 55% Google, 40% Microsoft and 5% other. That is 110,000 sends a month across 22 sending days.

## The pools

- **Google Workspace** — 3,000 sends/day from 200 inboxes across 67 domains, at 15/day each and 3 per domain. $1,600/month.
The 55% on Google, plus the 5% elsewhere

- **Azure** — 2,000 sends/day from 1,000 inboxes across 10 domains, at 2/day each and 100 per domain. $690/month.
The 40% on Microsoft 365 and Outlook

## Right for

An agency running several clients, or one company at serious volume. At this size the per-send economics of the Azure pool matter enough to be worth the operational weight.

## Wrong for

Anyone who has not run 1,000 a day cleanly first. Scale multiplies whatever your list quality and copy already are, in both directions.

## In the sequencer

Segment by recipient provider, then shard each segment across the pool so no single domain carries a disproportionate share. Rotation becomes worth switching on here: it halves what is live at any moment and gives you somewhere to move when a domain degrades.

## Why these numbers

67 Google domains is the number that surprises people, and it is the direct consequence of 3 mailboxes per domain. Packing more mailboxes onto fewer domains concentrates reputation: one domain in trouble takes more of your sending with it.

The Azure side inverts that — 100 mailboxes to a domain, 2 sends each. The per-mailbox rate is what keeps a domain that dense survivable, and it is why the Azure numbers cannot be read with Google intuitions.

At this volume the bottleneck stops being mailboxes and starts being list quality. 5,000 sends a day is 110,000 a month, and a bounce rate that was survivable at 500 a day is a reputation problem at this one.

Budget for replacement. Across a fleet this size some mailboxes will degrade, and the plan above has no spare capacity in it.

No reserve capacity is included beyond rounding up. [Measure your own recipient mix →](https://warminboxes.com/esp-calculator)

[All infrastructure recipes →](https://warminboxes.com/recipes)