Resend is selling to the agent and handing the humans free templates

The proprietary hook is not in the templates. React Email's documentation lists SendGrid, Mailgun, Postmark, MailerSend and Amazon SES as integrations ^[4], and the designs run with no Resend account at all ^[3]. What does not travel is one of the three Email Skills the company shipped in January: the file describing Resend's own API ^[5]. The other two are general craft, covering React components, Tailwind styling, plain-text output, authentication records, suppression lists, retries and idempotency ^[6]. Any competitor could write comparable instruction files. On the evidence supplied, none has.

That asymmetry is the whole trade. Resend says the skills work with Claude Code, Codex, Cursor and Gemini ^[7], which means the guidance sits inside the tool a developer is already typing into, at the moment the email code gets written rather than at the moment a vendor gets chosen. The August workflow completes the loop by handing the agent a finished design and a brand prompt instead of a blank page ^[1].

The reason a template layer is worth anything to a model is narrower than it looks. An agent can produce HTML unaided; producing email that survives several mutually incompatible clients is a small domain with years of accumulated edge cases, per runtimewire ^[11]. Resend's repository claims its components are tested against Gmail, Apple Mail, Outlook, Yahoo Mail, HEY and Superhuman ^[9]. That is the part an agent cannot infer from first principles, and it is the part Resend gives away.

The adoption numbers should be read as distribution, not revenue. Resend reported 2 million weekly npm downloads at the React Email 6.0 release, up 108 percent from the previous major version five months earlier ^[8], which puts the earlier baseline at roughly 960,000 ^[13]. Every one of those installs is compatible with five rival senders ^[4]. Resend's delivery service is where the money is, on free and paid tiers ^[12], and the material supplied carries no figure for how many template users cross over.

One claim in the pitch is worth flagging as the company's own. "We paid designers so you don't have to" is Resend's line ^[2], and runtimewire notes the payment claim is unverifiable while the code and the integrations are not ^[14]. The founders came to this from the authoring problem first: React Email predates the January 2023 launch of the sending platform, and delivery, authentication, bounces and spam placement became the commercial surface afterwards ^[10]. The agent funnel is that same ordering, run again with a different reader at the top of it.