Lifecycle and Email
Email deliverability
Make sure the messages arrive, which is invisible until it is catastrophic. It is a defined piece of work rather than a retainer line item.
What is meant by email deliverability?
Make sure the messages arrive, which is invisible until it is catastrophic. In practice that means authentication done properly: SPF, DKIM and DMARC, with a policy that moves beyond monitoring, and then the harder half: domain and IP warm-up at a pace the mailbox providers accept.
Why this work exists
It is the sort of work that never makes a slide, and shows up in every result that does.
Lifecycle and Email holds the whole discipline. This page is one defined piece of it.
The nearest piece of work to it is getting consent recorded in a way that survives an audit. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
Success looks like fewer meetings about this, not more reporting on it.
The gap between that and where most accounts start is why this is scoped as email deliverability rather than as a line inside something larger. Finding where the email promises something the landing page does not deliver is the usual second step once it is in place.
When this is the right work
The signs that this is where the problem sits:
- Open rates fell sharply with no change in content
- Your DMARC policy is set to none and has been for years
- A major mailbox provider stopped delivering and nobody knows when
If none of those is true, something else is probably the constraint, and the Lifecycle and Email overview maps the alternatives. The usual neighbours are deciding what to automate and what still needs a person and keeping the sending domain healthy before scale makes it urgent.
What the work covers
The pieces of work inside it:
- Authentication done properly: SPF, DKIM and DMARC, with a policy that moves beyond monitoring. Straightforward in principle; the detail is where it stops being quick.
- Domain and IP warm-up at a pace the mailbox providers accept. Boring, necessary, and the first casualty when a deadline moves.
- Engagement-based sending, so inactive addresses stop dragging the whole list down, handled before the parts that depend on it rather than alongside them.
- Monitoring that catches a reputation problem in days rather than in a quarterly report, done before anything downstream is committed to.
How it runs
It runs in three passes. The order is not interchangeable.
Agreeing what failure looks like
The conditions under which this would be called off are written down at the start. It is uncomfortable and it prevents a year of drift.
Handing back the keys
Access, documentation and whatever was built end up with the client in a form they can use without us, which is the only honest definition of finished.
Before anything is changed
Nothing moves until the current position is written down and agreed. That takes days, not weeks, and it is the only defence against arguing about whether something improved.
What each part runs into
Taken one at a time, against real markets:
- Authentication done properly: SPF, DKIM and DMARC, with a policy that moves beyond monitoring, which in Kota runs into a sector mix that pulls the brief in several directions
- Domain and IP warm-up at a pace the mailbox providers accept: the Mumbai version of this has to deal with a seasonal peak that arrives before the content is indexed
- Engagement-based sending, so inactive addresses stop dragging the whole list down, where a Kolkata engagement contends with a reporting line that averages away the market in question
- Monitoring that catches a reputation problem in days rather than in a quarterly report – working in Dubai this means accounting for a market where buyers qualify by area rather than by city
The version that does not work
Buying or importing a list. One bad import can cost a domain reputation that takes months to rebuild.
The reason it matters is that the failure is invisible from the report: the activity happened, the number did not move, and the conclusion drawn is usually the wrong one.
How it is measured
Inbox placement by provider, complaint rate, and bounce rate. It is reported with the existing metrics rather than replacing them, because a new number nobody recognises persuades nobody.
A single reading means little. The shape over a quarter is the thing worth looking at.
What you end up with
Specifically: a full authentication setup, a sending policy based on engagement, and monitoring with alerts.
Given with the raw working attached, so the conclusion can be re-derived.
How it differs by sector
How the sector changes it:
- Finance and fintech: the thing that changes the scope here is that regulated claims, compliance review in the publishing path, and trust signals that have to be real.
- For Travel and hospitality, aggregators hold the demand, so direct booking depends on being the specific named property. and that shapes how far this can go.
- Marketplaces and platforms brings its own limit: two sides to acquire, and a programmatic page set that can sink the whole domain.
The industry pages carry the rest of that detail. Finance and fintech and Travel and hospitality are the two where this piece of work most often decides the outcome.
Common questions
Why did our open rates drop?
Either a deliverability problem or a measurement one, since privacy features inflate opens for some providers. Check placement before rewriting subject lines.
Do we need DMARC?
The major providers now expect it for bulk senders. A policy of none protects nobody; it only reports. Read Analytics and Measurement for the standard approach and Answer Engine Optimization for when the standard approach does not fit.
What happens if we stop after this?
You keep everything: A full authentication setup, a sending policy based on engagement, and monitoring with alerts. Documented so your own team can continue it, including the parts we would have done next and why. 301 redirect or Canonical tag is the obvious next page from here. Broad match or Exact match is the one people wish they had read first.
What if we disagree with the diagnosis?
Then we look at the data together. Inbox placement by provider, complaint rate, and bounce rate is the test, and a finding that cannot survive being questioned is not a finding worth acting on. Pair this with How long does SEO take to show results?, and with How many words should a page be? if the market is competitive.
Does anything need doing before email deliverability?
Sometimes. The signals above are the honest test, and where something upstream is the real constraint we will name it even though it is not the work on this page. Read Enhanced conversions for the standard approach and Entity disambiguation for when the standard approach does not fit.
Ask about email deliverability
Send the site and the symptom. The reply names the first thing we would look at and why.
Have someone senior look at the numbers
One call, no sequence of follow-up emails afterwards. If the timing is wrong we will leave you to it.