Deliverability: the tool nobody sells you
There is a stage of the pipe that no vendor puts at the centre of its pitch, because it is unglamorous infrastructure rather than shiny AI, and it quietly decides whether any of your other tools matter. That stage is deliverability. You can stack a perfect data waterfall and write the sharpest opener in your market, and if your email lands in the spam folder, none of it happened.
Warmup decides whether you are seen
A sending domain has a reputation, and that reputation is earned over time through consistent, well-received sending. A brand-new domain has no reputation, and the mailbox providers treat it with suspicion, routing its mail straight to spam until it proves itself. This is why domain warmup, the gradual ramp of sending volume from a new domain while it builds trust, is not optional housekeeping. It is the gate every send passes through. The AI copy is irrelevant to a message nobody sees, and a fresh un-warmed domain hides a large share of your sends from the people you are trying to reach. Warm your domains first, ramp slowly, and treat warmup as part of the stack rather than a thing you remember after the bounces start.
Google's hard ceiling
Deliverability is not just reputation, it is also a published rule you cannot negotiate. Google's sender guidelines require bulk senders to Gmail to keep their spam-complaint rate below 0.3 per cent, which is roughly three complaints per thousand emails. Breach it and Google can block your domain from Gmail entirely, which is not a slap on the wrist but a death sentence for that domain. This is a hard ceiling on how aggressively any AI tool can scale your send volume. It does not matter how clever your sequencing is; if you push volume past the point where complaints climb over that line, the channel closes on you. Volume, beyond a point, destroys the very deliverability it depends on.
The infrastructure that protects you
The practical defences are not exotic, but they have to be deliberate. Separate sending domains keep a reputation problem on one domain from poisoning your primary domain. Warmup runways give each domain time to earn trust before you load it. Volume throttling keeps your daily send under the threshold where complaint rates spike. These three together are the deliverability infrastructure, and they are the real substance behind the "send" tool you choose.
What this means for tool choice
Reframe stage three accordingly. When you pick your sending tool, you are not really choosing a writer, you are choosing a deliverability platform. The question is not how good its AI personalisation is, it is whether it manages separate domains, runs proper warmup, and throttles volume to keep you under Google's ceiling. A tool that writes beautifully but lands in spam is worse than useless, because it spends your domain reputation while producing nothing. Choose the send layer on its deliverability features first, and treat the copy as a bonus on top of infrastructure that actually delivers.