Email & CRMResend review
Email built for developers: the sending layer behind receipts, password resets, and the mail your product has to deliver.
Is Resend right for you?
Resend does a different job from everything else on this shelf. The other tools own your list and run your marketing. Resend owns the email your product has to send (the receipt after a purchase, the password reset, the notification that something needs attention) and makes sure it arrives.
It was built by developers, and it behaves like it (a compliment): a clean API, sensible domain and authentication setup, and clear visibility into what was sent and what landed. It’s designed for someone wiring it into an application, not clicking through a dashboard, so integrating it is pleasant instead of a half-day of documentation.
The distinction matters because transactional email is where deliverability quietly goes wrong: mail that must reach an inbox has different requirements from a newsletter, and a marketing platform tends to fight you on it. Resend is built for the job, which is why it’s the email layer in the lean stack we recommend. It does that one job properly, then leaves you alone. The free tier covers a single project, and you start paying once your product is being used, which is the right time.
The flip side: it deliberately isn’t a marketing platform. There’s no campaign builder, no automation canvas, no contact management. To nurture a list, buy one of the tools further up this shelf. For application email that’s reliable and out of your way, reach for this one. Running both is a normal setup.
Questions about Resend
What people usually want to know before committing, answered the way we'd answer them on a call.
Can I send a newsletter with Resend?
Not in any way you'd enjoy. There's no campaign builder, no automation canvas, and no real subscriber management. It's a sending API, and that's a deliberate design choice, not a gap. To write something and send it to a list, buy one of the marketing platforms on this shelf. Resend for your product's email plus a separate marketing tool is a normal setup, not a compromise.
Why is Resend in your lean stack?
Because a custom-built system still has to send email, and this is the least painful way we've found to do it. Built by developers for developers, it has a clean API and sensible domain and authentication setup, then gets out of the way. When a build is about fewer moving parts, an email layer that does one job properly and asks nothing else of you is exactly right.
Read about the lean stackIs the free tier enough to start on?
For a single project, comfortably. It's a real plan, not a trial, so it's easy to reach for early. The limits are on volume and on how many domains and projects you run, so you move to a paid plan when your product gets used or a second build arrives. That's the right way for a cost to grow: only when something is working.
Should I just use my marketing platform to send transactional email?
You can, and it's where deliverability quietly goes wrong. Mail that must reach an inbox (a receipt, a password reset) has different requirements from a newsletter, and marketing platforms are built and reputation-scored around newsletters. Route that mail through them and you'll usually fight the tool and get worse delivery on the messages you can least afford to lose. Separating the two is cheap insurance.
Still deciding?
Not sure if Resend is the right call?
The tool is rarely the hard part; fitting it to what you've already got is. Five minutes with the concierge: honest fit, no pressure, and a real person follows up.
More Email & CRM
The rest of this shelf, if you're weighing your options.
Kit
ActiveCampaign
HubSpot
Keap
OntraportDisclosure: there's no affiliate link on this page. We don't earn anything if you sign up for Resend; it's here because it's good. Other tools in the toolkit do carry affiliate links, and each of those pages says so.