Issue Four Is Where Founder Newsletters Die

Issue one is easy. So is issue two, sometimes issue three. Those first sends usually come from notes you already had, opinions you already held, or a burst of energy that felt durable at the time.

Issue four is different. By then, the backlog is gone. The newsletter is no longer a thought you had before you started. It is a recurring job, and it is competing with product, sales, support, and hiring.

That is where most founder newsletters stall. Not because the writing is bad, and not because the platform is wrong. They stall because the newsletter was designed around what the founder intended to write, rather than around what the company already produces.

What the data says

Newsletter Circle’s analysis of 74,858 public Substack newsletters gives this pattern some scale. In the report, 45 percent of newsletters were inactive, about 34,000 out of 75,000. That is the first warning sign.

The second is structure. Ninety-five percent of active newsletters had exactly one creator behind them, for both paid and free publications. In other words, the typical newsletter is a single point of failure.

The third is cadence. Monthly was the most common publishing rhythm at 24 percent, ahead of weekly at 21 percent, with daily at 3 percent. That matters because monthly sounds sustainable, but it often creates the longest gap between work and publication.

One more number matters. Eighty-two percent of those newsletters had under 10,000 subscribers. This is not a story about giant media brands. It is a story about small newsletters, which is the relevant population for founders and first marketers.

Read together, the mechanism becomes clear. A one-person channel, run by someone whose day job is not writing, on a cadence that gives the least practice and the longest decay between issues. That combination does not need a better platform. It needs a different operating model.

Limits matter

Be precise about what this does and does not show. This is cross-sectional data on Substack specifically, drawn from one independent analysis. It does not prove causation. It does not tell us whether founder-run newsletters behave exactly like the broader Substack population. It cannot distinguish a newsletter that stopped from one that is simply between issues.

Those are real limits. They are also why this piece is more useful than the usual argument that newsletters are dead, or that founders simply need more discipline.

The failure is usually not effort. It is supply.

The real mechanism

Most founder newsletters are designed backwards. The founder starts with a topic, then imagines a channel around that topic, then commits to publishing on a schedule that feels respectable. The problem is that every issue becomes a fresh act of creation.

Fresh creation is expensive. It competes with the rest of the week. When the product is on fire, support is loud, or the pipeline needs attention, the newsletter is the first thing to slip.

Monthly can make that worse, not better. A four-week gap is long enough for the habit to decay, and short enough that you never build fluency. Weekly is often easier, not because it is lighter, but because it keeps the work close. You stay in touch with the material.

This is why newsletters die after a few issues. The writer does not run out of opinions. They run out of produced material.

Start with supply

The fix is not to ask, “What will I write about?” The fix is to ask, “What does my company already produce that a customer would care to read?”

That is a supply-side question. It changes the job from invention to capture.

Here are the raw materials that already exist inside most early-stage software companies:

• Support tickets, and the answers you already typed.
• Sales-call objections, and the reply you already gave.
• The changelog, and the reason each item exists.
• A customer question that came up twice this week.
• A decision you made, and the option you rejected.
• A number you watched, and what you changed because of it.

Each of those is a byproduct of work that happens whether or not you publish. That is the point. The newsletter should harvest what already exists, not demand a new category of work every seven days.

Example, support

A customer asks why a feature behaves a certain way. You answer in Slack or Intercom. That exchange becomes the core of an issue about design tradeoffs, not a generic thought piece about user experience.

Example, sales

A prospect asks whether your product replaces a workflow or just improves it. The answer becomes an issue about where your product fits, and where it does not.

Example, product

You shipped a small change because ten users asked for it. The newsletter explains the decision, the pattern you saw, and the constraint that shaped it.

Build capture

Once the supply is clear, the job is to capture it before it disappears.

A simple two-column system is enough for most small teams.

Raw materialReader valueCustomer question, date, sourceOne sentence that reframes why it mattersSales objection, date, sourceOne sentence that answers it for a broader audienceSupport issue, date, sourceOne sentence that turns it into a lessonProduct decision, date, sourceOne sentence that explains the tradeoff

The rule is simple. Nothing enters the second column unless it came from real work.

That constraint matters. It keeps the newsletter from drifting into commentary that sounds smart but has no operational core.

Here is what four weeks of capture can look like:

1. Week 1, a support question about pricing becomes a short explanation of how buyers evaluate the product.
2. Week 2, a sales objection about switching cost becomes an issue on implementation risk.
3. Week 3, a product change request becomes a note on why you did not build the obvious thing.
4. Week 4, a customer pattern you noticed becomes a field memo on what buyers keep missing.

Four issues, no blank page, no invented topic, no crisis at the end of the week.

Pick cadence

Cadence should follow supply, not aspiration. If your company generates one useful story every two weeks, publish every two weeks. If you have enough material for a weekly issue, publish weekly.

Do not promise a rhythm your input cannot support. That is how teams end up with a silent list and an internal story about lack of discipline.

Weekly raw materialPractical cadence1 to 2 useful itemsFortnightly3 to 5 useful itemsWeekly6 or more useful itemsWeekly, with a backlog

Fortnightly is not a failure. It is an honest match between production and publication. A fake weekly schedule is usually worse than a measured biweekly one.

Remove the bottleneck

The 95 percent number from Newsletter Circle is the real warning. If one person owns the newsletter, the newsletter inherits that person’s bandwidth, mood, and calendar.

For a company of one to five, the answer is not hiring a content team. It is making capture routine.

• Set a standing 15-minute capture slot each week.
• Have whoever owned support that week add raw material to the log.
• Use one template, every time, so the writing becomes mechanical.
• Define what happens when a week is missed, so silence is not the default.

That is the operational fix. It reduces dependency on one person, and it gives the newsletter a supply chain.

Why this matters

The broader conversation keeps asking whether newsletters are dead, whether they still matter, or whether people are simply unsubscribing more often. Those are demand-side questions. They matter, but they are not the first problem for a founder newsletter.

The first problem is whether the channel can survive the next six weeks of real company life.

That question is not about taste. It is about whether the newsletter has a source of inventory.

Better Marketing takes that same view in its own work. Before anyone writes, we look at what a company already produces, then we build from that supply. The channel has to fit the business, not the other way around.

What to do now

If your newsletter has stalled, do not start by rewriting the intro or changing platforms. Start by listing the material your company already creates.

• Three customer questions from the last month.
• Three objections heard in sales.
• Three support issues with reusable answers.
• Three product decisions worth explaining.

Then choose one cadence you can actually support. Finally, create one capture template, and use it every week.

That is enough to restart most founder newsletters. Not because the writing suddenly improves, but because the supply problem is finally addressed.

Takeaway

Your newsletter did not fail because your writing was weak or your platform was wrong. It failed because you designed it around what you would write, instead of around what your company already produces, and because you were the only person who could make it.

Fix the supply, and the cadence stops being a willpower test. The work becomes easier to continue, which is usually the real test.