Templates and ESP builds

Your system, coded into the platform you use.

Hand-coded, responsive blocks that hold up in Gmail, Outlook and Apple Mail, set up in the ESP you already send from.

What we hear

Sound ~familiar?~

From a client

We copy the copy of the copy.

That's how a Frankenstein email gets built.

From a client

The person who maintained our email templates left last March.

No documentation has been found.

From a client

Can we just ignore dark mode, or turn it off?

You can't turn it off: the inbox switches on its own and recolours the email.

From a client

It's just an email. Why does it take me all week?

Without a system, every email starts from scratch: layout, copy, code and testing, one at a time.

Templates break in Outlook.

What looks right in the preview falls apart in the inbox.

Broken sends get noticed by customers first.

Missing images or broken links show up in replies, not in review.

Only one person knows how the templates work.

When they're away, production stops.

The brand drifts from send to send.

Spacing, buttons and colours change depending on who built the email.

Every campaign needs a developer.

Small changes wait in a queue because nobody else can touch the code.

Dark mode turns logos invisible.

Dark logos vanish on dark backgrounds and colours shift unexpectedly.

New team members break things.

Without a guide, every new person learns by trial and error.

Dark mode is an afterthought.

Nobody decided how the brand should look in dark mode, so the inbox decides.

Moving ESP means starting over.

The templates are tied to one platform and can't come along.

Nobody is sure the emails are accessible.

Screen readers, contrast and alt text have never been checked.

The system drifts back into one-off emails.

Without a process, shortcuts become the norm.

What you get

Blocks that *hold up everywhere.*

Built into *the platform you already use*, or into Denada and exported to any ESP.

Book a consultation ↗
  • Master templates and block libraries in Klaviyo, Braze, Salesforce Marketing Cloud, Marketo, Iterable, Customer.io and more
  • Block libraries in Denada, so your team builds emails visually from the system and exports to any ESP
  • Responsive layouts that adapt to desktop, tablet and phone
  • Interactive and animated email where the inbox supports it, with a solid fallback where it doesn't.

How it works

From first call *to handover.*

  1. Review. The design, the ESP and how the team builds today.
  2. Block plan. Which blocks the system needs, and their options.
  3. Hand-coded blocks. Responsive HTML that holds up in Gmail, Outlook and Apple Mail.
  4. Testing. Every block across clients, in light and dark mode.
  5. Setup. Loaded into your ESP or a Denada library, ready to use.
  6. Handover. Guides and training, so the team builds on its own.

The tools behind it

Built with *our own tooling.*

Developed in-house by EmailBoutique and included in every project.

Questions

Good ~to know.~

Which ESPs do you work with?

Over 36 so far, including Klaviyo, Braze, Salesforce Marketing Cloud, Marketo, Iterable, HubSpot, Customer.io and Brevo.

Can you work from our existing designs?

Yes. Existing Figma files or live emails are a fine starting point; they're turned into reusable blocks rather than rebuilt one by one.

What is Denada, and do we need it?

Denada is a visual email builder for running a block library: your team assembles emails from the system's blocks and exports to the ESP you already use. It's optional; templates can also live directly in your ESP.

Ready for *templates* that *hold up*?

Describe the inbox problems and the ESP you send from. You'll hear back how the build could work, before you commit to anything.

YouIt's messyNo name for it yet. That's fine.
NextA First LookA page showing how it could be solved.
ThenYours to runBuilt to own, not rent.
This site uses cookies to understand how it's used. Essential cookies are always on; the rest is up to you.