Documentation and training

So your team can run it.

Guides, a production process and team courses, so the system keeps working long after the build.

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 that *outlasts the project.*

Written down, taught and supported, so it *never depends on one person*.

Book a consultation ↗
  • Block and options guides with light and dark views
  • A production process from wireframe to send
  • Copy deck templates, version control and a sample library
  • Team courses and on-call help as the team grows

How it works

From first call *to handover.*

  1. How the team works. A look at who builds, reviews and sends today.
  2. Block guides. Each block and its options, in light and dark.
  3. Production process. From wireframe to send, written down.
  4. Team course. Live sessions built around your system.
  5. On-call help. Support as the team grows.

The tools behind it

Built with *our own tooling.*

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

Questions

Good ~to know.~

Can you document a system you didn't build?

Yes. Existing templates and blocks are reviewed first, then documented as they are, with notes on what to fix.

Is training live or recorded?

Live sessions with your team, with recordings and guides to come back to.

What does on-call help cover?

Questions as the team builds: a block that won't behave, a new layout, or a check before a big send.

Ready to make the system *outlast* the *project*?

Describe how your team builds today. You'll hear back how guides and training could fit.

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.