Agencies pitch websites on design, performance, and SEO — and then lose the client relationship eighteen months later over something that was never in the pitch: email. The invoice that landed in spam. The enquiry form whose messages silently vanished. The marketing campaign that went out to 4,000 subscribers and reached the inboxes of a few hundred.
Here is the uncomfortable truth behind those failures, and the commercial opportunity inside it: most email deliverability problems are decided by infrastructure choices made long before anyone hits send. Which host, which IP addresses, which DNS records, configured by whom. That means deliverability is not a black art you hope goes well — it is a feature of your hosting stack. And a feature can be sold.
Why the hosting choice decides deliverability
When your client’s message arrives at a mailbox provider, it is judged on evidence that mostly has nothing to do with the message:
The reputation of the sending IP. On bargain shared hosting, your client sends from the same IP addresses as hundreds of strangers — including, statistically, a few compromised sites pumping out spam. When one of them gets the IP blocklisted, every innocent tenant’s mail bounces with it. Your client can do everything right and still inherit someone else’s punishment. A host that actively manages sender reputation — monitoring its ranges, isolating abuse quickly, keeping reverse DNS (PTR records) correct on every sending address — is doing invisible work that shows up as your client’s invoices simply arriving.
Authentication: SPF, DKIM, DMARC. These three DNS-published standards are how a domain proves that mail claiming to come from it actually does. SPF declares which servers may send for the domain; DKIM cryptographically signs each message so tampering and forgery are detectable; DMARC ties the two together, tells receivers what to do with failures, and sends the domain owner reports about who is sending as them. Since the major mailbox providers tightened their sender requirements in 2024, authentication has moved from best practice to entry requirement: unauthenticated mail is increasingly filtered or refused outright.
The catch: these records must be created correctly, per domain, and maintained — new sending services added to SPF, DKIM keys managed, DMARC policies tightened sensibly over time. On most platforms this is left to whoever set up the site, which is why the internet is carpeted with wrong SPF records and absent DMARC. On FXRM’s platform, SPF, DKIM, and DMARC are configured correctly on every hosted domain as standard. Not a checklist you follow; a default you inherit.
The mail platform itself. Filtering that stops inbound spam and viruses, TLS on the mail paths, infrastructure that is monitored by people who understand mail. FXRM runs its own Zimbra mail infrastructure in UK data centres, operated by engineers with decades in the mail business — the same discipline, applied continuously, that no generic web host’s side-of-desk mail setup can match.
Reframing: from support burden to sales advantage
Most agencies experience email as unpaid support: the “our emails are going to spam” call, hours of forum-trawling, a fix nobody billed for. The reframe is to move email from the incident column to the proposition column. Concretely, that means saying — in pitches, on your website, in reviews — some version of this:
“Sites we host send authenticated email from properly managed UK infrastructure. SPF, DKIM, and DMARC are configured on every domain from day one, so your invoices, order confirmations, and enquiries reach inboxes.”
Almost no competing agency says this, because almost no competing agency can. They are hosting on platforms where authentication is DIY and IP reputation is a lottery. If your stack does the work by default, you get to make a differentiating promise that is also — and this is the rare part — true.
Where the money is
Treating deliverability as a feature opens three commercial doors:
1. Sharper retainers. “Hosting and maintenance” is a commodity line clients try to trim. “Hosting, maintenance, and managed email deliverability — authentication kept correct as your tools change, sender reputation looked after” is a service with a visible reason to exist. Same infrastructure cost to you; materially better story on the renewal call.
2. A migration wedge. The most receptive prospect in the world is a business whose email is currently going to spam. When one arrives complaining about their incumbent host, deliverability is your wedge: demonstrate the missing DMARC record or the blocklisted shared IP, then move site and mail onto infrastructure where the problem structurally goes away. FXRM migrates an agency’s first five client sites free, with email continuity handled — so the rescue story costs the client nothing to test.
3. E-commerce clients who cannot afford failure. For a WooCommerce shop, every order confirmation, dispatch notice, and password reset is transactional email. Deliverability failure is not an annoyance there — it is refund requests, chargebacks, and one-star reviews. When pitching e-commerce work, putting inbox placement in the proposal signals a seriousness your competitors’ proposals will lack.
Make it visible: the sixty-second demonstration
Deliverability’s sales problem is invisibility — when it works, nothing happens. The fix is to demonstrate the mechanics. In a pitch, with the prospect’s permission, look up their current domain’s records live: no DMARC record, an SPF record broken by a decade of accumulated marketing tools, no DKIM signature on the mail they sent you. Then show a domain on your stack: all three present, correct, reporting. Two minutes, no slides, and the prospect has watched you find a real, fixable risk in their business that their current provider never mentioned. That demonstration closes work not because it is theatre, but because it is a genuine audit finding — and it leads naturally into the follow-on services (authentication audits, DMARC monitoring) that several agencies on this platform already sell as productised engagements.
The retainer that writes its own monthly report
One more property makes deliverability unusually good retainer material: DMARC generates evidence. Once a domain publishes a DMARC record, the world’s mailbox providers send back aggregate reports describing who is sending mail as that domain and whether it authenticated. Read monthly, those reports become the rarest thing in agency retainers — a recurring deliverable that demonstrates its own value: “here is everyone who tried to send as you this month, here is what got through, here is the new SaaS tool your marketing team added that we caught and authorised before it broke anything.” Clients rarely cancel a service that shows them, every month, an attack surface they did not know they had.
There is a procurement angle too. For clients in regulated or data-sensitive sectors, “email and hosting on UK infrastructure, data never leaving the UK” is a line that pre-empts an entire section of the security questionnaire. FXRM’s platform is UK data centres end to end — another sentence your competitors on commodity international stacks cannot honestly write.
What to require from your host
If you are evaluating infrastructure with deliverability as part of your pitch, hold the host to this list:
- SPF, DKIM, and DMARC configured on every domain by default — not documented for you to do yourself.
- Correct reverse DNS on all sending IPs, and a straight answer to “who monitors your IP ranges’ reputation, and what happened last time one was listed?”
- Real spam and antivirus filtering on a mail platform the host actually operates — ask what the mail infrastructure is and who runs it; vagueness here is an answer in itself.
- DNS you can edit properly, with support for the records modern mail requires, on nameservers that can carry your own brand.
- Engineers on the phone who can talk about mail flow without escalating — because when a deliverability question does arise, tier-one script support is where client trust goes to die.
FXRM was built by people who have run UK mail infrastructure since the early days of the commercial internet, and it shows in the defaults: authentication on every domain, owned mail infrastructure, DNS done properly, and engineers who answer. That is the stack under the promise.
The takeaway
Every agency’s pitch says fast, beautiful, and found on Google. Almost none say “and your email will arrive” — even though email is where client relationships actually fracture. If your hosting platform makes deliverability a default rather than a project, you are sitting on a differentiator that costs you nothing to include and is nearly impossible for competitors on commodity stacks to copy honestly. Put it in the pitch. Demonstrate it in sixty seconds. Charge for keeping it true.
