The $0 Validation Playbook

A founder showed me a demo last month that made my stomach drop.

It was beautiful. Six months of nights and weekends, a real engineering budget, animations that actually worked. He was proud, and he should have been. It was good work.

Then I asked the only question that matters. “How many people asked for this before you built it?”

Silence. He had built the whole thing on a hunch, and now he needed the hunch to be right, because there was no money left to be wrong.

Building is the most expensive way to ask a question

Here is what nobody tells first-time founders. Code is not how you find out if people want your product. Code is how you find out if the thing you already validated actually works.

Those are different jobs, and founders do them in the wrong order constantly.

They fall in love with the idea, disappear for six months to build it, and treat the market like a jury that will deliver a verdict on launch day. By then the verdict costs a fortune, because you cannot un-spend the six months.

When I was early on my own ventures, I made a version of this mistake too. I built ahead of the demand more than once. It taught me the most useful skill I have as a founder and now as an investor at Henson Venture Partners. Learn to get a no before you write a line of code, because an early no is a gift and a late no is a funeral.

The whole game before you build is to buy the truth as cheaply as possible. And the truth is almost always available for free.

Four tests that cost nothing but nerve

Here is the playbook I give every pre-seed founder before they open an editor.

The first is the conversation test. Go talk to twenty people who have the problem. Not friends. Strangers who feel the pain. Do not pitch. Ask them what they do about it today and how much it costs them. If they shrug, you have your answer, and you just saved six months.

The second is the wallet test. Talking is cheap, so make it cost them something. Ask for a small deposit, a pre-order, a signed letter of intent, a paid pilot. “I love it” is free. A card number is data. Nothing separates real demand from politeness faster than asking someone to pay before the thing exists.

The third is the fake door test. Put up a one-page site that describes the product as if it is real. Add a button. Buy is fine, join the waitlist is fine. Send a little traffic to it and count who clicks. You are not lying if the page is honest that it is early. You are measuring intent before you fund it.

The fourth is the concierge test. Deliver the outcome by hand before you automate it. If your idea is software that sorts something, sort it yourself in a spreadsheet for ten customers first. If they pay you to do it manually and ugly, they will pay you to do it with a product. If they will not pay for it done by hand, no interface will fix that.

None of these need engineers. All of them need you to risk hearing no. That is the only real cost, and it is the one founders avoid by building instead.

Set a bar before you start

Here is the part that keeps you honest. Decide what a pass looks like before you run the test, not after.

Founders who skip this move the goalposts. Two out of twenty people are mildly interested and suddenly that is validation. It is not. Write the number down first. “If fewer than five of twenty will put money down, I do not build this yet.” Then respect the number even when it hurts, especially when it hurts.

I told that founder with the beautiful demo to run the wallet test retroactively. Go back to the people he built it for and ask them to pay. Eleven conversations later he had one yes. One. The product was gorgeous. The demand was not there, and no amount of polish was going to conjure it.

The good news is he still had a skill, a market he now understood, and a much cheaper way to find the next idea. He just learned it the expensive way instead of the free one.

Validation is not a phase you rush through to get to the fun part. It is the fun part. It is where you find out if you are about to spend a year of your life on something real.

Test first. Build second. Fall in love last.