Cold Email Infrastructure for Agencies: The Complete Guide
Key Takeaways
- Client isolation is non-negotiable. Each client must have dedicated domains and mailboxes. Shared infrastructure creates cross-client reputation contamination.
- Plan for 5-10 domains and 15-40 mailboxes per client depending on their volume requirements.
- White-label infrastructure lets agencies resell email infrastructure under their own brand, creating a recurring revenue stream.
- Centralized monitoring with per-client views is essential — you need to see the health of every client’s infrastructure from a single dashboard.
- Warmup pipelines must be continuous. An agency running 10 clients needs replacement domains warming at all times.
Why Agency Infrastructure Is Different
Running cold email infrastructure for a single company is straightforward. Running it for 10, 20, or 50 clients is an entirely different operational challenge.
The core difference is isolation. When you manage a single company’s outbound, all domains, mailboxes, and campaigns serve the same brand. Reputation is pooled, and that is fine — it is all one sender. When you manage multiple clients, reputation must be strictly separated. Client A’s aggressive campaign should never impact Client B’s inbox placement.
This guide covers the infrastructure architecture, domain strategy, warmup operations, monitoring, and scaling playbook that agencies need to run multi-client cold email profitably and reliably.
Infrastructure Architecture for Agencies
The Three-Layer Model
Agency cold email infrastructure has three layers:
Layer 1: Sending Platform This is your campaign management tool — Instantly, Smartlead, Lemlist, or similar. It handles sequences, scheduling, and analytics. Most agencies choose one platform and standardize on it across clients.
Layer 2: Infrastructure This is the domains, mailboxes, DNS configuration, warmup, and monitoring that sit beneath the sending platform. This is what this guide focuses on.
Layer 3: Lead Data Prospect lists, enrichment, verification. Important, but separate from infrastructure.
The critical principle: Layer 2 must be isolated per client. Layers 1 and 3 can be shared (the same Smartlead account, the same data provider) as long as Layer 2 is separated.
Per-Client Isolation Requirements
| Component | Isolated per Client? | Why |
|---|---|---|
| Domains | Yes (mandatory) | Domain reputation is the primary deliverability signal. Cross-client sharing means one client’s bad campaign poisons another’s domains. |
| Mailboxes | Yes (mandatory) | Mailbox reputation is tied to sending behavior. Each client’s behavior profile must be independent. |
| DNS records | Yes (automatic) | DNS is per-domain, so isolation follows from domain isolation. |
| Warmup | Yes (recommended) | Warmup builds reputation per mailbox. Mixing clients in warmup schedules creates operational confusion. |
| Monitoring | Per-client views (mandatory) | You need to diagnose issues at the client level. Aggregate monitoring hides per-client problems. |
| Sending platform | Shared OK (with sub-accounts) | Sub-accounts in Smartlead or workspaces in Instantly provide sufficient campaign isolation. |
Domain Strategy per Client
How Many Domains per Client
The formula is the same as for any cold email operation, but applied per client:
Domains per client = Client's daily volume / (40 emails × 3 mailboxes per domain)Typical agency client profiles:
| Client Type | Daily Volume | Domains Needed | Mailboxes Needed |
|---|---|---|---|
| Small client (SMB, startup) | 200-400/day | 2-3 | 8-12 |
| Medium client (mid-market SaaS) | 500-1,000/day | 5-8 | 15-25 |
| Large client (enterprise, staffing) | 1,000-3,000/day | 10-20 | 30-80 |
Domain Naming for Agency Clients
Each client’s domains should be branded to that client, not to your agency. If your client is “Acme Solutions” with the primary domain acmesolutions.com:
- Good: getacme.com, acmeteam.com, tryacmesolutions.com
- Bad: youragency-acme.com, agency-client-acme.com
The domains represent the client’s brand in the recipient’s inbox. They should look like the client’s own outreach, not your agency’s infrastructure.
Domain Ownership
Establish clear domain ownership from the start. Two models:
Agency-owned domains: You purchase and manage the domains. The client pays for infrastructure as part of your service fee. You retain control, which simplifies management but creates a dependency — if the client leaves, they lose their domains and reputation.
Client-owned domains: The client purchases the domains (or you purchase them on their behalf and transfer ownership). The client owns the asset. If they leave your agency, they keep their domains and accumulated reputation.
Recommendation: Client-owned domains with agency management access. This gives you operational control while the client retains the asset. It also reduces churn risk — clients are less likely to leave when they know their infrastructure is portable.
Mailbox Provisioning at Scale
Google Workspace vs Microsoft 365 for Agencies
Most agencies standardize on one provider for operational simplicity. The tradeoffs:
Google Workspace:
- Better deliverability to Gmail recipients (roughly 60% of business email)
- Easier OAuth integration with most sending platforms
- Google Postmaster Tools provides direct reputation visibility
- Admin console is straightforward for bulk management
Microsoft 365:
- Better deliverability to Outlook/Hotmail recipients (roughly 30-35% of business)
- Some compliance-heavy clients require Microsoft
- SNDS provides some reputation visibility
Best practice for agencies: Use Google Workspace as your default, with Microsoft 365 available for clients that specifically need it or for diversification. A mix of 70% Google / 30% Microsoft covers the full recipient spectrum.
Bulk Provisioning
At 10+ clients, manually creating mailboxes through the Google Admin console is not scalable. You need:
- API-based provisioning: Google Workspace Admin SDK and Microsoft Graph API allow programmatic user creation.
- Template-based DNS: Standardize your DNS records so each new domain follows the same configuration template.
- Automated warmup enrollment: New mailboxes should automatically enter the warmup pipeline.
Outspun’s Agency plan includes a bulk provisioning API that handles all three steps. Submit a domain and mailbox count, and the system provisions Google Workspace accounts, configures DNS records, and enrolls mailboxes in warmup — all via API call.
Warmup Operations for Agencies
The Agency Warmup Pipeline
An agency with 10 active clients needs a continuous warmup pipeline. Here is how it works:
Active pool: Mailboxes currently sending campaigns. These should still receive low-volume warmup to maintain positive engagement signals.
Warmup pool: New mailboxes in the 3-4 week warmup phase. These are not yet assigned to campaigns.
Resting pool: Mailboxes or domains that have been pulled from active use due to reputation decline. They receive warmup-only traffic while reputation recovers.
Reserve pool: Fully warmed mailboxes ready to replace any mailbox that needs to be rested.
Pipeline Sizing
| Agency Size | Active Clients | Active Mailboxes | Warmup Pipeline | Reserve |
|---|---|---|---|---|
| Small agency | 3-5 | 30-60 | 10-15 | 5-10 |
| Medium agency | 5-15 | 60-200 | 20-40 | 10-20 |
| Large agency | 15-50+ | 200-800+ | 50-150 | 30-80 |
Rule of thumb: Keep 20-25% of your total mailbox count in the warmup and reserve pools combined. This ensures you can handle domain burns, client onboarding, and volume increases without delays.
Per-Client Warmup Isolation
Each client’s warmup should be tracked separately. Why:
- Different clients start at different times.
- Different clients have different volume targets (and therefore different warmup schedules).
- When a client churns, their warmup resources should be decommissioned cleanly without affecting other clients.
- Performance attribution requires per-client visibility — if warmup metrics are poor, you need to know which client is affected.
Monitoring and Reporting
What Agencies Must Monitor
| Metric | Frequency | Per Client? | Action Threshold |
|---|---|---|---|
| Domain reputation (Google Postmaster) | Weekly | Yes | Drop below “Medium” — investigate |
| Spam rate (Google Postmaster) | Weekly | Yes | Above 0.1% — adjust volume. Above 0.3% — pause domain |
| Blacklist status | Daily | Yes | Any listing — immediate investigation |
| Bounce rate | Per campaign | Yes | Above 3% — check list quality. Above 5% — pause and clean list |
| Warmup inbox placement | 2x/week | Yes | Below 85% — investigate warmup issues |
| SPF/DKIM/DMARC pass rate | Weekly | Yes | Below 99% — investigate DNS configuration |
Building a Client Dashboard
Agencies need two views:
Agency overview: A single dashboard showing the health of all clients at a glance. Color-coded (green/yellow/red) per client. This is your daily operational view — it tells you where to focus attention.
Client detail: Drill-down view for each client showing domain-level metrics, mailbox-level performance, warmup status, and campaign delivery stats. This is what you use for client reporting and troubleshooting.
Outspun’s monitoring service provides both views. The agency dashboard shows per-client health at ₹1,499 per 10 domains/month, and integrates with Google Postmaster Tools for direct reputation data. See our Google Postmaster Tools guide for setup.
Client Reporting
Most agency clients do not understand (or care about) the technical details of infrastructure. They care about results: meetings booked, replies received, inbox placement rates.
A good client report includes:
- Inbox placement rate: Percentage of emails reaching primary inbox
- Domain health status: Simple green/yellow/red indicator
- Volume delivered vs planned: Are you hitting the agreed-upon daily send target?
- Reply rate: The client’s primary success metric
- Recommendations: Any infrastructure adjustments needed (more domains, list quality issues, etc.)
Keep reports simple. Infrastructure is your operational concern, not the client’s.
White-Label Infrastructure
What White-Label Means for Agencies
White-label infrastructure lets you resell email infrastructure under your own brand. Instead of telling clients “we use Outspun for infrastructure,” you present it as “our proprietary infrastructure platform.”
This has several benefits:
- Recurring revenue: Infrastructure becomes a line item in your client billing, not a pass-through cost.
- Stickiness: Clients who use your branded infrastructure are less likely to churn — switching agencies means rebuilding infrastructure.
- Professional positioning: A branded dashboard positions you as a technology-enabled agency, not just a freelancer with a Smartlead account.
White-Label Setup
Outspun’s white-label dashboard is available at ₹14,999/month. It includes:
- Your agency’s branding (logo, colors, domain)
- Client-facing health dashboards
- Per-client reporting
- API access for integration with your existing agency tools
You set your own markup. If Outspun charges you ₹7,999/month for a Starter-equivalent setup, you might bill your client ₹15,000-25,000/month for “managed infrastructure” — a healthy margin that scales with your client count.
Scaling the Agency: From 3 Clients to 30
Phase 1: 1-3 Clients (Bootstrap)
At this stage, you can manage infrastructure semi-manually.
- Total domains: 10-20
- Total mailboxes: 30-60
- Management approach: Spreadsheet tracking, manual DNS configuration, basic monitoring
- Recommended infrastructure: Outspun Growth plan (15 domains, 60 mailboxes at ₹19,999/month) covers 2-3 small-to-medium clients
Phase 2: 4-10 Clients (Systematize)
Manual management breaks down. You need systems.
- Total domains: 30-80
- Total mailboxes: 80-250
- Management approach: Standardized onboarding process, automated DNS templates, centralized monitoring dashboard
- Recommended infrastructure: Outspun Agency plan (40+ domains, 160+ mailboxes at ₹49,999/month) or a custom configuration with a la carte pricing
- Key investment: Set up the monitoring dashboard and establish a weekly review process
Phase 3: 10-30+ Clients (Operationalize)
At this scale, infrastructure management is a dedicated operational function.
- Total domains: 100-500+
- Total mailboxes: 300-1,500+
- Management approach: API-driven provisioning, automated monitoring and alerting, dedicated infrastructure team member or managed service
- Recommended infrastructure: Custom agency pricing with Outspun, potentially with white-label dashboard
- Key investment: Hire or designate an infrastructure operations person. At 15+ clients, the monitoring, warmup, rotation, and troubleshooting workload justifies a part-time or full-time role
Common Agency Mistakes
Mistake 1: Sharing Domains Across Clients
This is the most dangerous mistake. A domain used for Client A’s aggressive recruitment campaign will carry that reputation when used for Client B’s B2B SaaS outreach. If Client A burns the domain, Client B’s deliverability suffers.
Fix: Strict per-client domain isolation. No exceptions.
Mistake 2: Underprovisioning Infrastructure for New Clients
New agencies often onboard a client, spin up 2 domains with 5 mailboxes, and promise 1,000 emails/day. The math does not work. Two domains with 5 mailboxes can support roughly 150-200 emails/day, not 1,000.
Fix: Use the domain planning formula before making volume commitments. Under-promise, over-deliver.
Mistake 3: No Buffer for Client Churn
When a client leaves, their domains and mailboxes are decommissioned. If you have been running at maximum capacity with no reserve, losing a client does not free up resources — it just shrinks your capacity. Meanwhile, new clients need freshly provisioned and warmed infrastructure that takes 4-6 weeks to prepare.
Fix: Maintain the warmup pipeline. Always have at least one client’s worth of infrastructure in the warmup queue.
Mistake 4: Skipping the Warmup for Impatient Clients
Clients want results immediately. The 4-6 week infrastructure setup and warmup period is hard to sell. Some agencies skip or abbreviate warmup to meet client expectations.
Fix: Set expectations during the sales process. Infrastructure setup takes 4-6 weeks. Clients who understand this convert better than those who are surprised by it. Include the warmup period in your onboarding timeline from day one.
Frequently Asked Questions
How should agencies price infrastructure to clients?
Common models:
- Bundled: Include infrastructure cost in your monthly retainer. Simplest for the client.
- Cost-plus: Pass through infrastructure costs with a 50-100% markup. Transparent but exposes your cost structure.
- Value-based: Price infrastructure as part of your “meetings booked” or “leads generated” outcome. Highest margins.
Most successful agencies use bundled pricing. Infrastructure is a cost center that enables the value you deliver (leads and meetings). Clients care about outputs, not inputs.
What happens to infrastructure when a client churns?
If domains are client-owned: Transfer full access to the client. They keep their domains and reputation. If domains are agency-owned: Decommission the mailboxes, let the domains rest, and consider repurposing them for future clients after a reputation reset period.
In either case, remove the client from your monitoring dashboard, cancel their warmup, and document the transition.
Can I use the same sending platform for all clients?
Yes, with proper sub-account isolation. Both Smartlead and Instantly support multi-client setups. Smartlead’s sub-account system is generally more mature for agency use. See our Instantly vs Smartlead comparison for details.
How do I handle clients with very different sending volumes?
Use tiered infrastructure packages:
- Small client package: 3 domains, 12 mailboxes (400/day capacity)
- Medium client package: 8 domains, 30 mailboxes (1,000/day capacity)
- Large client package: 15+ domains, 60+ mailboxes (2,000+/day capacity)
Each package has a fixed monthly cost, which simplifies billing and expectations. Clients can upgrade packages as their needs grow.
Building a Sustainable Agency Operation
Cold email infrastructure is the operational backbone of any lead generation agency. The agencies that invest in proper infrastructure — isolated per client, continuously monitored, with warmup pipelines and rotation strategies — deliver better results, retain clients longer, and scale more sustainably than those that cut corners.
Infrastructure is not a one-time setup cost. It is an ongoing operational function. Treat it accordingly, and it becomes one of your agency’s strongest competitive advantages. The ability to guarantee inbox placement — backed by real monitoring data — is a differentiator that few agencies can credibly claim.
Start with the fundamentals: client isolation, proper domain ratios, systematic warmup, and active monitoring. Scale from there using the phased approach outlined above. And review the complete deliverability checklist to make sure nothing falls through the cracks.