Everyone's starting a newsletter. Substack, Beehiiv, MailerLite*, Ghost — the tools are everywhere and the barrier to entry is zero. Which is exactly the problem. When anyone can start a newsletter, most of them will be bad. Most of them will be abandoned by issue six, when the subscriber count is still in double digits and the writer runs out of things to say.
I've been writing online for almost twenty years. I run my own newsletter on Substack, and before that I published on Medium, on personal blogs, and on platforms that no longer exist. The lesson that took me the longest to learn is also the simplest: knowing how to write a newsletter isn't about writing well. It's about writing something people actually want to open.
Here's what I've figured out about making that happen.
Nobody subscribes for "updates" — what people actually want
The most common newsletter pitch is some variation of "sign up to stay updated." Updated on what? Nobody lies awake at night hoping for updates. People subscribe to newsletters for one of three reasons: to learn something useful, to feel something real, or to get a perspective they can't find elsewhere.
That's it. Everything else is noise.
If you're writing a newsletter about productivity, your readers don't want a roundup of productivity news. They want to know what actually works — tested by someone who's done the work. If you're writing about writing, they don't want theory. They want the specific thing you did that moved the needle.
Before you write a single issue, answer this question honestly: why would someone read this instead of the ten thousand other things competing for their attention right now? If the answer is "because I'm sharing my authentic journey," you need a better answer. Authenticity is table stakes. Value is what gets people to open email number seven.
The newsletters that survive are the ones where the writer has a clear point of view and delivers on a specific promise. Not a vague promise like "insights." A concrete one. "I'll teach you one copywriting technique per week." "I'll tell you which new apps are worth your time and which are hype." "I'll share the numbers behind my business with total honesty."
Pick your promise. Then keep it.
The format that works (and why most writers overcomplicate it)
New newsletter writers spend too much time designing templates and not enough time thinking about structure. The format that works for most solo newsletters is embarrassingly simple: a short intro that sets up the topic, a body that delivers on it, and a close that tells the reader what to do next.
That's the whole thing.
You don't need sections called "What I'm Reading" and "Quote of the Week" and "Tool of the Day." Those sections feel productive to write but most readers skip them. They subscribed for your main piece. Give them that and get out.
Some of the most successful newsletters I read — the ones I actually open — are just one idea, explored well. No fancy layout. No five-section template. Just clear thinking in plain text. If you want to learn how to write a newsletter that people actually read, start by stripping away everything that's there because you saw someone else do it.
The format should serve the content, not the other way around. If your best ideas need 400 words, write 400 words. If they need 2,000, write 2,000. The worst thing you can do is pad a tight idea to fill a template or compress a big idea because you decided newsletters should be short.
Subject lines that get opened (not clickbait — clarity)
Your subject line is not a headline. It's a promise made to someone who's already given you their email address. The relationship is different from a social media post competing for attention in a feed. Your reader opted in. They want to open your email. The subject line just needs to give them a reason to open it right now instead of later — because later usually means never.
What works: specificity. "3 things I learned from losing 200 subscribers" beats "Thoughts on subscriber growth." "The $0 tool that replaced my $300/year setup" beats "My favorite tools." The reader should know what they'll get and feel curious about the details.
What doesn't work: vague cleverness. "It's happening..." tells me nothing. "You won't believe this" tells me you don't respect my time. "Issue #47" tells me you've given up on trying.
A formula I keep coming back to: [specific thing] + [unexpected angle]. "Why I stopped using analytics (and what I track instead)." "The writing advice that ruined my first newsletter." These aren't clickbait — they're clear about the topic and honest about the angle. The reader knows what they're getting. They just don't know the specifics yet.
Test your subject lines by reading them out loud. If it sounds like something a real person would say to a friend, it's probably good. If it sounds like marketing copy, rewrite it.
How long should a newsletter be? (it depends on what you're trying to do)
This is the question every newsletter writer asks, and the honest answer is: there's no correct length. There's only the right length for what you're trying to accomplish.
Short newsletters (under 500 words) work for curated links, quick tips, and regular check-ins. They're easy to produce consistently and easy to read. But they're hard to build deep loyalty around because they don't give the reader enough to connect with.
Long newsletters (1,500+ words) work for essays, tutorials, and deep analysis. They build authority and trust. Readers who finish a 2,000-word piece feel like they've invested time in you — and that investment makes them more likely to stay. But long newsletters are harder to sustain, and if the quality drops, readers feel it immediately.
My advice: write until the idea is done, then stop. Don't count words. If you're learning how to write a newsletter for the first time, err on the side of shorter. It's easier to keep a short newsletter going than to burn out trying to write a weekly essay. You can always go longer once you've built the habit.
The one rule that matters: every sentence should earn its place. Whether your newsletter is 300 words or 3,000, the reader should never feel like you're wasting their time.
Writing for scanners AND readers
Here's an uncomfortable truth about email: most people scan before they read. They open your newsletter, scroll through it in about three seconds, and then decide whether to actually read it. If nothing catches their eye during the scan, they close it and move on.
This means your newsletter needs to work on two levels. For scanners, it needs bold text on key points, short paragraphs, clear section headers, and enough white space that the eye has somewhere to land. For readers, it needs depth, specificity, and a voice that rewards careful attention.
Writing for both isn't as hard as it sounds. The same techniques that make writing scannable — short sentences, strong openings for each paragraph, concrete details instead of abstractions — also make writing better for careful readers. Good structure helps everyone.
The practical version: lead every paragraph with the most important sentence. Bold the phrases someone scanning would want to catch. Use headers that tell the reader what each section is about, not headers that are cute but vague. Break up walls of text. One idea per paragraph.
If a scanner can get the gist of your newsletter in ten seconds and a reader can spend five minutes with it, you've done your job.
The publishing rhythm that's sustainable
Weekly is the standard. Most successful newsletters publish once a week, on the same day, at roughly the same time. It's frequent enough to stay relevant and infrequent enough to be sustainable for a solo writer.
But here's what I believe more than any scheduling advice: consistency matters more than frequency. A newsletter that goes out every other Tuesday without fail will outperform one that goes out "weekly" but skips three weeks when the writer gets busy. Your readers are forming a habit. Every time you skip, that habit gets weaker.
If weekly feels like too much, go biweekly. If biweekly feels like too much, go monthly. But whatever you choose, treat it as a commitment. Put it on your calendar. Write ahead when you can. Have a backup issue ready for the weeks when life gets in the way.
The writers who last are the ones who chose a pace they could maintain when things got hard — not just when they were excited about the project. I've seen more newsletters die from unsustainable ambition than from a lack of ideas. If you're just getting started with your newsletter, pick the frequency that lets you sleep at night.
Your newsletter is also a blog — treat it like one (SEO angle)
Most newsletter writers think of their issues as emails. Emails that get sent, read (hopefully), and then disappear into inboxes forever. That's a waste.
Every newsletter issue you publish on a platform like Substack also lives as a public web page. It can be indexed by Google. It can rank for keywords. It can bring in new subscribers months or years after you hit send. If you understand how to write a newsletter with search in mind, every issue you publish becomes an asset that compounds over time.
This is one of the things I feel most strongly about. Your newsletter is a blog that happens to also get emailed to subscribers. Treat it like one. Write titles that include phrases people actually search for. Structure your posts with headers that answer real questions. Think about what someone who's never heard of you would type into Google — and write the post that answers their search.
I wrote a full guide on Substack SEO that goes deep on the specifics. The short version: your newsletter can be a search engine growth channel if you write with search intent in mind. Most newsletter writers ignore this completely, which means the opportunity is wide open.
This doesn't mean stuffing keywords or writing for algorithms instead of humans. It means choosing titles that are clear and searchable, writing posts that are thorough enough to rank, and thinking of your archive as a library — not a pile of old emails.
When to go paid (and when it's too early)
The dream: quit your job and live off newsletter revenue. The reality: most paid newsletters make less than minimum wage when you do the math on hours invested.
That doesn't mean going paid is a bad idea. It means timing matters. Turning on paid subscriptions too early — before you've built trust, before you've proven consistency, before you have enough readers to make the conversion math work — can actually hurt your growth. Free readers who see a paywall before they're convinced of your value will leave, and they won't come back.
A reasonable threshold: wait until you have at least 500 to 1,000 free subscribers who regularly open your emails. At that point, you have proof that people want what you're writing. You have data on which topics resonate. And you have a large enough base that even a modest conversion rate produces meaningful revenue.
When you do go paid, the strategy matters as much as the timing. I broke down the full conversion system in my guide on how to get paid subscribers. And if you want to see the full picture of how to monetize a newsletter in 2026, paid subscriptions are just one of several revenue streams worth considering.
If you want a head start on the paid strategy and SEO side of newsletter growth, my Prostack toolkit bundles the frameworks I use for my own newsletter.
For a broader look at growing your subscriber base across every channel, I put together a complete guide to growing on Substack that covers what's working right now.
The bottom line on learning how to write a newsletter that lasts: pick a clear promise, deliver on it consistently, write for humans first and search engines second, and don't rush the money. The writers who build real audiences are the ones who show up, issue after issue, with something worth reading. That's the whole secret. It's simple, but it's not easy.
A writer is nothing without a reader. If you found this helpful, consider becoming my dear email friend. Nothing would make me happier.
* This article may contain affiliate or SparkLoop partner links. I may earn a small commission at no extra cost to you.