Launched this week
Brew is the fastest way to design and send beautiful, on-brand emails and automations that render perfectly in every inbox. Describe a campaign or a multi-step automation in plain English, and Brew builds the whole thing in seconds: copy, design, audience, and logic. Works with any AI agent: paste our docs into OpenClaw, Viktor, Claude, or Lovable. No lock-in: send from Brew or export to your ESP. Free to get started.
Free Options
Launch Team / Built With
congrats on the launch :) this feels like a very obvious pain point to go after. i like that it’s not just “generate an email”, but the whole messy part around brand, sequence logic, variants, and inbox-safe html.
curious how the workflow feels once brew has made the first version. do teams usually treat it as ready to send, or is there a review/tweak step before it goes live?
Thanks @kar_re, and you have summed up the hard part exactly...
The first version is meant as a strong starting point, not a press-send-and-walk-away moment. Most teams treat it like a great first draft: it gets you 90 percent of the way there, then you refine in chat (make this punchier, swap the hero, tighten the CTA) and give it a quick review before it goes live.
The point is not to remove the human, it is to delete the tedious production work so the human can focus on the judgment calls.
Honestly, for email going out to thousands of people, you want that review step, and we would never want to take it away. ❤️🔥
@philip_sorensen nice, that’s a good distinction. also love that the “human stays in the loop” part is explicit instead of pretending review can disappear entirely.
Exactly @kar_re. The tools that pretend review can vanish are the ones that scare me, especially in email where a mistake goes to thousands of people at once. Appreciate you thinking it through with me, and thanks again for the support. 🔥
"Renders perfectly in every inbox" is the claim I'd stress-test first, because Outlook's rendering engine has buried prettier email tools than this. When Brew generates a layout, is it producing battle-tested table-based HTML under the hood, or modern CSS that looks great in Apple Mail and falls apart in Outlook 2016? That one answer decides whether I'd trust it for a real send.
Great question to stress-test first @sounak_bhattacharya, and the honest answer is that the safety lives in how generation is constrained, not in a cleanup pass afterward. We do not let the model emit free-form modern CSS and hope it survives Outlook. Output is locked to a vetted set of email-safe building blocks, the battle-tested kind that hold up in the Word rendering engine, so it cannot produce something that looks great in Apple Mail and collapses in Outlook 2016. On top of that we have done a lot of testing and evals across real clients to find what actually holds everywhere. Outlook specifically is the one we obsess over. Happy to go deeper if useful.
The "renders perfectly in every inbox" claim is what caught my eye —
Outlook's rendering quirks alone have killed so many email tools.
How are you handling that under the hood?
Outlook is exactly the one that has killed prettier tools than ours @hirogure, so we treated it as the hard problem from day one. Without giving away the recipe, it comes down to a combination of things: generation constrained to email-safe markup rather than free-form CSS, plus a lot of testing and evals across real clients to make sure it holds up. The result is rendering you do not have to babysit, Outlook included.
Gents, this is an amazing tool but am I going crazy or isn't there any undo button? I've been trying to perfect an e-mail for almost an hour but always seem to mess things up by dragging or fiddling after which my only option is to start over with a previous version but losing all the steps in between that said version and the point where I messed up. What am I missing? *sweating profusely : )
Brew
@kristof_bogaerts1 Hey Kristof! Great question. We have control + z or command + z for manual edit undos and versioning for any agent chat changes. Let me know if you have any issues with it, happy to walk you through it in a personal loom or call as well :)
mailX by mailwarm
Which ESPs do you support today, and does the export include the automation logic or just the HTML templates?
@karimbenkeroum we have a whole list of ESPs here on our integration doc (https://docs.brew.new/integrations/integrations). Right now, our ESP integrations are to export the HTML templates directly over. What do you have in mind?
renders correctly in outlook is doing the real heavy lifting here. you can build the most beautiful email in the world and outlook will find a way to break it. if this actually solves the rendering nightmare across inboxes thats worth it on its own
You are speaking our language @tina_chhabra. You can build the most beautiful email in the world and Outlook will still find a way to break it, which is exactly why we built for it first instead of treating it as an afterthought. Getting the rendering right across inboxes was the whole point, and honestly the part we are proudest of. Thanks Tina.
mailX by mailwarm
Brew
@daniel_nwankwo Hey Daniel! Yup, you can import html directly into Brew in the email canvas or just forward emails to hello@email.brew.new and find them in your templates.