Email Marketing
Marketing automation that converts while you sleep
Marketing automation sends the right message when behaviour triggers it: a sign-up, an abandoned cart, a customer going quiet. We build the flows once and they convert around the clock, no manual sending involved.
Who it is for: Businesses where every email is still sent by hand, leads go cold waiting for follow-up, and new customers get silence instead of onboarding.
Everything in this service
- Flow mapping across your full customer lifecycle
- Welcome, onboarding, nurture, recovery and win-back sequences
- Behaviour triggers wired to your site and CRM
- Every email in every flow written and designed
- Flow-level revenue reporting and ongoing refinement
What to expect
- Leads followed up within minutes, automatically
- Revenue from flows that run without anyone sending
- A lifecycle with no silent gaps
How marketing automation actually works
The flows worth building first
Automation projects go wrong when they start with a diagram of every possible journey. The sensible order is to build where money is currently being lost, prove it, and extend from there. For almost every business the same three or four flows come first.
A welcome sequence, because new subscribers are more interested in you at signup than they will ever be again, and a single confirmation email wastes that. Recovery for abandoned actions, whether that is a cart, a part-finished form or an enquiry that went quiet, because these people demonstrated intent and a well-timed reminder recovers a meaningful share of them. Onboarding for new customers, which reduces early cancellations and support load by telling people what to do next. And a win-back or re-engagement flow for customers who have gone quiet, which is cheaper than acquiring their replacement.
For businesses that sell through conversations rather than a checkout, the lead nurture and follow-up flows matter more than the commerce ones. Speed of first response is usually the single biggest lever, because an enquiry answered within minutes converts far better than one answered the next day, and an automation is the only way to guarantee that at nine on a Sunday evening.
- Welcome, abandoned action, onboarding and win-back come first
- These sit at the biggest leaks in most businesses
- For enquiry-led businesses, speed of first response is the main lever
- Prove one flow before mapping the whole lifecycle
- Extend from what worked, not from the diagram
Designing triggers that fire at the right moment
A flow is only as good as what starts it. The trigger decides whether the message arrives as helpful or as intrusive, and the difference is often a matter of timing and precision rather than content.
Good triggers are specific and observable. Someone submitted this form. Someone added to cart and did not purchase within an hour. Someone viewed the pricing page three times in a week. Someone has not opened anything for ninety days. Vague triggers such as showed interest produce vague messages that land wrong. The trigger should also carry context into the email, so the message can reference what actually happened rather than sending a generic nudge.
Timing needs deliberate thought at each step. Too fast reads as surveillance, particularly for browsing behaviour. Too slow and the moment has passed. A cart reminder within an hour or two performs well because the intent is still live. A re-engagement email sent the moment someone misses a window feels aggressive. Delays should also respect business hours and time zones where the message expects a response, and every flow needs exit conditions so that someone who buys stops receiving reminders to buy. Forgetting exit conditions is the most common and most embarrassing automation fault.
- Trigger on specific observable events, not vague interest
- Carry context into the message so it can be specific
- Match delay to intent: fast for carts, slower for browsing
- Respect time zones and business hours where a reply is expected
- Always set exit conditions so buyers stop getting sales reminders
Avoiding over-messaging
Every flow built in isolation looks reasonable. The problem appears when several are live at once and one person qualifies for four of them in the same week. They do not experience four thoughtful sequences. They experience a company that will not leave them alone, and they unsubscribe from all of it at once.
The controls that prevent this are worth setting up before you have a problem. A cap on how many automated emails one person can receive in a period, applied across all flows rather than per flow. Priority rules so that when two flows compete, the more relevant one wins and the other waits or is skipped. Suppression during active conversations, because a lead in a sales discussion should not be receiving nurture emails about getting started. And coordination with your campaign calendar, so a person does not receive a newsletter, a promotion and three automated messages in the same two days.
The mindset that helps is counting from the recipient side. Nobody in the business ever sees the total, because each flow is owned separately and each looks modest. Adding up what a single realistic person receives across a month is a five-minute exercise that regularly changes how a programme is built.
- Cap total automated messages per person across all flows
- Set priority rules for when flows compete
- Suppress marketing while a sales conversation is active
- Coordinate flows with the campaign calendar
- Count what one realistic person receives in a month
Writing each step for its moment
The temptation with a five-email sequence is to write one email and vary it. It shows immediately. Each step sits at a different point in someone understanding of you, and the message that suits step one is wrong for step four.
A welcome sequence, for example, has distinct jobs across its steps: confirming the person made a good decision and delivering whatever was promised, then establishing who you are and why you are worth attention, then showing the thing you do best, then making an offer once some trust exists. Compressing all of that into one email or repeating the same pitch four times both fail, in different ways.
A few habits keep sequences readable. One purpose per email, so the reader is never choosing between three actions. Reference what actually happened, since a message that mentions the specific item or the specific enquiry outperforms a generic reminder by a wide margin. Vary the format, because five identical templates in a row feel like a machine. And write the last step to be genuinely final rather than trailing off, since a clear last email often performs better than the ones before it.
- Each step has a different job, write it for that job
- One purpose and one action per email
- Reference the specific action that triggered the flow
- Vary format so a sequence does not read as a template
- Give the sequence a real ending, not a fade out
Flows decay, and nobody notices
The comfortable idea about automation is that you build it once and it works forever. What actually happens is that it works, and then the business changes around it. A product is retired but still recommended in step three. A price is out of date. A link points at a page that was redesigned. A discount code expired eighteen months ago. A tone that suited the company at twelve people reads oddly at forty.
The technical side decays too. An integration changes and a field stops populating, so emails go out addressed to a blank space. A trigger stops firing because a form was rebuilt. A flow keeps running against a segment that no longer means what it meant. None of this announces itself, because automated systems fail quietly by design, and the first sign is often a customer mentioning something odd.
The fix is a scheduled review rather than vigilance. Quarterly, walk through each live flow as a subscriber would: check every link, every price, every claim, every merge field, and confirm the trigger still fires. Look at the numbers per step to see where people stop. Retire flows that no longer serve a purpose instead of leaving them running. This is unglamorous maintenance and it is the difference between a system that earns for years and one that quietly embarrasses you.
- Walk every live flow as a subscriber each quarter
- Check links, prices, claims and merge fields
- Confirm triggers still fire after any site or form change
- Review per-step numbers to find where people drop
- Retire flows that no longer have a purpose
Measuring incremental revenue, not attributed revenue
Automation platforms report attributed revenue: any purchase within a window after an automated email is credited to that email. On that basis, an abandoned cart flow always looks spectacular, because a significant share of the people who receive it would have come back regardless. The email did not cause all of that revenue. It received the credit for it.
Incremental revenue is the number that answers the real question, which is what the flow added. The way to find it is a holdout: a randomly chosen share of the eligible audience is excluded from the flow, and you compare their outcomes with everyone else. The difference is what the automation caused. It is a small amount of setup and it changes conversations, because the flows people assume are their best performers are sometimes mostly taking credit, while a quieter flow turns out to be doing real work.
Two other measures deserve tracking alongside it. Cost, meaning the effort to build and maintain against what the flow returns, because a complex sequence earning modestly may not be worth its upkeep. And harm, meaning unsubscribes and complaints attributable to the flow, since a sequence that earns revenue while burning through your list is borrowing from next year. We report all three, and we would rather show a smaller honest number than a large attributed one.
- Attributed revenue credits purchases that would have happened anyway
- Use a holdout group to measure what the flow actually added
- Expect some celebrated flows to shrink under this test
- Weigh build and maintenance cost against real return
- Track unsubscribes and complaints per flow, not just revenue
Platform choice and the data underneath
Platform arguments occupy more time than they deserve. The mainstream tools are all capable of the flows described here, and the difference in outcome between two reasonable choices is far smaller than the difference between a well-built programme and a neglected one. What matters is fit: does it connect to the systems you already have, can your team use it without a specialist, and does the pricing model behave sensibly as your list grows.
What does determine success is the data underneath. Automation runs on knowing who someone is, what they did and where they are in their relationship with you. If that information is scattered across a website, a checkout, a CRM and a spreadsheet, no platform will rescue it. Getting the events flowing correctly, and agreeing what each status means, is usually the real project, and it is the part that takes longer than the flow building.
That is also why automation and CRM work belong together. The flows depend on lifecycle stages being accurate, and the lifecycle stages depend on someone maintaining them. Where a client wants automation and the underlying data is not there, we say so and sequence the data work first. Building sophisticated flows on unreliable data produces confident messages sent to the wrong people, which is worse than sending nothing.
- Most mainstream platforms can do the work, fit matters more than features
- Check integrations, team usability and how pricing scales
- The real project is usually getting the underlying data right
- Flows depend on lifecycle stages being accurate and maintained
- Fix the data before building sophisticated automation on top of it
A clear path, step by step
- 01
Map the lifecycle
Where leads and customers currently go quiet, and which flows would catch them.
- 02
Build the flows
Sequences, triggers, timing and branching logic set up in your platform.
- 03
Write every step
Each email written for its moment in the journey, not copied down a template.
- 04
Refine on data
Flow revenue reviewed monthly, weak steps rewritten, winners extended.
Why choose us for this
We map the whole lifecycle before building any single flow
Copy is written per step, because journey context changes the message
Flows are refined monthly, not built and abandoned
Common questions
Which automated flows should we build first?
A welcome series for new subscribers, recovery for abandoned actions, and onboarding for new customers. These sit at the biggest revenue leaks in almost every business, and each pays back quickly.
Will automated emails feel robotic to customers?
Only if they are written that way. A triggered email that lands at exactly the right moment feels more personal than a scheduled blast, because it responds to what the person just did.
Explore related work
Want this for your business?
Book a free visibility call and I will tell you honestly whether I can help.
How this is delivered
One person leads every project. Where a job genuinely needs a specialist, I bring in people I have worked with before and manage them, so you get one point of contact and one invoice rather than three suppliers blaming each other.
- You talk to the person responsible for the work, not an account manager
- Specialists are briefed and managed by me, and their work is checked before it reaches you
- One contract, one invoice, one place to chase