A newsletter is the one channel where your reader chose to hear from you and no feed decides who sees your words. That makes it a calm place to teach, build trust and talk with the people who might buy from you later. Yet many newsletters stall after three issues, because they started with a tool instead of a reader.
This guide walks through starting one the other way around: reader first, promise second, software last.
Who is your newsletter for?#
Your newsletter is for one specific reader with one recurring problem, not for "anyone interested in my work". Name that person in a single sentence before you write anything. For example: "solo founders who sell a small course and struggle to write each week."
If you already wrote an ideal customer profile, reuse it. The person who would buy your product is usually the person who would read your newsletter, and the problems they keep asking about become your issue topics.
Vague
- My thoughts on business and life
- Sent whenever I have time
- Written for everyone
- Ends with a link to my product
Clear
- One pricing lesson for course creators
- Every Tuesday morning
- Written for one named reader
- Ends with one question to answer
What promise should your newsletter make?#
Your newsletter should promise one kind of value on one rhythm, in words a reader can repeat. "One teardown of a landing page every Thursday" is a promise. "Updates and insights" is not, because nobody knows what they get or when.
A good promise has three parts:
- What: the single type of thing each issue delivers (a lesson, a teardown, a checklist).
- For whom: the reader you named above.
- When: a day and a pace you can keep for a year, not a month.
Write the promise at the top of your sign-up page and repeat it in the welcome email. Then keep it. Every issue that matches the promise makes the next one more likely to be opened.
- Visits the sign-up page
- Subscribes
- Opens the issue
- Reads to the end
- Replies
Each stage keeps only part of the one before it. A clear promise helps at the top; a useful issue and a real question help at the bottom.
How do you write the first issue?#
Write the first issue as if it were your best one, because it is the issue that decides whether people open the second. Keep it short and give one complete win. A reader should finish it able to do something they could not do before.
- Frame 01One question
Pick a question your reader asked recently, in their own words.
- Frame 02One answer
Answer it in the first two lines, then explain why it works.
- Frame 03One example
Show the idea applied to a real case the reader recognises.
- Frame 04One step
Give a small action the reader can try in under fifteen minutes.
- Frame 05One question back
End by asking what they are stuck on. Their answer is your next issue.
Send it to people who already know you first: past customers, friends in your field, followers who replied to your posts. Ask personally whether they want it; never add anyone without permission. A small list of people who chose you is worth more than a large list that never asked.
How do you know your newsletter is working?#
Your newsletter is working when readers reply and stay, not when the list grows fastest. Open rates are a rough signal at best, since some email apps load messages automatically, so treat replies and unsubscribes as your main gauges in the first months.
Illustrative example, not measured data
Read the example from right to left. Six replies from two hundred readers looks small, but each reply is a person telling you exactly what they want to learn. Save every reply in one note and look for repeats. If you want help turning those questions into lessons, see education content marketing.
Summary#
Start a newsletter by naming one reader, making one clear promise on a rhythm you can keep, and writing a first issue that gives one complete win. Send it to people who chose to hear from you, end every issue with a question, and judge progress by replies more than by list size. When you want help drafting the posts that bring readers to your sign-up page, OpenCMO prepares drafts you approve and publish.