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 Kit if you are a creator selling digital products or paid newsletters, want landing pages and forms in the same account, and design each email yourself.
THE BROWSERCOMPANY
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In Kit, AI drafts copy; your team still designs and sends each email.
 Brew | Kit | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Kit: Partly. Partly: AI drafts and organizes; your team runs the rest in Kit |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Kit: No. AI writes subject lines; you design each email |
| Your agent takes it live | Brew: Yes. Sends, schedules and runs automations; OAuth and org-scoped MCP require confirmation, brand API keys do not | Kit: Partly. Partly: Drafts broadcasts; you click Confirm in Kit to send |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Kit: Partly. Partly: Saved templates and branded sections, reused by hand |
| Unlimited contacts | Brew: Yes. On every plan; you pay for sends | Kit: No. Priced by confirmed subscribers |
| Unlimited team seats | Brew: Yes. No seat limits on any plan | Kit: Partly. Partly: 1 user on Free, 2 on Creator, unlimited on Pro |
| Brew | Kit | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Kit: Yes. Email designer with 40+ templates |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Kit: Yes. Custom templates in HTML and CSS |
| A/B testing | Brew: No. Not built in | Kit: Yes. Subject lines on Creator; content too on Pro |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Kit: Yes. Signups, link clicks, purchases and inactivity |
| Automations on every plan | Brew: Yes. No step or flow limits on any plan | Kit: Partly. Partly: Unlimited on Creator and Pro; none on Free |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | Kit: No. Built in the visual builder or from templates |
| Channels and commerce | ||
| SMS | Brew: No. Email only | Kit: Yes. SMS marketing on Creator and up |
| Landing pages and forms | Brew: No. Email only | Kit: Yes. Landing pages and forms |
| Sell products and paid newsletters | Brew: No. Not built in | Kit: Yes. Digital products, paid newsletters and memberships |
| Agents and developers | ||
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Kit: Partly. Partly: Subscribers, tags and drafts on paid plans; no automations |
| API | Brew: Yes. REST API, typed SDK and CLI | Kit: Yes. API and webhooks |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Kit: Confirmed subscribers; unsubscribes don’t count |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Kit: Free plan up to 10,000 subscribers, no automations |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Kit: Creator, $39/month for 1,000 subscribers; $33 billed yearly |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Kit: Pro, $79/month for 1,000 subscribers; $66 billed yearly |
| Top plan | Brew: Enterprise: custom volume and a dedicated account manager | Kit: Pro; no enterprise plan listed |
| Security and compliance | ||
| SOC 2 and ISO 27001 | Brew: No. Not yet; security review and DPA on request | Kit: No. Not listed for Kit; its hosting providers hold them |
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 Kit sending until Brew passes your tests. We’ll do the move with you on a call if you like.
In Kit, open Subscribers, select all and choose Export. A download link arrives by email and expires after five days. The CSV includes each subscriber’s status, tags and custom fields. 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 custom Kit template or forward a sent email to hello@email.brew.new; imports are free.
Connect Stripe, Shopify, 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 and seats on every plan. Brew is email only, so landing pages, forms and product sales stay in another tool.
Yes. You can design in Brew and keep Kit for landing pages, forms and product sales. Export the finished email as HTML and save it as a custom template in Kit, which accepts HTML and CSS.
In Brew, your agent designs the finished email from your brand, builds audiences, runs automations and sends. Kit’s AI writes subject lines in the editor, and Kit MCP lets Claude, ChatGPT and other clients manage subscribers and draft broadcasts and sequence emails on the Creator and Pro plans. A broadcast only sends after you click Confirm inside Kit, and the MCP has no tools for automations.
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.
Kit’s AI does not design the email. It writes subject lines in the editor, Kit MCP drafts broadcast copy, and you design each email from Kit’s templates. 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 much you send. Kit bills on confirmed subscribers, and unsubscribed ones do not count; its free plan covers up to 10,000 subscribers without automations. Brew bills on sends and AI credits with unlimited contacts. Teams with a large list they email in part 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 landing pages, SMS or a storefront keep a separate tool for those, or keep Kit for them and design the emails in Brew.
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 their status import from Kit’s CSV export, most teams have Brew redesign their emails rather than import them, and each flow is rebuilt by describing it. Keep Kit 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 Kit? 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