Topics Pioneers Insight Method Author
Back

Designing for Agents — Zeno Rocha, Resend

·Latent Space

Rendering the long image…

Topics Autonomous Agents Reshaping Enterprise SaaS AI Inference Gateways and Intelligent Routing Enterprise AI ROI and Cost Optimization Mindset and Psychology of Tech Founders
Pioneers Zeno Rocha

Summary

  • 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.

Deep dive

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.