Why our startup idea report gives no single score
A single score hides what an idea rests on and invites false comparisons. What Startup Intelligence shows instead: ranges, evidence rungs and stop points.
Startup Intelligence
Practical guides, each checked against the product.
A single score hides what an idea rests on and invites false comparisons. What Startup Intelligence shows instead: ranges, evidence rungs and stop points.
If your idea is this good, why has nobody done it? How to answer why now, what compounds, what is melting and whether the downside is bounded.
What you submit to Startup Intelligence, where it is stored today, who can see it, the planned move to India, and what to ask us about your data.
Why Startup Intelligence refuses ideas with too little detail, the minimum it needs, how to add it, and why a refusal beats a confident guess.
The nine stages of a Startup Intelligence run, from your idea to the finished report: what each stage does, why runs go one at a time, and what you can watch.
Six questions to ask any startup idea validator before you trust its report, and our own honest answers for Startup Intelligence, limits included.
Five common ways to stress a startup idea compared: asking people, a spreadsheet, a premortem, a one-page canvas and a de-risking report. What each catches.
What a load-bearing assumption is, how to find the few that decide your startup's outcome, and how to write each one so it can be tested.
A kill threshold is the result that would make you stop. How to set one before you test, read results against it, and tell stopping apart from pivoting.
Why a common frame helps incubators review startup ideas fairly, what to compare across ideas, and what no report can decide for a review panel.
Start with assumptions, not features: find the few your idea rests on, grade the evidence, set a stop point and run the cheapest experiment first.
A short slot with a review panel goes further with five things: your claims, the assumptions behind them, your bar, your stop points and your tests.
Friends say they love it; strangers say they would use it. Why kind answers carry little information, and how tests designed to break the idea tell you more.
Most forecasts can never be checked because nobody wrote down a range, a date and the reasons. How to record yours, and what a report records for you.
How to match a cheap experiment to your riskiest assumption, set a pass mark before you start, and act on the result instead of explaining it away.
The assumptions that sink plans are often the ones nobody doubts: market share, channel cost, cost to serve, retention. How to find them by working backwards.