54% of indie startups reportedly made $0 in 2026. That figure is hard to scroll past when you build software on your own, because it raises a direct question about the order of work. If so many startups brought in no revenue, how much effort went into making products before anyone knew whether a customer would pay?
The familiar sequence is easy to follow. Start with a product idea. Add features. Polish what is there. Spend another week making it feel finished. Each step produces something visible, so the work can feel like progress. Yet the question that determines whether all that work matters may still be waiting for an answer: will someone pay for this?
That gap is where the statistic lands for me. It reportedly represents 8,817 startups in 2026. I do not know what happened inside each one, and the figure alone cannot explain why any particular startup made no money. It does make the risk of delaying the payment question difficult to ignore. Independent builders have limited time, and every extra round of product work uses some of it.
The mechanism is about what building work can tell you. More features can make a product more capable, and polish can make it feel closer to finished. Neither gives you direct evidence that the person you have in mind wants the offer enough to pay. If you keep building before asking, you can improve the product while leaving its biggest assumption untouched.
So I would move the payment question closer to the front: show someone the thing, ask for the sale, and see what happens. Their response gives the next build a real point of reference. Maybe the product needs work. Maybe the offer does. Maybe the person you had in mind does not care. Any of those answers can shape what you do next, and you can learn them before committing to another round of building.
The rule I am adopting is simple: put revenue on the task list while the product is still taking shape. Testing whether someone will pay does not require you to declare the product finished. It gives you a chance to learn whether the thing you are making connects with a buyer while you can still change what you are making.
If you are building independently, look at the next feature or polish task and ask what assumption it will answer. If the answer is only about how the product works or feels, consider showing it to someone and asking for a purchase first. Treat the response as information for the next decision. A sale, a concern, or a lack of interest can all help you decide whether to build, revise the offer, or reconsider who you are building for.