The list was the last thing I moved
MailerLite has an Export button that hands you your whole list as a spreadsheet. I'd been paying them for a year and never once clicked it. The morning I finally did, I understood exactly what I'd been renting.
The file that came down was every reader who had ever raised a hand. Names, addresses, the date each one decided I was worth hearing from again. That spreadsheet is the actual asset of a writing business. Not the books. The permission to show up in someone's inbox and have them glad you did. And it had been living in a building I didn't own, under terms I didn't write, one pricing change or policy shift from becoming leverage against me.
Everything else on the platform, if I broke it, I lost a feature. Break email, and I lose the list. So email was the last thing I moved, and the thing I moved most carefully.
What the middleman was actually doing
I want to be fair to MailerLite, because the fear was real and specific.
An email service isn't just a "send" button. It's a small mountain of unglamorous work you never see. Keeping your mail out of spam folders. Handling the addresses that bounce. Honoring unsubscribes instantly so you stay legal. Guarding a "sending reputation" that, once wrecked, sends every future email straight to junk. That reputation is invisible and it's everything. It's the difference between a newsletter that lands and a newsletter that vanishes.
Roll your own email and you inherit all of that. Get it wrong and you don't get an error message. You get silence, which is worse, because you can't tell the difference between "nobody cared" and "nobody received it."
So I didn't try to be a hero about it. I don't run mail servers. I send through Resend, a delivery service that handles the raw physics of getting a message into an inbox. The split is the whole point: they own the pipes, I own the list, the content, the templates, the automations, and the data. If Resend ever annoys me, I change one setting and send through someone else. My readers come with me. That's the difference between a tool and a landlord.
Building the newsletter I own
With delivery outsourced and everything else mine, I built the part that actually carries my voice.
The composer lives in my own admin now. I write an issue, pick who gets it, and a live counter tells me exactly how many people that is before I send. Audience targeting runs on checkboxes: just the free subscribers, or members too, or the patrons on top of that. I can schedule a send for the last Thursday of the month and walk away. Each site signs its own mail, so a dispatch from the Integration Era world arrives as the System talking, and a Charlie Forêt issue arrives as me, from my domain, in my colors.
When a send actually fires, it doesn't run inside the website. It hands the job to a background worker, Oban, that grinds through the list on its own time. This matters more than it sounds. Publishing a chapter can kick off a thousand emails at once, and the reader clicking around the site while that happens should never feel it. The site stays quick; the mail goes out behind the curtain.
There's a security tax on all this that I paid on purpose. Every new signup has to confirm from their own inbox before they're real, which keeps bots and typo'd addresses off my reputation. Changing your account email takes a click in both the old inbox and the new one. And the confirmation emails are rate-limited per address, so nobody can weaponize my own "please confirm" mail to flood a stranger. Boring work. The kind you only notice when it's missing.
Moving it without losing it
The migration itself came down to two buttons, and I care about both of them equally.
The first is import. I built CSV subscriber import so I could carry my existing list in from MailerLite without anyone noticing a thing, no re-confirmation, no "hey, resubscribe please" email that quietly kills a third of your list. They were already mine. The system just needed to agree.
The second is export, and it's the one that matters more. My admin has a subscribers page with search, filters, and a plain "export" button that hands me the same kind of spreadsheet MailerLite once guarded. I built the exit on purpose. A list you can't leave with isn't a list you own, it's a list you're allowed to use. Mine walks out the door with me whenever I say so, including out the door away from my own software. If owning the reader is the whole thesis of this project, the export button is where I prove I mean it.
The magnet goes inside the story
Here's the payoff, and it's the thing the old stack could never do cleanly.
The audit of my own sites turned up an obvious hole: my newsletter asked people to sign up for "just the updates, no noise." Nobody trades their email for the privilege of updates. You trade it for something. A free novella, an early chapter, a map, a quiz result. A reason.
So rewards are built into the page itself now. Anywhere in a post, I can drop a small tag,
, and it renders as a real offer: leave your email, confirm it from your inbox, and the file lands a moment later, delivered straight from my own storage. The signup and the gift and the writing all live in one place, wired together, instead of scattered across a form tool and a file host and a hope. I can preview the exact email the reader will get and send myself a test before a single stranger sees it.
That's the machine that used to be four services and a prayer. Now it's a tag in a paragraph.
If you want to see it work instead of reading about it, there's a reward waiting at the bottom of this one. Leave an address, confirm it, and something I made shows up in your inbox. That whole path, the part where the email actually arrives, is the part I was most afraid of. It works. Go break it.
Follow the build: Workshop posts land weekly. Next up, the part where I stopped letting a retailer keep my customers and started selling books direct. The reward below is real, and so is the list you'll be joining, the one you can walk out of anytime, spreadsheet in hand.
