Blog / Guides

Cold Email Infrastructure for Agencies: How to Scale

8 June 2026

Cold email infrastructure for agencies is the same setup individual senders use — dedicated domains, many mailboxes — but multiplied across clients and kept strictly isolated per account. The hard part is not the technology. It is scale: keeping every client’s reputation separate, running enough domains to hit each client’s volume, and absorbing the work of provisioning and rotating it all without a full-time infrastructure team.

This guide is for agencies that send outbound on behalf of clients. It covers why per-client isolation matters, how to size domain count, how per-domain cost makes margins predictable, and where the operational time goes. New to the underlying components? Start with what cold email infrastructure is.

Why per-client isolation is non-negotiable

The first rule of agency infrastructure is that no two clients should ever share sending reputation. Reputation travels with the domain and, more broadly, with the IP space and the sending org. If Client A’s campaign draws complaints or hits a blocklist, that damage must not touch Client B.

Sharing infrastructure across clients creates correlated risk. One aggressive or poorly targeted client can degrade deliverability for everyone in the same pool, and you have no clean way to quarantine the problem. Isolation means separate domains per client, and ideally separate Microsoft 365 tenants — an isolated Microsoft 365 organisation with its own users and settings — so the blast radius of any single failure is one client, not your whole book.

It is also a trust point. When a client asks whether their sending is mixed in with other agencies’ traffic, “every account is on its own isolated tenant” beats “we use a shared pool.”

How many domains an agency needs

Domain count is driven by volume, not by client count alone. The arithmetic is simple once you fix the per-mailbox rate.

Each domain hosts a number of mailboxes — up to 100, with 50 to 100 being typical for cold email. Each mailbox sends a small, deliberately capped number of messages per day, because spreading volume across many low-volume mailboxes looks like human email rather than bulk. So the levers are: mailboxes per domain, sends per mailbox per day, and domains per client. See how many mailboxes per domain and how many domains for cold email for the full reasoning.

On top of raw capacity, agencies run several overlapping domains per client so they can rotate. Sending domains wear out under sustained volume — their reputation degrades, often within a few months — so you retire worn domains and bring fresh ones online without a gap in sending. A client doing meaningful volume runs a rotating set, not one domain. Why cold email domains burn out covers the mechanics.

Client volume	Rough domain footprint	Why
Small / testing	1–2 active domains	Low daily send, little rotation needed
Steady outbound	3–6 active domains	Headroom plus overlap for rotation
High volume	Several+ rotating domains	Capacity and continuous replacement of worn domains

These are illustrative bands, not fixed rules — the right number depends on the client’s actual target volume and how fast their domains wear.

Predictable per-domain cost

The hardest part of agency economics is pricing your own service when costs are lumpy. Per-mailbox metering makes it worse: costs jump every time you add a mailbox. Per-domain pricing is easier to reason about because the domain is the unit you already plan around for capacity and rotation.

When the cost unit is the active domain, your spend tracks the number of domains in rotation, which you control directly. You can quote a predictable margin: plan size determines domain count, domain count determines your cost, and the difference is your markup. No surprise line items when a campaign scales mailbox count within a domain.

Pricing model	What you pay for	Forecasting
Per mailbox	Each individual inbox	Harder — cost moves with mailbox count
Per active domain	The domain in rotation	Easier — cost tracks domains you plan anyway

For a deeper comparison, see per-mailbox vs per-domain pricing and the broader cold email infrastructure cost breakdown.

Where the operational load actually goes

For an agency, the cost that quietly eats margin is not software licences — it is manual operations. Multiply the setup work for one sending account by every client and every domain, and the labour adds up fast:

• Provisioning. Buying domains, creating mailboxes, assigning distinct human sender names so messages do not look templated.
• Authentication. Setting SPF, DKIM, and DMARC correctly for every domain. Misconfigured records are a leading cause of new domains landing in spam.
• Warmup. Ramping each new mailbox’s volume gradually over its first weeks instead of sending at full rate immediately.
• Rotation. Watching for worn domains and replacing them before they drag down a campaign — continuously, across the whole client base.
• Sequencer connection. Wiring each set of real mailboxes into the campaign tool so outbound can actually run.

Done by hand, this is a recurring, error-prone workload that scales linearly with clients. The two ways out are building internal tooling or using managed infrastructure that handles provisioning, authentication, warmup, and replacement for you. Either way, the goal is to stop spending senior time on plumbing. Manual vs managed cold email infrastructure weighs the trade-off.

A checklist for agency-grade setup

Agency infrastructure that scales tends to share these traits:

• One isolated tenant and dedicated domains per client — no shared reputation.
• Enough domains per client to cover volume plus overlap for rotation.
• Real Microsoft 365 mailboxes, not shared SMTP relays, for isolation.
• Correct SPF, DKIM, and DMARC on every sending domain.
• Automatic warmup on every new mailbox.
• A repeatable process for retiring worn domains and standing up fresh ones.
• A cost model you can forecast and mark up cleanly.

How Mailionaire approaches this

Mailionaire is built for exactly this multi-client shape: each sending domain gets its own isolated Microsoft 365 tenant with up to 100 real mailboxes, distinct sender names, and SPF, DKIM, and DMARC set up automatically — so one client’s problems stay contained to that client. Pricing is a flat $50 per month per active domain, which keeps your per-client margins easy to forecast, and we monitor and replace worn mailboxes and domains as they wear out so rotation stops being manual work. EU/Swiss data residency is available as an option for clients who need it, though US IP space is the default. See how it works for the full provisioning flow.

FAQ

Why should agencies isolate each client's cold email infrastructure?

Isolation keeps one client's complaints, bounces, and blocklistings from affecting another's deliverability. Separate domains and separate Microsoft 365 tenants mean a problem with one account stays contained, which protects your other clients and your agency's reputation.

How many domains does an agency need per client?

It depends on volume. Each domain hosts up to 100 mailboxes, and each mailbox sends a small daily amount, so the domain count follows the target send volume. Agencies typically run several overlapping domains per client and rotate them as they wear out.

What is the main operational cost of running cold email at agency scale?

Not the software — the manual labour. Buying domains, provisioning mailboxes, setting SPF, DKIM, and DMARC, configuring warmup, and replacing worn domains across dozens of clients is the real load. This is what managed infrastructure or internal tooling is meant to remove.

Does running a client's infrastructure make their cold email legal?

No. Infrastructure decides where mail is sent from and how it is authenticated, not whether the recipient consented. Many markets, including Germany under UWG §7(2), require opt-in even for B2B. The sender remains responsible for consent and local law. This is not legal advice.

---