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
FiloMail
Congrats on the launch!
I really like the positioning here. It is easy to understand, but the part that stands out to me is the last mile: not just generating nice-looking email drafts, but turning them into on-brand, production-ready campaigns and automations that can actually be sent through the tools teams already use.
As someone working around AI + productivity, I think email is one of those areas where pretty demos are easy, but reliable execution is hard. Brand consistency, lifecycle logic, ESP handoff, and rendering across inboxes are where the real value is.
Curious how you think about the rendering/testing layer over time, especially for Outlook, Gmail clipping, and dark mode. If Brew can keep that reliable while making campaign creation feel this lightweight, this could become a very useful tool for growth and lifecycle teams.
Upvoted. Excited to see where this goes.
Thank you @justin_bao, and you have pinpointed exactly where we think the real value sits. Pretty demos are easy in email. Reliable execution across brand, lifecycle logic, ESP handoff, and rendering is the hard part, and it is the part we decided to obsess over.
On the rendering and testing layer over time, the way we think about it is that reliability has to be structural, not a patch we keep applying. Generation is constrained to email-safe building blocks rather than free-form code, so the output cannot drift into something that breaks Outlook, and we keep expanding our testing and evals across real clients as new quirks show up.
Outlook, Gmail clipping, and dark mode are the three we watch most closely, because they are exactly where tools quietly fail. The goal is that the reliability holds as the creation experience gets lighter, not at the expense of it.
Really appreciate the thoughtful read, and good luck with FiloMail.❤️🔥
Askmeety
Thank you @nalin_rajendran, and you have put your finger on the exact thing we worry about most...
Generic, bot-ish email is worse than no email. The way we fight it is by capturing both the art and the science of your brand: not just colors and fonts, but your actual voice and the feel of how you communicate, so the output sounds like you rather than like a model. On top of that we make it easy to experiment with different styles for your brand, so you are never locked into one look. Here is an example of what that looks like for one of our users.
The "describe a campaign in plain English, get the full thing rendered" framing is exactly what email needed — most teams aren't bottlenecked on having something to send, they're bottlenecked on the production tax of every send. I work on StoryRoute on the travel side and we see the same dynamic: people will narrate what they want a city walk to feel like, but they won't sit down and design the route step-by-step. The product that closes that gap wins. Congrats on the launch.
Thank you @samir_asadov , you put it better than we do. "Production tax" is exactly the phrase. The bottleneck was never the idea, it was the eight steps between the idea and the send, and that is where everything quietly dies. Love the StoryRoute parallel too. Narrating the feeling of a walk versus plotting every turn is the same gap, and you are right that whoever closes it wins.
Best of luck with it, and thanks for the kind words. ❤️🔥
@philip_sorensen The eight-steps observation is the part I always come back to. The unit cost of any one step looks trivial ("it's just two minutes to drop in the right image"), so it never gets prioritized — but compounded across every campaign and every team member, those two-minute taxes are where the actual marketing budget goes, just in unbilled hours nobody can see. The tools that win this space are the ones that collapse the eight to two, not the ones that polish step seven. Looks like that's exactly the call you made.
Exactly right @samir_asadov , and "unbilled hours nobody can see" is the cleanest way I have heard it put. That invisible cost is precisely why the category stagnated. Everyone optimized step seven because each individual step looked too cheap to bother rethinking, so nobody questioned the whole chain. Collapsing eight steps to two was the entire bet. It is a harder thing to build than a better step seven, but it is the only version that actually changes the economics for a team. You clearly think about this the same way we do. If StoryRoute is collapsing that same gap on the travel side, you are going to do well.
Been using Brew with the Customer IO integration the past two months, and it works perfectly. We send broadcast emails 5 times per week, and it's traditionally been a huge hassle to produce the content and design the emails — but it's fast (and much better) now. I especially like how we can get very differentiated versions of an email in no time. Reminds me of website building in Lovable. Highly recommend it to any marketers or founders out there!
Thank you @langhede! ❤️🔥
Five broadcasts a week is a brutal cadence to keep up by hand, so it means a lot to hear Brew made it fast and better. The differentiated variants are the feature we love most too, and the Lovable parallel is exactly what we are going for. Grateful for the recommendation, and glad @Customer.io has been working seamlessly with Brew.
Finley
wow! scaling signups -> customers has been a major painpoint, and automating personalized emails seems like it would be the missing piece. LFG brew ☕️☕️ @philip_sorensen
LFG indeed @kevin_suh ☕️ You put it perfectly: the signup is the easy part, turning it into a customer is where everyone leaks, and personalized lifecycle email at scale is exactly the missing piece. Appreciate the energy, now let's get you brewing. ❤️🔥
Finally an ESP that doesn’t feel like operating SAP through a microwave.
You can tell product taste was part of the roadmap, not just deliverability dashboards and 400 toggles.
@pierre_ljubic lol thank you Pierre. "SAP through a microwave" is going on the wall. That is exactly the feeling we were running from. The old tools bury you in 400 toggles and call it power. We wanted something that felt like it had actual taste, so it means a lot that it came through. ❤️🔥
Magic Patterns
Thank you @alexdanilowicz, means a lot coming from you and the @Magic Patterns team. Grateful to have had you with us since the early days. Bullish right back at you. ❤️🔥