What a decision-making tool for founders should actually do
A decision-making tool for founders should do four things a generic chatbot does not. It should surface the named operator framework instead of the internet's average, show you both sides of a real fork instead of one confident answer, apply the answer to your stage and situation, and record your reasoning so you can revisit the call when things change. That last one, a decision journal you can audit, is what separates a tool you decide with from a chat you forget. Below is each criterion, cited, plus the build-versus-distribution fork a good tool should show both sides of.
Why this matters. Founders make dozens of consequential calls with no record of why, then relitigate them from scratch six months later. A tool that keeps the framework, the fork, and the reasoning turns a decision into something you can actually revisit.
Bring a real decision. Gavel cites the framework, shows the fork, and keeps the reasoning you can revisit.