Startup Idea Stress-Test
Pressure-test a startup idea before you commit a year of your life.
A go / refine / drop verdict with the riskiest assumptions named.
Everyone a founder normally asks — friends, family, other founders — is structurally incentivised to encourage. This council is not. The Sceptical Investor has seen a hundred versions of the idea and asks what kills this one; the Pre-Mortem Analyst starts from “it failed — why?”; the First-Principles Thinker strips the pitch to what must be true; and the End-User Advocate asks whether the supposed customer feels the pain weekly or just nods politely. Sun Tzu weighs the terrain: who already owns the ground you want.
Stress-test this startup idea. I want a real fight about it, not encouragement. THE IDEA: [describe the idea, the problem it solves, and for whom] WHY NOW: [what makes this the right moment] THE WEDGE: [the narrow first beachhead] HOW IT MAKES MONEY: [the model] WHY ME / US: [unfair advantage, if any] Debate: 1. Is this a real, painful, frequent problem — or a vitamin nobody will pay for. 2. The riskiest assumption the whole idea rests on. 3. Market size and whether this can be big, or is a nice lifestyle business. 4. The wedge and whether it actually expands. 5. Why this might already exist, or why it has failed before. 6. The cheapest experiment to validate or kill it in two weeks. FINAL SYNTHESIS: - A verdict: GO, REFINE (with what to change), or DROP. - The two or three assumptions that must be true, ranked. - The single experiment to run next, and what result would change the verdict.
An illustrative excerpt for a hypothetical brief of this type: A first-time founder wants to spend a year building a marketplace that matches home cooks with nearby customers for weeknight meal pickup. Every real run is generated fresh from your specifics, debated across rounds, and audited before the verdict.
Both sides of this marketplace have a cheaper alternative already in their pocket: the customer has supermarket ready-meals and delivery apps; the cook has a WhatsApp group and a Saturday market stall. The question is not whether the idea is nice — it is which of those two walks past their existing habit, weekly, for this.
The cold-start problem is squared here because supply is hyper-local: twenty cooks in the wrong suburb is zero supply where your first customers live. And the regulatory surface — home-kitchen food safety — is the kind of thing that does not matter until the week it shuts you down. I want the wedge narrowed to one postcode and one cuisine before a line of code.
Working backwards from failure, month eighteen: it did not die from competition, it died from repeat rate. Occasion-based food purchases spike at launch from novelty, then decay. The kill-metric to define now: if fewer than a meaningful fraction of first-time buyers reorder within a month, the habit does not exist and no amount of supply fixes it.
Strip the platform away and the core claim is: home-cooked dinner nearby is enough better than the alternatives that people will change routine and pay a premium for it. That claim is testable in two weeks with a spreadsheet, one street, and zero engineering. The verdict should hinge on that test, not on anyone’s taste for marketplaces.
Prefer drop-and-go? Use the AI Business Idea Review tool — team pre-seated, included with Plus.
Will this just talk me out of my idea?
No — the format forces a verdict of GO, REFINE or DROP, and a GO from a council designed to kill weak ideas means something. What you actually get is the ranked list of assumptions that must be true, and the cheapest two-week experiment to test the fragile one — which is worth more than encouragement either way.
My idea is early and vague — is it too soon to stress-test it?
Earlier is better: the debate costs an evening, a year of building costs a year. Vague inputs produce one predictable finding — the council will tell you which part is too vague to evaluate, and that is itself the next piece of work. Founders typically re-run the brief after each refinement.
I’m worried about sharing the idea — is it confidential, and could the AI steal it?
Your brief is not used to train models and is processed only to run your council — see the security page for how sessions are handled. On the broader fear: ideas are rarely the scarce asset, execution is, and the fastest way to lose a year is refusing scrutiny of a fragile assumption.