Email marketing — lifecycle flows that reach the inbox and know your pipeline

Most businesses treat email as a megaphone: a newsletter when someone remembers, a discount blast when sales are slow, and a steady bleed of unsubscribes in between. The messages that would actually earn something never get built. Nobody is welcomed properly, nobody is followed up after a quote, and nobody hears from you again after an abandoned cart or a year of silence.

Email is the only channel you own outright. No algorithm sits between you and your customer. What does sit there is deliverability, and that is an engineering problem before it is a copywriting one.

What email marketing means in our hands

Deliverability is treated as infrastructure. Before a campaign goes out we authenticate your sending domain properly: SPF, DKIM, and a DMARC policy moved from monitoring to enforcement as the reports come in. Then a dedicated sending subdomain, domain warm-up, list hygiene, and monitoring of bounces, complaints, and inbox placement. A surprising share of "email does not work for us" is an authentication problem nobody looked at.

Lifecycle flows, not broadcasts. The compounding value in email is automated: welcome sequences that arrive while interest is highest, nurture tracks that keep a slow buyer warm, cart recovery, post-purchase and review requests, win-back for lapsed customers. Broadcasts sit on top of a working lifecycle, not instead of one.

Email that knows the pipeline state. We build and run our own CRM in production, so we wire email to live customer records rather than a stale export. Segments read real fields: stage, value, purchase history, service line, region, last interaction. A customer who just bought never gets the cart reminder; a closed deal exits the nurture track by itself.

What a typical engagement includes

• Deliverability audit and domain authentication: SPF, DKIM, DMARC, a dedicated sending subdomain, domain warm-up
• A lifecycle map: which flows exist, what triggers each, what exits each, and what a person sees when two could fire at once
• Flow build and copywriting: welcome, nurture, abandoned cart, browse abandonment, post-purchase, review request, win-back, re-engagement
• A segmentation model built from CRM or store data, with suppression rules so nobody gets contradictory messages
• A modular template system with dark mode and plain-text fallbacks, plus a broadcast calendar if you send them
• Integration wiring: CRM, store, booking system, and site forms feeding events into the platform both ways
• Compliance: consent capture, a preference centre, unsubscribe handling for CASL, CAN-SPAM, and GDPR

The approach and the stack

• Platforms: we work in what you already run (Klaviyo, Mailchimp, HubSpot, Brevo) and use Resend for transactional email inside custom apps
• Templates: hand-built HTML with table layouts and inlined CSS, because email clients render years behind browsers. Tested on Gmail, Outlook, Apple Mail, and mobile
• Data: site, store, and CRM events feed the platform, so segments stay current without manual exports
• Accessibility: real text over images, readable sizes, alt text, sensible contrast, the same WCAG 2.1 AA standard we hold every build to
• Testing: subject lines, send times, and offers tested one variable at a time, at volumes that make the result mean something

Nurture and newsletter copy is far easier with a content engine behind it: see /services/content-marketing.

What this looks like in practice

Two shapes most engagements take:

An ecommerce lifecycle build. A store sending the occasional newsletter gets the full automated layer: welcome and first purchase, cart and browse recovery, review requests, replenishment reminders, win-back for lapsed buyers, all segmented by purchase history. Usually paired with an ecommerce build so the events feeding the flows can be trusted.

A B2B nurture programme tied to the pipeline. A service business with a long sales cycle wires its CRM into email: an inquiry triggers a welcome and proof sequence, quiet deals get nudged on a schedule, closed deals exit automatically, won customers move onto onboarding and referral tracks. This is where /services/crm-development and email stop being two separate projects.

Pricing

Email work is scoped per project. The number of flows, the platform, how clean your data is, and the state of your sending reputation all change the work, so we quote after a short call, not from a rate card. Contact us with your platform and list size. Ongoing sends can run under a Care Plan.

Ready to start?

Send us your last three campaigns and your bounce rate, and we will tell you honestly whether the problem is the copy, the list, or your DNS records. We reply to every brief within four business hours.

Start an email marketing project → — or book a 30-min call