How to Start a Newsletter: My Tested Playbook for 2026

Most guides on how to start a newsletter tell you to pick a platform, choose a template, and write your first issue. I think that sequence is backwards. I've launched three newsletters, migrated between platforms, and watched technically sound emails disappear into spam because I treated inbox placement as a configuration detail instead of a launch requirement.

Email is still a direct channel with a huge existing audience. One widely cited estimate puts the number of email users above 4 billion, with a projection of about 4.6 billion by 2025, while the email marketing industry was valued at $7.5 billion in 2020 and projected to reach $17.9 billion by 2027 in the same source, email audience and industry estimates. That scale is useful only if I can reach the people who asked to hear from me.

Table of Contents

• Why Most Newsletter Guides Get the First Step Wrong
• Picking the Right Platform for Your Use Case
• Technical Setup That Keeps You Out of Spam
  • Start with a sending identity
  • Keep signup consent clean
• Planning Your First Eight Issues and Cadence
• Growth Tactics That Actually Moved My Subscriber Count
• When and How to Monetize Without Killing Engagement
• Your Launch Checklist and Weekly Metrics Dashboard

Why Most Newsletter Guides Get the First Step Wrong

I used to follow the standard how to start a newsletter checklist: pick a platform, choose a template, and write the first issue. That sequence cost me a launch because inbox placement never recovered. Before comparing beehiiv, Substack, Ghost, or another platform, I now establish who controls the list, the domain, and the sender reputation.

Three questions determine whether a platform is workable:

• Who owns the subscriber data? I want a clean export of addresses, consent records, tags, and engagement history.
• Can I export it without friction? Migration becomes expensive when a platform makes routine data access difficult.
• Will I control the sending reputation? Authentication and a sender identity tied to a domain I can manage give me a clearer path to diagnose delivery problems.

I learned this while migrating from Substack to beehiiv. Exporting subscribers was manageable, but rebuilding segments, checking consent, recreating automations, and updating signup points took longer than the import. My self-hosted Ghost setup created a different burden. I owned more of the stack, while updates, email-service configuration, and troubleshooting became my responsibility.

A new domain also needs time to establish sending history. I do not send to a full list from a cold domain. I begin with the most engaged, clearly consented subscribers, monitor bounces and complaints, then increase volume carefully. Shared infrastructure reduces setup work, but poor neighboring senders can affect the environment around a new account.

My rule: I judge a platform by how cleanly I can leave, authenticate, segment, and recover when delivery changes, not by how quickly it creates a landing page.

About one in six marketing emails fails to reach the inbox because it is filtered or blocked, according to newsletter deliverability benchmarks. Deliverability therefore belongs at the start of the process. Platform choice, content cadence, and growth tactics perform better after ownership and inbox access are secured.

Picking the Right Platform for Your Use Case

I've used beehiiv, Substack, Ghost, LetterBucket, and Kit for different jobs. None is universally right. I choose based on whether I'm building a free publication, selling subscriptions, or moving an existing list.

I'd pick beehiiv for a free newsletter aiming at sponsorships. Its built-in ad network and referral engine reduce the number of external systems I need to connect. The trade-off is that the product can feel more publication-focused than brand-focused, and the broader feature set takes time to configure well.

For a paid newsletter, I'd choose Ghost if I wanted the publication, website, and member database under my control. Ghost(Pro) removes much of the server work. Self-hosting costs less in platform dependence but adds maintenance, updates, backups, and email configuration. I've tested both approaches, and convenience is the reason I'd use Ghost(Pro) for a small team.

Substack remains my choice for a writer who wants to publish quickly and test whether readers will pay. The downside is limited design control, and free plans don't provide the same custom-domain flexibility I want for a long-term brand. Kit is a better fit for a creator selling courses, downloads, or several products because its automation model handles more than a publication alone.

I currently use LetterBucket in my stack when I want a focused newsletter workflow without building a larger marketing system around it. I like the directness, but I still need to verify export options, authentication, and the exact limits of the plan before committing a serious publication there. I wouldn't choose it solely because the interface feels simpler.

For a deeper feature-by-use-case comparison, I keep newsletter software options nearby during platform evaluations.

Technical Setup That Keeps You Out of Spam

I set up sending infrastructure before I write the welcome email. The order matters because changing the sender domain after launch can create confusion for subscribers and disrupt reputation signals.

Start with a sending identity

I use a dedicated subdomain such as mail.yourdomain.com for newsletter sending when the platform supports it. That separates newsletter reputation from the root domain used for normal business mail. It isn't a magic shield. A bad newsletter reputation can still hurt the wider brand, but separation gives me a cleaner boundary for diagnosis.

I then authenticate the domain with SPF, DKIM, and DMARC. The platform provides the records and values. I copy them into my DNS provider, wait for verification, and send a test to several seed inboxes. I begin DMARC with a monitoring policy, review authentication reports, and move toward quarantine only after I'm confident legitimate mail passes. I don't paste arbitrary DNS values into a guide because the correct values are unique to the sending provider and domain.

I use a recognizable From name, usually the publication name followed by my name, and a monitored Reply-To address. Replies tell me whether the promise on the signup page matches the experience in the inbox. They also surface broken links, confusing sections, and topics readers want expanded.

Keep signup consent clean

I use a dedicated landing page for the main promise, an embedded form on owned content, and a restrained exit-intent prompt where it fits the page. Each form asks only for the information I need. I use double opt-in when list quality matters more than adding every possible address.

I never buy a list. Consent-first signup, an easy unsubscribe path, and one-click unsubscribe are basic deliverability controls. Mailgun's inbox placement and spam guidance also recommends seed mailboxes for testing and keeping spam complaints below 0.1%.

Before scaling, I test Gmail, Outlook, and Apple Mail accounts, check the plain-text fallback, confirm the unsubscribe link, and inspect the Reply-To address. I also review the email deliverability checklist before the first scheduled send.

Planning Your First Eight Issues and Cadence

I don't start with daily publishing. Daily email sounds productive, but it creates pressure before I know which format earns replies, clicks, or sustained reading. I start with a bi-weekly cadence during the first month, then move toward weekly when the audience shows consistent engagement.

I batch-write the first four issues before publishing any of them. That gives me room to fix a weak premise without disappointing subscribers and exposes whether the idea has enough depth to support a real publication.

My first eight issues usually alternate among three formats:

1. A foundational deep dive, which answers a recurring audience problem.
2. A curated roundup, which proves I can filter information instead of merely adding to it.
3. A personal narrative, which shows how I made a decision, handled a failure, or tested a tool.

I repeat that pattern with new subjects. Each issue follows a simple shape: a specific hook, one core insight, an actionable takeaway, and a prompt that makes replying easy. I avoid stuffing several unrelated ideas into one email because readers need to understand what the issue is for.

I track ideas in a spreadsheet with columns for audience pain point, proposed promise, format, source material, reader replies, clicks, and whether I'd write the topic again. I don't treat one unusually strong issue as proof of a permanent winner. I look for repeated signals across adjacent issues.

The benchmark I use as an early guardrail is a 40% open rate, but I don't treat it as the only success measure. In 2025, benchmark sources reported average open rates around 42.35% and 43.46%, with an average click rate of about 2.09%, a click-to-open rate near 5.63%, and unsubscribe rates ranging from 0.08% to 0.22%, depending on the dataset, as shown in the 2025 email benchmark report. Privacy changes have also made opens less dependable, so I compare opens with clicks, replies, conversions, and unsubscribes.

Growth Tactics That Actually Moved My Subscriber Count

I tested seven acquisition channels across three launches. The tactics that held up shared one trait: they gave a prospective subscriber a clear reason to join, rather than placing a generic subscription request in front of them.

I used a swipe file as a lead magnet, connected it to a focused landing page, and wrote the welcome email around how to use it. That worked better than a broad “subscribe for updates” message because the visitor understood the immediate payoff. I don't treat the exact conversion rate from that experiment as a universal benchmark. Landing-page traffic, promise, niche, and trust all change the result.

Referrals worked after I gave readers a visible milestone and a reward worth sharing. SparkLoop handled the mechanics, but the program still needed a clear referral page, progress emails, and rewards that didn't attract people who had no interest in the newsletter. A large newsletter reference attributed roughly 30% of new subscriber growth, or about 450,000 subscribers, to readers inviting others, newsletter referral program analysis. That's a useful ceiling to think about, not a promise for a new publication.

Cross-promotions produced fewer signups than my broadest lead magnets, but those readers engaged more closely with the subject. I partnered with adjacent newsletters whose readers already understood the problem I wrote about. Organic social threads helped when each thread delivered a complete idea and the signup page offered the next step.

I'd add referrals only after I can describe the newsletter in one sentence and deliver it consistently. The newsletter referral program guide is useful for comparing reward structures, but I'm cautious with giveaways because they can inflate acquisition without improving readership.

Paid Meta ads were a poor fit in my tests. The acquisition looked easy, but the resulting readers churned more quickly because the ad promise was broader than the newsletter experience. Generic blog CTAs also underperformed. A contextual invitation inside a useful article worked better than a footer line that asked everyone to subscribe.

When and How to Monetize Without Killing Engagement

Monetization should follow inbox trust, not subscriber count. If readers do not regularly open, click, or reply, adding a sponsor gives you revenue pressure without a dependable audience habit. I wait until the newsletter has a clear promise, consistent delivery, and engagement I can monitor.

I use three models:

• Sponsorships suit a focused audience with clear buying intent. A sponsor slot within the useful part of the email usually feels less disruptive than a header takeover.
• Paid subscriptions work when the free edition has already earned trust and the paid tier provides a distinct outcome, rather than offering “more content.”
• Affiliate links can begin earlier, but only for products I would recommend without a commission. Relevance protects credibility and keeps commercial links from weakening the newsletter's editorial purpose.

I do not set an arbitrary list-size threshold before selling. Replies, clicks, unsubscribes, and requests for deeper material reveal more than raw subscriber volume. A smaller, specific audience may be commercially useful, while a larger passive list can be difficult to convert.

The benchmark is sobering. A Press Gazette analysis of newsletter pricing, conversion rates, retention, and churn reported a 0.62% median paid conversion rate, roughly 6 paying subscribers per 1,000 total subscribers, across a major newsletter platform's network, Press Gazette's 2026 newsletter pricing and conversion analysis. I use that figure for conservative forecasting rather than building a budget around a large share of free readers becoming paying customers.

Commercial test: If removing the sponsor would make the issue substantially better, the placement is wrong or the sponsor is not relevant enough.

During the first year of a new publication, I cap ad density at one sponsor in every three issues. I label affiliate relationships clearly, place links beside the relevant recommendation, and compare complaint and unsubscribe trends after each commercial send. Revenue matters, but losing reader trust can damage the engagement that makes future monetization possible.

Your Launch Checklist and Weekly Metrics Dashboard

Inbox placement comes before launch polish. If authentication, consent, or unsubscribe handling fails, a well-designed issue still misses readers. I use this checklist before sending:

• Authenticate the domain: Verify SPF, DKIM, and DMARC in both the sending platform and DNS provider.
• Publish the landing page: State who the newsletter serves, what subscribers receive, and how often it arrives.
• Place owned signup forms: Add forms to at least two channels I control, such as a website and a dedicated landing page.
• Test seed inboxes: Send to Gmail, Outlook, and Apple Mail accounts. Inspect rendering, links, authentication, and unsubscribe behavior.
• Schedule the first issue: Use a real date, a recognizable sender name, and a reply address I monitor.
• Prepare the next issues: Do not launch with one email and an empty calendar.

Every Friday, I record open rate, click-through rate, subscriber growth rate, unsubscribe rate, and spam complaint rate in a spreadsheet. Week-over-week movement matters more than one noisy send, especially after a list-source change or a new subject-line format.

For a small or niche newsletter, I use the commonly cited 40% to 55% open-rate range as a healthy reference, with the range documented in email newsletter benchmarks. I keep spam complaints below 0.05%, also using email newsletter benchmarks as the reference. I track unsubscribes against the roughly 0.1% to 0.3% per issue range from email newsletter benchmarks. Open rates can be distorted by privacy protections, so a flat open rate alongside rising clicks may still indicate stronger engagement.

A sudden complaint increase sends me to acquisition sources and the signup promise. Falling clicks point me toward the lead, link placement, and content format. A growth slowdown calls for a distribution review before I rewrite the newsletter. I give the publication a consistent run over 12 weeks before deciding that the core idea has failed.

Start by registering a domain you control, authenticating it, writing down the data-export plan, and publishing one focused signup page. Schedule the first issue after the next three are outlined. Dependable delivery and repetition create the asset, not a perfect launch day.