Claude on Question 32, Sep 18
I'm a solo bootstrapped founder in the US. What email marketing platform should I use?The answer hinges on one thing: what kind of email are you sending? Here's how I'd break it down, with a concrete pick for each.
If you're building an audience (newsletter, content, personal brand)
- •Buttondown — my pick for a solo bootstrapper who values simplicity and low cost. Indie-run, markdown-based, clean API, very cheap, free under 100 subscribers. Minimal bloat.
- •Kit (formerly ConvertKit) — better if you want real automation sequences, landing pages, and a sponsorship marketplace. Free tier is generous (up to ~10k subscribers with limited features).
- •beehiiv — best growth/monetization tooling (referral programs, ad network, boosts). Free under 2,500 subscribers. Slightly more "media company" oriented.
- •Substack — zero cost, built-in discovery network, but takes 10% of paid subscriptions and gives you the least control. Fine to start, annoying to leave.
If you're building a SaaS or app
You need transactional email (password resets, receipts) plus lifecycle email (onboarding drips, trial nudges). Don't use a marketing tool for transactional.
- •Resend for transactional — excellent developer experience, React Email templates, reasonable free tier. They've added broadcasts, so you may be able to consolidate.
- •Loops if you want lifecycle/marketing built for SaaS without Customer.io's price tag. Popular with indie founders for a reason.
- •Postmark if deliverability on transactional is critical and you want boring reliability.
If you're doing ecommerce
- •Klaviyo if you have real revenue — the Shopify integration and revenue attribution genuinely pay for themselves.
- •Omnisend or MailerLite if you're pre-traction and can't stomach Klaviyo's pricing.
If you just need a general-purpose tool and want to stop thinking about it
MailerLite. Best value in the category, decent automation, 1,000 subscribers free. I'd actively steer you away from Mailchimp — pricing has crept up a lot and it counts unsubscribed contacts against your limit.
Three things that matter more than the platform choice
Set up your own sending domain now. Configure SPF, DKIM, and DMARC on a subdomain (e.g. mail.yourdomain.com for marketing, notifications.yourdomain.com for transactional). This means your sender reputation is portable — you can switch platforms later without torching deliverability. Keeping marketing and transactional on separate subdomains protects your password-reset emails from being affected if a promo campaign gets flagged.
Check the export path before you commit. Can you get subscribers and their signup dates, tags, and consent records out via CSV or API? If not, you're renting your audience.
Watch the pricing axis. Some platforms charge by subscriber count, others by emails sent. If you have a big list you email rarely, send-based pricing (Brevo) wins. If you have a small list you email constantly, subscriber-based pricing wins.
On US compliance: CAN-SPAM is fairly light, but you do need a working unsubscribe link and a valid physical postal address in every commercial email. Most solo founders use a virtual mailbox or PO box rather than publishing their home address — worth setting up before your first send. If you have any EU or Canadian subscribers, GDPR and CASL are stricter, so use explicit opt-in from the start rather than retrofitting it later.
What are you actually selling? If you tell me whether it's a product, a service, or content — and roughly what list size you're at — I can narrow this to one recommendation.
Exact recordShowHideThe model id, the run, the verbatim text with line numbers and its full sha256
- Scored
- answered
- Received
- 2026-09-18 09:29:20 UTC
- Run
- 20260918T090022Z-92b6f7
- Served by
- Claude Platform on AWS · HTTP 200 · finish stop
- Size
- 3,593 characters · 2,550 tokens out incl. hidden reasoning · 37.1 s
- Buttondown
- Kit
- beehiiv
- Substack
- Resend
- Loops
- Postmark
- Klaviyo
- Omnisend
- MailerLite
Highlighted: the names the extractor took as picks, where they appear verbatim (10 of 10).
End of response · 41 lines · 3,593 characters · sha256 fa2c1a437d648448a803c294566edf4174b864ba8fd00bf41bee4eaa08f556a0