/hypotheses
Write down what you're assuming, so reality can correct you
Every product idea sits on a stack of beliefs about who, why, and how much. Naming them out loud — as statements that can actually be wrong — is the cheapest way to be less wrong before it gets expensive. The ones you don't want to write down are usually the ones you most need to.
👋 Hey, builder! Got a minute to help us shape our roadmap?
Take builder's survey
Surface the bets your idea is riding on
Every startup idea contains hidden assumptions about who has the problem, how painful it is, and whether anyone will pay to fix it. The advisor interrogates the idea — not you — to surface the specific, testable claims that are either true or they're not. Getting these wrong after building is expensive. Getting them wrong now is just learning.
The right test for every bet
Not all assumptions work the same way. A problem hypothesis needs conversations. A solution hypothesis needs a prototype. A willingness-to-pay hypothesis needs a pricing gate. Each hypothesis gets tagged by type and paired with the validation approach most likely to get you a real answer — not just a reassuring one.
Hypotheses that sharpen as you learn
As interview transcripts and survey results come in, the advisor links specific statements back to the hypotheses they support or challenge. Confidence builds across multiple sources, not a single conversation. When cross-interview patterns emerge, candidate new hypotheses surface automatically — so your model of the problem stays up to date.
See other features
startup superpowers