Newsletter audience guide
14 Newsletter Audience-Building Tools Compared: What to Pilot First
A practical, evidence-safe comparison of newsletter platforms for acquisition, referrals, publishing, segmentation, and retention. The right tool is the one that makes permission, source quality, retention, and publishing effort visible.
Short answer
Choose the smallest platform that can capture consent, identify acquisition source, deliver a useful welcome experience, and export what you need. Do not treat subscriber count as success: compare confirmed signups, early clicks, complaints, unsubscribes, and second-issue retention.
Quick comparison
| Audience job | Tools to shortlist | Validate before buying |
|---|---|---|
| Editorial publishing | Substack, Ghost, Buttondown | Ownership, archive, export, paid-subscription terms |
| Creator growth | beehiiv, Kit, MailerLite | Forms, referral mechanics, automation, source tracking |
| General marketing | Mailchimp, Brevo, Campaign Monitor, Constant Contact | Contact economics, templates, integrations, reporting |
| Lifecycle and commerce | HubSpot, Customer.io, Klaviyo, Omnisend | Event model, consent, suppression, data and channel costs |
Audience growth is a system, not a popup. A useful test connects the promise on the signup page to the welcome email, the first issue, and a measurable next action. Keep acquisition claims modest: a tool can provide forms, referrals, recommendations, or automation, but it cannot guarantee qualified subscribers or inbox placement. Check each vendor's current documentation for the exact feature and limit.
Pricing is similarly easy to misread. A platform may charge by contacts, sends, events, messages, seats, channels, or a combination. Free plans can exclude automation, custom domains, support, exports, or high-volume sending. The figures below are intentionally caveated because plan names and limits change; use the linked official site as the source of truth and calculate the cost of your expected list size after inactive-contact policy.
14 tools worth piloting
beehiiv: best for Publication teams testing recommendations and referrals
What it is: beehiiv is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For publication teams testing recommendations and referrals, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: The pricing page lists a free plan up to 2,500 subscribers, then Lite at $49 and Pro at $95 with yearly billing; network and referral terms sit on the same page. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Publish two issues, tag each acquisition source, and compare confirmed-subscriber retention. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Publication-oriented workflow with growth features to investigate. | Growth features may not matter if your acquisition is mostly owned channels. | Can your team prove source, permission, and retention in one test? |
Substack: best for Writers who want a hosted publishing and subscription experience
What it is: Substack is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For writers who want a hosted publishing and subscription experience, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Check current fee and payment terms; paid subscriptions introduce platform and payment economics. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Run one free series and one paid-interest test; export consent and source data before scaling. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Low setup burden for publishing and reader subscriptions. | Less control over a bespoke acquisition, data, or automation stack. | Can your team prove source, permission, and retention in one test? |
Ghost: best for Publishers wanting site, membership, and newsletter ownership
What it is: Ghost is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For publishers wanting site, membership, and newsletter ownership, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Plans vary by hosting and member volume; confirm included sends, staff seats, and migration support. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Launch a landing page and welcome sequence, then test signup, confirmation, unsubscribe, and export paths. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Strong ownership of publication, member, and content surfaces. | You may own more configuration and operational work than on a hosted network. | Can your team prove source, permission, and retention in one test? |
Kit: best for Creators building forms, sequences, and subscriber automations
What it is: Kit is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For creators building forms, sequences, and subscriber automations, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Check current subscriber tiers and automation or transaction limits; pricing can change as your list grows. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Use one lead magnet with a three-email sequence and measure confirmed signup to second-email click. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Creator-focused forms, sequences, and audience organization. | Advanced commerce or enterprise requirements may need other systems. | Can your team prove source, permission, and retention in one test? |
MailerLite: best for Small teams that need a simple newsletter funnel
What it is: MailerLite is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For small teams that need a simple newsletter funnel, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Verify subscriber, email, template, and automation limits on the current plan page. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Create two source-specific forms, send one issue, and check group membership, suppression, and exports. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Accessible editor and straightforward signup workflow. | Complex event models and large-team governance deserve careful testing. | Can your team prove source, permission, and retention in one test? |
Mailchimp: best for Generalist marketing teams with existing integrations
What it is: Mailchimp is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For generalist marketing teams with existing integrations, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Contact-based pricing and feature gates require a forecast at your target list size. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Connect one source, send a segmented campaign, and reconcile contacts, unsubscribes, and click tracking. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Broad ecosystem and familiar campaign production. | The cheapest-looking tier may not include the automation or reporting you need. | Can your team prove source, permission, and retention in one test? |
Brevo: best for Teams comparing email, automation, and other channels
What it is: Brevo is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For teams comparing email, automation, and other channels, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Check whether the current plan is based on sends, contacts, channels, or add-ons. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Test an email-only welcome path and document consent, suppression, and transactional separation. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Can cover several communication workflows in one account. | Cross-channel consent and cost forecasting need explicit ownership. | Can your team prove source, permission, and retention in one test? |
Buttondown: best for Lean editorial newsletters with a Markdown-friendly workflow
What it is: Buttondown is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For lean editorial newsletters with a markdown-friendly workflow, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Confirm current subscriber, send, API, and team limits; do not assume a free tier covers production needs. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Import only consented contacts, publish two issues, and validate unsubscribe and archive behavior. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Focused publishing workflow with relatively little surface area. | You may need external tooling for richer acquisition, commerce, or behavioral journeys. | Can your team prove source, permission, and retention in one test? |
Campaign Monitor: best for Teams prioritizing polished campaign production
What it is: Campaign Monitor is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For teams prioritizing polished campaign production, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Verify list-size, send-volume, automation, and transactional add-on pricing. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Build one reusable template, test mobile rendering, and compare source-level clicks and unsubscribes. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Strong presentation and campaign workflow for branded newsletters. | Cost can rise with both audience size and required functionality. | Can your team prove source, permission, and retention in one test? |
Constant Contact: best for Small organizations that value guided campaign setup
What it is: Constant Contact is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For small organizations that value guided campaign setup, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Current plans, contact bands, and add-ons should be checked before budgeting. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Run an event or announcement campaign and verify signup permissions, exports, and follow-up ownership. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Accessible campaign workflow and support-oriented positioning. | Technical teams may want deeper event and data controls. | Can your team prove source, permission, and retention in one test? |
HubSpot: best for B2B teams tying newsletter growth to CRM lifecycle stages
What it is: HubSpot is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For b2b teams tying newsletter growth to crm lifecycle stages, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Marketing features, contacts, seats, and automation can materially change total cost; request a current quote when needed. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Capture one source, enroll only eligible contacts, and verify lifecycle-stage changes stop the right emails. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Subscriber source and sales context can live in one CRM model. | It can be disproportionate for a publication that only needs sending and forms. | Can your team prove source, permission, and retention in one test? |
Customer.io: best for Product-led teams using events to personalize newsletters
What it is: Customer.io is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For product-led teams using events to personalize newsletters, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Check current people, event, message, and data-retention limits; model usage from real event volume. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Trigger one content path from a documented event, include a control group, and test exit conditions. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Useful event and identity primitives for behavior-aware messaging. | A clean event taxonomy and consent governance are prerequisites. | Can your team prove source, permission, and retention in one test? |
Klaviyo: best for Commerce brands growing through purchase-aware email
What it is: Klaviyo is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For commerce brands growing through purchase-aware email, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Confirm profile, email, SMS, and add-on pricing separately; commerce data can expand billable volume. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Run one welcome flow with a purchase-based branch and check consent across email and SMS. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Rich commerce segmentation can make acquisition-to-repeat-purchase measurement concrete. | Its breadth may be unnecessary for a non-commerce editorial list. | Can your team prove source, permission, and retention in one test? |
Omnisend: best for Online stores coordinating email and SMS acquisition
What it is: Omnisend is worth testing when its acquisition and publishing model matches the way your audience discovers and uses the newsletter. For online stores coordinating email and sms acquisition, start with one promise, one source-tagging scheme, and one welcome path. Review the official product documentation before relying on a named feature, because availability can vary by plan, region, or account type.
Pricing and implementation: Check current contact, send, SMS, and feature limits; channel costs should be forecast separately. Budget for migration, templates, domain setup, verification, data cleanup, and any external form, analytics, or referral service. The best pilot is not a full migration: Test email-only acquisition first, then add SMS only for an explicitly consented cohort. Record the work required to maintain consent, suppression, exports, and reporting alongside the performance result.
| Pros | Cons / watch-outs | Best-for check |
|---|---|---|
| Retail-oriented workflow for coordinated channel campaigns. | Email-only publishers may pay for capabilities they do not use. | Can your team prove source, permission, and retention in one test? |
Implementation pilot: four weeks of evidence
Run the same narrow pilot on any shortlisted tool. Use a consented test segment, a real-but-limited signup source, and the template you expect to keep. Avoid buying a list or using a high-pressure acquisition mechanic: those shortcuts can inflate the top-line number while damaging trust and deliverability.
| Stage | Test | Evidence to keep |
|---|---|---|
| Acquire | Two source-specific forms or landing pages | Confirmed signup rate and source attribution |
| Welcome | One short sequence with a clear preference or exit rule | Second-email click, unsubscribes, complaints |
| Publish | Two issues using the intended template and segment | Delivered, clicked, retained, and exportable subscribers |
| Decide | Compare quality, cost, and operational effort | Retained subscriber cost, not raw list growth |
At the end, choose the tool that produces useful subscribers with acceptable operational effort and a cost you can forecast. If two tools perform similarly, prefer the one with clearer exports, simpler suppression handling, and less lock-in. Read the site's newsletter best practices, deliverability guide, and email-tool selection guide before expanding the test.
Decision snapshot: who is this tool for?
A newsletter owner usually chooses a platform for one of three reasons: the free ceiling that fits the first thousand subscribers, whether readers will ever pay, or how much of the site and member system the writer wants to own. The table maps six audience situations onto the platforms in this guide, with the plan limits taken from each vendor's own pricing page, linked in the answers further down.
| Situation | Better fit | Why |
|---|---|---|
| Writer launching a free weekly issue with fewer than 2,500 readers | beehiiv | The free plan covers up to 2,500 subscribers with unlimited sends, one publication and one team seat |
| Creator who wants lead-magnet forms and tags before paying anything | Kit | Free to 10,000 subscribers with unlimited forms and broadcasts; sequences begin on Creator, listed at $33 a month billed yearly |
| Technical writer with about 100 subscribers who drafts in markdown | Buttondown | Nothing to pay for the first 100 subscribers, including a custom sending domain and hosted archive |
| Writer who may charge readers within the first year | Substack or Ghost | Substack keeps 10% of revenue plus card fees; Ghost Publisher is $29 a month billed yearly and adds paid subscriptions |
| Small shop owner collecting readers on a simple site | MailerLite | Free plan allows 250 subscribers and 2,500 emails a month, enough for a weekly issue at that size |
| B2B publication that must pass leads to a sales team | HubSpot | Subscriber source and lifecycle stage sit on the same CRM record as the sales owner |
Reader FAQ
Can a newsletter platform promise that new subscribers reach the inbox?
No. Gmail and Yahoo apply their own rules to every sender. Google's sender guidelines ask you to send only to people who opted in, to confirm each address before subscribing it, and to offer one-click unsubscribe on marketing mail once you send more than 5,000 messages a day to Gmail. The platform supplies the authentication and the unsubscribe headers; whether the welcome issue lands well is decided by what readers do with it.
How can a solo writer trial a platform without paying for it?
Pick one free plan and run the real signup form, the welcome email and the first two issues through it for a month. The free ceilings on beehiiv (2,500 subscribers) and Kit (10,000) leave plenty of room for that. The cost that matters is your own time spent rebuilding forms, importing consented contacts and testing the unsubscribe link, so write those hours down next to the bill. After the second issue, compare confirmed signups and unsubscribes between tools and keep only the one whose list you can export cleanly.
Which pricing mistakes trip up newsletter owners?
Three: reading the free plan as the price when the real question is the ceiling you will hit; missing that some paid features are sold as add-ons rather than as a higher plan; and counting subscribers who never confirmed. For a newsletter, compare the free ceilings first: beehiiv is free up to 2,500 subscribers (Lite shows $49 a month with yearly billing), Kit is free up to 10,000, and Buttondown charges nothing for the first 100 subscribers, with add-ons from $9 a month after that. Work out the month in which you expect to cross the ceiling you pick.
Your first 30 days: a practical rollout plan
| Period | What to do |
|---|---|
| Days 1-3 | Write the actual job description for the email program then note which free ceiling you will cross first: 2,500 subscribers on beehiiv or 10,000 on Kit. |
| Days 4-7 | Write the welcome issue, build the signup form with a confirmation step, and put your sending frequency and a one-line promise of what readers get next to the form. |
| Days 8-14 | Publish the first two issues to confirmed subscribers only, and tag every signup by source so you can see which channel brings readers who click in the second issue. |
| Days 15-21 | Ask new readers one question by reply in the welcome issue, read every answer, and use them to choose your next three topics and to decide whether a paid tier deserves a test. |
| Days 22-27 | Sign up twice with the same address, unsubscribe from your own list, and open an issue on a phone to confirm the form, the confirmation email and the footer link all behave. |
| Days 28-30 | Export the list with confirmation dates, count retained subscribers per source against what you paid, and choose between staying on the free ceiling, moving up a tier or switching platforms. |
Subscriber ceilings and monthly prices for newsletter platforms were read from the vendors' pricing pages on 2026-10-07, and the questions above link to the pages they come from.
What does a free newsletter plan really cost you?
Nothing on the invoice, but each plan holds something back. beehiiv's free plan is limited to one publication and one team seat. Kit's free plan has unlimited broadcasts, yet its Visual Automations and sequences start on the Creator plan, listed at $33 a month billed yearly. Buttondown charges nothing for the first 100 subscribers and sells tagging, automations and teams as separate add-ons. Mailchimp's free plan stops at 250 contacts and 500 sends a month. Before you build forms around any of them, write down which limit you would hit first and what removing it costs.
When does a newsletter outgrow beehiiv's free plan?
At 2,501 subscribers. Past that point you need Lite, which beehiiv's pricing page shows at $49 a month with yearly billing. The subscriber slider matters more than that headline: at 5,000 subscribers it reads $109 on monthly billing or $95 on yearly, and at 10,000 subscribers $139 monthly or $119 yearly. Multiply the yearly figure by twelve to see the commitment: $95 × 12 = $1,140 for the 5,000-subscriber band. Plan the upgrade for the month you expect to cross 2,500, not the month you actually do, so the switch never lands in the middle of a big issue.
How much of Kit's pricing sits behind the free plan?
Kit lets you collect up to 10,000 subscribers for nothing, with unlimited landing pages, forms and broadcasts plus tagging and segmentation. What it holds back is automation: unlimited Visual Automations and email sequences arrive with the Creator plan at $33 a month billed yearly, which also removes Kit branding and adds A/B tests on subject lines. Pro, at $66 a month billed yearly, adds Subscriber Signals, unlimited users, deliverability reporting and a newsletter referral system. A writer who only broadcasts can therefore stay free much longer than one who wants a welcome sequence running from day one.
Should a new newsletter charge readers from the first issue?
Usually not, but pick a platform that lets you change your mind. Substack costs nothing to publish and takes 10% of paid-subscription revenue plus credit card fees. Ghost Publisher, listed at $29 a month billed yearly, includes paid subscriptions, while its $15 Starter plan does not. Buttondown puts paid subscriptions, comments and surveys in its $9 add-on group. Whichever you choose, decide before the first issue whether the free list and a later paid tier will live in one place, because moving paying members between systems is harder than moving a free list.
How do I build a signup form that produces confirmed subscribers?
Ask for one thing, an email address, and say what people get and how often. Google's sender guidelines tell senders to make sure recipients opt in and to confirm each address before subscribing it, and they warn against opt-in boxes that are checked by default. In practice that means a confirmation email on every signup and a thank-you page that tells people to look for it. The source-specific forms in the MailerLite pilot above are a cheap way to compare placements. Count a reader only after they confirm: on plans priced by subscriber count, unconfirmed addresses inflate the bill and drag down every rate you measure.
What belongs in the welcome issue?
Say who you are, what the newsletter covers, how often it arrives and what the first useful thing is: a best past issue, a short guide or a link to the archive. Add one question readers can answer by replying; replies tell you the address is read and hand you topics to write about. Put a plain unsubscribe link in the footer, plus a way to change frequency if your platform supports it. Leave out discount codes, upsells and a pile of links, so the first message reads as the welcome it was promised to be and is easy for readers to judge.
Which acquisition source is worth keeping?
Tag every signup with where it came from, such as the site footer, a guest post, a social bio or a referral link, and compare sources on retention instead of raw signups. The measure that decides it is how many people from each source are still subscribed and clicking after the second issue. Kit does this with tags and MailerLite with groups; on any platform, set the tag at the form level so nobody has to reconstruct it later. A source that brings many people who leave after one issue costs more than one that brings a few who stay, even when its signup count looks better on the dashboard.
Do referral programs and recommendations belong in the first 90 days?
Only once the welcome issue and the first few editions keep people subscribed. Referral and recommendation tools multiply whatever your retention already is, so they amplify a leaky list as readily as a loyal one. beehiiv builds referrals and recommendations into its publication workflow, and Kit's newsletter referral system sits on its Pro plan at $66 a month billed yearly. Run one referral experiment with a control group after the first month, judge it by retained subscribers rather than by invites sent, and keep the incentive modest enough that you would still be glad to have the readers it attracts.
How should I handle unsubscribes and spam complaints as the list grows?
Treat every unsubscribe as normal and every spam complaint as a warning. Google's sender FAQ tells senders to keep the user-reported spam rate below 0.1% and to prevent it from ever reaching 0.3%, and Yahoo's best practices also say to stay below 0.3%. Google defines a bulk sender as one sending close to 5,000 messages or more a day to personal Gmail accounts, which most new newsletters are nowhere near, but the habits are cheap to build early: a visible unsubscribe link, prompt removal of anyone who leaves, and a regular look at your spam rate in Google Postmaster Tools.
How often should a young newsletter publish, and when should I prune?
Choose a cadence you can keep for six months, then keep it; irregular bursts teach readers to forget you. Google's sender guidelines suggest periodically confirming that recipients still want to stay subscribed and considering the removal of people who do not open or read your messages. For a newsletter that means either a re-permission email or a quiet removal of long-silent addresses after a stated period, applied the same way every time. Write the period on your signup page and apply it from the first issue, so shrinking the list becomes a routine step in the editorial calendar rather than a panic after a bad send.
What do I take with me if I switch newsletter platforms?
Export the subscriber list together with confirmation dates, signup source and tags, the unsubscribed and bounced addresses so they stay suppressed, and the archive of past issues. Then look at the sending domain: Buttondown's free plan includes a custom sending domain, and Substack documents how to set up a custom domain in its help center. Send the first issue from the new platform to a small cohort of recent subscribers before you move everyone. Ask each candidate for its export format before the pilot starts, because a platform you cannot leave cleanly carries a cost that never appears on a pricing page.
Which number tells me the audience is healthy?
Retained, confirmed subscribers per dollar, not total list size. Take the yearly cost of the plan and divide it by the confirmed subscribers still reading after three issues. beehiiv's 5,000-subscriber band reads $95 a month on yearly billing, so $95 × 12 = $1,140 a year, which is $0.228 per subscriber a year if all 5,000 stay and $0.456 if only 2,500 do. Track that figure beside the free ceiling you left behind, and expect it to look worse before it improves while the welcome issue is still being tuned.