[BidClub_]
Latent Space · · 86 min

Designing for Agents — Zeno Rocha, Resend

Zeno Rocha

AI & SoftwareCompany BuildingTechnical
YouTube ↗
TL;DR
  • Resend’s opening was developer neglect in a large, established email market. Zeno Rocha reports 4.3 million users and 120,000 paid customers, including Warner Bros. and HBO. Its SDK now has more than twice SendGrid’s npm downloads, although SendGrid still sends substantially more email: adoption momentum and infrastructure scale remain different measures.
  • Agent integrations are becoming both distribution channels and purchasing criteria. Resend’s MCP usage roughly doubled monthly and reached about 1.2 million calls by August’s end; CLI usage is growing more slowly. Rocha wants the product to be “formless,” and says he dropped Plausible for PostHog because he wanted an official, vendor-maintained MCP.
  • Deliverability depends on reputation management and abuse control, not simply sending capacity. A 100,000-recipient campaign needs queues, batches, provider-specific throttling, and careful audience ordering. Resend removes upfront approval friction, then intervenes quickly when sending signals deteriorate: “Most of the time, it’s just misuse. It’s not abuse.”
  • Resend is extending its developer experience advantage into infrastructure ownership. Having started on Amazon SES, it is building deeper sending infrastructure to control IP pools, throughput, performance, and observability. Rocha describes months of work and a forthcoming announcement; the sending path has already moved from JavaScript to Go.
  • Machine-readable product information can improve agent accuracy, while its distribution benefit remains harder to establish. The host recounts that models badly mispriced a 1.2-million-email scenario on the host’s own pricing page until the host supplied readable pricing information outside a JavaScript widget. The host also reports seeing recency bias in Opus 4.5, while the speakers question whether individual AEO tactics matter.
  • Enterprise expansion and marketing email expose different product and pricing requirements. Resend has just one account executive, and Rocha argues enterprise needs exceed SSO, SCIM, and audit logs. Meanwhile, fast-growing customers such as Mistral challenge contact-based marketing pricing; delivering Resend’s own campaign to 4.3 million users takes more than a day.
  • Rocha treats design and family priorities as explicit constraints on growth. A YC partner told him design obsession was slowing progress; he accepted the criticism but retained the differentiation. His hypothetical preference is a $10 million ARR company with a close daughter over a $100 million company without that relationship—not a disclosure of current revenue.
Digest · the substance, structured for research

1. Developer neglect created an opening among established incumbents

  • Rocha had used tools including Mailgun, Mailchimp, and SendGrid, and felt the market did not sufficiently care about developers. The host, who discloses being a Resend angel, framed the opportunity by noting Mailchimp and Postmark had exited and SendGrid was under Twilio. The host found Rocha’s pitch unusually straightforward. Coming from frontend development without email infrastructure experience, Rocha wanted “the Stripe of email.”

  • Resend now powers 4.3 million users and has crossed 120,000 paid customers, Rocha says. Warner Bros. and HBO sit alongside indie developers. The Warner Bros. discovery was bottom-up: browsing customer domains one Saturday, he investigated wbd.com and realized Warner Bros. Discovery was already using the service.

  • The host challenges why incumbent scale cannot win. Rocha thinks Twilio neglected its developer roots: “they’re sleeping on it.” Resend passed SendGrid’s SDK npm downloads earlier in the year and is now more than double, but he accepts the metric’s limits: SendGrid still sends far more email through its large enterprise customers.

2. Deliverability rewards controlled behavior rather than brute force

  • Sending 100,000 emails at Gmail simultaneously invites throttling. Rocha describes ordering the queue with the most engaged recipients first, then adjusting batches and spacing as mailbox providers observe engagement. Gmail, Outlook, and Yahoo behave differently; he estimates Gmail represents “at least” 60% of Resend’s destinations.

  • Providers want a consistently rising sending pattern, Rocha says, rather than a large blast followed by silence and another spike. Those bursts resemble abuse. New customers therefore face protective throttles, with sending speed changing as their history develops: “you need to do exactly what an abuser wouldn’t do.”

  • One example is what Rocha describes as a Japanese gang buying “maybe 20,000 domains,” across different TLDs and registrars. Resend checks domain age, website responses, and lookalike names. A domain purchased two days earlier starts with a reputation disadvantage; using a separate, similar-looking outreach domain can itself resemble phishing.

  • Reputation has become more domain-based than the industry’s earlier emphasis on IPs. Rocha recommends separating transactional and marketing streams with subdomains; Resend sends investor updates through confidential.resend.com. The host’s suggestion that buying a matching .com solves deliverability meets a warning: a lookalike domain can create more suspicion.

3. Frictionless onboarding transfers the abuse burden to the platform

  • Removing competitors’ roughly two-day human approval process means “we trust you by default,” followed by rapid blocks when bounce rates, complaint rates, or mailbox-provider feedback show something is off. “Most of the time, it’s just misuse. It’s not abuse.” Mailgun’s founder had warned Rocha that 90% of R&D went into fighting abusers; he wants automation to prevent that becoming Resend’s core business.

  • Resend automatically adds a plain-text version extracted from HTML, which Rocha says improved deliverability “a ton.” A host pushes back that plain text cannot carry an open-tracking pixel. Rocha’s response: open rates are already less reliable because Apple’s privacy changes and automated email inspection can register activity before a human reads anything.

  • Click tracking has its own reputation problem. Rewriting links through a shared tracking domain creates a “noisy neighbor” risk: one phishing customer can get that domain blacklisted for days or weeks. Rocha acknowledges Resend initially did this too. Matching link and image domains to the sender helps avoid patterns associated with abuse.

4. Support scales when recurring problems become product features

  • Rocha describes support as being around “major version four.” Hiring someone merely to occupy the chair failed; domain expertise alone also failed to prevent repeat tickets. One productive rule was that staff could answer only with a link, forcing documentation first. An answer might initially take an hour and a half, but the resulting article became reusable.

  • Resend went from about one million users in December to roughly four million, making proportional staffing unattractive. Lovable, Bolt, and v0 brought users who often could not troubleshoot independently. DNS dominates questions: people do not know where CNAME, A, or TXT records belong. Rocha wants to preserve the free tier because free developer products enabled his own career.

  • Domain Connect offers an “OAuth for domains,” replacing manual record entry with authorization. Rocha says Resend persuaded Vercel to participate alongside providers including Cloudflare. Adoption remains laborious: reaching IONOS took months, GoDaddy charges substantial fees, and protocol maintenance is thin. The host describes the appeal plainly: “You don’t type in anything.”

5. Open source and product craft widen the developer funnel

  • Rocha says user research during Resend’s development surfaced pain around converting designers’ files into email templates. HTML tables, inline CSS, and Outlook-specific comments made the work unpleasant. React Email uses JSX as templating; Rocha confirms it does not add interactive React applications: “you cannot ship JavaScript on an email.” The transcript gives differing chronology: the host says React Email came the year before Resend, while Rocha says he started Resend and, as he built it, heard the template complaints.

  • “React Email is our Next.js,” Rocha says of the open-source acquisition channel. He personally wrote integration guides for SendGrid, Mailchimp, and Mailgun, making the project useful beyond Resend. The strategy was to fix template creation and then offer the sending platform: “giving, giving, giving, and then asking.”

  • Craft extends to SDKs. Rocha says the team disliked output from generators including Stainless and Fern, so its SDKs were built by people. Java, Rust, and .NET users deserve good experiences in the language they use, even if only hundreds use a language out of millions overall. His reference point is growing up in Brazil with a poor Windows computer and unreliable internet.

  • Templates also serve different ownership preferences: some teams want source control; others want marketing to edit visually while engineers call a template ID with variables. Resend’s editor supports collaboration and conflict resolution. Internally, roughly 20 people use it for all-hands meetings, then send the jointly assembled email at the end.

6. Moving below SES gives Resend more control over the sending path

  • The host’s low-cost benchmark is freeCodeCamp sending to five million newsletter subscribers through SES for about $5,000 monthly. Rocha calls SES a good platform and says Resend started there too, concentrating first on underserved developer experience: language SDKs and practical guides such as sending email from Lambda.

  • The hidden cost is everything surrounding delivery. Feedback events require SNS; logs require CloudWatch; volume requires queues such as SQS; webhooks need additional work. “Your footprint will be much bigger than you would imagine very quickly.” SES’s domain structure and configuration-set model also imposed limitations as Resend grew.

  • Resend is now building deeper infrastructure “and going down to the metal,” after months of work. That means buying IP blocks, managing pools, and controlling throughput into individual providers. Relationships matter too: Resend hired deliverability veterans from Postmark and Mailchimp, borrowing networks it did not possess when Rocha started.

  • Better observability is a central goal: a developer wants to understand the gap between an email leaving the service and a recipient actually finding it. Performance is another. Formerly a TypeScript and Node.js shop, Resend now uses Go in the sending path and is challenging assumptions about how long P99 operations should take.

7. Official MCP access is becoming part of the buying decision

  • Rocha’s product principle is “I want my product to be formless.” API-first architecture lets customers choose their own workflow, including Claude Desktop and Codex. There is an irony for a design-focused founder: customers increasingly tell him they never open the dashboard he spent so much time polishing.

  • The host describes MCP usage accelerating from approximately 50% monthly growth to roughly doubling each month. Rocha says it reached about 1.2 million calls by August’s end. The first implementation came from Yoko at investor a16z, who built a local, open-source server that Resend later adopted. Rocha says CLI usage is also growing, but less quickly.

  • A proper remote MCP required revisiting the permissions model, building OAuth, and examining RBAC and resource access. Only after that came distribution through official stores and marketplaces. The growth was therefore not simply a connector appearing: shipping the integration exposed underlying product and authorization work.

  • Rocha’s purchasing example is dropping Plausible for PostHog because he wanted an official MCP. A Plausible integration maintained by Sentry did not satisfy him, despite trusting Sentry. “I need the owner of the software to own this piece of the integration too.” Local-only integrations also frustrate him because they do not work across desktop and phone.

8. Complete agent access exposes the long tail of product design

  • Resend’s MCP grew from around 20 tools or fewer to “eighty-something.” The host contrasts Cloudflare’s two-tool approach and asks what would change Rocha’s mind. Rocha relies on customer feedback and personal use, including assembling investor updates. His immediate concern is oversized responses exhausting context; tool-count confusion worries him less than it once did.

  • Getting from 90% to 100% dashboard coverage is difficult: billing, usage, invitations, provisioning, and deletion all need decisions. The host argues frameworks that bind data directly to pages discourage public APIs. Rocha recalls expensive Next.js hosting, a move to a traditional Node server, and duplicated public/private API work; a monorepo now makes reuse easier.

  • Resend’s careers page accepts applications through CLI and API, with skills allowing Claude to apply. The host challenges whether this invites “slop” and whether a founder should outsource recruiting software instead. Rocha sees the setup effort as a useful signal and filters CLI applicants differently: authentication and installation demonstrate someone went through the experience.

  • Another forthcoming product moves beyond inbound email toward programmatically creating dozens or perhaps 100 inboxes for agents. Receiving messages is only the base abstraction; the next layer needs APIs for reading, marking unread, starring, and labeling. Rocha describes this as API-driven and offers the host access behind a feature flag.

9. Readable pages can correct agents that misunderstand the product

  • Resend could not initially compete with incumbents’ decade-plus SEO investment. Its foundation was narrow, practical documentation: not just Python, but Python with Django. As question-based interfaces grew, Rocha added FAQs across marketing pages, making questions such as “Is Resend SOC 2 compliant?” directly answerable.

  • Resend has llms.txt on its marketing pages and Markdown versions of its documentation. Rocha says he plans to make Markdown versions of every marketing page too. Pages can be requested with a .md suffix; content negotiation is another option. In a separate example, the host says a Markdown version of the host’s pricing page receives access that ordinary browser analytics miss, visible instead through server-side Datadog data.

  • The host recounts a pricing test on the host’s own site: a model asked to compare sending 1.2 million emails badly miscalculated Resend’s price and called it obscure. The host says agents were not operating the JavaScript widget. After the host added a Markdown version, a repeat test days later returned correct numbers. Rocha notes the tradeoff: parallel Markdown and page content must both be updated.

  • Migration pages offered code converters instead of conventional comparisons; Rocha now thinks rivals’ explicit comparison pages earn more recommendations. He also spells out adoption-chart data in text. The host pushes back that computer-use agents increasingly inspect interfaces and images; Rocha distinguishes that from information-fetching workflows that do not execute widgets.

10. AEO matters commercially before its causal mechanisms are settled

  • The host reports seeing a recency bias “at least with Opus 4.5,” which seemed to help newer tools such as Resend despite weaker traditional SEO. Rocha says organic discussion in many places influences recommendations. His advice is to get as many people as possible talking about the product, not to follow a claimed formula.

  • The host says they tried multiple AEO services and have four subscriptions, but misses recommendations for concrete actions; the host describes those tools as mostly reporting what is happening while vendors are still figuring out what to do. The host also describes an experiment loop connecting agents to analytics, the codebase, Ahrefs, and SEO data, with human signoff before experiments.

  • Reducing signup friction is another unresolved frontier. The host raises account-free basic usage, followed by provisioning and claiming resources. Rocha says email has a lot of abuse, and the discussion does not settle whether that approach or a provisioning API is worthwhile.

11. Enterprise expansion tests product, pricing, and positioning

  • Resend is only beginning its sales motion, with one account executive. Rocha has deliberately introduced it gradually to protect the culture. He knows enterprise selling requires enablement and organizational machinery, but says the first AE is helping and the motion is going well.

  • Enterprise is “actually a different product,” not simply another sales channel. Its buyers care about different things from $20 users; adding WorkOS, SSO, SCIM, and audit logs to a pricing page is insufficient. The host’s example of a few deals doubling ARR is a general illustration of sales leverage, not a reported Resend result.

  • Marketing pricing conventionally charges per contact, but fast-growing AI customers such as Mistral make Rocha question that model. Sending also requires adaptive batches rather than a simple transactional queue. A campaign to Resend’s 4.3 million users takes more than a day; the host calls that unacceptable, and their exchange turns to paying more for different queue treatment.

  • The host distinguishes category dominance from creation: “AI-native SendGrid” does not yet establish a new category. The host’s benchmark is HubSpot’s inbound marketing—a phrase that makes the alternative feel undesirable without a manifesto. Rocha acknowledges the difficulty; the discussion leaves Resend’s next category-defining phrase unresolved.

12. Design and family priorities set Rocha’s definition of success

  • Rocha entered YC’s Winter 2023 batch with a one-year-old daughter and wanted to build the best company among roughly 250. Comparing himself with unmarried founders from elite schools initially felt disadvantageous. He later concluded “there’s no winner in YC”: fundraising rankings fade, cofounders separate, companies pivot, and the game continues.

  • After Paul Graham urged founders to heed partner advice, Rocha asked what he should stop doing. A partner said he cared too much about design and would otherwise be further ahead. “That hurt me so badly,” partly because he thought it was true. He still preferred 1,000 users of something he loved to 10,000 using something he did not want to use.

  • Expecting a second child, Rocha is spending more time in Brazil. His ten-year thought experiment favors a $10 million ARR company and a daughter who wants to play with him over a $100 million company and a distant relationship. “Maybe it’s right, maybe it’s wrong. I have no idea.” These are hypothetical outcomes, not current financial figures.

  • The host pushes on ambition and presence: family time can become checking a phone and thinking about work. Rocha offers no clean solution. He also feels like a failing father, husband, and CEO while switching roles at home. “Every day I try to be a little bit more present,” while insisting his ambition remains strong.

Full transcript
Zeno Rocha

It’s like, “Oh my gosh, how are we ever gonna beat SendGrid? It’s impossible.” Earlier this year, we passed SendGrid in downloads, and I was like, “That’s insane.” Now we’re more than double. Resend is powering 4.3 million users as of this morning. We have all sorts of customers, like Warner Bros. and HBO. There was a Japanese gang that recently came. They brought maybe 20,000 domains at Resend. Those are 20,000 different TLDs registered with different domain registrars, and we’re a $10 million ARR company.

I’d rather live in that reality than live in a reality where we’re a $100 million company and my daughter doesn’t wanna play with me, isn’t interested in me, and we’re not that close.

We’re building the infrastructure and going down to the metal now. It’s a big project. We’ve been working on it for months, and we’re gonna announce something soon about that.

Speaker 1

Okay, we’re in the studio with Zeno Rocha from Resend. You and I go back to your VS Code theme days, when you were just an indie hacker.

Zeno Rocha

Yeah.

Speaker 1

And I was like, “Man, I don’t know what this guy does, but everything he does has taste.” And then now you’ve built an email infrastructure platform. Anyway, welcome. You undersell being an indie hacker.

Zeno Rocha

Top 20 most active GitHub users under 20 in 2022.

Speaker 1

Nice. Right. Very, very active open-source stuff.

Zeno Rocha

Yeah, yeah.

Speaker 1

What’s your typical introduction these days?

Zeno Rocha

I think I just focus on my recent career. For the longest time, even today, when I say, “Oh, I created Dracula,” people know Dracula more than Resend.

Speaker 1

Still.

Zeno Rocha

Yeah, but it’s been nice. It’s changing.

Speaker 1

What was the impetus for picking email?

Zeno Rocha

People always bring up React Email and all those things.

Speaker 1

Yeah.

Zeno Rocha

I just don’t know if I would have made it a company.

Speaker 1

Yeah.

Zeno Rocha

If I knew how hard email was, I probably wouldn’t have started the company either.

Speaker 1

Were you primarily a JavaScript front-end—

Zeno Rocha

Totally.

Speaker 1

—CSS dev? No infrastructure, right? No email background. The HTML5 guy?

1. Building the Stripe of Email

Zeno Rocha

I was a front-end guy. What drew me to it was looking at all the tools around it. I’d used all of them before: Mailgun, Mailchimp, SendGrid. I always felt like there should be something where someone cares about this space. There are all these players, and it’s a massive market with a lot of competitors, but no one cares about the developer persona. Maybe they care about the marketer or the product manager, but not the developer.

I started building around the premise of, “If this was the Stripe of email, how would that look?” I had no idea or knowledge of email. I was a user of email, but I’d never built an email pipeline or any of that infrastructure before.

Speaker 1

Yeah, I mean, typically, if you ask me, Postmark was still a thing.

Zeno Rocha

Yeah.

Speaker 1

And then obviously SendGrid and all these folks. They’re still around, but maybe they’re not as innovative as a new YC startup trying to make it.

Zeno Rocha

Yeah.

Speaker 1

Just upfront, I like to let people brag a bit. For people who’ve never heard of Resend, what are the ways you talk about it? The most impressive numbers, the logos, anything?

Zeno Rocha

Resend is powering 4.3 million users as of this morning. We have all sorts of customers, like Warner Bros. and HBO—customers that are really big and have all sorts of demands—but also a lot of indie hackers and folks who are just building a website or their own application. We just crossed 120,000 paid customers. And, yeah, the endless logo wall.

Speaker 1

Oh my God. Yeah, the big logo wall. Do you think this is effective? You wanted the flex. There you go.

Zeno Rocha

You know what? In the beginning, I felt like I just needed some sort of social proof. In the end, I was like, “You know what? This is actually pretty cool.” I honestly found companies like Warner Bros. just on a random Saturday. This was before AI, so I’d go to my database and think, “Oh, let me see who I can put on the website.” I did the most naive thing you can do: I looked at the domains, filtered by .coms, and filtered by the small ones. There was this domain, WBD—Warner Bros. Discovery. I didn’t know what WBD.com was. I was like, “Oh no, Warner Bros. is using us.” I just love featuring customers.

Speaker 1

Pretty good. Specifically for listeners, one of the reasons I reached out for this interview: one, I should declare upfront, I’m an angel. When you sent me the memo, it was super simple. You were like, “Look, Mailchimp has exited. Postmark has exited. SendGrid is under Twilio. Who is doing this?” And I was like, “Okay, yeah, seems right.” Honestly, in terms of the pitches I get, I’ve invested in about 30-plus companies, and that was one of the most straightforward things ever.

And then, secondly, I don’t like to add API keys. I like to have everything on one platform, one API key, copy everything. Cloudflare has built-in email, and I had a project. I set up my Cloudflare email domain DNS and all that junk—DKIM, what have you. I don’t know all the alphabet soup of stuff. I already had this set up, and then I wanted to add another sort of email thing. The Claude model said, “You must add Resend.” I was like, “Who the fuck is telling me this? Resend? I already have Cloudflare email set up, and it’s still recommending it.” It’s on the screen now. This is him praising Resend, like, “I don’t need Resend, but you want me to keep adding Resend.” So who did you bribe at OpenAI and Anthropic to get Resend on there?

Zeno Rocha

I wish there was someone to bribe, because I’d definitely be paying them. But I personally spend a lot of time on that topic. That’s something I feel like every generation has: tools that define that moment. We remember the Heroku days, Netlify, Vercel. To me, it was like, yeah, there’s room for a new generation, and this new generation isn’t going to be distributed in the same places it was before. So from the beginning, I was very focused on, “Okay, we’ve got to be number one when someone asks about that.”

Speaker 1

You’re very number one. Claude Code recommends you 60% of the time or more. I think it’ll be fun to see the playbook. How do you win that?

I do want to get back to what you said about having no idea how to start with email. I think a lot of people don’t understand what goes into making a service like this. You might, because you’ve set it up. Some people would just say, “Okay, I can use Twilio, I can use SendGrid, I can use you guys.” But what goes into making a tool to mass-send emails? What do people not think about?

2. How Email Delivery Works

Zeno Rocha

There are a lot of different things you can do, because landing in the inbox, especially when you’re sending high volume, is different from scaling an app where you throw GPUs at the problem or scale vertically or horizontally. With email, you have to respect the rules of the game. Gmail behaves differently from Outlook, and differently from Yahoo Mail. It’s a fascinating, old-school industry that relies a lot on contacts.

What we found early on was that we knew nothing about this world. Coming from an extremely naive perspective was the best thing that ever happened, honestly, because there was no preconception of what was right or wrong. For example, with every app, the first thing you see is a form you have to fill out: how many emails you’re going to send, what the volume is, what you’re trying to do. Then you go through a human verification process. Two days later, they accept or deny you. Most of the time, they deny you. I was like, “This doesn’t make any sense. Why are we blocking people?” So I decided to remove that friction completely, and the friction would be on us. We would figure it out.

Of course, now, three or four years into this business, I get why they do that. There’s so much fraud, phishing, and abuse across the board. I don’t talk too much publicly about that, but we build all sorts of crazy systems internally for it.

To your question about how you architect that: when you’re sending an email to 100,000 people, if you just throw 100,000 emails at Gmail, Gmail will throttle them because it’s way too much, and they want to see the engagement.

So what you do is, they see, “Okay, are people opening the emails? Are people archiving or deleting them right away, or not interacting?” Depending on those initial interactions, what I do with the rest of the emails is dictated by that beginning.

There are clever things you can do. For example, put the most engaged audience members at the beginning of the queue. You have to put that in a queue. It’s an art and a science: you have to space out each batch. You also have to space things out between the different providers. Now we’re buying different IP blocks. You have to look at the history of the IP blocks, distribute people into different IP pools, and then balance the IP pools over time. It’s a whole crazy infrastructure game.

Speaker 1

How automated can that be, or is there still a lot of human judgment?

Zeno Rocha

It’s a lot of automation, for sure. Over time, we learned how fast we can send for new customers. Of course, if you’re sending more, maybe you can send faster, but there’s a throttle we have to apply to protect you as a sender.

What Gmail and all these players want to see is a graph that’s consistently sending more and more, versus what most people do, which is send once to a big audience and then never send again. Then it’s empty, and then boom, you send it again.

Speaker 1

Once a week? Twice a week?

Zeno Rocha

Yeah. Those are patterns an abuser would have, right? The whole way of thinking about email marketing and email in general is that you need to do exactly what an abuser wouldn’t do. It’s the opposite of that.

What does an abuser do? They buy a domain. We had a Japanese gang come in recently. They bought maybe 20,000 domains, registered across different TLDs and domain registrars, and we look at every single factor. They come in with a domain that was bought two days ago. Very new domains get a bad reputation. Then you look at the website: is it returning 200? Basic things like that. Some people don’t even set that up, or they use a lookalike domain. They might think, “Maybe I’ll use another domain for cold outreach.” That’s terrible because it looks like you’re phishing. You’re using a domain that looks the same.

They do all these little things, and they send a lot of emails all at once and then never send again. You have to reverse-engineer how phishing works and build a platform that does exactly the opposite.

Speaker 1

Do you have a list somewhere, or do you recommend people look at some well-known lists?

Zeno Rocha

What I’ve learned is that email is the type of world that requires a lot of education, but people aren’t interested in learning. The platform should do all those things for them. We added insights inside the product, so people can just apply them. We look at sending patterns, and now with AI it’s pretty cool, too. We have link checkers, spell checkers, and all these checkers before you send.

It’s a mix of teaching your audience and having the product do the teaching. The more you can bake in the best practices, the better. For example, when you send an email, you can send an HTML version and a plain-text version. Very early on, we thought, “The whole world is changing. There are way more agents than before. Let’s automatically generate the plain-text version of each email.” We can extract the Markdown from the HTML and then send that.

We started sending that automatically, and it increased deliverability a ton. It’s so much easier for spam filters to look at the content directly without having to parse it. Those are the kinds of things where we think, “Let’s bake this into the product.” Most people don’t do that, but we think it makes sense.

Speaker 1

But with plain text, there’s no tracking, right? There’s no tracking because you can’t embed the image.

Zeno Rocha

That’s right.

Speaker 1

So you don’t have open rates. How do you know you have deliverability if you don’t have open rates?

Zeno Rocha

This is very interesting because there are two ways of tracking in the industry: open tracking and click tracking. Open tracking includes a one-by-one GIF, a transparent image. If that image is loaded, then you detect that as an open.

The problem is all the changes Apple made recently around transparency and data privacy. They read emails before they land if they’re doing summaries and those kinds of things. So the open rate as a metric isn’t as reliable as it used to be, because all these spam filters are checking emails beforehand.

Then you rely on click tracking. Click tracking can also be difficult because you want the URLs to match the sending domain. You also want the image URLs to match the sending domain. That’s another pattern an abuser will use: they host images somewhere else, point links somewhere else, and send from these domains.

Speaker 1

I feel like I’ve used email services that rewrite links for tracking to their own domain. You’re saying that’s bad?

Zeno Rocha

That’s bad. We did that, too, at first.

Speaker 1

I thought that was normal.

Zeno Rocha

What’s bad is that you can have a noisy-neighbor problem, too. If one of the customers using that click tracking is an abuser and sends a bunch of phishing, that domain might get listed on a blacklist. Then it takes maybe days or weeks to get off the blacklist, and you’re screwed as a business.

Speaker 1

Isn’t that pretty common? You make it very easy to sign up for a free tier and send a bunch of emails. I’d assume you have a lot of spam and phishing. How are you able to avoid that? Is this why?

Zeno Rocha

I think what was different for me—and this is more of a philosophy—is that I saw those other products and the way they behaved, and I felt like it was almost as if you were born into a society where you first go to prison, and then you have to spend 18 years in prison. You have to prove you’re a good citizen, then you get out of prison and can do the things you want to do.

I always felt like, no, I want to live in a society where I’m born free. If I make a mistake, I might be punished just a little bit, or if I do something really bad, I get a bad punishment. That’s how I feel about it, too. You come in, and we trust you by default. Of course, that’s a naive way of thinking, but we’re going to trust you by default instead of making the whole platform worse for everyone because of those bad actors.

What we do differently from others is that, at the very first moment we notice something is off—by looking at bounce rates, complaint rates, and all the feedback we get from mailbox providers—we block you very quickly and then chat with you. Most of the time, it’s just misuse. It’s not abuse. We learned that we need to differentiate.

Speaker 1

Skill issue.

Zeno Rocha

It’s a skill issue. Exactly. It’s a skill issue. I think we learned we have skill issues, too, that we wouldn’t have expected.

Speaker 1

Yeah, we learned. Email is so important, and it’s so dirty and so secretive. I almost just want you to tell us everything we don’t know.

You have a fun page that you call your philosophy. I got lost just reading around it. And you have a pledge that you’ll make email safer.

Zeno Rocha

Mm-hmm.

Speaker 1

If you’re interested in this stuff, you have quite a bit up there. I want to ask about “How we scale support.” You remind me of another investment I had, Jake from Railway. They’re also very permissive and developer-oriented, but you have to scale support, right? The moment someone gets blocked, they come to you and say, “Hey, don’t keep me off your platform.” How do you scale support?

Zeno Rocha

Man, if support were software, we’d probably be on major version four or something. The very first version was me.

Speaker 1

You?

Zeno Rocha

Me. I was so stressed out. I was like, “Dude, I just need someone sitting on the chair. It’s that simple. I cannot be doing this anymore.” And it was just anyone. Anyone, I don’t care.

Then you do that. Of course, it doesn’t go well because you realize very quickly that you need someone who will actually try to prevent the tickets from happening in the first place. So then we went to V2, which was a new person we ended up hiring. They were like, “Okay, we’re answering the tickets. They have domain expertise.” But they still weren’t doing the proactive work, like, “No, let’s make sure this is documented before we talk about it.”

One policy we set was pretty cool: you can only respond to a ticket with a link. You can’t just give the answer right away. You have to stop and write a blog post, write documentation, or write a knowledge-base article. So it takes maybe an hour and a half for you to answer a ticket.

Zeno Rocha

But guess what? Now you’re sending that link all over again. So that was super cool, and it helped us build that knowledge base. But even so, when we crossed maybe 1 million users—we had 1 million users back in December, and now we have 4 million—I can’t throw people at the problem. That’s just not going to solve it, right? I’m just going to keep staffing, and that’s how it is. No. We really have to rethink everything from scratch again.

We want to keep that free tier. I don’t want to get rid of it. I started as an engineer because I was able to use those free products, right? If it weren’t for Heroku’s free tier and all these other products, we wouldn’t be here. So I want to keep Resend that way, but it took us many iterations to get there.

Speaker 1

How much of this is that it’s a domain people don’t know a lot about, with unique questions that need human support, versus Command-K with docs and a model? Customer service bots exist, right?

Zeno Rocha

Yeah. I think it’s much better now. There are a few things where there’s so much friction. DNS, oh my gosh.

Speaker 1

It’s always DNS.

Zeno Rocha

It’s always DNS, right? The majority of the questions we get today are from people not able to set that up. It’s fascinating because we’re serving a new audience—an audience that doesn’t even know how to troubleshoot. I remember last year, when Lovable, Bolt, and v0 came along, I could tell these were different users. When they have a problem, they get stuck. They don’t know how to get past it.

With DNS, they simply don’t know what a CNAME, an A record, or a TXT record is, or where to put those things. They would paste the wrong value or silly things. By the way, right now I use computer use, like Codex or Claude Code, and it completely manages my DNS records. It’s great. It debugs it, runs dig, and tries all the DNS stuff. I don’t have to worry about it.

One thing we did was find this super obscure protocol that very few people in the industry were investing in. It’s called Domain Connect, and it’s super interesting. It started with some domain providers.

Speaker 1

Oh.

Zeno Rocha

Yeah, this is like OAuth for domains, right?

Speaker 1

Exactly that. Is this Cloudflare-oriented?

Zeno Rocha

Some people have it, like Cloudflare. Then we convinced Vercel to be there as well, and we started getting more people. You have the two sides: the DNS providers and the service providers. We’re the service providers, for example, and then the DNS providers implement it.

It’s a crazy industry. GoDaddy charges a lot of money for that. It’s so weird. With IONOS, it took us months to get to the first person. No one really maintains the protocol and things like that, but it’s beautiful to have a protocol where you can do OAuth for domains.

Speaker 1

Yeah, yeah. For listeners who aren’t familiar, if you haven’t tried something like that, it’s literally like using Plaid or OAuth. You only click buttons. You don’t type in anything. There’s nothing to get wrong. You basically just sign in, as long as you trust this thing called Domain Connect, which you’ve confirmed is legitimate. Then it’s trusted. I literally used it for the first time two weeks ago. I was like, “What is this? I’ve never seen this before.”

Zeno Rocha

Yeah. It’s really cool.

Speaker 1

One of the things I’m trying to figure out is how you start this company. You said you tried to get in touch with the IONOS guy. I wouldn’t dare start Resend without knowing someone on the inside at Gmail. Even now, it’s like, “Okay, can we vibe-code our own email thing?” Clearly, no. But that’s even with tools today. You did this years ago. You want people at the domain providers, right? You need the guy.

Zeno Rocha

Yeah, but you need to pick up the phone. There were many times we had to pick up the phone. It’s fascinating. It’s an industry that relies a lot on relationships, and we didn’t have those relationships. So we hired for a few key roles, like deliverability roles—folks who had been at Postmark since the beginning or at Mailchimp 15 years ago—and then we leveraged that network.

What’s interesting now, of course, is that I didn’t know that when I started. I could never predict what was going to happen.

Speaker 1

You didn’t do the research?

Zeno Rocha

No. I could never predict what AI was going to do and all that, right? But I think we’re in a space where I’m glad we chose infrastructure. I’m glad we’re infrastructure as a service and not just software as a service.

Speaker 1

You had a little bit of that, right? You made React Email the year before, so you did dip your toes in open source work, and then came the company.

Zeno Rocha

Yeah. React Email is our Next.js, right? We wanted an open source channel for top of funnel. I remember doing some things very intentionally. If you go to the docs, for example, you’ll find docs about how to set this up with SendGrid, Mailchimp, and Mailgun. I wrote every single one of those docs. I wanted this to be for everyone, and we were trying to redefine how this works.

It was a strategy of giving, giving, giving, and then asking. If people are building an email template using React, now they’ll need a platform to send it. Where do they do that? Here’s Resend. It was a storytelling kind of way of approaching the market. We’re going to fix the first part of the journey, which is building the template. Once you have the template and that problem is fixed, you need a platform to send it. Here’s the platform.

Speaker 1

But did you have the idea for Resend when you started React Email, or was it a side project that then became a company?

Zeno Rocha

We started Resend, and as we were building it, I was doing a lot of user research. People were saying, “The pain is writing the template. I get the Figma file from my designer. It sucks. It’s HTML tables and everything.” They would cut out the images.

Speaker 1

Oh my gosh.

Zeno Rocha

It’s in there because there’s nothing else. And then there’s a special syntax of HTML that only works in email.

Speaker 1

Right? It’s a mess. Or CSS.

Zeno Rocha

It’s all inline CSS.

Speaker 1

That’s right. And then, for Outlook, you have some special comments, and then you’ve got to… It’s such a mess. It’s like a mess. To me, the reason React works is that it is basically a compiler. Somebody writes this once, and then, as long as you fit the API, it’s going to work everywhere. You can import your tokens from Tailwind. Now you have a type definition with TypeScript. No more empty comma in your emails. You can actually have string validation or whatever you want.

I think one of the initial people who pushed back on React Email was like, “Well, you’re not actually using React. There’s no state.” React is supposed to be views as a function of state. So is it mostly JSX as templating, or is there animation or interactivity? Expanding accordions?

Zeno Rocha

No, nothing like that.

Speaker 1

Okay. So you cannot ship JavaScript in an email. What you do is—

Zeno Rocha

We basically use—

Speaker 1

But CSS is Turing complete, if you—

Zeno Rocha

Yeah.

Speaker 1

Okay, cool. I do want to continue on this email path, but I see so many names I used to know. I was wondering if you can indulge us a bit and go through some of these names—what you learned from them, any cool stories, anything.

Zeno Rocha

Man, so much. I remember the very first year of Resend, I was like, “I’ve got to meet the founder of Mailgun,” because I was still a user of Mailgun. I talked to Ev. He built—oh my gosh, what is it? Blogger? Medium? No, it’s a separate product. It’s a security product that he’s building now.

I remember talking to him. I was like, “Man, why did you sell your company so quickly? What was the thing?” He told me, “Oh yeah, 90% of our R&D was just to fight abusers.” It was a terrible business. He said, “You shouldn’t go there.” I didn’t want to live in that world at all, so I was very worried about that. That was a big lesson for me: we’ve got to automate this thing. There’s no way we’re just going to build a massive organization for it. We do have a lot of people interested in safety now, but that’s not going to be our core business. We have to be pushing the industry forward.

That was one. SendGrid has always been my favorite out of those, and it’s always been the behemoth—the biggest, the…

Zeno Rocha

It’s like, “Oh my gosh, how are we ever going to beat SendGrid? It’s just impossible.” Earlier this year, we passed SendGrid in downloads, and I was like, “That’s insane.” Now we’re more than double.

Speaker 1

So, in terms of unique users—or what’s the number?

Zeno Rocha

npm downloads of the SDK.

Speaker 1

Is that the best metric out there?

Zeno Rocha

I think there’s something to that metric in terms of adoption, but if you look at how many emails they send, it’s obviously much more than us because they have big enterprise customers.

Speaker 1

One thing that’s surprising is that the whole point of the Twilio–SendGrid acquisition was that you’re no longer an email service; you’re a communications platform. You integrate across everything. It’s not just about cross-selling. It’s about reaching people across multiple channels, or having the scale. Twilio is, I don’t know, let’s call it a $13 billion or $15 billion company. You should have all the relationships, all the talent, all these things. So how do you compete with that?

Zeno Rocha

I admire Twilio so much. They kind of invented developer relations, or “Ask Your Developer.”

Speaker 1

Yeah, “Ask Your Developer.”

Zeno Rocha

Now, when I drive past that 101 billboard and see “Customer AI” or whatever, I’m pissed. I’m like, “Why?” You neglected the thing that got you there. Jeff isn’t there anymore.

Speaker 1

He bought The Onion.

Zeno Rocha

That’s right. So I feel like they’re sleeping on it. First they did that with SendGrid, and they’re doing that with SMS, too.

Speaker 1

My lesson here is that I’m trying to figure out the economics of scale in this industry. Clearly, they were 100 times larger than you when you started. How come they can’t use their size to just win? Maybe there are no benefits to scale. Maybe you just make a better product and slowly get there. I’ve also always wondered why Twilio acquired SendGrid and not the other way around.

Zeno Rocha

Twilio was bigger. SMS is big.

Speaker 1

But if email and communications are commodities, like SMS, your margins are even—

Zeno Rocha

Worse.

Speaker 1

Yeah, even worse. Have you looked into SMS?

Zeno Rocha

Yeah, for sure.

Speaker 1

Resend SMS?

Zeno Rocha

I think one day.

Speaker 1

What are the channels that matter? Email, SMS, what else?

Zeno Rocha

WhatsApp is big in many different countries.

Speaker 1

Oh, WhatsApp is free, right? You don’t pay anything.

Zeno Rocha

Yeah, but you have to go through Meta, and now business messages are going to be charged. There’s some friction there, for sure.

Speaker 1

Phone calls?

Zeno Rocha

Phone calls are a good one. I’m less interested in that, though.

Speaker 1

I don’t know if it’s a good one. I never take any robocalls.

Zeno Rocha

That’s true. I’m less interested in that, too. What I care about is what lets me connect with my audience. That’s what I ultimately care about. I don’t care about email.

Speaker 1

Direct messages?

Zeno Rocha

Direct messages are one. It’s hard because you can’t message a big crowd. Slack might be one, though.

Speaker 1

Oh, yeah, Slack.

Zeno Rocha

I have so many Slack connections, and I need to share news about a new feature we built.

Speaker 1

Pylon? I don’t know if you guys use Pylon.

Zeno Rocha

Yeah, Pylon. I think they kind of innovated this Slack support thing.

Speaker 1

You can obviously trivially build your own.

Zeno Rocha

Okay. The other one I want to touch on is AWS SES.

Speaker 1

My connection to this is that I learned to code with freeCodeCamp, with Quincy Larson and everything. They have about 5 million newsletter subscribers, sent through Amazon SES for about $5,000 a month.

Zeno Rocha

That’s cheap.

Speaker 1

It’s pretty cheap. I don’t know what it would cost you.

Zeno Rocha

More than that.

Speaker 1

To me, it’s the low-cost player. It’s Amazon; they’re super established. What do you take from them, and what should people know to stay away from?

Zeno Rocha

We started with SES, too. We knew that if we were going to innovate, I wanted to innovate on the developer experience layer because I felt that was the underserved space. So let me have SDKs for every single language. With Serverless, I remember we highlighted SES because no one had guides on how to send an email with Lambda or something. There was this underserved space in developer experience. We started with the highest-level layer, and that served us really well. We were able to scale because we were using SES behind the scenes.

It turns out there are a lot of limitations in how you structure domains, and they have this concept of configuration sets. The hidden cost of SES is that you might be paying only $5,000, for example, but then you need SNS for the events: all the feedback from bounces, complaints, opens, and clicks. Now you get the events. Great. Then you need CloudWatch for the logs. You need a queue because there are going to be a lot of events, so you add SQS. Once you have SQS, you start adding all these different layers. Want webhooks? Now you have to build another thing. SES is a great platform; it’s fine. But you’ll quickly find that your footprint is much bigger than you’d imagine because you need all the apparatus around it.

Speaker 1

Another YC startup that came up in the email area is AgentMail. I talked to the founder, too, and he was like, “We’re going to build on top of SES and not really compete with them.”

Zeno Rocha

For us, that’s changing now. We’re building the infrastructure and going down to the metal. We’ve reached the point where it makes sense to innovate on the most basic layer. We can get better throughput and better deliverability if we focus on that. It’s a big project. We’ve been working on it for months, and we’re going to announce something soon about that direction.

Speaker 1

What’s the hardest thing? Is it trusted IPs? Is it compute and data centers, or what’s the blocker?

Zeno Rocha

Definitely IPs. You’re buying a whole IP block, and then you’re managing the IP pools yourself. That’s one part. Then you’re almost doing traffic control, controlling the throughput into each mailbox provider, and you need relationships with the providers. Once you have that infrastructure established, you have much more control over what you can give users.

One of my biggest things is observability. As an engineer, I want to see exactly what’s happening, and I’ve always felt like there wasn’t enough information in this space. When an email goes out, is it really delivered? Is it in the spam folder? Is it in the Promotions tab? I never know. You just trust that the email goes out, and then you hear from a user, “Oh, I didn’t get the email.” I’m like, “What happened?” There’s this empty space between those things. The closer we get to the metal, the more data we have to surface for users. I’m really excited. It’s the flagship change we’re making now.

Speaker 1

You’re becoming—It’s really interesting for all these developer-experience businesses. You start with a thin layer, like React Email, and build on other people’s infrastructure. Once you get big enough, you can build your own infrastructure. Are you doing anything differently now that you own everything?

Zeno Rocha

I think we’re approaching it with the same naive mentality we brought to all the other problems. We’re like, “Okay, this shouldn’t be this way.” We’re challenging the most basic things: this shouldn’t be this way. The P99 shouldn’t take this long. How can we make it faster? That’s one of the things we’re doing now: focusing very deeply on performance. We’ve always been a Node.js shop, with TypeScript everywhere. Most recently, in the sending path, we stopped using JavaScript. We have Go there, and we’re changing other parts to be more performant in other ways.

Speaker 1

Because now languages don’t matter.

Zeno Rocha

Exactly. It’s so cheap to pick a problem and rewrite the whole thing in whatever the fast language is. I’m running Rust projects, and I don’t really know Rust. I know some theoretical things about Rust, but…

Speaker 1

I’ve never really bothered to learn it.

Zeno Rocha

Mm-hmm.

Speaker 1

I feel like we’re not really covering the recent product surface area.

Zeno Rocha

Yeah.

Speaker 1

Maybe you want to go.

Zeno Rocha

No, no. Everything we’ve talked about is what you’re solving, and then there’s also just sending emails from the CLI, Super Agent Forward. You have some takes on this. I think the other day you tweeted, “MCP is so back,” right? Over a million MCP calls. What’s the AI side of email?

Speaker 1

Yeah, everyone was saying MCP was dead a couple of months ago. The only thing that matters is the CLI.

Zeno Rocha

What I’ve noticed is that I’ve stopped paying attention to what’s in and what’s out. I really think about these problems as, “Okay, how do I want my product to be?” I want my product to be formless. Whatever people want to do with the product, it should be possible.

That’s why we’ve always been API-first. I had no idea how much this would help us down the line, but I knew I’d never be able to cover all the use cases, so I thought, “Let me just give them the API. You do whatever you want.”

With MCP, it’s fascinating. We’ve had at least 2x growth every month. In August, the numbers were even higher. This was before the end of August. I think it was 1.2 million by the time the month ended. People are starting to work from Claude Desktop or Codex. If work starts from there, then you need those integrations. It’s super important.

Speaker 1

I just want to clarify. You showed us the month-by-month numbers for MCP.

Zeno Rocha

Mm-hmm.

Speaker 1

It picked up from, let’s say, 50% month-to-month growth, which is already super high. Then it starts to double basically every month.

Zeno Rocha

Mm-hmm.

Speaker 1

Did you invest in MCP, or did you just have an MCP and, after some time, it got picked up?

Zeno Rocha

The fun fact is that our very first MCP was built by Yoko from a16z, our investor.

Speaker 1

Oh, wow. Value add.

Zeno Rocha

Yeah, right.

Speaker 1

Brilliant.

Zeno Rocha

She built the open-source version. It was a remote— a local MCP. Then it started to grow like crazy, and I was like, “Man, why are people using this? It’s so hard to set up MCP.” This was last year.

Speaker 1

Yoko.

Zeno Rocha

Yeah, exactly. She built that, and then I just asked her, “Hey, can you transfer it to our org?” It was just an engineer building something. It was nice to see the traction it was getting.

But to do MCP right, to do the remote one, we had to go back and revisit our entire permissions model because we needed OAuth. Then we were like, “Okay, now we have a blocker. Let’s build OAuth.” So we built OAuth, and then it was, “Okay, RBAC. Let’s look at that. Let’s look at how users have access to each one of the resources.”

It was a whole journey to build OAuth. After we had OAuth, we could build the remote MCP. Then came distribution. We had the remote MCP. Great, great, great. Observability was in place. Great, great. All the Datadog dashboards. Okay, now we’re all in. Let’s talk to everyone.

That was hard, too. It’s not as easy—I wish I had all your connections.

Speaker 1

You can talk to me.

Zeno Rocha

Yeah. I’m just supposed to talk to you. But talking to the labs and trying to get into the official stores and plugin marketplaces and stuff like that was hard.

Speaker 1

Do you think that actually matters?

Zeno Rocha

For sure.

Speaker 1

I think sometimes I’ve been on the other side where I try so hard to get these partnerships, we launch it, and then nothing.

Zeno Rocha

Oh, man.

Speaker 1

Which one matters?

Zeno Rocha

As a consumer, I make decisions based on whether I have access to that data or not. As a buyer of B2B software, if I go to the cloud connectors and I don’t see the company listed there with an official MCP, I don’t trust it as much.

We had this with Plausible and PostHog. Plausible had an MCP built by Sentry. I don’t care. If Plausible doesn’t maintain that and it’s not official, I can’t trust it as much. I love the Sentry team and I trust them, but I need the owner of the software to own this piece of the integration, too.

I made the call: “No, we’re getting rid of Plausible, and we’re just going to use PostHog here because I have the MCP there.” I did that as a consumer, too. I’m into running, and I thought, “Oh, let me…” Strava has an MCP. I can access my runs, so I use Strava because of that.

If it’s, “Oh no, we have an MCP, but you have to connect like this,” like the xMCP, for example, where I have to use the local one, it’s just so frustrating. It works on the desktop client, not on my phone. To me, if it’s not there, I don’t use it.

Speaker 1

Apart from being officially maintained by the vendor, what makes a good MCP versus a so-so MCP?

Zeno Rocha

Even for ours, as I interact with it, the tool calls are always collapsed. I’m always opening them and trying to understand what it did. Just a couple of days ago, there was one call where it couldn’t put everything on the context for some reason. I thought, “No, this shouldn’t happen. How much data are we sending? Maybe we’re sending way too much data to the client.”

The number of tools was a bigger concern earlier. People thought if you had way too many tools, it would get confused. I don’t see that as much anymore. In fact, we’re just adding more to the MCP. We had maybe 20 tools when we launched, or even fewer than that. Now we have 80-something tools.

Speaker 1

What the fuck?

Zeno Rocha

Yeah, and I’m adding more and more. That’s the long tail of the tool footprint, what I’ve noticed. You can do only 90% of what your dashboard does, or you can do 100%. Getting to 100% coverage of what your dashboard can do is actually very, very difficult. Now you’re doing usage, billing, team invites, account provisioning, deletion. Should that be exposed as an API or not? It’s really hard. It’s a difficult problem.

Speaker 1

In fact, you’re one of the few Latent Space guests I can ever talk about this with. I think this is one of the mistakes of Next.js.

Zeno Rocha

Oh, really?

Speaker 1

Because Next.js, Server Components, and the Pages Router or App Router make it easy for you to bind data to your page. So you never expose the public API.

Zeno Rocha

Yeah.

Speaker 1

By default, the thing that performs well and that they encourage you to do means you won’t have an API.

Zeno Rocha

That’s so true.

Speaker 1

Then you have to create separate code paths or whatever. You should always have a completely headless backend, and then your frontend just happens to be one of many clients that connects to your backend.

Zeno Rocha

We started with our API on Next.js. I remember that. First of all, the bill was just so high that we were like, “There’s no way we can pay for this.” So then we moved to a traditional Node server, or whatever you call it. Our dashboard was always a private API consuming the same thing. We had to duplicate a lot of code. It was a mess.

Now it’s so much better. Everything’s in a monorepo, and you can reuse stuff. Ideally, those frameworks just give us those components by default. We had to build a public API separately from that, and it sucks to maintain both.

Speaker 1

Okay, one more thing on the MCP front. You’ve got 80 tools in there, and you’re adding more. You’re very counter-consensus compared to Cloudflare, which only has 2 tools: search and execute or something like that. So far you haven’t felt that issue. What would make you change your mind? The numbers are going up, but do you actually know? Do you talk to your customers and hear them say, “This is the best MCP on earth”?

Zeno Rocha

I do try to get a lot of feedback on that. The way I like to build products is that I’ve got to use the product myself. The investor update that I sent you yesterday was built using the MCP. It was fetching data from one place, from another place, and then—

Speaker 1

You’re making me feel bad now.

Zeno Rocha

Don’t do all this and don’t use MCP now, basically, is what I’m hearing.

Speaker 1

Well, the other thing is, you do have a CLI and a regular SDK. Are those also growing a lot?

Zeno Rocha

The CLI is definitely growing, but not as much as the MCP. I have a lot of fun with the CLI, too. I’m proud of this: I built our Careers page on a weekend or something. If you go to any job and try to apply, you have three ways of applying. You can apply via CLI or API. You can log in, and it has an interactive mode. We also have skills baked into the CLI, and you can just ask Claude to apply for a product designer role at Resend.

Speaker 1

Okay, so you’re very— It feels like you’re filling yourself with slop, especially in Careers.

Speaker 1

Yeah, yeah. I think maybe those are also the people you want, right?

Zeno Rocha

Totally. I actually have a filter. If the source is the CLI, I look at it differently because I know people are going the extra mile, setting it up: “Oh no, I have to download this thing, authenticate, and go through that flow.” But people who do that always tell me, “Man, I’ve never applied for a job using a CLI before.” Even if they’re not accepted, it’s a different experience from other job applications.

Speaker 1

Yeah. Even applying for one job through the API.

Zeno Rocha

Exactly. It’s the same thing as the CLI.

Speaker 1

Yeah. So one of the things I’m trying to figure out is product philosophy. You’re clearly maxing out everywhere: every SDK, every language, every surface area. Obviously, that’s easier with agents. But some founders I know would say, “Hey, this doesn’t matter. Give that to Greenhouse or Ashby.” It’s your job application; you’re not going to differentiate this way, right? You clearly have a different philosophy. You care about everything, even though some of it is probably wasted.

Zeno Rocha

The way I see it, I’m trying to optimize not only for privileged users—the ones with the best Wi-Fi and MacBooks in San Francisco or New York—but also for people at the margins in other countries with terrible Wi-Fi.

Speaker 1

You mean Brazil?

Zeno Rocha

Brazil. Growing up, that’s how it was for me: a terrible Windows computer and terrible internet access. That’s why we have a free tier. We don’t have it without a reason.

When we have all the SDKs, I’m maxing out on them. Do you think building the .NET SDK was fun? We looked into Stainless, Fern, and the third one, but we didn’t like what was generated. Every one of those SDKs is generated by humans—the Java one, the Rust one, all of them. I do that because if you’re using a product, you should have the best experience in the language you’re using.

Speaker 1

“But there are only 500 people out of the 4 million.”

Zeno Rocha

I care about those 400 people.

Speaker 1

Wow. Why not? You have 4 million users.

Zeno Rocha

That’s why not. There’s a lot to do, but it’s good to have that opinionated side toward building this.

Speaker 1

Any other product surface area we should cover? You covered the CLI, templates, and MCP. I think it’d be good to get your high-level perspective on how much of this is traditional. You have dashboards and templates for manually writing emails, you have programmatic tools, and you’re also fully agent-pilled. Where do you see it going? How do you think about building for a fast-changing world?

Zeno Rocha

There’s definitely still a component of email moving out of single-player mode and becoming more multiplayer. We even built our editor that way. It’s multiplayer, and it fixes all the conflicts if two or three people are working together. We actually run all our all-hands through a private Resend account I have with all the teams. The all-hands is pretty much: you go there, and it’s a huge—

Speaker 1

You make an email?

Zeno Rocha

It’s an email, and we send it together at the end of the all-hands. It’s super fun. You have about 20 people in the same document. That editor alone is so hard to maintain, but I love it. I love that we have the UI for people who need it.

Speaker 1

Yeah.

Zeno Rocha

Some teams hate having the email template pushed into their source code. They just want to build a visual editor, make a template for the marketing team, and call the ID. “I don’t care about the template. I just want to call the ID with variables, and I’m done.” Other teams say, “No, I want to commit. I want source control over this and to own this piece of work.” I try to tailor the product to those different audiences and build something that feels like we care, which isn’t the feeling I get elsewhere.

Speaker 1

By the way, what does the Resend team use to read email? Superhuman?

Zeno Rocha

Yeah.

Speaker 1

Have you seen the latest Superhuman update this morning?

Zeno Rocha

I haven’t.

Speaker 1

You’ve been busy with other launches too, right? For listeners, we’re recording this on the day of the Astro launch, which I was pulled into. I’m not sleeping.

Zeno Rocha

What’s wrong with it?

Speaker 1

They just updated the UI a little. There’s a sentiment that it’s going in the direction of every other acquisition: now you’re fitting a brand that has other interests, like Grammarly and other things.

Zeno Rocha

Okay.

Speaker 1

This is just email. I do want to keep up to date on email tech in general. You’re on the sending side; other people are on the reading and receiving side.

Zeno Rocha

Yes. I think increasingly, agents are reading my email. I actually don’t read most of my email. I have Poke and two humans helping me with it.

Speaker 1

Nice. I love that.

Zeno Rocha

Poke is pretty good. Honestly, Instinct is super hot now—a $2.5 billion company with no revenue. People are trying to read email with agents. We’re definitely looking at that space. That’s another thing I’m spending a lot of my time on: how you can programmatically create dozens of inboxes, and how those inboxes are accessed by agents.

Speaker 1

Yeah, because you enable receiving email. What’s it called? Inbound?

Zeno Rocha

Inbound, yeah. Email inbound is the most basic abstraction. Now we’re going one step further: maybe you need 100 inboxes for some reason, and here are the APIs you need on top of that. You need a read API, a mark-as-unread API, a star API, and labeling. We’re going to launch a product around that soon. But again, it’s all API-driven.

Speaker 1

Fully. The comparable products I’ve been looking at are Missive, Help Scout, and other shared inbox products like Front.

Zeno Rocha

Yeah, so hopefully this can be a version of that. I can share it with you. There’s a feature flag for you if you want to try it out.

Speaker 1

I’m very interested in email tech. And then, what percentage of your email goes to G Suite? What’s the market share between Google, Outlook, Apple, and Hotmail?

Zeno Rocha

I don’t have the numbers off the top of my head, but the vast majority—at least 60%—is Gmail. Then you have the big three after that, like Outlook and Yahoo Mail, and then a long tail.

Speaker 1

Apple isn’t that big.

Zeno Rocha

Apple is big.

Speaker 1

Yeah. Especially with the privacy thing they did, it’s harder—

Zeno Rocha

You can’t sign up with an Apple ID?

Speaker 1

What? Sorry?

Zeno Rocha

Apple auto-generates an email address for you.

Speaker 1

Oh, yeah, yeah, yeah. If you’re signing up for something—

Zeno Rocha

Yeah, yeah.

Speaker 1

I use that. Is it a problem for you?

Zeno Rocha

They’re stricter about what can get into those inboxes. As a domain owner, we have an in-product wizard to help you register with Apple so you can get your emails delivered there.

Speaker 1

Yeah. I understand. Obviously, this is your job. The whole thing is deliverability. If you don’t have deliverability, you don’t have a business.

Zeno Rocha

Exactly. That’s kind of what they do. We can have the most beautiful Rubik’s Cube on the website, the coolest handbook ever, but if it’s down, it’s all for naught.

Speaker 1

And how correlated are they? If you get banned, downranked, or put in the Promotions tab in Google, does that transfer over to the other providers, or are they very decentralized?

Zeno Rocha

Thankfully, now there’s a lot of reputation associated with the domain. At the beginning of the email industry, it was very IP-based. If one IP pool was damaged, you got the consequences. Now people create different subdomains depending on what types of emails they’re sending: one subdomain for transactional emails that maybe don’t have click and open tracking, and another for marketing emails. Those subdomains help segregate the reputation of the stuff you manage.

Speaker 1

Would it be something like transactions.resend.com?

Zeno Rocha

Yeah, updates, notifications, whatever you want to use.

Speaker 1

Could I have more dots if I want, like a.b.c.resend.com?

Zeno Rocha

You could, but we just see that having five subdomains isn’t really practical.

People do some special ones. We do that at Resend for our own emails. Marketing has a different stream from transactional emails. Even the investor emails have a different one. I use confidential.resend.com to send those emails.

Speaker 1

I didn’t even know you could do that.

Zeno Rocha

Yeah. That’s good advice. It’s good practice.

Speaker 1

So before, it was very IP-based?

Zeno Rocha

Yeah. Now it’s very domain-based.

Speaker 1

I’ve received so much bad advice. I had to buy a separate domain because we use ai.engineer and latent.space. These are all weird TLDs, and nobody recognizes them.

Zeno Rocha

That’s right.

Speaker 1

Nobody recognizes them, right? So I was told to get .coms for everything, and then maybe that would improve deliverability. The problem with that is, let’s take Coca-Cola. Coca-Cola has a domain. Now you’re Coca-Cola, and you’re like, “Oh yeah, let’s buy another domain that looks like our domain.”

Zeno Rocha

It looks like phishing. It looks exactly like phishing.

Speaker 1

So the chances of damage are way worse. Is this still a thing when you’re buying the .com? I’d get it the other way, right? You’re latentspace.com, and I buy latent.space. That looks like phishing, right? But the .com still?

Zeno Rocha

Man, you’d be surprised. The things I see on a day-to-day basis are crazy.

Speaker 1

So what I’m hearing is that .com is worth it.

Zeno Rocha

Yeah.

Speaker 1

That’s all the sort of business of email. Obviously, some part of it is that you just got started before ChatGPT, and you were a leading player that people liked, so you popped up organically. You didn’t do anything special for AEO. What did you do for AEO?

3. Getting Recommended by AI

Zeno Rocha

I wouldn’t say we were the leaders. Coming up in 2023, very few people knew about Resend, and we were so behind. Twilio, Postmark, and Mailgun had invested in SEO for more than 10 years, so getting ranked for anything was an uphill battle. It was so difficult.

We decided to focus on the docs. We were very intentional about the docs and the long-tail searches they could target. For example, instead of just having docs for Python, we’d explain how to set it up with Django.

Speaker 1

How to do something with something.

Zeno Rocha

Exactly. Super short articles focused on that.

Speaker 1

That’s traditional SEO.

Zeno Rocha

Traditional SEO. Nothing fancy there. Then, when models started to come along, I thought maybe I needed to change the content on the page. If people are asking questions, I need to create content in an ask-and-answer format. So we added a lot of FAQs. Now, almost every page at Resend has an FAQ.

Speaker 1

You’d go to the pricing page, and of course pricing almost always has an FAQ. That’s pretty standard.

Zeno Rocha

Yeah.

Speaker 1

But you do FAQs on all sorts of pages.

Zeno Rocha

Security, too. You see the pattern: all pages have that, because people ask, “Is Resend SOC 2 compliant?” Then the answer is right there.

We added llms.txt to our docs, thankfully because of Mintlify, which we use. Then we asked how to bring that to the marketing site, too, so we added llms.txt to every marketing page. We did the same with the docs’ Markdown versions. I’m going to make Markdown versions of every page on the marketing website, too.

Speaker 1

Are you using content negotiation, or do you just append .md?

Zeno Rocha

You just append it. If you go to the security page and add .md, it works. You can also use content negotiation, and it’ll render the Markdown version on that page without going to another page.

Speaker 1

For listeners, I’m not sure that matters. I’m really not sure.

Zeno Rocha

I mean, you’re doing really well, so…

Speaker 1

One example where it changed things—and maybe it doesn’t help with distribution, but it helps with accuracy: go to the pricing page. I remember one random Sunday, I was doing competitor analysis. I asked, “If you send 1.2 million emails using Resend, X, Y, and Z competitors, who’s the cheapest and who’s the most expensive?” It got it completely wrong. It got the Resend number so wrong, and it actually said very bad things about us, like, “Resend’s pricing is very obscure.” I was like, “What the fuck? It’s not obscure at all.”

Zeno Rocha

Oh, so you made a calculator?

Speaker 1

Yeah. The problem was that agents don’t really run a JavaScript widget.

Zeno Rocha

Okay.

Speaker 1

So I made the .md version of this page.

Zeno Rocha

Which gets a tremendous amount of access, by the way. You get analytics on this?

Speaker 1

Yeah. Not through the regular analytics, because we can’t track that.

Zeno Rocha

Yeah, it’s server-side.

Speaker 1

So we have to go to Datadog to figure that out. It was really crazy. I made that change and pushed it, then I asked again a few days later, and it got the numbers right.

Zeno Rocha

I see.

Speaker 1

I’m like, “Okay, this already—”

Zeno Rocha

It’s a good way to live-update and fix stuff in your search entry.

Speaker 1

Exactly. This is what matters: accuracy.

Zeno Rocha

But it does mean you don’t have a single source of truth. You have to update the Markdown, and then you also have to update the—

Speaker 1

That sucks completely. But if I wanted the happy path and the easy path, I wouldn’t be doing email. That’s the price of it.

Zeno Rocha

Well, if you’re good at React, you can write a custom renderer.

Speaker 1

You know how to do this. What else? We talked about the basics: FAQs everywhere and basic SEO stuff. Comparison pages—us versus SendGrid, us versus Mailchimp. Although our page could be much better. Go to—

Zeno Rocha

This isn’t there.

Speaker 1

I’m sure you have it somewhere in a footer or something.

Zeno Rocha

Just go to /migrate. I can give you some—

Speaker 1

Ah, okay. By the way, for 404 pages, I always think we should guess what people meant. Take the slug and find the nearest neighbors.

Zeno Rocha

Oh, yeah.

Speaker 1

In case you ever break a URL, it just auto-fixes itself. Don’t just serve the 404.

Zeno Rocha

My intention with those was to try something that wasn’t exactly a comparison page.

Speaker 1

A comparison page.

Zeno Rocha

Yeah. But I don’t think it was a great idea, because our competitors actually built comparison pages, and they get recommended more than ours. What we try to do, if you go to Postmark, for example, is demonstrate first: “Hey, if you want to migrate, here’s a code converter.”

Speaker 1

Insert an example.

Zeno Rocha

So you can just put any code block there.

Speaker 1

Why? Why, dude? This is so extra.

Zeno Rocha

That’s what we do.

Speaker 1

There’s a cube on the landing page. Everything’s extra.

Zeno Rocha

The cube has been there for 2 years. Adoption is something I pushed this last weekend. Now we have a graph that compares our adoption with every competitor. Again, one thing I learned from the pricing page is that JavaScript widgets won’t be executed, so I spell out the same data in text so LLMs can read it.

Speaker 1

I think they’re getting somewhat better. I see a lot of agentic use: load the website, click on an image, interpret the image. It’s slower, but with computer use, they’re getting much better.

Zeno Rocha

I agree.

Speaker 1

If you’re fetching information and just comparing things, they don’t do that, right?

Zeno Rocha

I think they’re starting to go more toward computer use.

Speaker 1

I’ve been doing a lot of “compare this and this,” and browsing a website is pretty computer-use-heavy, I think.

Zeno Rocha

Okay.

Speaker 1

I noticed you don’t have another classic AEO tactic: “Here’s how to connect our thing with Claude Code. Here’s how to connect our thing with Codex.”

Zeno Rocha

Oh, yeah. It’s all an AI page.

Speaker 1

Okay.

Zeno Rocha

We do it as a separate AI page.

Speaker 1

Okay. Both, both MCP. There are some things that are interesting. If you go to the legal page, resend.com/legal, you can summarize or ask it to explain the complexity.

Zeno Rocha

I see.

Speaker 1

That’s just an external link.

Zeno Rocha

Yeah.

Speaker 1

Again, I’m not sure that matters.

Zeno Rocha

You mentioned a lot about recency for AEO compared with traditional SEO.

Speaker 1

Yeah. That was the thing I was really curious about in the beginning. There was no reason for any of the models to recommend us because we were so behind in SEO. We don’t have the typical glossary page or generic articles that are just SEO-heavy. I was trying to figure out what was going on. I could tell that, at least with Opus 4.5, there was a recency bias in terms of the technology and where it was fetching data. Recently, they said maybe Replit isn’t necessarily something people suggest anymore.

Zeno Rocha

Newer tools started popping up, and Resend was one of those. Because there was a lot of organic content about the tool, we started getting recommended more. The advice here is to try to get as many people as possible, in as many places as possible, talking about your product, because it definitely has an influence.

Speaker 1

I think that’s a class of its own. Did you ever engage SEO consultants or AEO consultants? Are they useful, or a waste of money?

Zeno Rocha

We never really did that.

Speaker 1

You seem like you’re doing everything yourself.

Zeno Rocha

Yeah. I think you were the AEO king.

Speaker 1

You had that 2024 tweet: “Let’s talk about AI SEO.” I think you were one of the first ones to pick it up.

Zeno Rocha

Yeah.

Speaker 1

The general state of things, since we did an AEO or GEO episode around this stuff, was that most people said, “Just do what normal SEO does, and don’t block AI chatbots.” Most tools, like Profound at the time, would track your mentions and let you run experiments. Those things are par for the course and normal. I’m trying to figure out what to do. People are pinging me because I’m also doing AEO experiments.

Zeno Rocha

Hmm.

Speaker 1

I have an unfair advantage because I’m a content business. I pump out content, whereas you actually have a product.

Zeno Rocha

Yeah.

Speaker 1

You’re doing very well, but how closely do you track how well your docs are used? How often you’re recommended compared to competitors?

Zeno Rocha

I feel it’s so crucial. Before, if we were unsure which tool to use, we’d ask Google, and it would show us comparison pages or the first few results. Now you just get one response out of the gate. If you ask, “Which tool should I use?” people want to go with the most frictionless option.

Speaker 1

Yeah.

Zeno Rocha

I think a free tier is very important. Michael Grinich from WorkOS is trying to promote this idea of authless usage. I don’t know if you’ve seen this. It’s very similar to Netlify, where you don’t need an account to do the basic action. It’s unauthenticated usage of your product.

Speaker 1

Yeah.

Zeno Rocha

It’s obviously very dangerous because it’s prone to abuse, but it’s the easiest thing: no sign-up.

Speaker 1

That’s the thing I’m trying to figure out. I’m debating whether to do that or not. Do we need a provisioning API?

Zeno Rocha

Provisioning and claims, right?

Speaker 1

Yeah. But then there’s the free tier.

Zeno Rocha

Yeah. I don’t know if it’s something about our industry, but there’s just a lot of abuse.

Speaker 1

Yeah, you just have abuse.

Zeno Rocha

Yeah, a lot of abuse.

Speaker 1

I think those are the main tactics. The other thing I’d tell listeners is to hook your clanker up to your analytics and your codebase. You need to fully complete the loop and basically automate research.

What I have now is my cycle. I have both a Latent Space CMO agent and an AI Engineer CMO agent. They spawn other agents. Their job is to research ideas and keep track of things we’ve tried. Then I sign off on the things we want to experiment with. We have an experiment window, and we run the experiments. Other agents monitor those experiments.

That’s the auto-research loop for doing this stuff. You also need to give it tools. I signed up for Ahrefs data for SEO. Most recently, I made my own AEO tracker, which you can make. Then you just want to make the number go up.

You don’t know; you’re throwing things at the wall. Does the thing on the legal page matter? I have no idea, but I’ll keep throwing things at the wall and seeing what works. I think Reddit doesn’t matter. Hacker News used to be big for you.

Zeno Rocha

Yeah.

Speaker 1

Now, not as much. Twitter doesn’t matter as much. It’s weird.

Zeno Rocha

It’s so crazy. Do you have a tracker?

Speaker 1

No. We use all of those Profound-like tools. We tried them all. People ask me, “Should I use Gauge or Profound or this other one?” I’m like, “Yeah, we have 4 subscriptions.” That’s what it takes now. You have to see which one works best.

What I miss from those tools is, “Give me the action.” I think the problem is they don’t tell you what to do because they’re also trying to figure out what needs to happen. “Write an article on Wikipedia.” Yeah.

Speaker 1

The old-school SEO tools like Moz would have more opinions about these things. Right now, the AEO tools, from what I hear—and I’m not an expert; we should probably talk to Profound—are mostly reporting tools. They’re analytics reporting tools, and that’s fine.

Zeno Rocha

It’s a big business.

Speaker 1

Exactly. Ahrefs is a Singapore business, and apparently they do, I don’t know, $300 million.

Zeno Rocha

Yeah, totally.

Speaker 1

The other parts of your business—we’re going to talk about the parenting side and the personal side. You seem very chill. You have 50 people working remotely all around the world. You’re worrying about MCP and AEO. That can’t be how you’re closing all these big customers, right? Where’s your fancy sales guy with the steak dinner and the golf course?

Zeno Rocha

We’re just starting that motion. We’re very lucky that we’ve been able to go this far without having it. I’ve worked at an enterprise-only company in the past, so I knew what that takes: the steak dinners and all the apparatus around the sales organization and enablement. There are all these things that are needed. I knew that when the time was right, we’d have to turn that key.

But I’ve been very cautious about doing that at Resend, in different layers, instead of doing everything at once. Maybe it’s because we’re remote, but I think we’re very protective of the culture. Let’s make sure we don’t damage the culture all at once. Let’s try to figure out who fits. We just have one AE now, and it’s been helping. It’s been going super well.

Speaker 1

Good enough. Once you double your ARR because of a couple of deals, you’re like, “Okay, this is a good sign.” People want to pay you more for things like having an agreement with you and having your software on their premises or in their VPC.

Zeno Rocha

For sure. What I’m learning, too, is that you’re building a different product, so that’s how you need to see it. It’s not only about building a different machine internally as a company. As I’m designing the company, I’m designing which department, who sits where, and how each person is better equipped to do their job.

For enterprise, it’s actually a different product. What they care about is very different from what $20 users care about. If I just add WorkOS, SSO, SCIM, and audit logs, it’s not going to be enough. It’s not just putting those items on the pricing page. It’s a journey, for sure.

Speaker 1

Any other things you want to reflect on in the journey before we go into the personal side?

Zeno Rocha

No, I think we covered a lot.

Speaker 1

Okay, then I’ll talk a little bit about my use case. I’m a content creator. The bulk of your business, I assume, is transactional email.

Zeno Rocha

That’s right.

Speaker 1

You have marketing emails and inbound emails. I’m sure that’s less outside of the business. I pay Substack something like $10,000 a year to send my emails, and that seems too high. Why is marketing email so different from transactional email?

Zeno Rocha

It’s a great question.

Speaker 1

Your business model is also different, right?

Zeno Rocha

It is. We’re more expensive, too.

Speaker 1

Then I was like, “I can’t do this.”

Zeno Rocha

The industry has this pattern of charging per contact. That’s the first thing. They try to price around the value you create with each contact. But now it’s crazy. The AI companies we serve grow so fast. Mistral’s users recently—the amount of users they add is just insane. The business model of contact-based pricing is kind of broken, and we’re realizing that and trying to fix it too.

But that's how it had always been. There’s something about transactional email: you put a message in a queue and get it out of the queue. With marketing email, you’re building an engine of batches and intervals between batches, analyzing and increasing or decreasing the speed as the sending is going, maybe blocking.

Speaker 1

So is there a maximum rate you should send emails at a time?

Zeno Rocha

Yeah, for sure.

Speaker 1

Per domain, specifically?

Zeno Rocha

Yeah.

Speaker 1

Okay. Let’s say I have 100,000 emails to send out. It should take me 10 minutes?

Zeno Rocha

Yeah. For example, now, with the 4.3 million users that we have, it takes more than a day.

Speaker 1

Oh, what? No, that’s unacceptable.

Zeno Rocha

Yeah, for sure.

Speaker 1

So then I pay you more to get in a different queue?

Zeno Rocha

Yeah.

Speaker 1

Okay. So you have to always be trying to figure out, “Okay, we need more at the door.” How does that work?

Zeno Rocha

Yeah, yeah, yeah.

Speaker 1

Oh, that’s interesting. It’s like rate limits for token limits.

Zeno Rocha

Yeah, exactly.

Speaker 1

Where’s my reset button?

Zeno Rocha

Yeah, exactly.

Speaker 1

You also went into YC and started this company as a young father. Part of the thing is that there are a lot of people without kids in San Francisco, and I think that’s part of the consideration. A lot of people listening might think, “I can’t be a founder. I have this great idea, but I have a young family.” How do you manage?

4. Choosing Family Over Growth

Zeno Rocha

You’ve got to preface that with the fact that you’ve left San Francisco for your kids.

Speaker 1

Yeah.

Zeno Rocha

This is recent news: I’m spending more time in Brazil now because we’re expecting our second kid. At first, it was crazy. I came to San Francisco when my daughter was one year old, and every YC founder around me had no idea what it meant to have kids.

Speaker 1

Yeah. What is this reproduction?

Zeno Rocha

Exactly. You don’t even have Series B. What are you doing married?

Speaker 1

Totally. Most of them weren’t married at all.

Zeno Rocha

It’s crazy. I always try to look at those things. At first, you see them as disadvantages: all of these guys came from MIT and all these amazing schools. That wasn’t the case for me. They weren’t married, and that wasn’t the case for me. They didn’t have kids, and that wasn’t the case for me. But I still went for that program thinking, “I just want to build the best company in this batch—not number four or number five, but number one out of 250.”

Speaker 1

Oh, yeah? Which cohort?

Zeno Rocha

Winter 2023.

Speaker 1

You realize in the middle of that there’s no winner in YC. There’s no such thing.

Zeno Rocha

Yeah.

Speaker 1

I’m pulling up Winter ’23 now just to see who I know.

Zeno Rocha

Especially what you understand is that it’s an infinite game. Even if you had an amazing batch and raised the biggest round, it doesn’t matter because life goes on and continues. Many of the people I met there aren’t here anymore.

Speaker 1

Yeah. Co-founder breakups, seven pivots, and they’re dead.

Zeno Rocha

But we’re here. I was very much like, “No, no, no.” Even when we bought the domain resend.com, we were like, “It’s going to be an amazing website with an amazing .com. It’s not going to be a .io or whatever.”

Doing that with kids was so freaking hard, especially because I wanted to enjoy my first daughter. I really thought about this. There was one point during YC—this story translates to what I’m going to say. I came to an event, and PG was there. I thought, “Oh, man, Paul Graham, the father of everything. God is here.” Everyone was paying attention to PG, and then he said, “You know what? We always tell you not to do something as partners, and then you end up doing it. Months later, you come to us and say, ‘Oh, I regret doing this or not doing this.’”

So he said that, and then I went to my partners and asked, “What are the things I’m doing now that I shouldn’t be doing, that you think are wrong?” One partner—not my main partner, but another partner—told me, “You worry too much about design. You care too much about that. If you didn’t care about it, you’d be much further ahead.”

That hurt me so badly because it was true. My slides when I was pitching were beautiful, and he was like, “Doesn’t matter.” I was like, “Yeah, now I know it doesn’t matter.” That really hurt, and a few days later I reflected on it. I thought, “If I were to build a product with this identity that only 1,000 people used, I’d prefer that to having a product with 10,000 people that I don’t want to use myself.”

So, you know what? I’m going to follow what I believe is right. In this industry, everyone had terrible products. There wasn’t enough design infused into them, so I felt that was a differentiator, and we needed a differentiator in such a crowded market.

I go back to that with my kid, too. Ten years from now, if I’m with my daughter, she wants to be with me so much, we play all the time, and we’re a $10 million ARR company, I’d rather live in that reality than in one where we’re a $100 million company and my daughter doesn’t want to play with me, isn’t interested in me, and we’re not that close.

That’s the decision I made. Maybe it’s right, maybe it’s wrong. I have no idea. I go extremely hard. I have a lot of ambition, and that’s not going to stop me or anything. But setting those priorities and figuring out for yourself what works for you is important. More than ever, she’s the most important thing for me, and I prioritize her a lot.

Speaker 1

How do you balance that with your ambition? I have this in a smaller way. I don’t have kids, but I have a lot of ambitious things and a family I should spend time with. When I spend time with them, I’m not present. I’m looking at my phone, saying, “Oh, I should be reviewing Astra”—you know, GPT-6. It’s like AGI. It’s not, right? But I really feel like I should be working, and at the same time, I feel guilty. I’m happy in both areas.

Zeno Rocha

Totally. That’s how I feel. I feel like I’m a terrible dad, a terrible husband, a terrible CEO, and like I’m failing in every single area of my life. I feel exactly like that. But every day I try to be a little bit more present.

Especially when you’re working from home, you leave your office, and now you’re a dad, and then you’re not anymore. Now you’ve got to be a husband and pay attention to your wife, while your mind is thinking, “Oh, man, how do I do this enterprise? I’ve got to close this deal.” I feel like I cycle all the time, too.

Speaker 1

Yeah, we’re on the same boat.

Zeno Rocha

Yeah.

Speaker 1

Well, it’s never easy. I think just naming the thing for your category is important, and people don’t think about category creation enough. This is something Netlify weirdly tried to do and failed with Jamstack. I think more people should try to create a category, because when they’re successful, they own the whole thing.

So for this, Resend is the next generation SendGrid, let’s call it, or something like “AI-native SendGrid.”

Zeno Rocha

Yep.

Speaker 1

I think—and I’m probably being too honest—that’s not category creation yet.

Zeno Rocha

Yeah.

Speaker 1

But it is category dominance. You own your category. That’s good.

Zeno Rocha

Mm-hmm.

Speaker 1

But it’s not clear enough yet what’s different. My classic example is another guest we’ve had, Dharmesh Shah from HubSpot.

Zeno Rocha

Uh-huh.

Speaker 1

Anyone who wants to think about category creation should read about inbound marketing versus outbound marketing and how they created the category of inbound. The ideal phrase for category creation is that once you’ve heard the category—the two words your company represents—you don’t want anything else. There’s no long essay, manifesto, or talk. It’s just two words, maybe some examples. That’s it. Your audience can take it from there.

Zeno Rocha

Mm-hmm. It’s very hard. I’ve seen friends trying to do that, like Svix. It’s webhooks as a service.

Speaker 1

Yeah. They took my name.

Zeno Rocha

Yeah. It’s just so freaking hard.

Speaker 1

I think they’re doing okay, right?

Zeno Rocha

Yeah.

Speaker 1

I don’t know if they’re still around. There was a webhooks company, and then there was an anti-webhooks company where you’d say, “We don’t do webhooks. We just help you publish a JSON file that you pull,” or something like that. It kind of reverses the push versus pull data flow. This was, again, the COVID-era dev tools. That was the most exciting thing at the time.

Yeah. Yep. Cool. Well, always a pleasure to catch up, and congrats on all the success. I’m still very curious how much you’ve dominated your category. I think you chose it very well, executed it very well, and you’re managing your family as well, so lots of respect.

Zeno Rocha

Thanks so much. Yeah, it was great chatting with you guys. Thanks a lot.