Day 3: Validate Your Idea Before You Build Anything

The Concept

The most expensive mistake an entrepreneur can make is building something before validating that anyone wants it. This mistake is remarkably common — not because entrepreneurs are careless, but because building feels like progress. Writing code, designing interfaces, setting up infrastructure — these activities are satisfying in a way that asking awkward questions of strangers is not. The problem is that building without validation is simply spending money and time to make your assumptions more elaborate. It does not test whether those assumptions are true.

The Mom Test, written by Rob Fitzpatrick, describes the core failure mode of validation interviews: asking questions that your mother — who loves you and wants your idea to succeed — would answer encouragingly even if your idea was terrible. "Would you use this?" is a Mom Test question. It invites affirmation, not honesty. "How do you currently handle this problem?" is a good question. It asks about behaviour, not opinions, and behaviour does not lie. People consistently tell entrepreneurs what they think they want to hear. People almost never lie about what they actually do.

What Smoke Tests Actually Test

A smoke test is any experiment designed to create the appearance of a product that does not yet exist, in order to measure real customer intent. A landing page with a sign-up form for a product you have not built is a smoke test. A LinkedIn post describing a problem and offering a solution in exchange for replies is a smoke test. A direct message to 20 people in your target segment asking if they would pay for a specific outcome — and what they would pay — is a smoke test. The point is not to deceive anyone. The point is to separate interest from intent. Interest is free. Intent costs something: a click, an email address, a pre-order, a scheduled call. The gap between the two is where most business ideas quietly die.

Vitamins vs Painkillers

This distinction comes up in early-stage investing constantly, and it applies with equal force to validation. A vitamin is something people think they should have. A painkiller is something they actively seek out because the pain of not having it is acute. Vitamins are nice-to-haves. Painkillers are must-haves. The practical difference shows up clearly in customer interviews: people who need a painkiller can describe their problem in vivid detail, they have already tried to solve it in other ways, and they express clear frustration with the current solutions. People who would buy a vitamin typically respond with moderate enthusiasm and cannot describe a specific situation where the problem caused real damage.

The 48-Hour Test Principle

One of the most useful reframes in early-stage entrepreneurship is replacing the question "should I build an MVP?" with "what is the smallest experiment that could teach me something real in the next 48 hours?" An MVP typically takes weeks or months to build. A 48-hour test takes an afternoon. It might be a manually delivered version of your service for one customer. It might be a Google Form that mimics a product workflow. It might be an email to your network describing the problem and asking who has experienced it. The signal from a 48-hour test is necessarily weak — a handful of data points, not statistical significance. But a handful of real data points is worth more than any amount of confident planning, and it takes a fraction of the time and money.

Why Good Interview Questions Do Not Mention Your Solution

The instinct in a validation interview is to describe your idea and ask if the person would find it useful. This instinct is almost always wrong. The moment you describe your solution, you have changed the conversation. Now the person is evaluating your idea rather than sharing their experience. They become polite, or encouraging, or they start trying to help you by generating use cases. None of this is useful data. The useful data comes from questions that make them talk about their own life: the last time they experienced this problem, what they tried to do about it, what that cost them, what they wish existed. Your job in a validation interview is to listen. The less you talk about your idea, the more you learn about whether it is worth building.