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 Ortto if you want SMS, push, in-app messages, popups and live chat on one customer data platform, and have someone to design each email.
THE BROWSERCOMPANY
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In Ortto, AI suggests subject lines; your team builds each email.
 Brew | Ortto | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Ortto: Partly. Partly: AI suggests subject lines and filters; your team builds emails |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Ortto: No. AI suggests 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 | Ortto: No. MCP creates HTML emails; it lists no send tools |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Ortto: Partly. Partly: Brand book restyles templates: colors, fonts, headers |
| Unlimited contacts | Brew: Yes. On every plan; you pay for sends | Ortto: No. Priced by contact tier |
| Unlimited team seats | Brew: Yes. No seat limits on any plan | Ortto: Partly. Partly: Up to 30 users on Professional |
| Brew | Ortto | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Ortto: Yes. Drag-and-drop editor and email templates |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Ortto: Yes. Custom HTML emails |
| A/B testing | Brew: No. Not built in | Ortto: Yes. Subject line, content, from name and send time |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Ortto: Yes. Journeys start on real-time customer data |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | Ortto: No. Built in the journey builder; AI sorts contacts |
| Channels | ||
| Email from your own domain | Brew: Yes. Marketing and transactional on every plan | Ortto: Partly. Partly: Transactional on Business and Enterprise only |
| SMS, push and in-app | Brew: No. Email only | Ortto: Yes. SMS, push and in-app messages |
| Popups, forms and surveys | Brew: No. Email only | Ortto: Yes. Popups, announcement bars, surveys and forms |
| Live chat and support inbox | Brew: No. Not built in | Ortto: Yes. Talk, with AI-suggested replies |
| Agents and developers | ||
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Ortto: Partly. Partly: Reads data and creates HTML emails, in Claude and ChatGPT |
| API | Brew: Yes. REST API, typed SDK and CLI | Ortto: Yes. API and webhooks |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Ortto: Contact tiers; email volume follows the tier |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Ortto: A 14-day free trial |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Ortto: Prices not listed on ortto.com |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Ortto: Business and Enterprise add transactional email |
| Top plan | Brew: Enterprise: custom volume and a dedicated account manager | Ortto: Enterprise, with a dedicated success manager |
| Security and compliance | ||
| SOC 2 and ISO 27001 | Brew: No. Not yet; security review and DPA on request | Ortto: Yes. Compliant; audit reports on request |
| HIPAA | Brew: No. Not supported | Ortto: Yes. HIPAA compliant, per its site |
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 Ortto sending until Brew passes your tests. We’ll do the move with you on a call if you like.
In Ortto, go to CDP > People and choose More > Export, or select people and choose Export selected. Pick visible or all data, and Ortto emails the CSV to the address on your account. 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 an Ortto email 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 journey. 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 SMS, push, popups and live chat stay in another tool.
Yes. Design in Brew, export the finished email as HTML and bring it into Ortto as a custom HTML email, and keep SMS, push, popups and live chat in Ortto. Many teams design in Brew first and move their email sending over later.
In Brew, your agent designs the finished email from brand files it reads every time, builds audiences, runs automations and sends. Ortto’s AI predicts open rates and suggests subject lines, builds audience filters from plain language and sorts contacts in journeys. Ortto MCP lets Claude, ChatGPT and other clients read campaigns, contacts and reports and create HTML email assets; its tool list has nothing to send a campaign or build a journey.
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.
Only as on-brand as the template your team styles. Ortto’s brand book applies your colors, fonts, headers and footers to a template, its AI suggests subject lines rather than designing the email, and an assistant using Ortto MCP writes the HTML itself. 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. Ortto prices on contact tiers, with email volume set by the tier and extra emails at $1 per 1,000, and lists no prices on its site. 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 SMS, push, popups or live chat keep Ortto or another tool for those and design their 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 journeys you run: contacts import from Ortto’s CSV export, most teams have Brew redesign their emails rather than import them, and each journey is rebuilt by describing it. Keep Ortto 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 Ortto? 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