Module 1: Your Niche & Promise
What you’ll write about and the one-sentence promise that makes strangers subscribe. Nail this module and every module after gets easier.

Picking your lane
Your niche isn’t a topic — it’s a specific reader with a specific problem. “Marketing” is not a niche. “Pricing tactics for freelance designers” is. The narrower the lane, the faster the trust, because every reader feels like the newsletter was written for them personally.
Test your niche with two questions. One: can you describe your ideal reader in a single sentence — their job, their problem, what they want? Two: can you name 50 things you’d write about for them? If the reader is blurry, nobody subscribes. If you can’t list 50 issues, you’ll run dry by month three. Specific reader, deep well — that’s the combination that survives a year of publishing.
Don’t copy a big newsletter’s niche. The big generalist newsletters won years ago, when the field was empty. Today the wins are in the corners: the narrower and more specific, the less competition and the higher the conversion. Own a corner, then expand.
Build brief
Write your one-sentence promise: ‘Every [schedule], [reader] gets [outcome].’ Write three versions.
Saved
The promise formula
The promise
Every newsletter that grows has a one-sentence promise — the reason a stranger hands over their email address. The formula: every [schedule], [specific reader] gets [specific outcome]. “Every Tuesday, freelance designers get one pricing tactic they can use the same day.” That’s a promise. “Thoughts on business and life, weekly” is a diary entry — it converts nobody.
The promise has two jobs: make the value obvious and make the schedule explicit. Obvious value answers “what do I get” before the reader has to wonder. An explicit schedule answers “when” — and a schedule is a commitment device: it tells the reader you’re serious, and it tells you to show up. Nobody subscribes to “updates.” People subscribe to outcomes on a schedule.
Write three versions of your promise. Read each to one person in your target group. Keep the one that makes them say “I’d subscribe to that” — their reaction is the only test that matters.
Build brief
List 20 issue ideas for your newsletter. If you stall before 10, your niche is too narrow or too vague — adjust and try again.
Saved
Testing your promise before you build
Don’t build the newsletter to test the promise — test the promise to earn the newsletter. The 10-conversation test: describe your one-sentence promise to ten people in your target group. If seven or more say they’d subscribe, you’ve got it. If fewer than five do, the promise is wrong — fix the words before you write a single issue.
The headline test is even faster: write four issue headlines for your newsletter. Real ones — the kind your ideal reader would click. If you stall at two, your niche is too thin or too vague. A year of weekly publishing needs 52 headlines; if four is hard, the well is dry. Four headlines now saves four months of struggling later.
Both tests are free and take an afternoon. Skip them and you’ll discover the problem in month three, when the list has stalled and every issue feels like pulling teeth. Test first, build second — always.
Build brief
Name 10 specific people (real or archetypes) who would subscribe to your newsletter. What do they have in common?
Saved
Dev’s newsletter promise is “Thoughts on startups, tech, and life, weekly.” Subscriptions are flat. What’s broken?
Your turn: Write 10 issue headlines for your newsletter. Real ones — the kind that would make your ideal reader stop and click.
Saved.
Your next 24 hours
Write three versions of your one-sentence promise. Read each out loud to one person in your target group. Keep the one that gets “I’d subscribe.”
Steal this template
THE PROMISE BUILDER
Every _____, _____ gets _____.
(schedule) (specific reader) (specific outcome)
Example: Every Tuesday, freelance designers get one pricing tactic they can use the same day.
Version 1: ___
Version 2: ___
Version 3: ___
Module cheat sheet
- A niche is a specific reader with a specific problem — not a topic.
- The promise formula: every [schedule], [reader] gets [outcome].
- Test the reader: describe them in one sentence. Test the well: list 50 issue ideas.
- The 10-conversation test: 7+ “I’d subscribe” means the promise works.
- The headline test: write 4 real headlines — if you stall at 2, the niche is wrong.
- Own a corner first. Expand later.