The Email API Rebellion Nobody Saw Coming
SendGrid has been the default answer to “how do I send transactional email?” for so long that the question barely warranted discussion. Developers building their first SaaS app, their first notification system, their first welcome email flow – they reached for SendGrid the way they reached for Stripe or AWS. That default is cracking. Resend, a developer-focused email API built by a small team, is pulling startup developers away from Twilio’s flagship email product in meaningful numbers, not through a marketing blitz, but through the thing that actually moves developers: a dramatically better experience of using the product itself.
Resend launched publicly in 2023 and positioned itself with a single clear argument – that the existing email infrastructure tools were built for marketing teams, not engineers. That framing landed. The product is built around React Email, an open-source component library that lets developers write email templates in React rather than wrestling with archaic HTML table layouts and inline CSS hacks. For a generation of frontend developers who learned to build interfaces in React, this is not a small convenience. It collapses hours of frustrating template work into something that feels native to how they already build.
Why Developers Are Moving
The technical case against SendGrid among startup developers is not subtle. SendGrid’s API is functional and well-documented, but it carries years of accumulated complexity. Deliverability settings, IP warming, domain authentication, suppression lists – each piece has its own interface layer, its own logic, its own potential failure mode. For a solo developer or a two-person startup engineering team, that surface area is a real cost. Debugging a dropped email in SendGrid often means navigating multiple dashboard tabs, parsing event logs, and cross-referencing suppression list behavior. Resend surfaces the same information in a single, clean activity log tied directly to each send.
The onboarding gap is where Resend wins the first impression. Developers report going from zero to a working email send in under ten minutes with Resend’s API, including domain verification. SendGrid’s onboarding has historically required more configuration steps, more waiting on DNS propagation confirmation, and more decisions upfront before anything works at all. In the startup context, where the engineering team is often one or two people trying to ship a product by end of week, that friction difference is decisive.
React Email is doing real heavy lifting here. The component library is open source and usable independently of Resend’s sending infrastructure, which means developers discover it through GitHub, through X threads, through their own search for how to stop writing email HTML by hand. Once they’re building templates in React Email, reaching for Resend’s API to send them is the path of least resistance. The product loop is elegant: the tool that solves the template problem also points toward the infrastructure product.
SendGrid’s Structural Disadvantage
Twilio acquired SendGrid in 2019 for roughly $3 billion, and the years since have not produced a product that feels aggressively maintained for developer experience. Twilio has had its own turbulence – leadership changes, layoffs, pressure from investors to find a clearer path to profitability – and SendGrid has sat inside that complexity. The product works. Deliverability is strong. The infrastructure is genuinely reliable at scale. But none of that addresses the experience of using it as a developer in 2024 versus 2018.
Startups in their earliest stages are not choosing email infrastructure based on enterprise SLAs or dedicated IP pools. They’re choosing based on time-to-working-code and how much the product gets out of their way. SendGrid was built to serve both the solo developer and the Fortune 500 marketing department, and that breadth creates a product that doesn’t feel purpose-built for either. Resend made a deliberate bet that the developer segment was underserved, and that a product optimized entirely for that segment could earn loyalty before a startup ever needed enterprise-scale features.
The Compounding Effect of Developer Trust
Email infrastructure is a switching-cost business. Once a startup has domain authentication configured, templates built, and event tracking wired into their application, they are not moving unless something goes seriously wrong or the new option is dramatically better. Resend is betting that capturing developers early – at the pre-product-market-fit stage when nothing is locked in yet – means those teams carry Resend with them as they scale. A startup that signs up for Resend at a five-person company and grows to fifty is a much more valuable customer than one acquired through an enterprise sales motion.
The pricing structure reinforces this. Resend’s free tier allows meaningful volume for early-stage products, and paid tiers are priced straightforwardly without the per-IP or dedicated infrastructure add-ons that make SendGrid’s pricing harder to reason about at small scale. Developers can estimate their Resend bill intuitively. That predictability is not trivial when a two-person team is watching every dollar of cloud spend.
Word of mouth inside developer communities is accelerating the shift faster than any paid channel could. The product shows up in “what stack would you use today” threads on Hacker News, in indie hacker forum discussions, in startup Discord servers where a junior developer asks how to wire up transactional email and gets a Resend recommendation before anyone mentions SendGrid. This is exactly how Stripe won the payments category before it became a sales-driven enterprise company – by being the answer that developers gave each other.
What remains genuinely unresolved is whether Resend can hold this position as the startups it serves grow into mid-market companies with more complex needs. Deliverability at high volume, dedicated IP infrastructure, compliance requirements, suppression management at scale – these are the places where SendGrid’s depth still matters. The segment Resend is winning now is specifically the segment where those needs don’t exist yet. Whether a startup that grew up on Resend stays when it’s sending ten million emails a month, or whether the enterprise sales team at SendGrid finally gets a call returned, is the actual question that determines how much market this shift represents.
