Activation teardown

Resend

Email API for developers · resend.com
Observed 20 Nov 2026
Public pages and docs, no account created
By Subomi Olagoke

A first test email takes a few documented steps. Sending to real recipients waits on DNS verification, which the docs say can take up to 72 hours.

What this covers. Observed from public pages, the rendered sign-up page and the documentation on 20 Nov 2026. No account was created, so in-product screens are described from the company's own docs, and onboarding emails were not seen.

Sign-up path

  1. Homepage: 'Get started'Observed1
    One click from the header or hero to /signup.
  2. Form: 'Create a Resend account'Observed3
    'Log in with Google', 'Log in with GitHub', or Email and Password (12+ characters, mixed letters, numbers, symbols). Button: 'Create account'.
  3. Create an API keyFrom docs5
    Name the key, choose Sending access or Full access. The key can be viewed only once.
  4. Send a test emailFrom docs8
    Quickstart sends from onboarding@resend.dev. The test domain only delivers to the account's own email address.
  5. Add a domainFrom docs7
    Domains page, Add Domain, choose a region, then copy DKIM and SPF records to the DNS provider.
  6. Wait for DNS verificationFrom docs7
    Often within 15 minutes of adding the records, occasionally up to 72 hours, with a Restart verification button after that.

Where a new user could stall

DNS verification can stall the first real send7High

Sending to anyone else needs a verified domain. Docs say verification is often 15 minutes but can take up to 72 hours, and needs DNS access.

Fix. Email accounts whose domain is still Pending after 24 hours, with their DNS provider's guide and a link to share the records with whoever owns DNS.

The first send to a colleague can return a 4038Medium

The quickstart sender onboarding@resend.dev only delivers to the account's own address. Other recipients get a 403 with a verify-a-domain message.

Fix. When an account gets its first 403 of this kind, show a dashboard banner and send an email that opens straight to Add Domain.

The docs introduction leads with the slower step4Medium

The introduction lists 'Your own domain, verified with Resend' first, before the API key, although the quickstart can send a test without a domain.

Fix. Reorder the introduction so a test email to yourself comes first and domain verification second, putting the first win before the DNS wait.

Sign-up buttons say 'Log in'3Low

The 'Create a Resend account' page labels its social buttons 'Log in with Google' and 'Log in with GitHub'.

Fix. Label them 'Sign up with Google' and 'Sign up with GitHub' on the sign-up page, and compare completion against the current copy.

Trial terms

Offer

Free forever plan, no trial: 3,000 emails a month, 100 a day. Pro from $20/month2
Not stated on the pricing page. The FAQ says there is no free trial, but a free forever plan.

Time to first value

First value

First email to a real recipient from your own domain
About 4 steps to a test email to yourself. Then 8 domain steps plus the DNS wait to reach customers, per the quickstart and the domain guide6

First run

Empty states and setup

Not observed
Docs do not describe a first-run screen. An added domain shows as Pending until DNS verifies, and free accounts get production access with no approval step.9

Onboarding emails

Not observed
No account was created, so no emails were seen, and the docs do not describe Resend's own onboarding emails.

What already works

  • Google and GitHub sign-up, the accounts developers already use
  • Production access from day one, no sandbox approval
  • 13 framework and language quickstarts, plus a CLI quickstart

How a sprint would measure it

Share of new accounts with a verified domain within 72 hours of sign-up, 20% holdout.

~8%
median B2B free-to-paid conversion within 6 months
ChartMogul SaaS Conversion Report
Day 7
where most trial conversions cluster
ChartMogul SaaS GTM Report
37.5%
average SaaS activation rate (product-led: 34.6%)
Userpilot activation benchmark