Email deliverability: what has to be true before you send volume

Deliverability is treated as a configuration problem and it is not. It is a reputation that accumulates slowly, can be destroyed in a week, and belongs to a domain rather than to a campaign. Most of the damage we see was done before anyone looked at the content.

The one rule that matters most

Never send cold volume from the domain that carries your business mail. A reputation problem does not politely stay in the outreach mailbox — it lands on invoices, project threads and password resets, which are the messages you cannot afford to have filtered.

Use a separate sending domain, related to the brand but distinct from the primary. Its reputation is independent, and that independence is the entire point of the arrangement.

Before any volume at all

1. A dedicated sending domain, separate from the one carrying business mail.
2. Sender authentication present and aligned — not merely present. A signature from a different domain than the visible sender is a partial pass at best, and partial passes are where placement problems hide.
3. A warm-up period before real volume. A new domain that opens at full send rate is a new domain that opens in the spam folder.
4. A suppression list that is actually consulted — every prior unsubscribe and every bounce. Re-sending to a hard bounce is the fastest reputation damage available to you.

What quietly destroys it

None of these announce themselves. Placement degrades, replies fall, and the campaign gets blamed for the content.

• Links in the first message. A first touch carrying no link is the highest-placement message you can send. The link belongs in a later touch, once a reply or an open has established that a human is on the other end.
• Sending to an unverified list. Invalid addresses bounce, bounces compound, and the domain carries the consequence long after the list has been discarded.
• One identical template at scale. Identical bodies in volume are a filter signal in their own right, independent of what they say.
• Treating anything that is not a yes as noise. An out-of-office is not engagement, and an unsubscribe buried in a sentence of prose still has to be honoured — which means suppressed, not noted.

A readiness check should be binary, never a percentage

The most useful discipline we run is a gate before any sequence sends its first message: a short list of things that must be true, each one pass or fail, with nothing weighted.

Weighting is what makes these checks useless. A campaign is not seventy-eight per cent ready. A percentage lets five easy passes bury the one check that actually mattered — and in practice the one that matters is almost always the last one, whether there is somewhere for the reader to land.

The checks worth gating on are ownership (a named person accountable from day one), a defined audience, an actual written sequence, something specific to say, permission to say it, and a destination that exists. Every one of those can be answered yes or no by someone who is not the person who wants to send.

Permission is a separate question from proof

One check deserves singling out, because it is the one nobody builds until it has gone wrong: nothing you send should cite a proof point you do not have permission to use in that form.

Describing work and naming the client who paid for it are two different permissions. A sequence that renders identically whether or not the naming was cleared is a sequence that will eventually put a client's name in a cold email. The check belongs in the tooling, not in someone's memory.

What actually does the work

The durable parts of a sending system are unglamorous: a queue with sensible retry behaviour, suppression enforced at send time rather than at list-build time, and honest reporting of what was delivered rather than what was dispatched.

There is no intelligence in any of that, and it does not need any. Deliverability is an operational discipline — the same checks, run every time, by something that does not get tired of running them.