Before you can build
Kill bad ideas early
I’m a solo builder, and I kept running into the same problem over and over:
I’d get excited about an idea, start building, and only months later realize the flaws were obvious in hindsight.
Most “idea validation” tools I found were designed to encourage you to keep going—often because they want to sell development, coaching, or services. That incentive never sat right with me.
So I built Before You Can Build.
You paste in an idea, and it stress-tests it for real risks and assumptions. Sometimes it gives a cautious “go,” and sometimes it gives a straight KILL verdict. There’s no upsell to development and no reason for it to be optimistic—the goal is to surface problems early, not motivate you to push through them.
It’s not meant to replace talking to users or building MVPs. It’s more like a first filter before you invest serious time.
There’s a free pre-check, and a paid full report if you want deeper analysis.
I’d genuinely love feedback from other indie builders:
Would you actually use something like this?
What would make you trust (or not trust) a tool that’s willing to say “don’t build it”?
Where do you think this breaks down?
Appreciate any honest thoughts—even skeptical ones.
2 Comments
Respect the angle. A tool that is allowed to say “kill it” is rare. Removing the incentive to push people forward is a strong positioning choice.
Since users paste raw startup ideas into the system, how are you handling storage and model usage of that data?
• Are ideas stored long term or processed transiently?
• Are they ever used for model training or analytics beyond the individual report?
• Can users delete their idea and report fully?
Idea validation tools handle pre-launch concepts that founders consider sensitive. Clear data boundaries can become a competitive advantage here.
For clarity: this isn’t meant to replace customer interviews or MVPs—it’s just a first-pass filter. If it says “kill,” I’d still expect people to sanity-check why.