The Indie Hacker Launch Playbook
A launch plan that assumes no team, no budget, and no audience — and still produces real users on the day.
One person, no budget, and a launch that still works
Most launch advice assumes resources that solo founders do not have: a team to run channels in parallel, a budget to buy attention, an audience accumulated over years. Stripped of those, the instinct is either to imitate the playbook badly across too many channels, or to conclude that launching properly is for companies and to simply ship quietly.
Neither is necessary. A solo launch works on different principles — concentration instead of coverage, presence instead of spend — and it produces real users on the day when it is planned around what one person can actually do.
The polishing trap
The most expensive habit in indie development is refining in private. Every additional week of polish delays the only thing that reliably improves the product, which is contact with people who are not you. Founders lose months this way and almost never lose anything comparable by launching something rough.
The useful discipline is to ship at the point of embarrassment — the version that solves the core problem for one type of user, described honestly, limits included. Honest framing costs you nothing with the audience that matters and saves you from the disappointment that a rough product oversold generates.
Write the post first
A surprisingly effective test: write the launch announcement before the product is finished. If the paragraph will not come out compelling, the problem is almost never the copy. It is that the positioning is vague, or the audience is undefined, or the product does several things and no single one of them well.
Discovering this while you can still change the product is worth far more than discovering it the night before launch, when all you can change is the wording.
Three channels, done properly
Coverage is a strategy for teams. One person attempting thirty channels produces thirty half-efforts, all of them visible as such. One scheduled placement, one community where you already have standing, and one owned channel is a plan a single person can execute well on the day.
The scheduled placement matters most because it is the only one whose existence does not depend on someone else's algorithm or a moderator's judgement that morning. It gives the launch a floor and, just as usefully, a deadline.
Presence is the advantage you actually have
You cannot outspend anyone. You can out-respond everyone. A founder answering every comment thoughtfully within minutes, all day, converts skeptics at a rate no company account achieves — and on most platforms that engagement directly feeds the ranking that brings more visitors.
Capture something, then plan the next one
Launch traffic is borrowed and it leaves. Without an email field or a community invite, a successful day returns you to exactly where you started. And plan the second launch now: almost no indie product succeeds on the first, and the second — with feedback, testimonials, and a sharper pitch — is usually the one that works.
The playbook
Ship at embarrassing rather than at perfect
The version you are embarrassed by usually still solves the problem, and shipping it starts the feedback loop months earlier. Solo founders lose far more to polishing in private than they ever lose to launching something rough with an honest description of its limits.
Write the launch post before you finish building
If you cannot write a compelling paragraph about what this does and who it is for, the problem is the positioning, not the copy. Writing it early surfaces that while there is still time to change the product rather than the wording.
Pick three places, not thirty
With no team, a launch spread across thirty channels becomes thirty half-efforts. Choose one scheduled placement, one community where you already have standing, and one owned channel, and do those three properly.
Spend the week before earning the right to post
The communities most worth launching in are the ones that remove drive-by promotion. A week of genuine participation in the run-up is a real prerequisite, not a nicety — and it is work you can do while the last features land.
Be present all day, because that is your advantage
You cannot outspend anyone, but you can out-respond everyone. A solo founder replying thoughtfully to every comment within minutes converts skeptics at a rate no company account manages, and the engagement itself lifts your ranking wherever you posted.
Capture something durable from the spike
Launch traffic is borrowed and it leaves. An email field, a community invite, or a follow is what converts a single day of attention into something you can use next month. Without it, a successful launch leaves you exactly where you started.
Plan the second launch now
Almost no indie product succeeds on one launch. Treat the first as the beginning of a sequence — a major feature, a rebuild, a new audience are all legitimate reasons to launch again, and the second attempt is usually better than the first.