top of page
SCOPE
Newsletter · Editorial System · Growth
ROLE
Editorial strategy, writing, production, analytics

Two newsletters from zero to 6,000+ subscribers.

Took an initial concept and built the editorial operation around it. Wrote nearly every issue. Ran the system end to end. Engagement didn't erode as the audience grew.

6k+

Combined subscribers
from zero

35-45%

Open rate sustained
vs 20% benchmark

3x/week

Publishing cadence

~150

Issues written
in first year
CONTEXT

Two audiences, one editorial operation

Two newsletters. One focused on AI, thinking, and business. The other on professional influence and knowledge work. Different audiences, tones, and content, but built on the same editorial infrastructure.
 

I took an initial concept and built everything else: audience personas, content pillars, a format library, a publishing pace sustainable at three issues per week, a metrics review process, and ongoing iteration based on performance data and reader feedback.

The system is what makes the difference between a newsletter that runs for three months and one that runs for three years.

THE WORK

What I built before writing a single issue

Before any content was produced, I defined the architecture for each publication:

​

  • Audience personas. Their worldview, not the demographics. What readers believed, what frustrated them, what they were trying to become.
     

  • Content pillars. The recurring territories each newsletter owned. Specific enough to create coherence. Broad enough to sustain weekly frequency for years.
     

  • Format library. Recurring formats that gave each issue structural consistency without making it feel templated. Readers knew what to expect. The content inside was always different.
     

  • Metrics review process. A system for distinguishing between topics that resonated and topics that merely landed. Open rates, click patterns, reply signals. Iterated format and topic selection continuously.

The question was always what would happen as the list scaled and diversified. Would engagement erode? It didn't.

RESULTS

Growth without engagement decay

Both newsletters started with the elevated open rates typical of small, highly motivated early audiences (55-60%). Every newsletter does. The real test is what happens as the list scales and diversifies.

​

The AI and business newsletter stabilised at 35% average open rate. The knowledge work newsletter stabilised at 45%. Both figures sit well above the 25-30% industry benchmark for Spanish-language business newsletters at comparable scale.

 

Engagement didn't erode as the audience grew. That's the metric that matters for a weekly newsletter. Not how many people subscribe, but how many keep opening it a year later.

Editorial architecture prevented content decay

The pillar system and format library meant the newsletters never ran out of direction. Each issue had a structural reason to exist, not just a calendar slot to fill.

Metrics-driven iteration kept relevance

Continuous analysis of open rates, click patterns, and reader replies fed back into topic selection and format evolution. The newsletters got sharper over time, not duller.

One-person operation at three issues per week

The system made this sustainable. Without the architecture (pillars preventing repetition, formats preventing blank-page paralysis, metrics preventing drift) this cadence would have burned out in three months.

The archive compounds

New subscribers who discover the newsletters find a coherent, navigable body of work. Not a random collection of posts. The system created retroactive value. Each new issue makes the archive more worth exploring.

What this project taught me

A newsletter is not a content format. It's a relationship maintained at publishing frequency. The open rate is a measure of whether readers trust that opening this week's issue will be worth their time, fifty-two weeks in a row.

​

Sustaining above-benchmark engagement across two publications simultaneously, over an extended period, requires an editorial operation , not just good writing. The writing matters. But the system is the product.

Need something like this?

I build editorial systems and run them. If you need a content operation that sustains quality at frequency, let's talk.

bottom of page