Teams will spend a month rewriting sequences to lift reply rate by half a point while forty percent of their sending lands in spam. The copy work is visible and satisfying. The deliverability work is invisible and worth an order of magnitude more.
Deliverability is treated as an IT hygiene task — set the records, tick the box, move on. It is better understood as a channel with capacity that you either maintain or destroy.
The three things that must be true before volume
Nothing else matters until authentication is correct. SPF, DKIM and a DMARC policy that is actually enforcing rather than sitting at none. Providers tightened bulk-sender requirements significantly and the tolerance for half-configured domains is now close to zero.
Check it from outside your own network, on the exact domain and subdomain you send from. A domain that passes on the marketing subdomain and fails on the sales one is extremely common and produces baffling results.
Never send cold volume from your primary domain
This is the single most consequential rule and the one most often broken by teams in a hurry. Cold outreach carries reputational risk. Your corporate domain carries your invoices, contracts, support and recruiting.
Use dedicated sending domains — close variants of the brand, separately authenticated, individually monitored. If one gets damaged you retire it. Nothing else in the business notices.
Cold outreach carries reputational risk. Your invoices should not be sharing a domain with it.
Warm-up is a schedule, not a product
A new mailbox that sends two hundred messages on day one is finished. Ramp slowly — a handful of messages a day, building over weeks — and keep the ramp going even after the mailbox is "ready", because reputation decays with inactivity too.
Reciprocal warm-up networks are common and increasingly detectable. They are not a substitute for real engagement, and over-reliance on them is a growing liability. Treat them as a supplement to genuine sending patterns at most.
Spread the load
Volume per mailbox is the variable that kills programmes. Thirty to fifty cold sends per mailbox per day is a defensible ceiling. If you need two thousand sends a day, that is a mailbox estate, not a bigger daily limit.
Rotate across mailboxes and domains, randomise send timing within business hours, and never send the same body from the same address at machine cadence. The pattern is as detectable as the content.
What actually gets you filtered
In rough order of impact: recipients marking messages as spam, sending to addresses that bounce, sending to spam traps on stale lists, and only then content signals like link count and image weight. Notice that three of the four are list quality problems, not copy problems.
Which is the whole point. Deliverability is mostly a data discipline wearing an infrastructure costume — verify before sending, suppress aggressively, and stop mailing people who never engage.
Instrument it or you will find out late
Track reply rate per domain and per mailbox, weekly. Reply rate is the earliest honest indicator you have; open rate has been unreliable since privacy protections became default. A domain whose reply rate halves in a fortnight is telling you something urgent, and it is the only warning you will get before the damage is expensive.