Building is the part indie hackers are good at. It is also the part that matters least to whether the product makes money.
The failure mode
The common story: six months building, a launch day, a spike of a few hundred visitors, twelve signups, two paying customers, and then silence. The product works. The code is good. Nobody knows it exists and there is no mechanism by which they would find out.
The mistake was made at the start, not at the launch. The product was chosen for what would be interesting to build rather than for whether the person building it had any way to reach the people who would pay for it.
Choose for distribution, not for interest
Before writing anything, answer: where do the people with this problem already gather, and can I reach them?
Good answers are specific. A subreddit you already read. A tool whose users you can reach through its integration directory. A search query with real volume that nobody has answered well. A newsletter whose author would plausibly mention you.
Bad answers: "on social media", "SEO", "word of mouth". Those are categories, not channels.
If you cannot name a specific place, the product will be built and then not sold. That is the whole failure in one sentence.
Charge from day one
Free tiers with a "we'll monetise later" plan mostly produce users who would never pay, and the feedback from someone who paid nothing is worth roughly what they paid.
Charging immediately gives you the only signal that matters. Ten paying customers at $20 tells you more than a thousand free signups, and it tells you in week two rather than month nine.
Price higher than feels comfortable. Almost every indie product is underpriced, and the churn cost of a higher price is consistently smaller than founders expect.
Scope to six weeks
If the first version takes longer than about six weeks of real work, the scope is wrong. Not because speed is virtuous, but because a longer build means a longer time before you learn whether anyone wants it - and that is the only clock that matters.
Cut until it fits. The feature you are certain is essential is usually the one nobody asks about.
Decide when to stop, in advance
Write down, before launch, the result that would make you stop. "If I have fewer than 10 paying customers after three months of active selling, I stop."
Without that line you will keep going out of sunk cost, and the cost is not the money - it is the two years you did not spend on the thing that would have worked.
What compounds
Three assets keep paying long after launch week:
A tool other people link to. It earns links passively and ranks for a query with real volume.
A number nobody else publishes. Aggregate something from your own data. It is the most reliable way for a small team to earn coverage.
Search-facing content that answers a real question. Slow, and the only channel that grows while you sleep.
Free toolSEO CheckerRun eleven on-page checks against any URL: title, description, canonical, headings, alt text, Open Graph, word count and indexability, with the exact fixes.What does not
Launch-day spikes, follower counts, and being active in communities without shipping anything. All three feel like progress and none of them compound.
The uncomfortable test: if you launched tomorrow and got zero traffic from the launch itself, is there any mechanism by which a stranger finds your product in month three? If the answer is no, build that mechanism before building more features.
Launch it where the numbers are checked
RankCert ranks products on domain control we verify ourselves. Listing is free and the link stays dofollow whether or not you display the badge.