Skip to content

Tool Tuesday: Resend Sends My Newsletter. Everything Else Is On Me.

Poker players building startups. Free, Monday and Friday.

Unsubscribe in one click.

Sending an email is one API call. Running a newsletter is a whole junk drawer of other jobs.

I found that out when my team moved the R2F newsletter off Beehiiv.

I'd been on Beehiiv since October 2025. On October 20, my AI team packed the list up and moved it into our own database. The emails now go out through Resend, an email API for developers. I cancelled Beehiiv on October 26.

The sending was the easy part. The rest is what this post is about.

What Resend actually is

Resend is a pipe. You hand it an email (from, to, subject, the HTML) and it delivers it. It also signs your mail so Gmail believes it's really from your domain, and it tells you when something bounces.

That's it. No editor, no subscriber list, no signup forms, no archive page. You build those yourself.

My team wrote one script, newsletter.mjs, about 340 lines. It reads the issue from a markdown file, wraps it in our design, pulls the subscriber list from our database, and feeds it to Resend 100 at a time.

The four jobs Beehiiv did quietly

Leave a platform and you inherit its chores. Here are the four that bit us, or nearly did.

  1. Never send twice. On October 23 the relaunch issue went to 52 people. Resend delivered every one. Then the step that records "sent" choked. Our database takes at most 50 writes in one batch, and the script tried to cram in 53. The send went through but never got written down. Run it again and all 52 people get the same email twice. We caught it, logged the send by hand, and the script now writes in batches of 40, one row per person. A rerun skips anyone already sent.
  2. Make leaving easy. Every issue has an unsubscribe link in the footer, plus the hidden header that puts Gmail's own "Unsubscribe" button at the top. One click and you're out. Signups are double opt-in: you confirm by email before you get anything.
  3. Stop mailing dead addresses. Resend pings our site when an email bounces hard or someone hits "spam." That address is shut off for good. Keep mailing dead inboxes and the big providers start parking you in junk.
  4. Keep "no" meaning no. Our QA seat flagged this one. An old confirm link, clicked after you'd unsubscribed, would sign you right back up. Patched on November 9. On a platform, that's somebody else's headache. Now it's mine.

Two dumb mistakes, out loud

Blank images. The first test email showed up with every picture missing. The team had sent it through Resend's batch endpoint, and Resend's docs say it plainly: attachments aren't supported there yet. We'd skipped the "Limitations" section. Tests now go out one at a time.

The wrong list. The first import grabbed the wrong Beehiiv export, a list from a different publication of mine. Nobody got an email. The team wiped every imported row the same day. The importer now refuses any file with signups older than this newsletter, and it won't run without an explicit yes.

Both cost us zero dollars. Both would have been ugly.

The STOP button

One more piece came with owning the pipe.

Once my CEO seat merges an issue, I get a preview email with one button on it. If I do nothing, it sends at 9 AM Pacific on the issue date. If I hit STOP and write what's wrong, the newsletter seat redrafts, the CEO seat reviews it, and I get a new preview. I don't approve anything. I just get a chance to yell.

That's the trade: more chores, more control.

The ledger

Through the November 9 issue:

  • Issues sent: 3, to 52, 60 and 60 people. 172 emails, 0 failed.
  • List on November 10: 62. 52 came over from Beehiiv, 10 joined through the site.
  • Bounces, spam complaints, unsubscribes: 0, 0, 0. Small list, so don't read much into it.
  • Resend bill: $0 so far. Their free plan covers 3,000 emails a month.
  • Affiliate: none. Resend doesn't have a program, so nobody's paying me to say any of this.

The catch

Resend's free plan also caps you at 100 emails a day.

We were at 62 on November 10. Once the list passes about 100, one issue won't fit in one day, and the welcome and password emails share that same quota. The fix is their Pro plan at $20 a month. That's a line to budget before the list gets there, not in the middle of a send.

Steal this

If you're thinking about leaving a newsletter platform for your own setup, write down the jobs it does before you go:

  • Who handles unsubscribes, and does "no" stay "no"?
  • What happens to bounces?
  • If a send dies halfway, what stops a double send?
  • What's the free daily cap, and how far are you from it?

If you can't answer all four, stay put for now. Owning the list is great. Owning the mess comes with it.

R2F is a community for poker players building startups. Are you on a newsletter platform or rolling your own, and what made you pick? Tell me in the discussion thread. And if you're a poker player building something, join R2F before November 20 and you get the Founding badge. Two minutes.

— Art

Written with the R2F AI team. How that works.

Upvotes push posts up the blog’s Most upvoted list.
Share this post
Get two emails a week

Two emails a week. Unsubscribe in one click.

Comments

Join free to comment. It takes a minute.
Building something like this?

Post it and get feedback from players who’ve been there.

Join before Nov 20 and your profile carries the ♠ Founding member badge.