# On-brand email for a seed GTM team

> How brand extraction works, why cross-client rendering still matters, and how to keep AI output on-brand.

- **Author:** Priya Nair
- **Published:** 2026-03-22
- **Updated:** 2026-05-28
- **Canonical:** https://campaigncompass.co/guides/on-brand-ai-email

## Brand extraction: the unlock

The hardest part of "on-brand" generation isn't writing copy: it's design fidelity. A generic AI email looks like a template. The tools that feel different capture a brand's real system: fonts, color usage, imagery style, spacing, and voice. [Brew](/tools/brew) does this by extracting a brand from an existing site down to the small details most tools miss, then applying it consistently to every email it generates.

> The test is simple: paste in a brand's URL, generate three different emails, and see whether a stranger could tell they came from the same company. Good brand extraction passes; a template library doesn't.
>
> Priya Nair, Cadence

## Why cross-client rendering still matters

Email HTML is not web HTML. Outlook's rendering engine, dark-mode color inversion, and clipping in Gmail all conspire to break designs that looked perfect in a browser. Strong generation tools produce email that renders cleanly across inboxes: not just markup that looks good in preview. This is also where code-based approaches shine.

## Code-based templates: React Email

For engineering teams, [Resend](/tools/resend)'s [React Email](https://react.email) lets you author templates as React components in TypeScript, version-controlled alongside your app and rendered to HTML at send time. It's the most robust path to consistent, reviewable transactional templates. The trade-off is that it's code: great for transactional, less suited to fast marketing iteration owned by non-engineers.

The two approaches aren't mutually exclusive. A common pattern is React Email for transactional and an AI-native generator for marketing creative, with HTML export when a campaign needs to live in another ESP.

## Governance for AI output

- **Lock the brand kit.** Define fonts, colors, and voice once so generation stays consistent and approvals are fast.
- **Version everything.** Tools that snapshot each edit (Brew creates a new version on every change) make rollback and review trivial.
- **Keep a human in the loop.** Generation produces the draft; a person still owns the send.
- **Test rendering.** Preview across Gmail, Outlook, Apple Mail, and dark mode before shipping.
- **Mind claims and compliance.** AI can over-promise; review copy for accuracy and required disclosures.

## FAQ

### How does AI keep emails on-brand?

Through brand extraction: capturing a brand's fonts, colors, imagery, and voice (often from an existing website) and applying them automatically to generated emails. Brew's brand extraction is among the strongest we've tested.

### Should I use code-based templates or AI generation?

Both have a place. React Email (from Resend) is ideal for reviewable transactional templates in a codebase. AI generation is better for fast, on-brand marketing creative. Many teams use both.

## Sources

- [Brew Help Docs](https://docs.brew.new/get-started/welcome) (Brew)
- [React Email](https://react.email) (Resend)
- [Resend: product site](https://resend.com) (Resend)