What we had
Until two weeks ago, the newsletter widget on this site was wired to a Buttondown placeholder, ready for a "BUTTONDOWN_HANDLE" string-swap before launch. The plan: ship the site, finalise the provider, hook up the form, watch a list grow.
We never finished hooking up the provider. Then we noticed the site was lighter, faster, and easier to reason about without the hookup. Then we ripped out the placeholder entirely.
What replaced it
The "subscribe" component on every page now renders two buttons:
- Subscribe via RSS →
/feed.xml - Email to join →
mailto:hello@pintoedai.comwith a prefilled subject and body
That's the whole subscribe flow. Twenty lines of JS in
enhancements.js. No accounts, no tracking pixel, no
double opt-in dance, no inbox heat-up nonsense, no monthly bill,
no DPA to sign.
Why this is fine
Five things we'd been told mattered, that turn out not to:
- "You need a list." Everyone with an opinion on creator-economy mechanics says this. For a B2B consulting studio whose core distribution is search and word of mouth, the list is a tertiary asset, not a primary one. We checked.
- "RSS is dead." Empirically false. Our analytics show steady RSS reads from the existing feed. The "RSS is dead" cohort confused "consumer aggregators consolidated" with "the protocol stopped working." It didn't.
- "You need analytics on opens and clicks." We don't, actually. We need to know if engagements close. The newsletter funnel was never going to tell us that.
- "You need a sender reputation." Only if you're sending mass mail from your domain. We're not. The mailto-driven "send me when you publish" arrangement is one-to-one.
- "You need to capture email addresses." For what? We're not retargeting. The contact form already captures the people we want to talk to. The blog drives them to the contact form. Layering an email capture in the middle was friction without function.
What we measured before deciding
Before pulling the trigger we quickly mapped the costs and benefits of each path. The honest version:
- SaaS path: ~$30–60/mo at our scale (Buttondown class), 2–4 hours of setup time, indefinite maintenance burden, ongoing questions like "did the welcome email get the right link" forever.
- RSS + mailto path: $0/mo, 1 hour of work, no maintenance.
The benefit side: SaaS gives you opens, clicks, segmentation, scheduled sends, automation. We don't need any of those. The blog post is the artifact. The RSS feed broadcasts it. The mailto handles the small set of readers who want a one-to-one ping.
What we'd do differently if we did need a list
For the audience that says "but I really do need a list," our take is: most of you don't until you have product-led monetization, lead-magnet-driven SaaS, or a content-business revenue model. If you're a consulting studio, an agency, a contractor, an indie service-provider — your list is your contact form, and it always has been.
If you do need one (course business, info-product, newsletter monetisation), pick from the reviews we've published — Beehiiv, Kit, Klaviyo depending on the shape. None of them is the right tool for "I write 1-2 blog posts a month and want them to reach interested readers."
The brand-voice argument
The site says "AI automation that actually ships. No demos, no decks." Carrying around a SaaS subscription for "growing a list" we hadn't proven we needed was the marketing equivalent of the bloat we make fun of in client briefs. Removing it was alignment between what the site says and what it does.
We give clients the same advice constantly: don't add the subsystem until you have evidence you need it. We were doing the thing we'd told clients not to do.
The two-line summary
RSS still works. Email still works. Most B2B blogs do not need a SaaS in between. If your business model depends on a list, this advice doesn't apply. If it doesn't — and it probably doesn't — kill the SaaS, ship the feed, get back to writing.