Should I Launch Now or Wait Until It's Ready?

The word "ready" is the problem. Founders who ask whether the product is ready have already accepted a framework that will lead them to the wrong answer. A product is never ready. The question is whether it is honest.

By honest I mean: does the product do the thing you claim it does, for the person you claim it serves, in a way that does not embarrass you when they use it? That is a much lower bar than "ready," and it is the right bar. An honest product is one that you can put in front of a real user without managing their experience, without explaining what they should click, without apologies for missing features that matter. If you have to be in the room to make the product work, the product is not honest.

The reason founders wait too long to launch is not perfectionism in the noble sense. It is perfectionism in the cowardly sense. They are building a product for an imaginary user — a user who will understand the vision, forgive the gaps, and use the tool the way it was intended to be used. Real users are not like that. Real users will click the wrong button, misunderstand the core use case, and tell you things about your product that you would rather not hear. Launching means inviting those users into the process. Waiting means protecting yourself from what they have to tell you.

The products I am most proud of were launched when they were honest, not when they were perfect. The first Mac was not everything I imagined it could be. But it did what it claimed to do, it did it with integrity, and it changed what users understood computers to be. Every subsequent improvement was shaped by what real users did with the honest first version — not by what we imagined they would do in the six months we would have spent waiting.

My counsel is this: when you can put the product in front of a real user without being in the room, without managing their experience, and without apologizing for what is missing — launch. The day after you can meet that standard is the day you are waiting.

Jobs describes the product's honesty as the threshold. I want to describe the founder's readiness for what comes after the launch — which is the part that most founders have not genuinely prepared for.

I spent years in campaign — in the field, managing armies and logistics and alliances — before I felt anything like readiness for what each new campaign would bring. And every time I discovered I was not ready: I was not ready for the way the enemy adapted, not ready for the way my own generals' limitations showed under new pressure, not ready for the combination of conditions I had not anticipated. What I had was not readiness. I had the discipline to act when readiness was not available.

The launch is not the hard part. The hard part is what you do with what the launch reveals. Most founders who are waiting for the product to be "ready" are actually waiting for the feedback from real users to be manageable — for the gap between what they built and what users need to be small enough that the feedback is encouraging rather than disorienting. This is not a product question. It is a character question about whether you are prepared to hear hard things and act on them.

I have watched founders launch when their product was honest — Jobs's standard — and then fail to do anything useful with the signal that came back. The launch revealed that the core use case was not the use case their early users cared about. The feedback was clear. But the founders were not prepared to act on what they heard because they had spent so long optimizing for a frame that the feedback contradicted. The launch happened at the right time. The response to the launch happened at the wrong pace.

My counsel is not about when to launch. It is about whether you have done the internal work of preparing yourself to be genuinely changed by what the launch tells you. If you have, launch when Jobs's honesty threshold is met. If you have not, the launch will be real but its value will be wasted because you are not yet ready to receive what it brings.

Both my colleagues have addressed the right questions about the founder's relationship to the launch. What neither has addressed rigorously is the empirical question: what specific signal will this launch generate, and is it the signal you actually need?

I am precise about measurement because imprecision about measurement is how scientists — and founders — reach conclusions that the data does not support. The launch that generates no interpretable signal is worse than no launch at all. It consumes attention, creates noise, and produces a false confidence that the product has been tested in the market when it has actually been exposed to a set of users whose response cannot be cleanly interpreted.

The signal question has two components. The first is: who will the launch reach? If the product launches to a general audience whose relationship to the core use case is heterogeneous, the signal will be too mixed to act on. The founder who launches to everyone and gets average reviews has learned nothing useful. The founder who launches to the specific segment most likely to care and gets a clear positive or negative signal has learned something actionable.

The second component is: what specific question does the launch answer? A launch that is intended to validate product-market fit must be designed to measure product-market fit — not vanity metrics like signups or page views, but the behavioral signals that indicate whether users return without prompting, whether they use the product in ways that reveal real dependency, whether they refer others in ways that suggest genuine enthusiasm rather than polite support. If the launch is not designed to answer a specific question with measurable precision, it is not an experiment. It is a performance.

My counsel: before you ask whether the product is ready to launch, ask what specific question the launch is designed to answer and whether you have designed the measurement to give you an interpretable answer. A launch that is not designed to generate specific signal is premature regardless of how ready the product feels.