// Marketing automation

THE RIGHTNEXT STEP.ON TIME.

// The useful starting point

Connect the enquiry, the message and the person responsible. Marketing workflows designed around real customer journeys, with rules you can understand and own.

// 01 / The short answer

Automate a useful journey, not a loose end.

Marketing automation connects customer actions to agreed next steps: acknowledge an enquiry, notify the right person, welcome a subscriber or deliver a relevant nurture message. I map and build defined workflows using the capabilities of your chosen platforms and agreed connections, then test the rules before they go live.

Every workflow needs an entry point, a purpose, a responsible owner and a way to stop. We define what happens when someone replies, buys, unsubscribes, submits twice or no longer fits the audience. The service covers marketing journeys and their immediate handoffs; it does not assume responsibility for your whole CRM, sales operation, finance system or business processes.

// 02 / Where this fits

Repeat the useful part.

A focused workflow is valuable when the rules are clear and the people behind it are ready.

// 01

Enquiries need a reliable handoff

Messages arrive through different forms, acknowledgement is inconsistent or the next owner is unclear. We define routing and notification rules while keeping human follow-up visible.

// 02

People need help between decisions

Subscribers or prospects have a predictable next question. A short welcome or nurture journey can provide useful information without sending the same message to everyone.

// 03

The process is ready to be defined

You can name the source data, owner and desired action. If nobody agrees how the manual process should work, we settle that before automating it; software cannot resolve an unclear responsibility.

// 03 / What I do

Design the rules. Test the exceptions.

Each agreed workflow has a specification, implementation and handover rather than a diagram that stops before delivery.

// 01

Journey and data map

Define the starting action, eligibility, required fields, purpose and success condition. Identify which system holds each value and how changes will be passed between systems. Use the minimum data needed for the agreed journey.

// 02

Trigger, branch and exit rules

Specify entry and re-entry, wait periods, relevant segments, exclusions and stop conditions. Define what happens after a reply, completed action or preference change so people do not keep receiving an outdated sequence.

// 03

Workflow build and handoffs

Configure the agreed emails, audience updates, notifications and supported platform connections. Include clear human ownership where a person must call, review or approve. Custom development, connector subscriptions or deeper CRM changes are separately assessed.

// 04

Testing and operating guide

Use test contacts and documented cases to check eligible and excluded paths, duplicate submissions, missing data and downstream failures. Hand over the workflow map, editable assets, pause procedure and responsibilities for checking it after launch.

// 04 / In application

Small workflows. Clear responsibilities.

Illustrative marketing workflow applications, not claims about systems installed for these sectors.

// Automotive

Route a booking request without promising a booking.

A workshop receives service requests online but needs a staff member to confirm availability.

The approachAcknowledge receipt, notify the nominated team and preserve the request details. State clearly that the requested time is unconfirmed. Keep any service-reminder integration dependent on agreed records and platform access.

What to checkCheck acknowledgement delivery, handoff completion and whether requests reach the right owner.

// Membership organisations

Welcome the right member category.

New members need different resources according to category, but the onboarding email is sent manually.

The approachUse an agreed membership-status event and verified category to enter the correct welcome path. Exclude incomplete applications and provide a human review route for missing category data.

What to checkCheck correct journey entry, resource actions and member support questions.

// Landscaping

Follow an enquiry with useful preparation.

Prospects ask about a project and need to understand the next conversation before sending more information.

The approachAcknowledge the request, alert the project owner and, where appropriate, send an agreed preparation message. Stop nurture when the prospect moves to a live conversation or no longer wants contact.

What to checkReview successful routing, response ownership and the usefulness of information supplied before the meeting.

// Illustrative workflow specification

The stopping rule matters too.

Example rules for an enquiry follow-up journey. The actual platform, timing and messages are agreed for your business.

The stopping rule matters too.
Event or conditionWorkflow decisionOwner or safeguard
An eligible form submission is received.Acknowledge the request and notify the assigned person.A named staff member owns the response; acknowledgement is not acceptance or availability.
The same person submits again.Apply the agreed duplicate and re-entry rule rather than starting overlapping journeys.Check the record and preserve any materially new request.
The prospect replies or progresses.Exit or pause the nurture path when the connected system supports a reliable status signal.Use a documented manual stop when that signal is unavailable.
A contact opts out or is suppressed.Prevent subsequent marketing sends and update connected audience status where supported.Test suppression across every agreed path before activation.
A required field or connection fails.Hold the affected step and surface an exception rather than silently guessing.Name the person checking exceptions and the action they should take.
// 05 / The method

Map it. Build it. Try to break it.

// 01

Choose one worthwhile workflow

Review the manual process, platforms, data and business owner. Select a bounded journey with an observable outcome and a clear reason to automate.

// 02

Approve the specification

Agree the map, messages, fields, entry and exit rules, exceptions and account responsibilities. Check platform and connector capability before promising the integration.

// 03

Build and test the paths

Implement the agreed workflow and use test records to exercise success, exclusion, duplicate and failure paths. Resolve defects before activation.

// 04

Activate and hand over

Activate after approval, check the first real entries and hand over the operating guide. Define any ongoing review or maintenance separately, including who reacts when a connected tool changes.

// 06 / A clear agreement

Bounded workflows. Visible ownership.

The right scope makes the work useful. Agree the deliverables, dependencies and responsibilities before starting.

Included in the agreed work

  • Agreed marketing journey, data and workflow specification
  • Configuration of supported triggers, branches, messages and handoffs
  • Test cases, corrections and approved activation
  • Workflow documentation, pause procedure and owner handover

Separate or out of scope

  • Whole-business CRM implementation or operational transformation
  • Finance, inventory, payroll or other back-office automation
  • Unsupported integrations or unlimited custom development
  • Unattended sales decisions or ongoing maintenance unless agreed

What shapes the cost

Cost depends on workflow count, branches, data quality, platforms, connection methods, message content and testing complexity. Licences, usage fees, custom integrations and ongoing review are identified separately where needed.

What shapes the timing

The process map and platform capability check come first. Account access, agreed data fields and approved messages are dependencies for build. Activation follows successful testing and a named person accepting ownership of exceptions.

Who owns what

I specify, configure and test the agreed marketing workflows. You approve the business rules and messages, confirm contact permissions, supply account access and appoint the people owning responses and exceptions. Your business owns the accounts and documentation; connected providers control their own platform availability.

// 07 / Work you can inspect

Ask to see the rules, not a magic box.

The illustrative specification above shows the detail you should be able to inspect in a workflow: eligibility, re-entry, exits and failure ownership. The delivered map and test record make those rules reviewable, while the operating guide explains how your team can pause or maintain the journey. The email service covers the communication work that may accompany the build.

The messages inside the workflow

Audience, copy, templates and approval for the communication programme.

// 08 / Useful questions

Before we start.

What can you automate?

Defined marketing journeys such as enquiry acknowledgements and routing, subscriber welcomes, nurture sequences and agreed lifecycle follow-up. The exact actions depend on your data, permissions and platform capabilities. We verify the connection before including it, rather than assuming every tool can exchange every field.

Will this replace our CRM or sales team?

No. The scope is marketing workflows and their agreed handoffs. A CRM may provide a status or receive an update, but replacing it or redesigning the whole sales operation is a separate project. People still own conversations, exceptions and decisions that need judgement.

Can you work with our existing tools?

We start there. I review the required triggers, fields, supported connections, account permissions and ongoing cost. If a tool cannot provide a reliable event or update, we choose a simpler workflow, a documented manual step or a separately assessed integration.

How do you stop people receiving the wrong follow-up?

Define eligibility, exclusions, duplicate rules and exit conditions before build. Then test them with records representing different situations. Where a sales status or reply cannot be detected reliably, give the owner a clear manual pause or removal procedure rather than implying the system knows.

Who checks it after launch?

The handover names an owner for exceptions, data changes and stopping the workflow. Any ongoing monitoring or review work I provide is explicitly scoped. A connection can change, expire or fail, so the operating guide needs an escalation route and a way to pause sending.

What should we automate first?

Choose a repeated journey with clear rules, clean inputs and a useful outcome, such as getting a genuine enquiry to the right person. Start with the smallest complete workflow, including its failure path. A complex multi-stage nurture programme can wait until the first handoff is dependable.

// A useful next step

FIX THE HANDOFF.

Bring one repeated marketing task, the tools involved and the person who owns the next step. We can map a useful workflow before deciding what to build.