Email design systems

One source of truth for every email.

The recurring decisions in your emails, made once and logged: colour, type, spacing, modules and dark mode. Your team assembles on-brand emails in Figma instead of redrawing them.

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

A system *your designers run.*

Designed once, tested in *every major inbox*, in light and dark mode.

Book a consultation ↗
  • Colour, type and spacing tokens, built for email clients
  • A Figma library of modules with slots your designers mix and reuse
  • A style guide that logs every decision, including dark mode
  • Faster reviews and a clean handoff from design to code

How it works

From first call *to handover.*

  1. A short call. What's slow, messy or breaking, in your words.
  2. Audit of what exists. Current emails, brand guidelines and the ESP, reviewed together.
  3. Foundations. Colour, type, spacing, grid and dark-mode rules for email, decided once.
  4. Modules. A library built with your designers, reviewed as wireframes before anything is styled.
  5. Style guide. Every decision written down, so the system outlasts the project.
  6. Handover. Training for your team, ready to hand to development.

The tools behind it

Built with *our own tooling.*

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

Questions

Good ~to know.~

Do we need to replace our current templates?

No. The design system can start from what you have; an audit shows what to keep and what to rebuild.

Can our designers work alongside EmailBoutique?

Yes. The library is built with your designers, and it's theirs to run after handover.

Does it include coded templates?

The design system is the Figma side. Coding it into your ESP is Templates and ESP builds, and the two are often done together.

Ready to *stop redrawing* the *same email*?

Describe what's slowing your team down. You'll hear back how a design system could fit, 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.