Startup Readiness Assessment

What a real readiness assessment tests

Startups fail on a small set of dimensions, and they fail in a small number of ways within each dimension. A real readiness assessment tests each dimension independently, with a published rubric, against behavioural evidence rather than opinion.

Those dimensions are the seven pillars of launch readiness:

• Problem clarity — does the customer recognise the problem in their own words?
• Target customer — can you name the specific person who buys?
• Demand signal — is there behavioural evidence beyond stated interest?
• Differentiation — would the customer switch from substitutes, and at what cost?
• Execution feasibility — can this team ship this product on this timeline?
• Distribution readiness — is there a tested channel at acceptable CAC (customer acquisition cost)?
• Monetisation viability — do the unit economics survive contact with real customers?

A weakness in any one is recoverable. Weaknesses in three or more usually predict failure even before launch — the pattern is consistent across the failure database, regardless of sector or business model.

Why per-pillar diagnosis beats a single score

If a generic AI tool tells you your idea scores 87, you do not know whether that came from 87 across the board (good) or from 100 on six pillars and 13 on demand signal (catastrophic). The composite hides the structural risk.

Once a founder sees 87, they round up: "great, my idea is validated." The thinking stops. The pressure-test never happened. Founders also learn to optimise their inputs for the score — the score goes up, the reality stays the same, and the idea ships into a market that has not changed.

A signal-strength diagnostic across pillars is harder to game and impossible to misread. "Your demand signal is Insufficient and your differentiation is Emerging" is unambiguous. There is no rounding up. There is, instead, a list of specific things to go and find evidence for.

What 'evidence' has to look like

The evidence bar is what separates a real assessment from a quiz. For each pillar, the framework defines what counts:

• For demand signal, behaviour counts — payments, pre-orders with cards on file, paid pilots, signups with measured conversion. Stated interest does not count.
• For target customer, specificity counts — a job title, company size, industry, and a situational trigger that a job ad could be written from. "SMBs" and "founders" do not count.
• For differentiation, cost-of-switching counts — a customer's stated reason to leave their current substitute, with the time, money, and migration costs honestly estimated.
• For distribution, measured conversion counts — one tested channel with a real CAC number from at least 30 real (not friend) customers.

This is the bar Launch Control evaluates against. It is also the bar that separates a real diagnostic from a confidence-shaped quiz.

When to run the assessment

Three moments where the assessment pays for itself many times over:

• Before you build. The cost of finding a gap pre-launch is days of work. The cost of finding it post-launch is months of runway. The framework is calibrated against the failure database — which is, by definition, the set of teams who skipped this step.
• Before you raise. Investors ask the same questions the assessment asks. Better to surface the weak pillars yourself, on your own time, than discover them mid-pitch when the answer matters more.
• Before you pivot. A pivot is a new startup. Re-run the assessment on the new idea — the dimensions that were strong on the old idea are not automatically strong on the new one.

What the output looks like

The diagnostic resolves into one of four signal strength levels — Strong, Emerging, Weak, or Insufficient Validation — plus a per-pillar signal-strength reading and a written explanation of which gaps need closing and what evidence would close them.

The signal strength level is the headline. The per-pillar diagnosis is the actionable part — it tells you exactly which dimension is the rate-limiter and what to go and find. Most founders close one or two pillars per cycle and re-run the assessment to confirm; that loop is what turns "interesting idea" into a "buildable startup."

How to actually run it

Launch Control runs the structured assessment in 30 to 45 minutes. Three free trial credits on signup, no card required. The first run usually surfaces at least one pillar weakness the founder did not see — that is the system working, not failing.

Bring whatever you have today. The framework handles thin inputs by flagging them as Insufficient — that flag is the homework, and the homework is more valuable than a number.