Launch a Newsletter
12 weeks · 3 milestones
Build a newsletter to 500 subscribers with consistent weekly issues.
Milestone map
Milestone map
3 milestones
Define the newsletter concept and publish the first issue
2–4 weeks
Define the newsletter concept — topic, format, audience, and publication frequency — and send the first issue. A newsletter concept that works is one where the reader can answer 'what will I get from this?' with one specific sentence. The first issue must be sent to real subscribers — not just written and saved in a draft. The minimum viable launch is sending issue 1 to 5+ subscribers, even if they are personal contacts. The goal is to overcome the psychological barrier of sending creative work to real inboxes, not to build an audience from day one.
Proof required
Share the newsletter platform URL or a screenshot of issue 1 sent (Substack, Mailchimp, Beehiiv, or equivalent). State the concept (topic + format + audience + frequency). State how many subscribers received issue 1. Write one sentence on what you want readers to do after reading each issue.
What gets checked
- Issue 1 has been sent to real subscribers — screenshot of sent campaign or Substack subscriber post.
- Concept covers topic, format, audience, and frequency.
- What readers should do after reading is stated — a clear call to action or reader intent.
Common mistakes
- Issue 1 written but not sent: 'I'm not ready to send yet' — the milestone requires the first send.
- Sent to zero subscribers: 'I published it but no one signed up yet' — 5+ subscribers (even personal contacts) for the first send is the minimum.
- Frequency not committed: 'whenever I have something to say' — a frequency is part of the subscriber promise.
Resources
What a verifier looks for
- The first issue must have been sent — ask for the sent date and the subscriber count at the time of sending.
- Concept: ask what the newsletter is for — 'to share my thoughts' is not a concept; 'weekly roundup of overlooked science papers for busy professionals' is.
- What readers should do after reading: a newsletter without a call to action is a broadcast; one with a consistent call to action builds habits and replies.
You'll sign in first, then come straight back here.
Send 5 issues consistently and reach 50 subscribers
5–20 weeks (depending on frequency)
Send 5 issues at the committed frequency and reach 50 subscribers. 50 subscribers is achievable through personal outreach and consistent content without a following, and it is enough to establish a real readership pattern — open rates, click-through, and reply rates all become meaningful at 50. 5 issues at the committed frequency demonstrates that the newsletter is a sustainable practice, not a launch impulse. If the frequency changed between issues 1 and 5, that should be noted and the reason given.
Proof required
Share a screenshot of your newsletter analytics showing 50+ subscribers and 5 issues sent (Substack dashboard, Beehiiv dashboard, or Mailchimp analytics). State your open rate for the most recent issue. State whether any subscriber replied to or commented on an issue.
What gets checked
- 50+ subscribers and 5 issues sent — both shown in the analytics screenshot.
- Open rate for the most recent issue is stated.
- Subscriber reply or comment is addressed — even 'no one has replied' is a real answer.
Common mistakes
- 50 subscribers but fewer than 5 issues sent: 'I've been building the list' — the content consistency is as important as the subscriber count.
- Open rate not stated: analytics are available on every major newsletter platform — the open rate should be known.
- Subscriber reply absent entirely: even 'no one has replied' should be stated with a note on whether a reply CTA was included.
Resources
What a verifier looks for
- The analytics screenshot should show both subscriber count and issue count — ask whether all 5 issues were sent at the committed frequency.
- Open rate: industry average open rates for newsletters are 35–50%; ask whether the open rate has been improving or declining across 5 issues.
- Subscriber reply: ask whether the most recent issue included a specific question or prompt for readers to respond to — reply rate is dramatically higher when an explicit prompt is included.
You'll sign in first, then come straight back here.
Issue 10 — audience understanding and what keeps subscribers reading
10 issues after launch
Send issue 10 and write a reflection on the subscriber behaviour across 10 issues: which issues had the highest open rate, whether subscribers have grown or churned, and what the creator now understands about the audience that they did not understand at launch. The reflection is the primary proof at this milestone — 10 issues of data is enough to see meaningful patterns, and the creator's ability to articulate what they learned reveals whether the newsletter is being actively developed or mechanically produced.
Proof required
Share a screenshot of your newsletter analytics showing issue 10 published and your current subscriber count. Write one paragraph on what you have learned about your audience from 10 issues: which topics got the highest opens or replies, whether subscribers are more or less engaged than at launch, and one specific thing you are changing about the newsletter based on what you observed.
What gets checked
- Issue 10 is published — analytics screenshot with issue count visible.
- What topics got the highest engagement is addressed specifically — not 'people seemed to like it' but a specific issue or topic type.
- One specific change being made based on observed audience behaviour — demonstrates active iteration.
Common mistakes
- Only subscriber count reported: 'we now have 100 subscribers' — engagement data (open rate, replies) is required.
- Reflection is generic: 'people like good content' — the reflection must be specific to this newsletter's data.
- No change being made: 'I'm going to keep doing the same thing' — the absence of iteration suggests the audience data is not being used.
Resources
What a verifier looks for
- Which topics got the highest engagement: ask for the top 2 issues by open rate — the topics of those issues reveal what the audience specifically values.
- Subscriber churn: ask whether the unsubscribe rate has increased or decreased over 10 issues — sustained churn is a signal about content-audience fit.
- One specific change: the change should be observable — 'I'm going to add a reader question at the end of every issue' is observable; 'I'm going to write better' is not.
You'll sign in first, then come straight back here.
Part of