Developers own the code, marketers build the campaigns

In a large email team, developers and marketers work on the same campaigns and need different things from them. Developers need control of the HTML, because it has to render in Outlook, follow the brand, and work with the ESP's personalisation. Marketers need to get campaigns out without waiting for a developer every time.

Most email tools are built for one of the two groups. A shared email design system lets both work on the same system, each in their own way.

Why one side usually loses

When developers build every campaign, they become the bottleneck. A new campaign, a changed headline or an extra market version all wait in the same queue.

When marketers get a no-code builder instead, they can move fast, but nobody owns the code. Layouts drift from the design, fixes for email clients get lost, and the ESP's personalisation breaks in ways nobody notices until after the send.

No-code builders also come with constraints of their own. Most of them put campaigns together from a fixed set of blocks on a grid. That is fine for simple layouts, but it makes it hard to get campaigns that look like your brand and your website, and that stand out in the inbox.

Who does what

Developers own the design system

Developers write the base layout and the reusable modules in HTML and Liquid. Each module exposes only the settings marketers need, with validations on every input.

The design system can live in Git as Liquid and JSON files. With the Better Email CLI, teams review changes in pull requests, check them in CI, and push them to Better Email as a candidate version that a person publishes. Teams that already build with Maizzle or React Email can keep doing that.

Marketers build the campaigns

Once the design system is in place, marketing builds campaigns on its own in the visual editor. The editor is generated from the modules and settings the developers defined, so marketers can:

• build campaigns from approved modules without editing HTML
• change text, images, links, subject lines and preview text through defined inputs
• choose only approved colours and modules for each part of the campaign
• see validation errors while they work, not after export
• preview desktop and mobile versions before review and approval

Reviewers approve in the campaign

Brand, legal and local markets need to sign off, and in many teams that happens over email and screenshots. In Better Email, reviewers comment and approve inside the campaign, and approvals belong to the revision they were given on. People outside the company, like a legal firm or the agency's client, review from a private link without an account.

AI agents work inside the same rules

An AI agent that builds campaigns needs the same limits as a marketer. Betty, our AI agent, builds from the approved modules, and her campaigns go through the same validations and checks as everything else. Teams that prefer ChatGPT or Claude can connect them through our MCP server, and the same rules apply.

How work moves through the system

1. Developers define the system. HTML, Liquid, settings, validations, colour palettes and content zones decide what the editor can produce.
2. Marketers build the campaign from the approved modules, alone or with Betty.
3. Reviewers approve, and pre-flight checks run before the campaign can be exported.
4. The campaign is exported to the sending platform the team already uses. Better Email does not replace the ESP.

Changes to the design system follow the same path in the other direction. A developer opens a pull request, CI checks it, and the change is tested in real campaigns as a candidate before anyone publishes it to every campaign.

The owner doesn't have to be a developer

The design system needs an owner, but not every owner writes HTML. We see more and more people with less technical backgrounds own the design system and make changes together with Betty. Because every change can be previewed in real email clients before it goes live, they can make changes safely.

Some companies have their agency own the design system instead. The agency works in the company's own Better Email account, and the company's marketers build the campaigns.

When a tool for one group is the better fit

A tool made for only one of the two groups can be the right choice when only that group works in it.

Developer-focused tools such as Parcel suit teams whose developers create and maintain every campaign. Better Email adds a marketer editor generated from the design system the developers own, so day-to-day campaign production can move to marketing.

Marketing-focused tools such as Knak, Stripo and RGE Studio (formerly Beefree) suit teams that want a no-code setup and whose campaigns fit the drag-and-drop blocks and layouts these tools are built around. When a brand needs more than those blocks allow, teams get stuck. Better Email keeps the visual workflow for marketers, and gives developers direct ownership of the HTML, Liquid, settings and validation rules behind it, so the design system can look the way the brand does.

To see both sides, read how the code workflow works in Design Systems as Code, and what marketers get in the visual editor.