How to Import Figma, HTML, and Inbox Emails in Brew
With Thomas, CTO · 3:35
Bring the emails you already have into Brew from Figma, from HTML or by forwarding them from your inbox.
Watch on YouTube (opens in a new tab)
Choose Brew if you want a fully agentic setup, where your AI agent drives lifecycle marketing to engage and retain customers. Brew designs every email from your brand and runs your automations agentically.
Choose Klaviyo if you run an online store, want SMS, WhatsApp, push, recommendations and reviews next to your email, and have someone to finish each design.
THE BROWSERCOMPANY
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In Klaviyo, AI fills templates; you pay per active profile.
 Brew | Klaviyo | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Klaviyo: Partly. Partly: Composer drafts campaigns and flows; you review and launch |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Klaviyo: Partly. Partly: Fills sections into a template; you finish the design |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Klaviyo: Partly. Partly: Brand library of logos, colors, fonts and voice |
| Unlimited contacts | Brew: Yes. On every plan; you pay for sends | Klaviyo: No. Priced by active profiles you can email |
| AI agent in the plan price | Brew: Yes. AI credits included on every plan | Klaviyo: Partly. Partly: Small free allowance; Composer is $20/month on top |
| Brew | Klaviyo | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Klaviyo: Yes. Drag-and-drop editor and templates |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Klaviyo: Yes. HTML templates, or a screenshot for Composer |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Klaviyo: Yes. Store activity from over 350 integrations |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | Klaviyo: Yes. Composer drafts flows and their messages |
| Product recommendations | Brew: No. Not built in | Klaviyo: Yes. Personalized product recommendations |
| Channels | ||
| Email from your own domain | Brew: Yes. Marketing and transactional | Klaviyo: Yes. Campaigns and flows |
| SMS, WhatsApp and RCS | Brew: No. Email only | Klaviyo: Yes. Billed per message |
| Mobile push | Brew: No. Email only | Klaviyo: Yes. Push to your own iOS and Android app |
| Signup forms | Brew: No. No forms builder | Klaviyo: Yes. Web forms |
| Agents and developers | ||
| Your agent takes it live | Brew: Yes. Sends, schedules and runs automations; OAuth and org-scoped MCP require confirmation, brand API keys do not | Klaviyo: Yes. MCP tools create and send campaigns and create flows |
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Klaviyo: Yes. Over 260 tools, in Claude, ChatGPT, Cursor and VS Code |
| API | Brew: Yes. REST API, typed SDK and CLI | Klaviyo: Yes. Klaviyo APIs |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Klaviyo: Active profiles: contacts who can receive marketing |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Klaviyo: Free: 250 active profiles, 500 sends a month |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Klaviyo: $20/month for 500 profiles and 5,000 sends |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Klaviyo: $100/month at 5,000 profiles: 50,000 sends |
| Enterprise | Brew: Custom volume and a dedicated account manager | Klaviyo: Through sales; price not listed |
| Security and compliance | ||
| SOC 2 and ISO 27001 | Brew: No. Not yet; security review and DPA on request | Klaviyo: Yes. Certified |
Connect Claude, ChatGPT, Cursor or Grok over MCP and your agent gets every Brew tool. It designs emails from your brand, builds audiences, runs automations and schedules sends. OAuth and organization-scoped MCP connections ask you to confirm live sends and launches. Brand-scoped API keys can execute permitted calls without the MCP confirmation step.
Paste your website and Brew writes your brand into two files your agent reads for every email. Describe the email and it appears on the canvas, ready to edit by hand or in chat.
They had me at Lovable for email. 10/10 experience.
MiloRiff.aiHaving an AI assistant built into the platform has made creating emails so much faster, easier, and, honestly, a really enjoyable experience.
Alice MullinsMarketing Manager, RedSeedA great rethinking of everything about email. Love it so far.
Shan ZhongGrowth, NeticVery impressed with what y’all have built and can’t wait to use Brew.
Addie LevinskyOps & Strategy, The Browser CompanyI didn’t need to cold start it with context. I gave it a link and it gathered everything it needed to get me started. I liked its taste in design.
Nischal NaikCo-founder, ConstructKeep Klaviyo sending until Brew passes your tests. We’ll do the move with you on a call if you like.
In Klaviyo, build a segment of everyone who can or cannot receive email marketing and export it to CSV. Include every profile regardless of subscription status. Download the separate CSV for suppressed profiles too. Before importing, prepare a Subscribed column: true for opted-in contacts, false for unsubscribed, cleaned or suppressed contacts. Invert any Unsubscribed true/false flag first. Map the column to Subscribed and review the opt-out preview; new contacts default to subscribed if this value is missing.
Most teams have Brew redesign their emails from their brand, which is faster and looks better. You can also paste the HTML of a Klaviyo HTML template or forward a sent email to hello@email.brew.new; imports are free.
Connect Shopify, Stripe, Clerk or Supabase, or send your own events over the API, then describe each flow. Brew builds the emails, waits and branches, usually simpler than the original.
Connect and verify your sending domain, then review its health and inbox placement. For a new domain, select Gradual send to ramp the campaign in configurable batches before a large send. Gradual send is off by default; connecting a domain does not automatically warm it up.
With Thomas, CTO · 3:35
Bring the emails you already have into Brew from Figma, from HTML or by forwarding them from your inbox.
Watch on YouTube (opens in a new tab)We're here to help! Feel free to schedule a call.
Can't find what you're looking for? Contact us at +1-(332)-203-2145 or support@brew.new.
Yes, if email is your main channel and you want an agent to run it. Brew designs finished, on-brand emails from your brand, sends them and runs your automations from your AI agent, with unlimited contacts on every plan. Brew is email only, so SMS, push and reviews stay in another tool.
Yes. Connect Klaviyo in Brew with one click and push any email into Klaviyo as a template, ready for your campaigns and flows. You keep your profiles, SMS and reporting in Klaviyo and design the emails in Brew.
In Brew, your agent designs the finished email from brand files it reads every time, builds audiences, runs automations and sends, and AI credits come with every plan. Klaviyo’s Composer drafts campaigns, flows and segments and never sends or publishes on its own: you review and launch the work in Klaviyo. Its Email AI drafts sections from a reference template for you to finalize, and Composer costs $20/month beyond a small free allowance.
OAuth and organization-scoped MCP connections ask you to confirm live sends and launches. Brand-scoped API keys can execute permitted calls without the MCP confirmation step.
Not as finished designs. Klaviyo’s Email AI drafts sections from a reference template for you to finalize, and Composer drafts campaigns that you review and launch, so the design starts from your template, not from your brand. Teams that move to Brew tell us these drafts rarely look like their brand, so someone still redesigns them. Brew designs the whole email, layout, copy and images, from brand files your agent reads every time, so it goes out on-brand.
It depends on your list and how often you email it. Klaviyo bills email on active profiles, the contacts who can receive marketing, and each tier caps sends: $20/month covers 500 profiles and 5,000 sends, and $100/month covers 5,000 profiles and 50,000 sends. Brew bills on sends and AI credits with unlimited contacts. Teams with a large list they email a few times a month usually pay less on Brew. Start with the free trial and compare at your own numbers.
No. Brew is email only: marketing and transactional email from your own domain. Teams that need SMS or push keep Klaviyo or another tool for those, and can design their emails in Brew and push them into Klaviyo.
Not yet. We complete security reviews and sign a DPA on request, and our privacy policy, DPA, GDPR page and subprocessor list are public at docs.brew.new/legal.
Your first on-brand email is ready the day you start the trial. The rest depends on how many flows you run: contacts and unsubscribes import from Klaviyo’s CSV export, most teams have Brew redesign their emails rather than import them, and each flow is rebuilt by describing it. Keep Klaviyo sending until Brew passes your tests.
Before importing, prepare a Subscribed column: true for opted-in contacts, false for unsubscribed, cleaned or suppressed contacts. Invert any Unsubscribed true/false flag first. Map the column to Subscribed and review the opt-out preview; new contacts default to subscribed if this value is missing.
Yes. We get on a call to import your contacts and unsubscribe list, bring over or redesign your emails, rebuild your flows and connect your sending domain.
Brew publishes this comparison. Brew Team reviewed the linked first-party documentation. This is a documentation review, not a claim of hands-on testing of every product. Pricing and plan limits can change.
Work at Klaviyo? If anything on this page is wrong or out of date, email support@brew.new and we will correct it. We want to compete on the product, not on a mistaken comparison.
Updated October 2026