Building a Cold Email Agency from Scratch — The Infrastructure Playbook
By Puzzle Inbox Team · Mar 19, 2026 · 15 min read
Everything you need to build a cold email agency: client infrastructure setup, inbox provisioning, deliverability management, pricing models, and scaling systems.
The Agency Infrastructure Problem Nobody Talks About
Starting a cold email agency sounds simple: find clients who need meetings, send cold emails on their behalf, charge a retainer or per-meeting fee. The sales side of the business is straightforward. The infrastructure side is where most agencies either thrive or collapse within their first year.
I have consulted with over 40 cold email agencies on their infrastructure — from solo operators running 5 clients to established firms managing 50+ accounts. The pattern is consistent: agencies that build robust infrastructure systems early can scale smoothly. Agencies that figure it out as they go spend 60% of their time firefighting deliverability issues, managing client expectations around problems they created, and manually configuring things that should have been automated from day one.
This playbook covers the infrastructure side of building a cold email agency — the part that determines whether you can actually deliver results for clients or just promise them.
Phase 1: Your First Client Infrastructure Setup
Before you take your first client, you need a repeatable process for standing up their infrastructure. Every new client engagement starts with the same checklist:
Domain Acquisition
Every client needs their own set of sending domains. These domains should be lookalike variations of the client's primary domain — close enough to be recognizable but separate enough to protect the client's main domain from any deliverability issues.
For a client whose company is "Acme Solutions" with primary domain acmesolutions.com, you would purchase domains like:
- tryacmesolutions.com
- acmesolutionshq.com
- getacmesolutions.com
- useacmesolutions.com
- acmesolutions.co
Start each client with 4-5 domains. At 2-3 inboxes per domain, that gives you 8-15 inboxes per client — enough for most initial campaigns. You can always add more domains later.
Domain registration tips for agencies:
- Register domains under the client's name/entity, not yours. This avoids WHOIS correlation across all your clients' domains pointing to one agency entity.
- Use a reputable registrar (Namecheap, Cloudflare, GoDaddy). Avoid obscure registrars that are associated with spam operations.
- Enable WHOIS privacy on all domains.
- Do not register all 5 domains on the same day from the same registrar. Spread them across 2-3 registrars and acquire them over a week. This reduces pattern correlation.
Inbox Provisioning
For each domain, provision 2-3 inboxes. The mix should be:
- 60% Google Workspace: Best deliverability to Gmail recipients, OAuth support for sending tools
- 40% Outlook 365: Best deliverability to Microsoft recipients, lower cost
Using a provider like Puzzle Inbox dramatically simplifies this step. Instead of manually setting up Google Workspace admin consoles and Microsoft 365 tenants for each client, you order pre-configured inboxes with DNS already set up. For an agency managing multiple clients, this time savings is significant — manual setup takes 1-2 hours per domain, while provider-based setup takes minutes.
Inbox naming should match real people at the client's company. Ask your client for the names of 2-3 people on their sales or business development team. Create inboxes like sarah.johnson@tryacmesolutions.com, mike.chen@acmesolutionshq.com. If the client prefers not to use real employee names, create plausible fictional names — but never use obviously fake names like "John Smith" or initials-only like "jd@domain.com."
DNS Configuration
Every domain needs properly configured SPF, DKIM, and DMARC records. If you are using an infrastructure provider, this should be handled automatically. If you are setting up DNS manually, follow our SPF/DKIM/DMARC guide exactly.
The critical point for agencies: keep a record of every DNS configuration for every client domain. When a client has a deliverability issue 3 months after setup, you need to be able to quickly verify their DNS without starting from scratch. Build a documentation template that captures all DNS records for each domain, and update it any time you make changes.
Warmup
Every inbox needs warmup before sending cold email. For agencies, warmup creates a delay between signing a new client and delivering results — and that delay can strain the relationship if not managed properly.
Set expectations upfront: During your sales process, make it clear that there is a 2-3 week warmup period before any cold emails go out. Frame this as a quality control measure, not a delay. "We warm up every inbox for 14-21 days to ensure your emails actually reach the inbox. Agencies that skip this step see 50-70% of client emails go to spam."
Alternatively, use pre-warmed inboxes from providers like Puzzle Inbox to eliminate the warmup delay entirely. Pre-warmed inboxes can start sending within 24-72 hours of setup, which means you can start generating results for new clients in their first week.
Phase 2: Client Infrastructure Management at Scale
Managing infrastructure for 1-2 clients is manageable. Managing infrastructure for 10+ clients requires systems.
The Client Infrastructure Dashboard
Build a centralized dashboard (spreadsheet, Notion database, or purpose-built tool) that tracks every piece of infrastructure across all clients:
- Client name
- Domains: List of all domains, registration dates, registrar, expiration dates
- Inboxes: List of all inboxes per domain, provider (Google/Outlook), warmup status, daily send volume
- DNS status: SPF/DKIM/DMARC verification date and status
- Deliverability health: Current Google Postmaster reputation per domain, last GlockApps test results
- Monthly cost: Infrastructure cost per client (inboxes + domains + warmup tools)
- Sending tool: Which campaigns are running, which tool, current daily volume
This dashboard is your operational center. Review it weekly — every domain, every client. It takes 30 minutes once you have the system set up, and it catches problems before they become crises.
Deliverability Monitoring Across Clients
When you manage 10+ clients, deliverability monitoring becomes a weekly discipline, not an ad-hoc check. Here is the monitoring protocol:
Weekly checks (every Monday morning):
- Check Google Postmaster Tools for every client domain. Flag any domain with reputation below "High."
- Review bounce rates per inbox across all clients. Flag any inbox above 2%.
- Review reply rates per inbox. Flag any inbox significantly below the client average — this often indicates spam placement.
- Check warmup tool dashboards for any inboxes with declining warmup engagement.
Monthly checks:
- Run GlockApps tests on a sample of inboxes from each client (test 2-3 inboxes per client).
- Verify DNS records are still correctly configured (records can be accidentally changed by client IT teams).
- Review domain expiration dates — a lapsed domain takes down all inboxes on that domain.
Handling Client-Side Issues
Agencies face a unique challenge: clients sometimes break their own infrastructure without telling you. Common scenarios:
- Client IT changes DNS records: They are updating their main website and accidentally modify or delete MX/TXT records on a sending domain. Your inboxes stop authenticating properly, deliverability tanks.
- Client sends from the same domains: The client starts sending their own marketing emails or newsletters from domains you set up for cold outreach, mixing warm/transactional traffic with cold traffic and confusing the domain reputation.
- Client shares inbox credentials: The client logs into a cold email inbox to "check how things look" and accidentally sends manual emails that mess up the sending pattern.
Prevent these by establishing clear ground rules at onboarding: the cold email infrastructure is managed exclusively by your agency. The client should not touch DNS records, log into cold email inboxes, or send any other emails from the cold email domains. Document this in your service agreement.
Phase 3: Pricing Your Infrastructure
One of the hardest parts of running a cold email agency is pricing infrastructure correctly. Price too low and you lose money on infrastructure costs. Price too high and clients balk at the setup fees.
Infrastructure Cost Breakdown Per Client
Here is what infrastructure actually costs per client at different scales:
Small client (10 inboxes, 4 domains):
- Domains: 4 × $12/year = $48/year ($4/month)
- Google Workspace inboxes (6): 6 × $3.50 = $21/month
- Outlook inboxes (4): 4 × $0.35 = $1.40/month
- Warmup (if not included): 10 × $15 = $150/month (or $0 with pre-warmed inboxes)
- Total with separate warmup: ~$176/month
- Total with pre-warmed inboxes: ~$26/month
Medium client (25 inboxes, 9 domains):
- Domains: 9 × $12/year = $108/year ($9/month)
- Google Workspace inboxes (15): 15 × $3.50 = $52.50/month
- Outlook inboxes (10): 10 × $0.35 = $3.50/month
- Warmup (if not included): 25 × $15 = $375/month
- Total with separate warmup: ~$440/month
- Total with pre-warmed inboxes: ~$65/month
The warmup cost difference is massive. An agency managing 10 medium-sized clients saves $3,750 per month by using pre-warmed inboxes instead of separate warmup tools. That is $45,000 per year in pure cost savings — often the difference between a profitable agency and one that is struggling to break even.
How to Charge for Infrastructure
There are three common models for agency infrastructure pricing:
Model 1: Infrastructure included in retainer. Your monthly retainer covers everything — infrastructure, sending tool, list building, copywriting, campaign management. The client pays one flat fee and does not see the infrastructure costs separately. This is the cleanest model and the one I recommend for most agencies.
Pros: Simple for the client, no nickel-and-diming, you control the infrastructure budget. Cons: You need to price your retainer high enough to cover infrastructure costs plus your margin.
Model 2: Infrastructure as a separate line item. You charge a base retainer for campaign management and a separate infrastructure fee. "Campaign management: $2,500/month. Infrastructure (15 inboxes, 5 domains, warmup): $350/month." Total: $2,850/month.
Pros: Transparent pricing, easy to scale infrastructure up or down. Cons: Clients question infrastructure costs ("Why does an inbox cost $3.50? I can get a Gmail account for free."), and you spend time justifying technical decisions to non-technical clients.
Model 3: Client-owned infrastructure. The client purchases their own domains and inboxes, and you manage them. You charge a setup fee ($500-1,500 one-time) and your retainer covers campaign management only.
Pros: Lower ongoing costs for the client, no infrastructure liability for you. Cons: You have less control over the infrastructure, the client can make changes that break things, and transitions are harder because the infrastructure stays with the client if they leave.
For most agencies starting out, Model 1 is the best choice. It gives you full control over the infrastructure quality, simplifies your pricing, and avoids the "why does this cost so much" conversations that distract from the actual value you deliver (meetings booked).
Phase 4: Scaling to 10+ Clients
Sending Tool Architecture
At 1-3 clients, you can manage all campaigns in a single sending tool account. At 10+ clients, you need a more structured approach.
Option 1: One master account, separate workspaces. Tools like Instantly support workspaces or sub-accounts within a single agency account. Each client gets their own workspace with isolated campaigns, inboxes, and analytics. This is the most efficient setup — one login, one billing relationship, centralized management.
Option 2: Separate accounts per client. Each client gets their own sending tool account. This provides better isolation (a client leaving takes only their account, not disruption to your master setup) but increases management complexity and cost.
Most agencies start with Option 1 and only move to Option 2 for enterprise clients who require data isolation for compliance reasons.
Team Structure for Infrastructure Management
At 5+ clients, you need someone whose job includes infrastructure management. This is not the same person writing copy or building lists — infrastructure requires a different skill set (DNS knowledge, deliverability diagnosis, inbox monitoring).
Typical agency team structure at 10 clients:
- Agency owner: Client acquisition, strategy, relationship management
- Campaign manager (1-2): List building, copy, sequence setup, A/B testing — each handling 3-5 clients
- Infrastructure/deliverability manager (1): Domain management, inbox provisioning, warmup monitoring, deliverability checks, DNS troubleshooting — handles all clients
- Reply manager/SDR (1-2): Processing replies, booking meetings, managing the centralized inbox — split across clients based on volume
The infrastructure manager role is the one most agencies skip, and it is the one that causes the most pain when absent. Without a dedicated infrastructure person, deliverability issues go undetected for weeks, DNS records drift, domains expire, and warmup gets neglected.
Onboarding Automation
At scale, you cannot spend 5 hours manually setting up infrastructure for each new client. Build an onboarding checklist and automate what you can:
- Domain purchase: Semi-automated. Use bulk domain search tools to find available lookalike domains, present options to client for approval, purchase in batch.
- Inbox provisioning: Automated via provider. Order inboxes from Puzzle Inbox with desired configurations — they handle DNS, warmup, and delivery within 24-72 hours.
- Sending tool setup: Semi-automated. Create workspace, connect inboxes via OAuth/SMTP, configure default send limits and schedules. Build templates for common configurations so each new client takes minutes, not hours.
- Documentation: Automated. Have a template that auto-populates with the client's domains, inboxes, DNS records, and account details. Store in your client infrastructure dashboard.
The goal is to reduce new client infrastructure setup from 5 hours to under 1 hour. At 2 new clients per month, that saves 8 hours monthly. At 5 new clients per month, it saves 20 hours — more than half a work week.
Phase 5: Advanced Agency Infrastructure
Multi-Provider Diversification
Do not put all your clients on one infrastructure provider. If that provider has an outage, a policy change, or a quality issue, every client is affected simultaneously. Spread your infrastructure across 2-3 providers:
- Primary provider (60-70% of inboxes): Your most reliable, best-deliverability provider. Puzzle Inbox is the go-to for most agencies we work with.
- Secondary provider (20-30% of inboxes): A backup that covers a different inbox type or price point.
- Tertiary/experimental (5-10% of inboxes): Test new providers here before committing client infrastructure to them.
This diversification protects your agency against single-provider risk and gives you leverage in provider negotiations as you scale.
Client Reporting on Infrastructure Health
Clients want to see results (meetings booked), not infrastructure metrics. But including a brief infrastructure health section in your monthly reports builds trust and demonstrates the work that goes into making the campaigns run smoothly.
Include in monthly client reports:
- Number of active inboxes and domains
- Average inbox placement rate (from GlockApps or similar)
- Domain reputation status (from Google Postmaster Tools)
- Any infrastructure changes made (inboxes added/retired, domains added)
- Deliverability trend (improving, stable, or needs attention)
Keep this section to half a page. Clients do not need to understand SPF records — they need to know their infrastructure is healthy and professionally managed.
Handling Client Churn
When a client leaves your agency, infrastructure handoff is a critical process. If you used Model 1 or Model 2 pricing (infrastructure owned by the agency), you need to decide what happens to the domains and inboxes.
Option A: Transfer to client. Transfer domain ownership and inbox access to the client. This is the cleanest exit but means the client can continue using the infrastructure you built — including any reputation you developed. Charge a transfer fee to cover your time.
Option B: Decommission. Retire the domains and inboxes. The client starts fresh with new infrastructure (their problem or their next agency's problem). This is simpler but leaves value on the table — well-established domains and inboxes with strong reputations are assets.
Option C: Recycle. If the domains are generic enough (and not branded to the specific client), retire the inboxes but keep the domains for future clients. This only works if the domains do not contain the client's company name.
Document your churn process in your service agreement before you sign any clients. The last thing you want is a contentious negotiation about domain ownership when a client is already unhappy enough to leave.
The Agency Infrastructure Stack
Here is the complete infrastructure stack I recommend for a cold email agency in 2026:
- Inbox provider: Puzzle Inbox (Google Workspace + Outlook 365, pre-warmed, DNS included)
- Domain registrar: Namecheap or Cloudflare (bulk pricing, reliable DNS management)
- Sending tool: Instantly (best agency features) or Smartlead (better API for custom integrations)
- Deliverability monitoring: GlockApps (inbox placement testing) + Google Postmaster Tools (domain reputation)
- Data/list building: Apollo.io (best value) or Clay (best enrichment for complex ICPs)
- CRM: HubSpot (free tier works for most agencies) or Close.com (built for outbound teams)
- Client dashboard: Notion or Google Sheets (track all infrastructure across all clients)
Total tool cost for an agency managing 10 clients: approximately $500-800/month depending on sending tool tier and data tool usage. Infrastructure cost (inboxes + domains) adds approximately $300-650/month for 10 clients at 10-25 inboxes each. Your total operational cost for a 10-client agency is roughly $800-1,450/month — well within the margins of a properly priced retainer model.
Common Agency Infrastructure Mistakes
- Using the same domains across clients. Each client must have their own domains. Sharing domains means one client's bad data or aggressive messaging can tank deliverability for another client. Total isolation is non-negotiable.
- Skipping warmup to impress new clients. "We will have your first campaign live tomorrow" sounds great in a sales pitch. It is a deliverability disaster in practice. Warmup or pre-warmed inboxes — no shortcuts.
- Not monitoring deliverability proactively. Waiting for a client to complain about low reply rates before checking deliverability means the problem has been festering for weeks. Monitor weekly, not reactively.
- Underpricing infrastructure. If your retainer does not cover infrastructure costs with margin, you are subsidizing the client's email sending from your profit. Know your costs, price accordingly.
- No documentation. If your infrastructure manager quits and nothing is documented, you are in crisis mode. Document every domain, every inbox, every DNS record, every client configuration. This is not optional at any scale.
- Ignoring domain renewals. A domain that lapses because nobody renewed it takes down every inbox on that domain. Set up auto-renewal on every domain and calendar reminders as backup.