What is launch readiness?

Launch readiness is how prepared a just-shipped product is to win its first real users, not how finished the product is. It is the gap between “the code works” and “a stranger can find this, understand it, and trust it enough to try.” Those are two different jobs, and most builders, especially now that AI tools make shipping fast, only finish the first one. This guide gives you the plain definition, the two halves launch readiness splits into, why one half is weighted heavier, and the honest limit of what a high score buys you.

01 · The gapWhy "built" isn't "launched"

“Built” measures your product against your own spec: the features work, the bugs are closed, the design looks right. “Launched” measures it against a world that has never heard of you and was not waiting. Those are different finish lines, and clearing the first does nothing to clear the second.

This is why the most common founder experience is a product that is genuinely good and has genuinely no users. Nothing is broken. The product simply has no launch readiness: no stranger can find it, and the few who land cannot tell what it does or why they would trust it. The work that closes that gap is a separate discipline from the work that closed the product, and it rarely gets done because it does not feel like building. We give that thesis its own treatment in built isn’t launched.

02 · The definitionA plain definition

The shortest version: launch readiness shifts the question from “is my product done?” to “is my product findable and legible to someone who has never heard of it?” A product can pass the first test completely and fail the second completely. It is not one toggle either. It is a stack of signals that sorts cleanly into two halves.

03 · The two barsThe two bars: Readiness and Footprint

Launch readiness is two numbers, not one. Nilkick reports them as separate bars because they fail independently and you fix them differently.

Readiness is the page itself: sharp, clear, and machine-parseable. Footprint is everything off the page: whether you are indexed, whether you own your own name in search, whether anyone anywhere references you. A product needs both. A flawless page nobody has heard of is invisible; a well-known mess converts no one. The mechanics of the split, and how to tell which bar is sinking you, get their own guide in readiness vs footprint.

04 · The weightingWhy footprint carries more weight

Nilkick weights the final score 40% Readiness and 60% Footprint. That is deliberate, and it is the opposite of where most builders spend their time.

Readiness is the easy half. It is fully in your control, it has a clear ceiling, and almost every item is a concrete fix you can ship in an afternoon: write a real H1, add the meta tags, server-render the content. Once it is done, it is done. Footprint is the hard half: it is slower, it depends on other people and other sites, it has no ceiling, and it is the half that actually determines whether a single person ever arrives. You can max your Readiness bar in a weekend and still have zero users, because a perfect page that nothing links to and no one searches for is a perfect page no one sees.

So the weighting reflects reality: the controllable, bounded half is worth less to your outcome than the slow, unbounded one. That is also why distribution, not the product, is the wall most launches hit.

05 · Necessary, not sufficientWhat it does not promise

Launch readiness makes you findable, legible, and credible. It does not make you wanted.

This is the part most readiness tools skip, because “you also need a product people actually want” does not sell a scanner. But it is the honest boundary. Clearing your readiness checks removes the silent blockers that were costing you the users you could have had. It cannot generate demand that was never there. The single most-cited reason products fail is not a broken page or a missing meta tag; it is no real market need, which CB Insights puts behind roughly 42% of startup post-mortems. Launch readiness is the floor you clear so that a product people do want is not held back by problems you could have fixed. Treat it as necessary groundwork, not a growth strategy.

06 · Check itWhere you actually stand

You do not have to guess which half is failing. A readiness check scores both bars and, more usefully, separates them, so you can see whether your problem is the page (Readiness) or the obscurity (Footprint). On a brand-new product, expect the Footprint bar to be the low one. That is the normal starting state, not a verdict on your work, and almost every gap it surfaces is a named, shippable fix rather than a vague “do more marketing.”

The practical next step is to read the number correctly: what the composite score means, what each bar is telling you, and what to fix first. That is covered in how to read your readiness score, and the bare-minimum version of the work is in the zero-to-handful checklist.