Your riskiest assumption is the belief your whole idea depends on most that you're least sure is actually true. To find it, list everything that has to hold for the idea to work, rate each one by how badly it hurts if it's wrong and how confident you really are, and the highest impact-times-uncertainty is the one to test first — before you build anything.
Every idea sits on a stack of beliefs that all have to be true at once: that a specific person has this problem, that they'll pay to solve it, that you can reach them affordably, that you can actually build it. Your riskiest assumption is the one where being wrong is fatal and you have the least real evidence either way. It's not your biggest worry — it's the quiet belief the whole thing silently rests on.
Founders avoid naming it precisely because it's load-bearing. If it's false, the idea is over, so it's more comfortable to work on the parts you can already do. That's exactly backwards: the scariest assumption is the one worth testing first, while changing your mind is still cheap.
Write the idea as a sentence, then list every belief it depends on as a plain claim: "solo bookkeepers lose hours chasing invoices," "they'll pay $30/month to automate it," "I can reach them through accounting subreddits," "I can build the integrations." Get them all out — demand, willingness to pay, reachability, feasibility, and anything else the idea quietly needs.
Be specific and falsifiable. "People want this" can't be tested; "a solo bookkeeper will enter a card to automate invoice chasing" can. The more concrete each claim, the easier it is to rank and the cheaper it is to check.
Score each claim on two axes: how much it hurts if it's wrong (impact) and how unsure you genuinely are (uncertainty). Multiply them. The highest score is your riskiest assumption — usually a demand or willingness-to-pay belief, almost never the technology. That's the one to test this week.
Design the smallest experiment that could prove it false: ten honest customer conversations, a landing page with a real buy button and paid traffic, a pre-order, a paid pilot. Decide the pass/fail line before you run it. If it fails, you've saved months; if it survives, you've earned the right to test the next one. Keep going down the list — validation is a loop, not a one-time gate.
Try it now
Free worksheet — find the assumption most likely to kill your idea
It's the belief your idea most depends on that you're least sure is true — usually that a specific person will pay to solve a specific problem. If it turns out false, the idea doesn't work, which is why it's the first thing worth testing rather than the last.
Design the cheapest experiment that could prove it wrong, and set the pass/fail line before you start. For demand, that's 10–20 honest customer conversations or a landing page with a real buy button and paid traffic; for willingness to pay, a pre-order or paid pilot. Measure behaviour, not compliments.
Rarely. Most ideas die because nobody wanted the thing badly enough to pay, not because it couldn't be built. The riskiest assumption is almost always about demand or willingness to pay — test that before you write much code.
Skip the guesswork. Kasspian is your honest AI business co-founder — it validates your idea, builds your business pack, and gets you paying customers.
Try it freeOne week, a dead startup and why it died. The next, a play to get your next customers.
No fluff, no spam. Unsubscribe anytime.