Pre-Build Checklist: Caution-Zone Idea to Go/No-Go
A pre-build scorecard helps first-time founders decide whether an idea has enough demand proof and distribution to justify spending.
You have an idea, no incorporation, no revenue, and a build budget ready to disappear. Before it disappears, ask whether the idea has demand proof and a distribution plan strong enough to justify building. A pre-build scorecard answers that question without turning the idea into a project you cannot stop. In Preuve's benchmark set, the median model assessment score was 54 out of 100. In that benchmark, 76.0% of assessment records were in the 40-to-69 caution band. Fewer than 0.2% of assessment records scored above 90. A mid-range score is common, so it should not be the whole decision. It is a warning to check demand proof and a path to buyers before the build starts.
Most ideas sit in the caution band
A validation score is only useful if it tells you when to stop. The caution band is where most ideas live, so the scorecard should not celebrate a 54. It should point to the next evidence step. A mid-range score points to a demand test or a distribution test, not another round of planning.
The scorecard should force a go/no-go decision
Keep the scorecard small enough to finish before the build budget starts moving. Each item should be checkable quickly, because the value comes from catching a weak spot early. The scorecard is a pre-build check, not a project that runs forever. It asks whether someone will pay, whether you can reach them, and what would make you stop.
- Score band: record the band your validation score falls into, then say what the next evidence step would be.
- Demand proof: show written signals that someone will pay, from people who do not know you, not just compliments.
- Distribution plan: name the channel you will use to reach the early buyers and the next action you will take.
- Top risk label: write the biggest threat as a plain label, then add the next test that would lower it.
- Go/no-go trigger: set the condition that stops the build before you start spending, and say who will enforce it.
Demand proof and distribution decide the build
Demand proof should be boring. A written signal that someone will pay is stronger than a polite reaction. The person has something to lose when they do not follow through. A pre-build demand check should be short and uncomfortable. Ask the person to do something that costs time or money. A no is useful information. Enthusiasm alone keeps the idea in the caution zone.
Distribution is where many caution-zone ideas get stuck. A good plan names the channel, the audience, and the next action. It should be the path you will test next, not a list of possible channels. A channel you have used before is easier to test than a channel you are guessing at. When you cannot say how the early buyers will find you, the build depends on reach, not on demand.
Risk labels help you pick the next test. In tagged Preuve model analyses, early-stage risk was the most frequent primary risk label at 36.9%. Go-to-market was the second most frequent primary risk label at 25.7%. Use those labels as a shortcut: early-stage risk points to a harder demand test; go-to-market risk points to a harder distribution test.
The go/no-go trigger should be set before spending
A CB Insights report dated March 5, 2026 covered 431 venture-backed firms that ceased operations after 2023, leaving out any with an earlier exit. Those companies had raised $17.5 billion in equity before closure, with a median of $11 million. Money can keep a weak idea alive long enough to make the damage large.
Write the trigger before the build starts. A trigger written after the spend loses its force. Your go/no-go trigger should be boring and checkable. Stop when demand proof is missing, distribution is a hope, or the top risk has no next test. A failed scorecard calls for a fix or a wait; do not build yet. A passing scorecard calls for the smallest version that tests the trigger. Re-run the scorecard after the first test.