Launch Playbook for Solo Founders: One Person, One Channel at a Time
A solo founder should launch in one place at a time and finish each before starting the next. You have one set of hours, so every channel you add competes with the product and with replying to the people you just reached. Pick the single place where your users already talk, publish there, reply for two days, then decide what to add. Skip anything that needs a team to run.
What changes when nobody else can cover for you?
A team can split a launch: one person ships fixes, one answers comments, one writes the post. You are all three, and they need the same hours. The practical result is that a solo launch fails less from a weak product than from a maker who posted in five places on Tuesday and could not answer any of them by Thursday.
So the plan is built around capacity, not ambition. Before you pick a channel, count the hours you can really give, outside your paid work and sleep, for the next month. Most solo makers overestimate this number by half, because a launch adds interruptions, not just tasks: a comment at lunch, a bug report at night, a confused email on a Sunday.
How should you split a small pool of hours?
The split below is a planning budget for a person with about ten free hours a week, not a measurement of anything. Scale it up or down, but keep the order of the rows: reaching and replying come before building anything new.
| Job | Hours | Why it gets that much |
|---|---|---|
| Publish and prepare the page | 2 | One clear page and one tagged link per place you will post |
| Replying to people | 3 | A reply from the maker is the part no tool can do for you |
| Fixing what first visitors trip on | 3 | Two people stuck at one step means that step is broken |
| Looking for the next place to post | 1 | Reading threads, not posting yet |
| Writing down what you learned | 1 | Notes turn into copy and into a decision at month end |
Notice what is missing: new features. For the first month of a solo launch, build only what first visitors prove they need. The MVP scope planner helps you write the one-line boundary and defer the rest.
How do you choose the one channel to start with?
Use these rules in order and stop at the first that applies:
- If nobody knows you and you want a public page today, publish on the free launch board. It has no queue and no scheduled day, so it never asks you to clear a date in your calendar.
- If the product is a tool a developer can try in a minute, a Show HN post is the better first move, as long as you can stay near the thread for a few hours. Read the Show HN playbook first.
- If your users gather in one community, write a useful answer there before you mention the product. The community playbook covers how.
- If your users are searching for a fix right now, write one page that answers their exact query. It is slower, but it keeps working while you sleep, which suits one person.
Product Hunt-style daily races reward a crowd you can summon on a set day. If you have no crowd, they cost a week of prep for a day of competition, so treat them as a later experiment. The launch without an audience guide explains the channels that do not need one.
What does a realistic four-week solo schedule look like?
- Week one: publish and watch. Publish in your first place. Reply to every comment within a day. Do not post anywhere else yet. Note the three questions people ask most.
- Week two: fix, then add one place. Change the page to answer those three questions. Then add one second channel, chosen from the rules above, with its own tagged link.
- Week three: write the thing that keeps working. Turn your best reply into one short page on your site. One honest page beats a social post that disappears by evening.
- Week four: compare and cut. Look at visits, trials and conversations per link. Keep the one channel that produced conversations and stop the rest. The directory traffic calculator makes the comparison quick.
What should a solo founder not do?
- Skip paid queue-jumping. A lone maker has no spare cash or hours to justify paying to skip a queue before knowing the page converts.
- Skip multi-platform blasts. Eight posts on one day produce eight inboxes you cannot answer.
- Skip a launch video until a person asks for one. It eats a weekend and rarely changes the decision of a visitor who can try the product directly.
- Skip custom analytics dashboards. A table with visits and replies per tagged link is enough for the first month.
- Skip lonely guessing. Ask for a reaction in the discussion forum before posting widely.
When is it time to stop being solo?
Not at launch. Add help when a specific recurring job costs you more than a few hours a week and does not need your judgment, such as answering the same support question or testing a release. Hire or swap work for that job alone. Many micro SaaS ideas are small enough that one person can run them for years, so staying solo is a valid end state, not a stage to escape.
Before month two, read the pre-launch checklist once, then browse productivity app ideas for a quick sense of how other one-person products describe themselves in a sentence.
Frequently asked questions
How many hours does a solo founder need for a launch?
Plan on a month of small, steady effort rather than one big day. Around ten free hours a week is workable if most go to replying and fixing what visitors trip on. If you only have three, launch in one place and stay there, because spreading thin leaves every thread unanswered.
Is a solo founder at a disadvantage on Product Hunt?
On any daily ranking you compete against teams that can mobilise people in the first hours. A solo maker with no following starts behind there, so a free board with no queue, a Show HN post or a community answer usually costs fewer hours for a similar chance of a useful reaction.
Should a solo founder launch before the product is finished?
Yes, if a stranger can complete the main task. Waiting for polish costs hours you could spend learning from users. Ship the one workflow, say plainly what is missing, and let the first visitors tell you which gap matters. The unfinished-product answer page covers how to word that honestly.
How do I handle support while still building?
Batch it. Reply in two fixed windows a day, keep a note of repeated questions, and turn each repeat into a line on your page or an FAQ. When the same question stops arriving, the page has done its job and your reply time shrinks.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.