What we hear
From a client
That's how a Frankenstein email gets built.
From a client
No documentation has been found.
From a client
You can't turn it off: the inbox switches on its own and recolours the email.
From a client
Without a system, every email starts from scratch: layout, copy, code and testing, one at a time.
What looks right in the preview falls apart in the inbox.
Missing images or broken links show up in replies, not in review.
When they're away, production stops.
Spacing, buttons and colours change depending on who built the email.
Small changes wait in a queue because nobody else can touch the code.
Dark logos vanish on dark backgrounds and colours shift unexpectedly.
Without a guide, every new person learns by trial and error.
Nobody decided how the brand should look in dark mode, so the inbox decides.
The templates are tied to one platform and can't come along.
Screen readers, contrast and alt text have never been checked.
Without a process, shortcuts become the norm.
What you get
Built into *the platform you already use*, or into Denada and exported to any ESP.
How it works
The tools behind it
Developed in-house by EmailBoutique and included in every project.
Questions
Over 36 so far, including Klaviyo, Braze, Salesforce Marketing Cloud, Marketo, Iterable, HubSpot, Customer.io and Brevo.
Yes. Existing Figma files or live emails are a fine starting point; they're turned into reusable blocks rather than rebuilt one by one.
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.