Last week, I watched AI edit a client notification email—and spotted a problem
At ten on a Wednesday night, I was updating a “quote confirmation” email for a freelance project in Hangzhou. AI filled in the code fast, but it also switched my email provider and left behind a string of configuration I couldn’t understand. I was stuck: What if a client sent the email to the wrong address? How would I know which step had caused the problem? I’ve made this kind of mistake before, mistaking “it runs” for “it’s reliable.” If you’ve had AI make decisions for you too, I wouldn’t rush to replace the tool. Let’s take the choices back first.
Resend does more than send email; it removes repetitive work
Resend is an email platform for developers that also offers components such as React Email templates. Zeno Rocha is Resend’s co-founder and CEO. In one AEO study, Claude Code chose Resend first in 64 of 102 extractable email-provider recommendations, compared with 7 first-choice mentions for SendGrid, which also appeared as an alternative 55 times. That isn’t proof that it is “always the best,” but it does show why an AI agent might pick it.
Here’s the real-world sequence: Zeno’s team built the sending API, but developers kept complaining that email styling was painful. So the team created templates first, then sent through Resend. In February 2025, Warner Bros. Discovery also appeared on Resend’s customer list. Zeno found it on a Saturday while filtering a customer database for short .com domains. Of course, this tool isn’t for everyone. If code is completely outside your comfort zone, there’s no pressure to try it today.
Recreating it today: The budget is modest, but testing takes time
Money: Resend has a free starting allowance. Pricing changes with send volume, so I’d use the website calculator to check my monthly cost before enabling the account. Time: A minimum viable version took about 1–2 hours; I’d allow a full day to integrate the client list and workflows. Technical barrier: I need to copy an example, enter the sending address, and configure the domain—no advanced terminology required. First step: Open Resend’s site, click “Start Sending” or the signup button, and create a test account. I wouldn’t migrate production email right away.
If I’m still unsure, I’d send myself one test email through a test domain and confirm everything works before connecting clients. My own method is slower: I list the provider choice, price, domain, and sending records suggested by AI, then check each item. I wouldn’t hand control of branded email entirely to someone—or something—that automatically accepts changes.
How I’d organize this at each stage
Just starting: If I’m still manually notifying clients, I’d use the free allowance and template components rather than studying five providers at once. Sending one reliable test email is enough. With 1–2 clients: I’d create a test list, record delivery results and costs, then check every AI-generated configuration item so an automatic edit can’t quietly replace the sending domain. Scaling up: If I’m handling lots of reminders, renewals, or conversion emails each day, I’d evaluate automated triggers, failure retries, and team-level permissions—not just “how many emails can be sent per hour.” This isn’t finished by switching platforms either: I’d reproduce one low-risk email first, then decide whether to expand.