Many founders picture a launch as one big day: you post the link, the attention arrives, and the product takes off. Then the day comes, a few friends react, and by evening the post has scrolled away. The disappointment is so common that some founders stop launching altogether.
The problem is usually not the product. It is treating the launch as a single moment instead of a short plan with a before, a during and an after. This playbook gives you that plan, sized for one person with a day job's worth of time.
What is a product launch plan?#
A product launch plan is a short schedule of what you share, with whom, and when, from a few weeks before release to a few weeks after. Its goal is simple: when the product goes live, people who already care are waiting for it, and the people who try it tell you what to fix next.
Most launch advice is written for teams with a budget. A solo founder has a different strength: you can talk to every early user yourself. A good plan leans on that. Instead of trying to reach everyone on one day, you reach the right few people several times.
Launch as one day
- Silence until the link goes out
- Posted to strangers first
- All attention lands in a few hours
- Over when the post scrolls away
Launch as a plan
- Weeks of sharing the problem first
- A warm list hears about it first
- Attention arrives in several waves
- Each update becomes a new launch
When should you start planning a launch?#
Start about four weeks before you want to launch. That is enough time to share the problem in public, collect a list of people who want to hear about the release, and fix your page based on their questions. It is short enough that you won't lose momentum.
- Frame 01Week 1
Share the problem, not the product. Post what you learned from people who have it.
- Frame 02Week 2
Show work in progress. Invite anyone interested to join a short list for launch day.
- Frame 03Week 3
Give a few people early access. Fix the biggest confusion they hit.
- Frame 04Week 4
Finish the page with their words. Write launch posts and the email to your list.
- Frame 05Launch
Email the list first, then post in the places your buyers gather. Reply to everyone.
Two habits make the runway work. First, share the problem more than the product. A post about why freelancers chase late invoices interests the right reader; a post about your new reminder feature only interests people who already know you. Second, give people a way to raise their hand: a short sign-up for launch news, or simply "reply and I'll send you the link". Every hand raised is someone who will see your launch on day one.
Your launch page deserves time in week four. The headline should tell a visitor what the product does and who it is for in one look. Our landing page headline tips cover how to write and test it quickly.
Who should you tell first?#
Tell the people who asked to hear about it first, then the communities your buyers already use, and strangers last. The order matters because early reactions shape what happens next. A post that gets a few thoughtful comments early tends to travel further than one that sits silent.
- Your list. Everyone who raised their hand during the runway. Send them a personal email or message, with the link and one line on what to try first.
- Early users. People who tested it in week three. Ask them to share honest feedback publicly if they found it useful.
- Your own channels. Your posts on X, your newsletter, your profile. If you don't have a newsletter yet, our guide to starting a newsletter people open is worth reading before your next launch.
- Communities. Places where your buyers already talk. Follow each community's rules, add something useful to the conversation, and never post the same message everywhere.
What should you do on launch day?#
On launch day, send your messages early, then spend the rest of the day replying. The replies are the launch. Each thoughtful answer to a question shows future users how you treat customers, and each comment you answer keeps the conversation visible a little longer.
| When | What to do |
|---|---|
| Morning | Email your list. Publish your launch post on your main channel. |
| First hours | Reply to every comment and email. Fix any broken link or sign-up issue at once. |
| Midday | Share in one or two communities, adapted to each one. |
| Evening | Write down every question and complaint. These become your next posts and fixes. |
Expect attention to come in waves, not one spike. The first wave comes from your list. Later waves come from people your early users told, and from posts you write about what happened. That is why it pays to keep going after day one.
- Day 1
- Day 2
- Day 3
- Day 4
- Day 5
- Day 6
- Day 7
| Day 1 | 42 sign-ups |
|---|---|
| Day 2 | 18 sign-ups |
| Day 3 | 11 sign-ups |
| Day 4 | 24 sign-ups |
| Day 5 | 9 sign-ups |
| Day 6 | 7 sign-ups |
| Day 7 | 15 sign-ups |
Illustrative example, not measured data
In an example like this one, day one is the biggest, but it isn't the whole story. The bump on day four might come from a follow-up post about what users asked, and the one on day seven from an early user sharing their own result. Plan for those second and third waves on purpose.
What should you do after the launch?#
After the launch, turn what you learned into the next round: fix what users found, write about it, and launch again when you have a meaningful update. A solo founder rarely wins with one launch. They win by launching often, each time to a slightly larger and warmer group.
- Share the problem
- Build a small list
- Launch to them first
- Learn from replies
- Ship an update
Every update is a reason to launch again. Each turn starts with more people who already care.
Good reasons to launch again include a feature users asked for, a new kind of customer you can now serve, or a big improvement to something that confused people. Each one gets a smaller version of the same plan: a week of sharing, a message to your list, a day of replies. If you are selling a course instead of software, the same loop applies; our playbook on how to presell an online course shows the first turn.
Summary#
A solo founder's launch works best as a short plan, not a single day. Spend about four weeks sharing the problem and building a small list. On launch day, tell that list first, then your own channels and communities, and spend the day replying. Afterwards, fix what people found and launch again with each real update. If you want help drafting the posts for each stage, OpenCMO drafts posts you approve and publish.