All articles

Where should you start with email automation?

Build the right journey instead of sending more messages. Start with permission, segmentation and a clear first flow.

Understand where the list comes from

Before automating, establish who you are contacting and on what permission basis. Transactional emails and marketing campaigns serve different purposes. Check the origin and permission status of contacts before adding them to campaigns. Purchased or unclear lists undermine customer trust and data quality.

Give the first flow one purpose

A welcome flow is a useful starting point. Introduce the brand, explain what subscribers can expect and make the next action clear. Answer one question per message rather than reproducing the entire catalogue. A first-time visitor and an existing customer do not necessarily need the same message.

  • Define the trigger: signup, purchase or another event.
  • Decide who should be excluded.
  • Choose one primary action for the message.

Treat cart reminders as a customer experience

Not every abandoned cart is waiting for a discount. Delivery information, a payment question or uncertainty about a product may have stopped the purchase. Offer useful information and a clear link. Make sure people leave the flow after completing an order.

Do not rely on a single metric

Open rate alone cannot explain commercial impact. Review clicks, store behaviour, orders and unsubscribes together. Understand the reporting window and revenue attribution before comparing campaigns. Establish a baseline, then change one variable at a time, such as subject line, content or timing.

Test the actual journey

Subscribe with a test contact, inspect the mobile layout and open every link. Check discount conditions where relevant. A working unsubscribe mechanism matters as much as visual design. Assign an owner and review schedule so automation becomes a maintainable process.

Let’s build your roadmap

What you need to know before deciding.

A productive partnership starts with clear expectations. Here are practical answers before our first conversation.

Discuss your project scope
Which email flows should come first?

After reviewing list sources and consent, we prioritise welcome, cart recovery or post-purchase communication against business goals. Entry, exit and sending conditions are defined for each flow.

Can we keep our existing email platform?

We review the tool, store integration, segments and data quality. Improving the current setup may be preferable to migration. Licensing and any data transfer are scoped separately.

Is open rate the main success metric?

Open rate alone is insufficient. Clicks, orders, flow exits and unsubscribes are considered together. Attribution windows and store records are reviewed before interpreting revenue.

How is the project priced?

Page and language counts, product data, design and integrations determine scope. Setup and development are considered separately from ongoing services. Media spend, platform subscriptions, paid themes and apps are third-party costs to clarify separately in the proposal.

When can we start and finish?

Timing depends on content readiness, catalogue size, migration, integrations and approval cycles. Discovery produces a phased plan with dependencies. We establish a realistic scope before committing to a delivery date.

How are accounts, code and support handled?

Access to stores, domains and ad accounts, code handover, documentation and maintenance responsibilities should be agreed in writing in the proposal. Post-launch support and further development need a separate scope, duration and pricing arrangement.