Somewhere in your first few weeks in a new marketing or growth role, someone asks you a straightforward question about email performance, and you don't have a good answer. Not because you're unprepared. Because the programme was built by someone else, and nobody left you a map.
This is a familiar pattern across UK marketing teams right now. The person who originally set up the sending infrastructure has moved on. The agency that built the lifecycle flows finished its contract eighteen months ago and nobody renewed the relationship. Or the whole thing was assembled by a contractor who's no longer reachable to explain why a particular segment exists, or why the domain is authenticated the way it is. Whoever built it is gone, and what's left behind rarely comes with documentation worth reading.
Why the problems stay invisible at first
None of it looks broken. Emails still send. Some people still open them. Nothing throws an error or sends you an alert. That's what makes this dangerous: deliverability problems build slowly, and the symptoms that eventually surface, a drop in open rates, a spike in bounces, a customer asking why their confirmation email never arrived, are usually the tail end of something that's been developing for months, sometimes years, before you arrived.
You can't see any of this from a dashboard. Whether authentication is actually enforced or just switched on and forgotten, what the domain's sender reputation history looks like, how much of the list has quietly gone dormant, none of that shows up in a weekly open rate report. You'd need to go looking for it specifically, and most new hires don't know to look until something has already gone wrong. By then it's a much bigger conversation than it needed to be.
Three things nobody hands you on day one
- Whether authentication is actually enforced, or just monitoring. A DMARC record can exist and do almost nothing. Plenty of programmes sit at a policy of none indefinitely, reporting switched on, but nothing actually blocked or quarantined when a check fails. If you don't know whether your inherited setup has moved past that stage, you don't know whether your domain is properly protected from spoofing, and you don't know whether inbox providers are already treating your mail with more suspicion than you'd like.
- What the domain's reputation actually looks like. Reputation builds up over time and it doesn't reset when the person responsible for it leaves the business. Every bounce, every spam complaint, every batch sent to a list that hasn't been cleaned in years leaves a mark. We've written elsewhere about what sender reputation actually is, but the short version is this: if nobody has checked Google Postmaster Tools or Microsoft SNDS since the handover, there's a reasonable chance you've inherited a reputation problem that's already been quietly suppressing your inbox placement, and you simply don't know it yet.
- How old the list really is, and how much of it is still active. Programmes that run for years without a working sunset policy build up large blocks of subscribers who haven't opened anything in a long time. That group doesn't sit quietly in the background waiting to be dealt with. Inbox providers judge your reputation at the sender level, not per subscriber, so a large dormant segment actively drags down delivery for everyone else on the list, including the people who are genuinely engaged and paying attention.
Why the obvious first moves tend to make things worse
The instinct, understandably, is to start doing something. New templates, a refreshed subject line style, perhaps a "we miss you" campaign aimed at waking the whole list back up. None of that is wrong on its own. The problem is sequencing. If the authentication, reputation, or list quality underneath is already compromised, sending a broad re-engagement campaign to a list you haven't assessed yet is one of the riskier moves available to you. It puts your least engaged contacts, the ones most likely to complain or simply ignore you again, directly in front of inbox providers who are already watching closely how people respond to your mail.
None of this gets solved by writing better emails. If the underlying issue is structural, good copy is sitting on top of a broken foundation, and inbox providers will keep filtering the mail regardless of how well it reads. It also isn't solved by sending more, whether that's more frequency or a bigger reactivation push. More mail to a shaky foundation usually just confirms to inbox providers that the foundation is shaky.
If you're not sure whether what you're seeing is a symptom of something structural or just a rough patch, it's worth reading why emails end up in spam in the first place, since the underlying causes are the same ones sitting inside most inherited programmes.
The clock is already running
Here's the part that makes this urgent rather than something to circle back to eventually. For the first month or two, any deliverability problem clearly belongs to whoever was in the seat before you. That window closes faster than most people expect. By month three, leadership has generally stopped thinking of the programme as inherited. The numbers are yours now, whether or not you built whatever is producing them. If something is quietly wrong and you haven't found it yet, you're the one explaining it the next time someone asks why performance hasn't moved.
The businesses that come out of this well tend to treat the first few weeks as a discovery exercise rather than a delivery deadline. Find out what you've actually got before you promise what you're going to change about it.
Where to actually look first
Rather than guessing at which of the three areas above is the problem, or checking each one separately over several weeks with no baseline to work from, the faster route is a structured review across all of them together: authentication, sender reputation, list quality, and how current sending behaviour is affecting all three. That's what our Deliverability Review and Fix covers. You get a full written picture of exactly what you've inherited, in plain English, within three to five business days, plus the quick fixes handled inside the first thirty. No guesswork, no weeks-long internal investigation with nobody left to ask.
Once you know what's actually wrong, fixing it properly is a separate step again, and one worth getting right the first time.
If you've just taken on an email programme you didn't build and want a clear, fast picture of what's actually underneath it, we can help.
Book a free check-up 15 minutes · no obligation
