Evidence over opinion
Most people building something new ask friends, post on social, or start building and hope. All three feel like validation and none of them are. BRAINS AI exists to replace that feeling with something you can check.
What we refuse to do
Rules we hold even when they make the product look worse in the short term, because a validation tool that tells founders what they want to hear is not validation.
- We never soften a weak signal to be encouraging
- If the research turns up little evidence anyone has the problem, the report says so plainly. A founder who hears what they wanted to hear from us has learned nothing they could not have gotten from a friend.
- We show the case against as deliberately as the case for
- Research that only collects agreement is flattery. Every report keeps the strongest counter-evidence in its own section, so it cannot quietly get folded into a positive summary.
- We screen responses for quality, not for agreement
- A generic or clearly AI-written survey response does not count toward your score, whichever way it answered. Rejecting only the negative ones would bias every score upward, which is the most damaging thing a validation product could do.
- We never invent a source to fill a gap
- If live search turns up nothing, the report is flagged as unsourced rather than dressed up with plausible-sounding citations. An invented statistic is a trust problem, not a formatting one.
- A low score is a reason to sharpen, not a verdict on you
- Validation is a loop. If the signal is weak, the idea can be reworked and run again with no limit on rounds, and every past version stays readable, including the ones that did not pass.
What a score can and cannot tell you
A validation score is a measure of the evidence gathered so far. A high one means the problem looks real to the people who have it, that they describe it unprompted, and that some already pay to solve it. That reduces the risk of building something nobody wanted.
It cannot tell you whether the business will work. Pricing, distribution, timing, and execution all sit outside what any validation round can measure, and a strong signal on the problem says nothing about whether you will reach the people who have it.
The honest framing is narrow on purpose: this reduces one specific risk well, rather than claiming to reduce all of them a little.
If that sounds like the kind of answer you want, try it with your idea.