Resend scored 7.4/10.

The page’s single differentiation claim — “email for developers” — is doing no work because every competitor the page is implicitly fighting (Mailgun, SendGrid, Mandrill) has spent years making the same claim. Three of the testimonials name those competitors directly: Brandon Strittmatter says “I’ve used Mailgun, Sendgrid, and Mandrill and they don’t come close to providing the quality of developer experience you get with Resend.” That sentence is the most powerful positioning statement on the page, and it’s buried in a scrolling testimonial carousel. Resend actually has a defensible wedge — React Email, the code-first template workflow that means a developer never leaves their environment to build an email — but the hero doesn’t name it, and the page treats it as one feature among nine rather than the category-defining move it is. Pull the differentiation out of the testimonials and put it in the hero: the page should open on the specific thing Resend does that SendGrid cannot, not on a category label every competitor already owns.

The page has no narrative arc — it opens with a claim and immediately lists features, which means the visitor has to do the work of understanding why any of this matters. The developer who lands here already knows email is broken; they’ve fought spam folders, wrestled with legacy SDKs, and debugged deliverability issues at 2am. None of that frustration is named on the page. The hero skips directly to “here’s what we do” without first saying “here’s the world you’re living in and why it’s costing you.” The result is that the page reads like a product spec rather than a case for switching. Add a single section above the feature grid — before the testimonials, before the code snippet — that names the specific failure state the developer came here to escape. The testimonials already contain this language: “clunky tools,” “don’t hear complaints about emails landing on spam anymore,” “not having to leave my dev environment.” Use it.

The page asks one type of visitor to act — a developer ready to integrate — but the testimonials and feature list reveal at least two distinct buyers: the individual developer building a side project or startup, and the engineering team at a scale-up migrating off SendGrid or Mailgun. These two buyers need different things from the page. The solo developer wants “working in five minutes”; the migration buyer wants “here’s how you move your existing setup without breaking production.” The page has a “Migrate” link buried in the footer, which is exactly backwards: migration is the highest-stakes objection for the scale-up buyer and it’s invisible above the fold. Add a second CTA path — not a second button, but a second sentence under the primary CTA — that speaks directly to the team already on a legacy platform: something like “Switching from SendGrid? Here’s how.” The current single-path “Get started” forces both buyers through the same door and serves neither well.

The proof section is structurally strong — fourteen named testimonials with titles and companies — but it’s doing less work than it should because none of the quotes are anchored to a specific outcome with a number. “Our deliverability improved tremendously” (Vlad Matsiiako, Infisical) is the closest the page gets to a concrete result, and “tremendously” is doing the heavy lifting where a percentage or a before/after metric would close the sale. Resend has 3 million users — there’s a blog post about it — and that number appears nowhere on the homepage. Move “3,000,000 developers trust Resend” above the testimonial carousel, and push at least two of the testimonials toward a specific outcome: open rate improvement, time-to-integration, reduction in support tickets about missed emails. Named proof with numbers converts the skeptical buyer who has already been burned by a platform that promised deliverability and didn’t deliver it.