The most expensive thing a first-time founder can do is build the wrong product really well. The second most expensive thing is build the right product really slowly while the market moves.
Validation is the discipline that prevents both. Here’s the playbook we use with every founder who applies, before they pay us a dollar.
Run these four tests, in order
Each one costs less than the next and rules out a different kind of mistake. Skip any of them and you’re betting on something you haven’t checked.
Test 1: Can you describe the problem in one sentence?
Cost: 30 minutes.
If you can’t articulate the problem your product solves in one specific sentence, naming the user, the situation, and what hurts, your idea isn’t ready for any further investment.
Bad: "I’m building a tool that helps people manage their work better."
Good: "Solo bookkeepers who serve 15–40 clients can’t do month-end close in QuickBooks without recreating spreadsheets they built last month."
The good version names a who, a context, and a pain. The bad version describes a category. The good version can be tested. The bad version cannot.
If you’re stuck at the bad version, the validation work is narrowing your idea, not building anything yet.
Test 2: Can you find ten people who have the problem?
Cost: A week of conversations. Free.
Once you have a sharp problem statement, find ten people who’d nod when you read it to them. Not friends being supportive, actual people who, when you describe the situation, get visibly tense or excited because it’s their life.
LinkedIn search by job title. Subreddit threads where the problem comes up. Discord communities. Twitter replies to relevant content. Cold email is fine; ten responses to fifty cold emails is a great rate.
What you’re testing: does this problem exist outside my own head?
If you can’t find ten people, the problem may be too narrow, too rare, or imagined. Either way, building the product won’t fix that.
Test 3: Will any of them pre-pay?
Cost: A landing page and a Stripe link. A few hundred dollars and a weekend.
Build the simplest possible landing page that describes the product as if it exists. Be specific, pricing, features, who it’s for. Add a "buy now" or "pre-order" button that goes to a real Stripe checkout (you can refund automatically). Send it to the ten people from Test 2.
What you’re testing: will anyone pull out a credit card?
Two pre-orders means you’ve found something real. Zero pre-orders after twenty pitches means the problem is real but the solution doesn’t fit, or the price is wrong, or the framing is off. Iterate before you build.
This is the single highest-signal test on the list. Stated interest is cheap. Money on the line is the only signal that doesn’t lie.
Test 4: Can you ship something they can use within a week?
Cost: $2K to $10K (or your weekends, if you can code).
Now you’ve confirmed the problem exists, the audience is reachable, and someone will pay. The remaining risk is that the actual product doesn’t solve the problem the way you imagined, or it solves a different problem you didn’t notice.
Build the smallest version that can deliver the value. Ship it to your pre-paid customers. Watch what they do.
This is where most founders fail, they spend $50K and four months on the build, run out of patience, and never run Test 4 honestly because admitting the product doesn’t work means admitting they wasted the money.
A 5-day MVP keeps the cost of being wrong low enough that you can run the test honestly. That’s the actual reason productized MVPs exist.
What "burning runway" really means
For bootstrapped founders, runway is your savings minus your monthly burn. For funded founders, it’s the dollars in the bank minus the burn rate. In both cases, the thing you’re burning when you skip validation isn’t just money, it’s time when the question is still open.
A founder with $30K and 9 months of runway who skips validation and spends $25K on a 4-month agency build has 5 months of runway left when they discover the product is wrong. They have to either raise more (hard, with no traction), pivot (hard, with no remaining money), or shut down (failure mode).
The same founder, running the four tests above, spends maybe $3K total: a $200 landing page, $300 in cold-email tools, $2,500 on a 5-day MVP. They have $27K and 8 months of runway left, plus actual signal about whether to keep going. If the answer is no, they’ve lost a month and 10% of the budget. If the answer is yes, they have the money and the time to scale it.
The math overwhelmingly favors validation.
What changes after the four tests
If your idea survives all four, sharp problem statement, ten interested people, two pre-orders, and a working MVP they actually use, you’ve graduated from "validating" to "building." Now the problem becomes:
- How do I get from 2 paying customers to 20?
- What’s the next feature that drives retention?
- Should I raise, or stay bootstrapped?
These are good problems to have. They’re what most of validation is designed to get you to.
If your idea fails any of the four tests, you’ve learned something for cheap. That’s also a win, small loss now beats big loss later.
The point of validation isn’t to never build. It’s to build the right thing, with confidence, having spent the minimum to get that confidence.
That’s the playbook. The tools, landing page builder, no-code prototype, productized MVP service, are interchangeable. The discipline is the asset.