惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
Cisco Talos Blog
Cisco Talos Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
博客园 - 三生石上(FineUI控件)
Martin Fowler
Martin Fowler
WordPress大学
WordPress大学
D
Docker
S
SegmentFault 最新的问题
博客园 - 聂微东
美团技术团队
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
GbyAI
GbyAI
L
LangChain Blog
Vercel News
Vercel News
博客园 - 叶小钗
MongoDB | Blog
MongoDB | Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
T
Threat Research - Cisco Blogs
T
Threatpost
Scott Helme
Scott Helme
T
Tailwind CSS Blog
Latest news
Latest news
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
The Register - Security
The Register - Security
罗磊的独立博客
P
Proofpoint News Feed
腾讯CDC
S
Schneier on Security
雷峰网
雷峰网
A
About on SuperTechFans
T
Tenable Blog
F
Full Disclosure
Cyberwarzone
Cyberwarzone
博客园_首页
有赞技术团队
有赞技术团队
K
Kaspersky official blog

文章列表

Compulsive curiosity, or, how I built an infinite idea machine Gift details on the subscriber portal Portal link in the archive nav The physicists who convinced Fermilab to send Brazil's emails First, add no friction: How micropayments lost and subscriptions won Filter subscribers and automations by source Automations, rebuilt What email will look like in the future Filter subscribers by bounce date and reason Email could have been X.400 times better Three features are moving behind the paywall Firewall changes and improvements Put your name and voice into your company newsletter Simplified email address settings Subscription wall Inboxes were overwhelming before we'd even named them The US government tried really hard to screw up email Public postmortem: database connection exhaustion Ask a nerd: what is the best way to unsubscribe from newsletters? Bookshop.org embeds Email was into agents before they were cool Passwordless login Rename metadata keys in bulk A spring cleaning for our legal docs Ask a nerd: what happens when you click the spam button? Passkey support for two-factor authentication How Buttondown's API versioning works Safer defaults for the email creation API How to send email to space How we enabled Content Security Policy for everyone Recovery codes for two-factor authentication Filter sent emails by engagement rate How we migrated to TypeIDs without breaking clients How we check every link in your email Use newsletter metadata in your emails Should we bring back email exploders? Sort and filter by open and click rates Custom click tracking domains More newsletter settings in the API Revamped replies Custom email templates for everyone Simplified cancellation Ask a Nerd: Does email length affect deliverability? The changelog, reborn Swedish localization Forwarding an email is not always straightforward Public descriptions for tags OpenAPI spec for archives How Rodrigo brings a humanistic view to consumer technology Survey responses on the web How Brandon Lucas Green shares his music and supports artists Subscribers can come from anywhere. Even another newsletter platform's form. Your newsletter's archives are more valuable than your list Better tag self-management Smarter automation filters Granular API keys New design settings pages Snippets Ask A Nerd: How does newsletter cadence affect deliverability? Starred views More ways to customize your archives Inbox filtering Mastodon follower analytics Ask a Nerd: What are good open, click, and response rates for an email newsletter? How we migrated our database to PlanetScale Two new archive themes Custom buttons now work in Markdown mode Ask a Nerd: Does attaching files to your newsletter hurt deliverability? Seline and Tinylytics support Unban subscribers Public postmortem: archive downtime Bang paths, source routing, and how email trips were planned Announcement bars for your archives 2025 disposables.app Russian localization Ask a Nerd: Can you improve email deliverability with a personal domain? More locale options How we interview customers at Buttondown Bluesky analytics Minimum viable complexity Reply to conversations How Jeffery Hicks goes behind-the-scenes in his newsletter Changes to our stack in 2025 2026: Emails Randomize survey answer order TK reminders in the editor What the hell is a UTM? Why we insourced analytics Scroll sync in the editor 2026: Archives How Kelly Jensen uses Buttondown to discuss key library issues How Jamie Thingelstad uses Buttondown to explore tech topics Keeping feature creep at bay Improved filters Content Security Policy in archives Open source Sniperl.ink Auto-activating RSS reader subscriptions What the hell is ActivityPub? Gift subscriptions
How often should you send your newsletter?
Justin Duke · 2024-03-04 · via

If you're spinning up a newsletter and have chosen a topic you're passionate about, it's time to decide the second most important thing — how often you're publishing!

There are three main criteria that your publishing cadence should fulfill. Let's introduce them, and then talk about each more in depth.

Your ideal publishing cadence should be:

  1. Maintainable over a very long period of time.
  2. Frequent enough that your audience stays informed and engaged with your work.
  3. Concurrent with your success criteria and subject matter.

Maintainability

I'm gonna get the most important thing out of the way first: the most common — and the most dangerous — way newsletters fail is by burning themselves out.

Newsletters — just like any sort of content creation, like a podcast or a video series or anything! — are a serious commitment! They take time and energy and can feel often feel Sisyphean, especially in the early goings when it might feel like you're writing to an empty room.

Frequency

On the other side of the spectrum — it might be infinitely easy to maintain a publishing cadence of "whenever I have time and/or feel like it", but your subscribers will not be having a great time.

Subscribers — and the finicky email algorithms that make sure they see your writing front and center — like consistency. Consistency may be the hobgoblin of little minds, but consistency — even at a very slow publishing cadence, like once a month or once a quarter — is the key to success:

  1. It's easy for you to build the habit of writing and sending if you know you need to always have something ready to go by, say, Friday morning.
  2. It primes your subscriber base to expect your email in their inbox, which means they'll read and engage with it more.
  3. It provides an air of professionalism and stability that is important for almost any success criteria, whether its driving folks to be patrons of your writing or establishing your credibility as a consultant.

If you run something monthly, your subscriber base will grow very slowly. Eventually, it almost felt like it’s not worth it. The impact was too low and I wanted to see results. Also, very few people wait for or expect a monthly email. Stefan Judis

Concurrency

The final variable — and the trickiest to reason about sometimes — is to make sure your publishing cadence matches what you're writing about.

If you're largely commenting on breaking news or industry buzz, temporality is everything!

Conversely, if you're trying to write long-form, atemporal pieces, publishing every week will cheapen the effect that an email has on your subscribers.

The hidden variable: email length

There is one cheat code to the publishing cadence discussion that gets overlooked fairly often, which is (roughly):

Writing one 500 word emails is about the same amount of effort as two 250 word emails.

This is not exactly true, of course — there are lots of fixed costs to writing an email, like lining up sponsors or coming up with subjects and so on — but it's mostly true, especially when you're planning out your time.

So if you find yourself really confident that, say, the right cadence for you is three-times-a-week but you're a little skittish about the commitment that entails... maybe experimenting with shorter-form or commentary/riff-driven emails as opposed to longer, extemporaneous missives is the way to go!

All of this is to say:

If you expected this essay to end with a conclusion along the lines of: "therefore, just write a weekly newsletter and be done with it", I hate to disappoint. The right schedule does not exist: there's only a schedule that best aligns with your goals, commitments, and energy level.