Part IV · Applying it · Chapter 15 · 5 min read
Product X: Buttondown in WordPress
What a Buttondown-style newsletter needs, what WordPress already gives you free, and who you can sell it to first.
Three products in one#
Buttondown looks simple, but it's really three products. WordPress already gives you about 40% of it free. The part WordPress can't do, sending email at scale and landing in the inbox, is also the part people pay for.
1. Writing and publishing: WordPress mostly has this#
| Buttondown | In WordPress | Work for X |
|---|---|---|
| Editor (Markdown or visual) | Gutenberg | Small: an email-safe block set |
| Drafts, scheduling | Built in | None |
| Email preview, test send | — | Build |
| Email templates, custom CSS | — | Build. Blocks → email HTML that works in Gmail and Outlook is real work |
| Web archive | Posts are pages | Free, WordPress's big advantage |
| Custom domain, SEO, RSS, comments | Built in | Free |
| Premium-only posts | — | Build, or reuse the membership engine |
2. Audience and money: you build this#
| Buttondown | Work for X |
|---|---|
| Subscriber list | Custom table, not wp_users; it must scale to 50k rows with metadata |
| Statuses: active, unconfirmed, unsubscribed, bounced, spam, paid, gifted, churned | Build the state machine |
| Double opt-in, tags, custom fields | Build |
| Segments ("tag = X and paid = true") | Build. "Marketing = SQL query", taken literally |
| CSV import/export + importers from Substack, Mailchimp, beehiiv | Build. This is how people switch to you |
| Subscribe forms: block, embed, popup | Build |
| Subscriber portal | Build |
| Paid subscriptions via Stripe | Big. Reuse the membership engine |
| Automations: welcome, drip, triggers | Build (Action Scheduler) |
| RSS-to-email | Easy: hook on publish |
| Analytics: opens, clicks, growth | Build, privacy-first |
| API, webhooks | WP REST API gives the skeleton |
3. Delivery: WordPress can't do this at all#
| Buttondown | The reality |
|---|---|
| Sends 10k–100k emails reliably | wp_mail() on shared hosting gets people banned. You need a sending service (SES, Postmark, Mailgun) |
| Custom sending domain (SPF, DKIM, DMARC) | Build a setup wizard that checks DNS |
| Bounce and complaint handling | Webhook receivers from the sending service |
| One-click unsubscribe headers (Gmail/Yahoo 2024 rules) | Required, or you land in spam |
| Queue and throttling | WP-Cron is unreliable; you need a real queue plus rate limits |
| Scale | 50k subscribers per send must not time out on a $5 host |
The business model is decided by delivery#
- A. Bring your own sending service. The user pastes an SES/Postmark key; you sell a yearly license. Cheap to run, but setup is hard for writers and churn is high.
- B. X Cloud sends for them. Free plugin; sending billed per subscriber per month, like Buttondown and beehiiv. Revenue grows with their list, not once per sale.
Pick B, maybe with A as a free "advanced" option. B is where the money is, and it's what "Buttondown in WordPress" actually means.
Competitors to study#
- Jetpack Newsletter (Automattic): free, Substack-like, most distribution. You can't beat it on price.
- MailPoet (Automattic): mass-market, feels like 2015.
- Newsletter Glue: closest to the idea (Gutenberg-based, "Substack in WP"). Study it closely.
- FluentCRM: a marketing CRM, not built for writers.
The opening: a tool for writers and small newsrooms, not marketers. Buttondown's taste (clean, Markdown, privacy-first) plus owning your archive and domain.
Smallest version that earns the first dollar#
- Subscriber table, subscribe block, double opt-in, CSV import (including Substack).
- Send a post as an email, with one template that works in Gmail and Outlook.
- Sending through one service, with bounces and unsubscribes done right.
- A basic open/click count.
Later (v2): Stripe paid subscriptions, automations, segments, surveys, teams. Paid subscriptions merge into the membership engine.
Who you can sell it to: queryable segments, easiest first#
| # | Segment | How to find them | Pitch | Ease |
|---|---|---|---|---|
| 1 | Past theme customers you can email | direct-sale and support lists | "Add a newsletter to the publication you already run, in 10 minutes." | 5 |
| 2 | Current free-theme users (~220 sites) | theme dashboard, docs, site | "Built to work with your theme." | 4.5 |
| 3 | WordPress sites already using Mailchimp / Kit / Substack forms | technology lookup (BuiltWith, Wappalyzer) or a crawler: WHERE cms = 'WordPress' AND newsletter = 'Mailchimp' |
"Stop paying per subscriber for a second platform." | 4 |
| 4 | Substack leavers | public "leaving Substack" posts | "Keep 100% of your revenue, own your site." | 3.5 |
| 5 | Unhappy users of rival plugins | 1–3 star reviews, unanswered forum threads | "The simple one." Plus comparison pages | 3.5 |
| 6 | WordPress and newsletter communities | groups, subreddits, Post Status | help first, mention X when it fits | 3 |
| 7 | Lifetime-deal marketplaces | apply to list | "Lifetime deal" | 3 |
| 8 | wp.org plugin search | publish the free version | — | 2.5 |
| 9 | WordPress YouTubers and bloggers | sponsorships, affiliates | reviews, tutorials | 2.5 |
| 10 | Agencies building sites for writers | directories, communities | "Recommend X to clients" | 2 |
| 11 | SEO / AI search | comparison and alternative pages | — | 2 |
| 12 | Paid ads | "substack alternative wordpress" | — | 1.5 |
| 13 | Writers not on WordPress yet | — | adopt WordPress and X | 1 |
When to use which:
- First 10 paying customers (weeks 1–8): #1, #3, #4, #5. Warm or precise pain, free to reach. #3 is the hidden weapon: a list of people with the exact problem, found by querying their technology.
- Months 2–6, start snowballs: #6, #8, #11.
- Once proven: #9, #10. Pay to amplify only after you know it converts.
- Skip for now: #12, #13.
You don't need to build an audience before you sell. You build it while selling: turn every rented contact into an owned one (an email, an account, a spot in the umbrella's publisher newsletter). And X has a small built-in loop: a "Sent with X" footer on every newsletter.
Cold outreach, done right
Keep it personal, small and relevant. Mention something you noticed about their site, send a handful a day, and follow CAN-SPAM, plus GDPR for people in the EU. Twenty thoughtful emails beat 2,000 blasts, for results and for the brand.
First step this week
Count how many past customers you can actually email (#1). Run one technology lookup for #3 to see how big that list is. Those two numbers tell you how fast your first 10 customers can come.
Takeaways
- WordPress gives you the writing and the archive. Build the audience layer and the delivery layer.
- Delivery decides the business model. Hosted sending = revenue that grows with the customer's list.
- Ship the smallest version someone pays for; merge paid tiers into the shared engine later.
- First customers come from warm lists and precise queries, not from search.