Built isn't launched: why a finished product still has zero users

A finished product with zero users is not broken. It is undistributed, and often unvalidated, which feels the same from the outside but is a completely different problem with a completely different fix. The instinct is to assume something is wrong with the product and go back to building. Usually nothing is wrong with the product. The launch simply never happened, because shipping the code and launching the thing are two separate jobs and you have only done one.

01 · Done vs launchedTwo different finish lines

“Done” is an internal verdict. It measures the product against your spec: the features work, the edge cases are handled, the UI is tidy. You can declare it alone, at your desk, and be right.

“Launched” is an external verdict, and you cannot declare it yourself. It measures the product against a world that has never heard of you: can a stranger find it, work out what it does in a few seconds, and find any reason to trust it enough to try. Every part of that test is decided by other people. Passing the “done” test tells you nothing about the “launched” test, because they grade different things. This is the whole idea behind launch readiness: being built is the half you control, and it is not the half that gets you users.

02 · The cheap-to-build eraWhy this is now the default

There was a time when finishing a working product was hard enough that finishing it felt like most of the battle. That time is over. AI coding tools collapsed the cost of building, so more products ship, faster, than ever before. The result is that “finished but invisible” has gone from an edge case to the default state of a new product.

That cuts two ways, and the honest version matters. Building being cheap means your finished product is no longer rare or impressive on its own; thousands of equally finished products shipped the same week. The scarce thing is no longer the build. It is attention, and a reason to be trusted. Which means the part you have not done, distribution, is now the entire contest. We make that argument in full in distribution is the wall.

03 · The wrong instinctThe trap: fixing it by building more

Faced with zero users, the builder’s reflex is to open the editor and add something. A new feature, a redesign, another integration. It feels productive because building is the thing you know how to do, and shipping produces a visible diff.

It is almost always the wrong move at zero users. Adding features assumes the product is why nobody came, but at zero users you have no evidence of that, because nobody has used it enough to tell you. The far more likely reasons are that strangers cannot find you, or land and cannot tell what you do. More features turns an invisible product into a more polished invisible product. The same effort spent on clarity and distribution would actually move the number.

04 · The other disciplineWhat actually closes the gap

Launching is its own discipline, and the reason it gets skipped is that none of it feels like building. It breaks into roughly four jobs, none of which involve your editor: make the page clear enough that a stranger gets it in five seconds, make it findable (real title, link previews, metadata), get indexed so you exist in search at all, and get referenced somewhere other than your own domain so an algorithm or a person has a reason to surface you.

That work is unglamorous, slow, and mostly text and legwork rather than code. It is also the difference between a product that is built and a product that is launched. The zero-to-handful checklist lays out the minimum version of it.