The Agency Scaling Blueprint

how to go from 10 inboxes to 100+ without killing deliverability. from someone who ran an agency and built the infrastructure fix.

READ THIS FIRST

i ran a cold email agency.

we scaled it to $170K a month in cash collected. growing month on month. adding clients constantly.

and infrastructure nearly burned the whole thing down.

accounts not delivered for 48 hours after we told a client they'd be live in 6. that's instant churn. a $25,000 invoice we got held to ransom over because our provider decided to "re-bill" us. and every single client had some kind of infrastructure issue. every one of them.

the business becomes unstable when one of the core pillars you're building on isn't stable. like building a house with missing bricks at the bottom.

that's why we built Premium Inboxes. not as a new business. as a fix for our own. people asked what we were using, we shared it, and within four weeks we were at a million in annual revenue.

this blueprint is everything we learned scaling infrastructure across hundreds of client accounts. the mistakes that cost us money, the systems that saved us, and the exact framework for scaling without burning through domains every two weeks.

what's inside:

  1. infrastructure audit template for your current client accounts
  2. vendor evaluation checklist (so you don't get held to ransom like we did)
  3. the two-lane provider strategy for scaling safely
  4. volume planning framework with sending calculations
  5. client onboarding SOP for adding new accounts without breaking existing ones

who this is for: agency owners and outbound operators managing cold email for multiple clients. if you're running 10+ inboxes and want to scale to 100+ without deliverability falling apart, this is for you.

QUICK WIN: infrastructure health check

run through this for your biggest client account right now. takes 5 minutes.

  • [ ] all sending domains have SPF, DKIM, and DMARC configured
  • [ ] no cold email is being sent from the client's primary business domain
  • [ ] inboxes have been warmed for 14+ days
  • [ ] sending volume is under 15 emails per inbox per day
  • [ ] inboxes are split across Google and Outlook (not all on one provider)
  • [ ] you can see which sending IPs each inbox is on
  • [ ] no IPs are on any blacklist (check mxtoolbox.com/blacklists)
  • [ ] you have a clear process for rotating inboxes when they degrade

score: if you ticked 6+, your setup is solid for that client. if you ticked fewer than 5, fix that account before adding more clients. scaling on broken infrastructure just scales the problems.

Section 1: Audit Your Current Infrastructure

before you scale, know what you're scaling on.

the biggest mistake agencies make is adding more inboxes on top of infrastructure that's already shaky. more volume on a bad foundation just breaks things faster.

the full audit

run this across EVERY client account. not just the ones with problems.

per-client checklist:

| Check | Client A | Client B | Client C |

|-------|----------|----------|----------|

| DNS records (SPF/DKIM/DMARC) configured | | | |

| Sending from lookalike domains (not primary) | | | |

| Warmup completed (14+ days) | | | |

| Warmup still running alongside campaigns | | | |

| Volume under 15 per inbox per day | | | |

| Provider split (Google + Outlook) | | | |

| IP reputation clean | | | |

| Reply rate tracked per inbox | | | |

fill this in for every active client. any blank or "no" is a risk you're carrying. fix them before you add capacity.

common patterns i see in agency audits

→ client A has been on Google-only for 6 months with no diversification

→ client B's domains were set up 3 days ago and are already sending at full volume

→ client C's inboxes all share the same IP block and one of them got blacklisted last month

every one of those is a ticking clock. scale over them and you lose the client.

Section 2: Choose Your Infrastructure Stack

the old days of cold email were the wild west. you were paying $7 per inbox from Google direct, or you were getting held by the balls by some reseller who could wipe your accounts and invoice you whatever they wanted.

those days should be over. but a lot of agencies are still stuck with providers who manage everything through CSVs, overcharge by thousands, and won't refund it when they get caught.

vendor evaluation checklist

before committing to any infrastructure provider, ask these questions:

  • [ ] do you own the accounts, or does the provider?

→ if the provider owns them, they can revoke access at any time. that's not infrastructure. that's a lease.

  • [ ] what's the guaranteed setup time?

→ "we'll get it done" is not a guarantee. if they can't commit to a timeframe, your client timelines are at risk.

  • [ ] is there a customer portal or dashboard?

→ if they manage everything through CSVs and manual emails, you have zero visibility into what's happening with your accounts.

  • [ ] what happens if accounts get suspended?

→ every provider will tell you their accounts don't get suspended. ask what the PROCESS is when it happens. because it will.

  • [ ] can you move your accounts to a different provider?

→ if you're locked in, you're at their mercy. client-owned accounts mean you can take them anywhere.

  • [ ] what are the actual costs per inbox per month?

→ if you're paying $6+ per inbox and someone else offers the same quality at $3.50, you're overpaying for a middleman.

the ransom test

ask yourself: if this provider disappeared tomorrow, would my clients' campaigns still run?

if the answer is no, your infrastructure is a single point of failure. fix that before you scale.

Section 3: Set Up for Scale

the two-lane provider strategy is how you scale without getting wiped out when one provider updates its filtering.

how it works

split your sending between Google Workspace and Microsoft Outlook.

→ 70/30 split: 70% Google, 30% Outlook. this is the default for most agencies. Google has higher inbox placement rates currently, Outlook provides the safety net.

→ 50/50 split: equal distribution. more defensive. use this if you've been burned by a single-provider collapse before.

the point: if Google tightens filtering next month (and it will, eventually), your Outlook lane keeps running. if Outlook has an issue, Google carries the load. you never go to zero.

volume planning

for each client, calculate:

target emails per day: ___
emails per inbox per day: 10-15 (MAX)
inboxes needed: target ÷ 12 (using 12 as midpoint)
domains needed: inboxes ÷ 3 (max 3 inboxes per domain)

example:

→ client wants to send 200 emails per day

→ 200 ÷ 12 = 17 inboxes needed

→ 17 ÷ 3 = 6 domains needed

→ split: 12 inboxes on Google (4 domains), 5 inboxes on Outlook (2 domains)

domain purchasing guide

  • buy domains that look legitimate. "getacme.co" and "try-acme.com" work. "xvf7spamblast.xyz" doesn't.
  • one domain per purpose. don't reuse burned domains.
  • register 14+ days before you need them. new domains need time before they're trusted.
  • set up DNS records on DAY ONE. don't wait until campaign launch day.

Section 4: Monitor and Maintain

scaling isn't a one-time event. it's ongoing maintenance.

the agencies that burn through domains every 2-3 weeks aren't scaling. they're churning infrastructure as fast as they're churning clients.

weekly monitoring checklist

for each client, check these weekly:

  • [ ] reply rates per inbox (flag any inbox below 2%)
  • [ ] deliverability scores (flag any below 90% inbox placement)
  • [ ] IP reputation (any blacklist appearances)
  • [ ] sending volume per inbox (flag any above 15/day)
  • [ ] warmup health (flag any inbox with declining warmup engagement)

throttling detection

silent throttling is the biggest invisible threat. your emails are "sending" but they're being quietly deprioritised.

warning signs:

→ open rates declining gradually over 2-3 weeks

→ reply rates dropping with no change in copy or targeting

→ newer inboxes performing better than older ones

→ deliverability tool says "delivered" but engagement is falling

if you see these patterns:

  1. pause the affected inboxes
  2. increase warmup ratio for 7 days
  3. check IPs for blacklisting
  4. if no improvement, rotate to fresh inboxes and domains

when to add capacity

add inboxes when:

→ existing inboxes are consistently at 10-12 sends per day

→ reply rates are healthy (5%+ across the board)

→ client wants to increase volume AND has the pipeline to handle more calls

→ you've verified the new domains are warmed and ready

DON'T add inboxes when:

→ existing inboxes are underperforming (fix first, then scale)

→ reply rates are below 3% (the problem is copy or targeting, not volume)

→ the client is asking for "more emails" without knowing their current metrics

Section 5: Client Onboarding SOP

every new client you bring on is a risk to your existing clients IF you don't onboard them properly.

the onboarding sequence

day 1: domain setup

  • [ ] purchase 3-6 lookalike domains for the client
  • [ ] configure SPF, DKIM, DMARC on every domain
  • [ ] verify DNS propagation (can take up to 48 hours)
  • [ ] set up forwarding to client's primary email for replies

day 2-3: inbox provisioning

  • [ ] create inboxes across Google and Outlook (two-lane split)
  • [ ] assign sending IPs (verify no blacklisting)
  • [ ] connect to sending platform (sequencer)
  • [ ] start warmup on ALL inboxes

day 3-17: warmup period

  • [ ] warmup running for minimum 14 days before any campaigns
  • [ ] monitor warmup engagement daily
  • [ ] flag any inboxes with poor warmup metrics

day 17+: campaign launch

  • [ ] start with 5 emails per inbox per day
  • [ ] increase by 2-3 per day until reaching 10-12
  • [ ] monitor reply rates from day one
  • [ ] first review after 7 days of sending

the non-negotiable rule

never, under any circumstances, let a new client's infrastructure interfere with an existing client's. separate IPs where possible. separate domains always. if one client's sending behaviour triggers a crackdown, it should never cascade to another client's accounts.

this is why client-owned infrastructure matters. if the accounts belong to the client, their problems stay contained.

Home

Why Us

Pricing

Contact

Testimonials

Affiliates

Resources

API

Sign In

Get Started