Why we cap sending at ~30 a day

On paper, capping an inbox at around thirty sends a day looks like leaving reach on the table. If you could send three hundred, why send thirty? The answer is that the cap isn't a limit on ambition — it's the thing that keeps your mail arriving at all.

What high volume actually buys you

A fresh domain blasting hundreds of cold emails a day looks, to a mailbox provider, exactly like a domain that's been compromised or is running a spam operation. The pattern is the signal. It doesn't matter that your copy is thoughtful and your list is clean — the behavior trips the filter, and once you're filtered, your inbox placement falls off a cliff.

So the high-volume play buys you a short burst of reach followed by a long stretch of invisibility. You "sent" three hundred emails; a fraction were delivered, fewer were seen, and the domain is now worth less than it was that morning.

How you actually scale: more inboxes, not more sends

The disciplined version looks different. Each inbox stays inside a modest daily ceiling that mirrors how a real person sends. When you need more reach, you don't raise the ceiling — you add another warmed inbox running at the same safe rate.

Ten inboxes at thirty a day is three hundred sends — the same reach the reckless approach was chasing — except every one of those sends is coming from an inbox behaving in a way mailbox providers reward. The reach is identical. The risk profile is not.

Why "looks slow" is a feature

Outbound that mimics human sending behavior is harder to flag, easier to keep alive, and far more predictable month over month. You're not gambling the whole operation on a volume spike. You're building a sending footprint that stays healthy long enough to compound — which, as we've argued elsewhere, is the only thing in outbound that does.

The cap isn't caution for its own sake. It's the most reliable way we know to keep reaching more people without quietly burning the ability to reach anyone.