Blog

How to scale cold email volume safely: the mailbox math from one live call

Sunny Ray · · 7 min read

Cold email Campaign teardowns

To scale cold email volume safely, add mailboxes, not emails per mailbox. Keep each mailbox at a low daily send, spread mailboxes across many sending domains, start each new domain with a few mailboxes, and ramp slowly before you increase. On a live call on August 27 we added mailboxes at 3 per domain across 7 domains, at 10 emails per mailbox per day, and took our live count from 268 to 296.

The reason to scale this way is simple. Each mailbox stays well-behaved, so mail providers keep trusting it, while total volume grows with the number of mailboxes. And volume, it turns out, is the lever for almost everything else in outbound.

Why volume is the lever, not filtering

On our weekly call on August 26, we wrote down a thesis I'd been circling for months: volume is the lever, not filtering.

That sounds backwards. Most advice says to send fewer, better emails to a tighter list. And targeting matters. But at low volume, you never get enough replies to learn from, and you never have enough conversations to get good at them.

At 200 mailboxes instead of 20, filtering stops being a philosophy and becomes a necessity. You have so many replies that you're forced to get sharp about who's worth a call. AI can handle the tire-kickers. Only the high-signal people reach your calendar.

The goal we set that day was to go from one or two calls a day to ten, with all ten feeling closeable. You can't get there with a handful of mailboxes.

The next day Charles made the closing side of the same argument. Closing gets better with reps. Thirty calls a day versus three is a different game. You learn faster, you hear every objection, you find your best lines. Volume upstream is what makes the reps possible downstream.

We put a line on our pricing page that says it in four words: volume is the answer.

The mailbox math

On the August 27 team call, Amir screen-shared the mailbox builder he'd made and we did it live.

We picked domains, created mailboxes across 7 of them at 3 mailboxes per domain to start, and added them to the sending tool through its API. Each mailbox sends about 10 emails a day. Three mailboxes per domain means each domain carries about 30 emails a day.

We sent a test email to confirm delivery. It landed. Then we turned on 28 mailboxes and verified them. The live count went from 268 to 296.

That's the whole technique. Low volume per mailbox, a few mailboxes per domain, many domains. To double your volume, you don't double what each mailbox sends. You double the number of mailboxes.

The bigger picture that week: about 200 active mailboxes were generating 20 to 30 leads a day. The goal was 500 to 1,000 mailboxes. Charles's view was that the marginal cost of another 100 mailboxes is close to zero. When the cost of capacity is that low and capacity drives results, the decision is easy.

Ramp slowly, then increase

Amir's rule for new domains was clear: ramp slowly, then increase over time. That's why we started at 3 mailboxes per domain, not the full number.

A new domain and new mailboxes have no history. If they suddenly carry a full load of cold email, mail providers notice. Starting small gives them time to build a record, through warmup and through light real sending, before they carry more.

The same applies to everything new in outbound. New campaign, new audience, new copy: start light, watch bounces and replies, then turn it up.

Deleting what was built wrong

Not everything on that call was additive. We found 151 existing mailboxes that were paused and couldn't be activated. They'd been created incorrectly earlier and were taking up the namespace on those domains.

The decision was to delete all 151 and recreate them properly with Amir's builder.

That's a hard call emotionally. Those mailboxes existed. Someone had spent time on them. Deleting them feels like going backwards. But a mailbox you can't activate isn't capacity, it's clutter. Worse, it blocks you from building the right ones in the same place.

If you're scaling and you find broken infrastructure, don't route around it forever. Tear it out and rebuild it properly. Clean foundations are what let you add the next few hundred mailboxes without surprises.

We also checked bounces across campaigns that day. They were effectively zero, which we credited to cleaning the lists through a verifier before sending. Volume only works if the basics are right.

Podcast invites versus direct sales: different limits

One more piece of guidance from Charles that day changes the math depending on what you're sending.

For direct sales emails, about 10 mailboxes per domain. For podcast invites, about 20 per domain. His reasoning: invites carry lower spam risk and get better responses than direct pitches.

That fits everything we've seen. An invite to be a guest on a show is a message people want to receive. It gets replies, and positive replies. Mail providers watch engagement, so a message that people engage with can carry a little more volume per domain than one that gets ignored or reported.

It's another reason the offer matters so much. A better offer isn't just more replies. It's more room to scale safely.

A scaling checklist

If you're planning to grow your sending, this is how I'd sequence it.

Keep your main domain out of it. Cold email goes from separate sending domains only.

Set a low daily send per mailbox, around 10, and don't raise it to get more volume.

Add domains, then add mailboxes to each domain gradually. Start with a few per domain.

Know your per-domain ceiling for what you're sending. Pitches carry less per domain than invites.

Test delivery on new mailboxes before they join campaigns.

Clean your list before you send. Volume amplifies bad data as much as good.

Watch bounces by sending domain, not just overall. When something breaks at scale, it usually breaks in one place.

And clear out broken infrastructure instead of working around it.

Keep your setup separate and yours

One detail from the call that matters as you scale: the full stack runs per workspace. Domains, hosting, the sending relay and the sending tool, each set up with its own credentials. Every team member or client gets their own workspace, and it's a one-time setup per person.

That separation is worth the effort. When something breaks in one workspace, it doesn't spread. When a client leaves, their infrastructure is theirs. And when you add the next hundred mailboxes, you know exactly where they live.

What volume is really for

None of this is about blasting. Each mailbox sends a small number of emails to people chosen on purpose. The scale comes from doing that across hundreds of mailboxes.

What you get is more conversations. More replies to learn from, more guests on the show, more calls to sharpen your close. That's what moves a founder from one or two calls a day to ten.

If you'd rather not build mailboxes yourself, our Growth and Team plans include our warmed mailboxes, so the volume is ready on day one.

Frequently asked questions

How many emails can one mailbox send per day?

We run about 10 emails a day per mailbox. To scale, we add mailboxes and domains rather than raising the per-mailbox number.

How many mailboxes per domain is safe?

We start new domains at 3 mailboxes and ramp from there. As a working ceiling, Charles's guidance is about 10 per domain for direct sales and about 20 per domain for podcast invites, which carry lower spam risk.

Does more volume hurt deliverability?

Volume per mailbox does. Volume spread across many mailboxes and domains, each sending lightly to a clean list, scales without that problem. Watch bounces by sending domain as you grow.

Related posts