How Resend got its users

Resend's wedge is React Email, a free library for the worst chore in the job, hand-coding responsive HTML email. Its docs show sending through SendGrid, Mailgun, AWS SES and Postmark, not only Resend, and the footer just says "Brought to you by Resend". Copy the shape: take the chore your product removes, ship it standalone and free, and make it work with the competitors people already pay for. Nobody adopts a tool that only pays off if they switch first.

done whenHand your free tool to someone paying a competitor. If they can run it end to end without creating an account with you, it is a wedge. If it stops at a signup wall, it is a demo with extra steps.

react.email/templates asks for no imagination: "Recreate an existing email or submit a pull request to add your template here." The gallery is Stripe Welcome, Notion Magic Link, Vercel Invite, Apple Receipt, Linear Login Code, filed under Magic Links, Receipts, Reset Password, Notifications. Each card carries the contributor's avatar and handle. Build that surface: one shallow folder, an ask that starts from something they already own, and public credit on the page.

done whenTime yourself doing your own contribution flow from a clean clone. If a stranger cannot land one in a single sitting without asking you a question, the ask is too vague or the folder is buried too deep.

Resend ships a repo per room, not one quickstart: resend-nextjs-app-router-example, plus examples for Remix, Hono, Cloudflare Workers and RedwoodJS, and a separate SDK for node, python, ruby, php, laravel, go, rust, java and dotnet. With no budget, pick the two ecosystems you already write in, ship a runnable repo for each, then post it where those people sit: that framework's Discord, its subreddit, a PR to its awesome-list.

done whenClone your own example repo into an empty folder and run it cold. If it needs one step that only lives in your head, it is a snippet, not an example, and it will produce issues instead of users.

resend.com/open-source lists what they fund, not only what they built: Tailwind CSS, Input OTP, and Can I Email?, the neutral compatibility reference every email developer checks before shipping. They back the referee of the category, not a customer. Free version: find the two neutral references in your niche (the compat table, the awesome-list, the benchmark), and contribute data, fixes and docs under your own name for months before your product comes up.

done whenCheck whether your contributions to that reference stand on their own with your product deleted from them. If removing your name makes the work useless to its maintainer, you wrote an ad, not a contribution.

resend.com/handbook is public: Company, People, Engineering, Design, Success, Marketing, Sales, down to how they run RFCs, code review and on-call. The marketing page states the rule out loud, amplify externally what is being built internally, and says they write for the right narrow audience instead of the biggest number. Copy it: a public handbook and a public changelog, one entry a week, aimed at the person deciding whether to trust you in production.

done whenRead your last three changelog entries as an outsider. If any says "various improvements" or needs internal context to parse, you are publishing noise and nobody will subscribe to it.