Email automation: raising ROI without annoying anyone

Email automation is useful when a message follows a real customer need and someone remains responsible for maintaining it. A sequence needs review as products, availability, customer expectations and the business itself change.

Here is the smaller version that works.

Build four sequences, then stop

Welcome. Triggered when someone joins the list. Three messages over ten days. The first arrives within minutes and delivers whatever was promised. The second, three days later, answers the question that person is most likely to have next. The third introduces what you sell, once, plainly. Treat this sequence as a starting hypothesis. Measure delivery, clicks, purchases or qualified enquiries before deciding how many messages it needs.

Abandoned enquiry or cart. Where a follow-up is appropriate, define the trigger, permission, timing and stop conditions. A completed order or resolved enquiry should stop the sequence. Review responses and complaints before adding more reminders; there is no universal number of messages that recovers the most sales.

Post-purchase or post-project. Triggered on completion. Useful information first, how to use it, what to expect, who to contact, then a review request, then a relevant next offer several weeks later. This is where repeat business comes from, and it is the sequence most businesses skip entirely.

Re-engagement. Triggered by 120 days with no opens or clicks. Two messages, then remove the contact from the active list. This one feels like throwing money away and is the reason the other three keep landing in inboxes.

Deliverability is the ceiling on everything

The major mailbox providers tightened bulk sender requirements substantially, and the practical effect is that a technically sloppy sender no longer reaches the inbox at all.

Check the requirements of the mailbox providers and sending platform before launch. For personal Gmail recipients, Google sets authentication requirements and additional rules for bulk senders. Marketing and subscribed messages covered by those bulk-sender rules need one-click unsubscribe and a visible unsubscribe link. See Google’s sender guidelines for the applicable scope.

Then the ongoing part: remove hard bounces immediately, remove people who have not engaged in four months, and never import a list you did not collect. A bought list does not merely underperform. It damages the reputation of the domain you send everything else from, including your invoices.

Timing that respects the reader

Transactional and triggered messages go immediately. Marketing sends go on a predictable day, so people know what to expect. No more than one marketing message a week for most B2B clients, no more than two for retail with an active catalogue.

Send-time optimisation needs enough suitable data to assess. Compare it with a consistent sending schedule and use clicks, qualified responses and downstream outcomes to judge the difference.

Frequency complaints are relevance complaints

When unsubscribes rise, the instinct is to send less. Usually the problem is that the wrong people are receiving the message.

Segment on behaviour rather than demographics: what they looked at, what they bought, how recently they engaged. Three segments handled well beats fifteen maintained badly. One client cut broadcast volume by a third, split the list into bought before and has not bought, and revenue per send rose while unsubscribes halved.

Measure what still works

Open rate has been unreliable since mail privacy protection started pre-loading images, and it gets worse every year. Treat it as a weak directional signal, not a metric.

Report clicks, conversions attributed to the send, revenue per recipient, list growth net of unsubscribes, and complaint rate. Revenue per recipient is the number telling you whether the list is an asset or a liability.

The consent question

Collect consent explicitly, record when and how you got it, and keep that record. This matters legally in the EU and UK, increasingly in India under the DPDP framework, and practically everywhere, because unconsented lists complain.

The practical version: an unticked box with plain language, a separate checkbox for marketing distinct from service messages, and a preferences page that lets people receive less rather than nothing. The preferences page is the cheapest unsubscribe reducer we know of and almost nobody builds one.

What we do not build

Add lead scoring, personalisation and longer nurture tracks only when there is a useful decision for them to support. Define the inputs, review ownership and exit conditions. A birthday message may make sense for one business and be irrelevant for another; it needs a customer reason rather than an automation slot to fill.

A realistic build order

Week one: authentication, list clean-up, unsubscribe handling. Week two: the welcome sequence. Week three: abandoned enquiry. Week four: measurement, then let it run for a month before adding anything. Post-purchase and re-engagement in month two.

Estimate setup and maintenance against your actual catalogue, integrations and review process. Compare the cost with attributable revenue or qualified enquiries over a stated period. The pre-send rules that keep each message out of trouble are in our twelve email rules.

When to get help

The authentication step is the one worth outsourcing if DNS is not something you touch often, because a DMARC record with a wrong policy can stop your ordinary business mail as well as your campaigns. After that, most teams can run this themselves. We build the four sequences, hand over a documented account and leave, or keep running it as part of email marketing when there is nobody in-house to own it. If email is going in alongside search and paid, sequence the whole thing using the full-funnel order.