Validating Your Idea

By the end of this module, you'll know how to validate a startup idea before building anything — using customer interviews (The Mom Test), market sizing (TAM/SAM/SOM), and a validation stack from cheap tests to pre-sales.

The $40 million lesson in not asking

In 2013, a startup called Clinkle raised $25 million from some of Silicon Valley's most respected investors — before launching a product. The founder, a Stanford student, had a vision for a mobile payments app that would replace your wallet. He hired a team, rented fancy offices, and spent over a year building in secret.

When Clinkle finally launched, almost nobody used it. The app solved a problem that didn't exist in a way nobody wanted. Employees started quitting. Investors stopped returning calls. The company shut down after burning through nearly all of the money.

Clinkle didn't fail because the team was bad. They failed because they never validated the idea. They assumed people wanted what they were building — and by the time they found out otherwise, the money was gone.

The number one killer of startups isn't running out of money, bad technology, or fierce competition. It's building something nobody wants. Validation is how you avoid that fate.

What validation actually means

Validation is the process of testing whether your idea solves a real problem for real people who will pay real money. It's not asking your friends if they like your idea (they'll say yes to be nice). It's not building a product and hoping for the best. It's gathering evidence — before you build — that your business has a chance.

Think of it like a scientist testing a hypothesis. You don't run a 5-year experiment without first checking if the hypothesis is even plausible. You design small, cheap tests that give you data fast.

The Mom Test: how to talk to customers without lying to yourself

The most important validation tool is a customer interview — but most founders do them wrong. They ask leading questions like "Would you use an app that does X?" and get polite yeses that mean nothing.

Rob Fitzpatrick's book The Mom Test (2013) nails the core principle: even your mom will lie to you about your startup idea if you ask the wrong questions. The trick is to ask about their life, not your idea.

The Mom Test rules:

Great customer interview questions:

1. "Tell me about the last time you dealt with [problem]."
2. "What did you do about it?"
3. "What was the hardest part?"
4. "Have you tried any solutions? What worked? What didn't?"
5. "How much time/money does this problem cost you?"

There Are No Dumb Questions

"How many interviews do I need?"

At minimum, 10-15 conversations with people in your target market. You'll start hearing patterns after 5. If you've done 15 interviews and every person describes a different problem, your market isn't clear enough. If 10 out of 15 describe the same pain, you're onto something.

"What if people say they have the problem but wouldn't pay for a solution?"

Then it's a nuisance, not a problem worth solving. Real problems have budgets — either people already spend money on bad alternatives, or the problem costs them measurable time and money. If they wouldn't pay $10/month to fix it, reconsider.

TAM, SAM, SOM: is this market big enough?

Even if people want your product, the market needs to be big enough to build a business. Investors and founders use three layers to size a market:

The key insight: investors don't expect you to capture 100% of TAM. They want to see that you understand the difference — and that your SOM alone is big enough to build a real business ($10M+ for a venture-backed startup).

Two ways to calculate market size:

Bottom-up is more credible because it's rooted in real assumptions you can test.

There Are No Dumb Questions

"What if my market is small? Does that mean it's a bad idea?"

Not necessarily — it might mean you're not venture-scale, and that's fine. Many great businesses are built in $10M-$100M markets that VCs ignore. You just need to match your funding strategy to your market size. Bootstrapping works great in smaller markets. VC funding requires big TAMs because they need 100x returns.

Validation techniques beyond interviews

Customer interviews are step one. Here are five more techniques to test demand before building:

1. Landing page test

Build a simple landing page that describes your product as if it exists. Add a "Sign up for early access" or "Join the waitlist" button. Drive traffic with $100-200 in ads. Measure how many people sign up.

Dropbox did this. In 2007, Drew Houston created a 3-minute video showing how Dropbox would work — before writing a single line of code. The waitlist went from 5,000 to 75,000 people overnight. That was validation.

2. Fake door test

Add a button or feature description in an existing product (or landing page) for something you haven't built. When people click, show a message: "Coming soon — enter your email to be the first to know." Count clicks. This measures actual intent, not opinions.

3. Concierge MVP

Deliver your product's value manually to a small group, without building any technology. A meal planning startup might personally create weekly meal plans for 10 people via email before building an app. This tests whether the value proposition works before investing in development.

4. Wizard of Oz test

Like a concierge MVP, but the customer thinks they're using a real product. Behind the scenes, a human does the work. Zappos famously started this way — the founder photographed shoes at local stores and posted them online. When someone ordered, he went to the store, bought the shoes, and shipped them. No inventory, no warehouse, no risk.

5. Pre-sales

Ask people to pay for your product before it exists. Kickstarter is the most famous version, but you can do this with a simple landing page and a Stripe checkout. If people put down money, that's the strongest validation signal there is.

The validation stack: a step-by-step framework

Don't try to validate everything at once. Stack your tests from cheapest and fastest to most expensive:

At each stage, you're asking: "Is there enough signal to justify spending more time and money on this?" If the answer is no at any stage, pivot or kill the idea. That's not failure — that's validation working.

Signs your idea is validated (and signs it isn't)

What Clinkle could have done differently

Imagine an alternate timeline. Instead of raising $25 million and building in secret for a year, the Clinkle founder spends two weeks running customer interviews at Stanford. He asks students: "Tell me about the last time paying for something was frustrating." He discovers that most students are fine with their existing payment apps. The pain isn't there.

He runs a landing page test. 500 visitors, 4 signups. A 0.8% conversion rate — far below the 5% threshold that signals real demand. He kills the idea, saves $25 million, and starts working on a problem people actually have. That's not failure. That's validation doing its job.

Key takeaways

• 42% of startups fail because they build something nobody wants — validation prevents this
• Customer interviews are the cheapest, fastest validation tool — but ask about their life, not your idea (The Mom Test)
• TAM/SAM/SOM tells you if the market is big enough — use bottom-up calculations for credibility
• Stack your tests from cheapest to most expensive: interviews → landing page → concierge MVP → pre-sales
• Real validation signals: people pay money, invest time, or come back unprompted. Everything else is vanity
• Killing a bad idea early is a win, not a failure — it saves you months and thousands of dollars