SMF·BEEHIIV
Can a prompt replace beehiiv?
Newsletters & publishing — newsletter platform
Exhibit tracking slip
Verdict
Writing posts, storing subscribers, and sending campaigns through an email API is a real multi-day build. What doesn't come with it is beehiiv's actual product: inbox deliverability tuned by someone else's sending reputation, and a cross-publication recommendation network that grows a list without buying ads.
Exhibit A — The prompt
Received on30.07.2026Build a personal newsletter sender: posts written in Markdown, a subscriber list in a database with a public sign-up form that requires double opt-in (a confirmation link by email before anyone is actually added), and an admin view to write, preview, and send a campaign to the full list or to a tag. Send through a transactional email API (Resend, Postmark, or similar) rather than raw SMTP, and record a sent/failed status per recipient so an interrupted send can resume without emailing anyone twice. Every email must carry a working one-click unsubscribe link and the List-Unsubscribe header — that's a legal requirement, not a nice-to-have, and it should be impossible to send a campaign without it. Publish a plain web archive of past posts, and support CSV import and export of the subscriber list so someone can move in or out in one file.
Do not build open/click analytics beyond a basic send count, a recommendation network, or paid subscriptions — those are the actual product beehiiv sells. In the README, say plainly that a new sending domain needs to warm up gradually or the mail lands in spam; that reputation-building, more than any code here, is what the subscription fee buys.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 inbox deliverability tuned by someone else's sending reputation
- B.2 the cross-newsletter recommendation network that brings in new subscribers
- B.3 the built-in ad marketplace
- B.4 automations beyond a single welcome email
- B.5 one-click migration tooling
Prior art
Exhibit C — Why people still pay: deliverability/network/monetization
Writing and sending an email is the easy part. Reaching the inbox reliably, and growing the list without buying ads yourself, is what beehiiv's infrastructure and network actually do.
Questions
Can I import my existing subscriber list?
Yes — the build supports CSV import and export, so your list travels with you either direction. What doesn't transfer is your sender reputation; a new sending domain starts from zero no matter how many subscribers you bring.
Will it work on my phone?
The admin view is a plain web page, usable on a phone for a quick send, but there's no dedicated app, no push notifications, and no mobile-optimized composer.
What does it cost to run?
Hosting plus a domain, plus a transactional email API — most of those have a free tier that covers a small list, growing to a few dollars a month as your list does.
What's the one thing that doesn't survive the rebuild?
Growth that isn't your own doing. beehiiv's cross-newsletter recommendation network sends other publications' readers your way automatically; a self-hosted sender only ever reaches people who already found you.
Related tools
Receipt