Nov 10, 2026 · 1h 26m
Resend turns email infrastructure into an agent-ready platform
Designing for Agents — Zeno Rocha, Resend
The conversation shows how a developer-first email company must solve infrastructure, trust, distribution, and founder-life tradeoffs simultaneously.
- 1Resend used open source and developer experience to challenge established email infrastructure providers.
- 2Deliverability requires deep operational controls, abuse prevention, mailbox relationships, and increasingly owned sending infrastructure.
- 3AI-native interfaces are reshaping email products, documentation, inboxes, and how companies reach users through agents.
Don't miss
Zeno Rocha explains why he is choosing greater presence with his daughter and family over maximizing the company’s valuation.
The brief
Zeno Rocha traces Resend’s path from React Email and open-source developer tools to a major email infrastructure company, while questioning how much ambition a founder should trade for family time.
Resend’s developer appeal rests on a deceptively difficult system: provider throttling, reputation, queues, abuse detection, DNS configuration, and support processes that must scale without abandoning trust.
The company is moving closer to the sending infrastructure itself, managing IP blocks, throughput, and observability to expose better delivery information and improve performance.
Resend’s CLI, MCP integrations, collaborative editor, and agent-managed inboxes reflect a broader product philosophy: email should work through many interfaces, not just a dashboard.
The sharpest tension arrives in the closing reflections, where Rocha weighs category dominance and company-building against being present for his growing family.
Books & mentions
Some links are affiliate links — PodLume may earn a commission if you buy.
Weekly email
State of the Pod, every Monday
The week's most-discussed names and stories from podcasts, with the moments behind them. Free, five minutes, unsubscribe in one click.