Real validation means money in the bank, not sign-ups on a waitlist

The founders with the most enthusiastic early feedback often have the weakest products. That sentence sounds wrong. It should be wrong. But I have watched it play out enough times that I no longer treat it as a paradox. I treat it as a pattern.

Enthusiasm is cheap to give. It costs nothing to tell a founder their idea is brilliant. It costs nothing to fill in a survey saying you would pay for a product that does not exist yet. It costs nothing to type your email into a waitlist form. But that frictionless generosity is precisely what makes these signals worthless as predictors of actual demand. The validation theatre begins the moment a founder mistakes politeness for purchase intent.

What my first startup taught me about false signals

At my first startup, we built a project management tool for freelance designers. The idea came from my own frustration, which felt like a good sign. The early conversations were better than good. They were intoxicating. Every designer I spoke to nodded along. "I need this." "I would definitely pay for this." "When can I get access?" We built a waitlist. Within six weeks, we had four hundred names on it.

We celebrated. We hired a second developer. We expanded the feature set beyond our original scope because, with this much apparent demand, we figured we should build something more complete. More complete meant more expensive, but the waitlist kept growing, and every new sign-up felt like a vote of confidence.

Then we launched. We sent the email to all four hundred people on the waitlist with a monthly subscription price attached.

Eleven converted.

Not eleven percent. Eleven people. Out of four hundred who had said, in one form or another, "I would definitely use this." The gap between "I would definitely use this" and "here is my credit card number" turned out to be an ocean. And we had built an entire company on the assumption that it was a puddle.

A waitlist is not validation. It is a list of people who were polite enough to give you their email address.

We spent weeks trying to figure out what went wrong. But the answer was simpler and more uncomfortable than any diagnosis we considered. The product was fine. The validation was fake. We had validated against a question that cost nothing to answer, then acted as though the answer predicted whether people would spend real money on a recurring basis.

The validation theatre

I call this the validation theatre. It is the collection of activities that look like validation, feel like progress, and produce data that resembles evidence, but predict almost nothing about whether anyone will pay.

Waitlists are the most visible form. But surveys run a close second. You ask a hundred potential users whether they would pay for a solution to a specific problem. Seventy say yes. The founder reads that as 70% demand. But the question "Would you pay for X?" and the act of actually paying for X occupy entirely different psychological spaces. In a survey, you are reacting to a hypothetical with zero consequences. When the payment screen appears, the consequences arrive. The psychology shifts completely.

The validation theatre persists because it protects founders from the one thing they most need to experience: rejection. A waitlist cannot say no to your face. A survey respondent who ticks "yes, I would pay" has not rejected you. But a potential customer who looks at your price and walks away has given you something far more valuable than encouragement. They have given you information.

The transaction test

A founder I was mentoring earlier this year took the opposite approach, and it changed how I talk about validation entirely.

She was building a scheduling tool for independent physiotherapists. Narrow market. Specific pain point. The temptation to build a waitlist was strong. Everyone she spoke to was enthusiastic.

But she did something different. Instead of asking them to sign up for a waitlist, she asked them to pay. Before a single line of code was written, she contacted fifteen clinic owners and said: "I am building this tool. It will cost one hundred and fifty pounds a month. If you pay for the first three months now, I will build it to your specifications and you will shape what it becomes."

Fifteen conversations. Fifteen chances for the validation theatre to collapse into reality.

Eleven said no. That information was gold.

Four said yes and transferred the money within two weeks.

I call this the transaction test. The difference between "would you pay?" and "did you pay?" is the entire difference between the validation theatre and real validation. The transaction test does not ask people to predict their future behaviour. It asks them to demonstrate their current commitment. Those are different things.

But here is what made the transaction test even more valuable than the money itself. Because those four clinic owners had paid in advance, they became genuinely invested in the outcome. They gave detailed, specific feedback. They tested early versions with a rigour that no free beta user ever matches. They told her what was missing, what was unnecessary, and what would make them stay past the initial three months. The payment was not just validation. It was a filter for the kind of customer who produces a good product through honest collaboration.

The only feedback that matters is the kind that comes with a receipt.

Why asking for money feels wrong (and is not)

Most founders resist the transaction test because it feels presumptuous. You are asking someone to pay for a product that does not exist yet. It feels like you are exploiting trust. It feels pushy.

But it is the opposite of pushy. It is respectful. You are respecting the customer's time by asking them to be honest about whether this problem is worth solving with their money, not just their words. And you are respecting your own time by refusing to spend months building something validated by nothing more than polite encouragement.

But the discomfort is real. Asking for money requires you to believe that what you are building is worth paying for before you can prove it. That is a psychological leap most founders are not prepared for. At Boeing, at Adobe, at Freshworks, the product was always finished before anyone saw a price tag. Selling an unfinished thing felt like professional malpractice.

It is not malpractice. It is the most honest conversation a founder can have with the market.

My physiotherapy scheduling founder shipped her first version in eight weeks. It was not polished. It was not feature-complete. But it solved the exact problem her four paying customers had described, because they had described it with the specificity that only comes from having spent real money. She did not need to guess what they wanted. They told her, because they had a financial stake in the answer being useful.

The founder who builds for four hundred curious email addresses builds a product shaped by assumptions. The founder who builds for four paying customers builds a product shaped by commitment.

But the transaction test does not just produce better products. It produces better founders. The discipline of asking for money before you build teaches you to separate signal from noise in every conversation, every meeting, every piece of feedback you receive. You stop hearing what you want to hear. You start hearing what people are willing to pay for. That shift in listening is worth more than any accelerator programme or advisory board.

One of those products still exists. The other one taught me everything I know about the distance between enthusiasm and commitment.