Startup Readiness Score

What startup readiness actually measures

Readiness is not confidence. It is the amount of independent evidence you hold that the thing you are about to build will be wanted, reachable, buildable and payable. Founders routinely score highly on solution clarity and badly on customer access, which is exactly the pattern that produces a beautiful product nobody sees.

The five sections in this score map to the five ways early companies actually die: solving a problem nobody has, being unable to find the people who have it, building too much, running out of time or skill, and having no route to the first ten customers.

Each answer is scored against what evidence would satisfy a sceptical investor, not what feels reasonable at 11pm. That is deliberate. The score is more useful when it is uncomfortable.

The evidence bar that matters most

If you only fix one thing, fix the commitment question. Verbal enthusiasm is the cheapest signal in existence and the one founders over-weight most. A signed pilot agreement, a paid deposit or a letter of intent costs the customer something, which is precisely why it means something.

With Co-Ride, the pre-seed carpooling platform I started in November 2025, the useful early signal was not survey interest in shared journeys. It was whether people would commit to a specific journey on a specific date. Intent expressed in the abstract is close to worthless.

Behavioural evidence is also faster to gather than most founders expect. A landing page with a real commitment step, forty targeted conversations and two weeks will usually settle the question.

Why runway and focus are in a readiness score

• A six-week MVP built by someone working evenings takes five months, and five months of drift changes the market you validated.
• Under three months of runway changes every product decision into a fundraising decision, and it shows in the product.
• One named acquisition channel beats five hypothetical ones, because you can actually test it before launch.
• Undecided pricing is a scope problem in disguise: you cannot cut features sensibly if you do not know what the product is worth.

What a good next step looks like at each band

At idea stage, the correct next action is almost never design or code. It is fifteen conversations and a written problem statement. That work costs nothing but time and routinely saves a five-figure build.

In the evidence-gaps band, resist the temptation to fix everything. Take your three weakest answers and close those. Broad improvement across fifteen dimensions is slower and less useful than depth on the three that are actually blocking.

Once you are build-ready, the risk profile inverts. The threat is no longer ignorance, it is scope. Fix the release to a single user journey, agree the launch metric before the first commit, and treat every addition as a decision that costs a week.

The full sequence, with timeboxes and kill-or-continue decisions at each stage, is set out in The Crossley Method.