GODELIAN

Playbook — validation

How to validate a startup idea before you build anything

The cheapest MVP is the one you don't have to build. Before you write a line of code, prove someone actually wants it — here's how, in order of how much it tells you.

By Andrew, Founder & CTO10 min readUpdated 2026-07-12

The cheapest MVP is the one you never have to build. Before a line of code, prove someone actually wants the thing.

Most failed startups didn't fail at building — they built beautifully, then discovered nobody cared. Validation is how you avoid that: a set of cheap, fast tests that tell you whether there's real demand before you spend months on it. Here they are, in order of how much each one actually tells you. When you're ready to build, pick up how to build an MVP.

First principle

Why validate before you build

An idea in your head is a hypothesis, not a business. The whole game of early-stage startups is turning hypotheses into evidence as cheaply as possible — Entrepreneur First calls it starting from your edge and testing it hard; the lean-startup world calls it validated learning. Either way, the enemy is the same: building on a belief nobody checked.

What people say is cheap. What people do — click, sign up, pay — is the truth.

Every test below is designed to move you from opinions toward actions. The further down this list you get real signal, the more confident you can be.

Step 1

Talk to people (the Mom Test)

Start with conversations — but the right kind. The trap is asking “would you use this?” Everyone says yes to be nice, and you learn nothing. The fix is the Mom Test: ask questions so grounded in the person's real life that even your mum couldn't lie to you.

  • Ask about the past, not the future. “When did you last run into this problem? Walk me through what happened.” — not “would you use a tool that…”
  • Ask what they did about it. Did they build a spreadsheet, pay for something, give up? Effort and money spent are proof the problem is real.
  • Don't pitch. The moment you describe your idea, they start being polite. Stay curious about their world, not your solution.

Step 2

Test demand (smoke & fake-door tests)

Conversations reveal problems; the next tests reveal whether people will act. Both take an afternoon and cost almost nothing.

The smoke test. Build a single landing page that describes the product as if it exists — the promise, who it's for, and one clear call to action (“Get early access”). Drive a little traffic to it (your network, a small ad, a relevant community) and measure how many people give you their email. Real sign-ups from strangers are a genuine signal.

The fake-door test. Put a button for the feature or product where people would actually look for it. When they click, show “coming soon — leave your email.” The click-through is a measure of real intent, captured at the exact moment of interest. (Use it honestly and sparingly — you're measuring demand, not tricking anyone.)

Step 3

Pre-sell — the strongest signal

Nothing validates like money. If people pay before the thing fully exists, you don't have a hypothesis anymore — you have customers.

Pre-selling can be a founding-customer deal, a paid pilot, a deposit, a Kickstarter, or simply an invoice for a service you deliver manually at first. It's the highest bar and the most honest one: a credit card is a vote that costs the voter something. Even a handful of pre-sales tells you more than a thousand “that's a great idea” comments.

It also does something subtle: it forces you to name a price and make a real offer, which sharpens the whole idea. If you can't get anyone to pay, better to learn it now — for free — than after a year of building.

Step 4

Then, and only then, build

Once you have evidence — real conversations, sign-ups, clicks, or better yet pre-sales — you've earned the right to build. Now the MVP has a job: not to discover whether anyone wants it (you already know), but to deliver it well enough that they stay.

That's where the build guide takes over — scope to one loop, build it on a stack you own with AI, and then measure product-market fit properly:

And if you'd rather validate the idea yourself and have a founder-operator build the real version, that's what Godelian does.

Andrew, founder of Godelian

Written by Andrew

Founder & CTO of Godelian. Fifteen years building AI systems, trained as a founder at Entrepreneur First, a published AI researcher (Nature Scientific Reports), and had a startup acquired in 2025. He builds first versions that actually get used — and helps founders build theirs.

Questions, answered

How do you validate a startup idea?

Validate demand before building by talking to real potential customers about their actual problems (the Mom Test), then testing whether they'll act — a landing-page smoke test, a fake-door test, or, strongest of all, taking pre-orders or a deposit. What people do (click, pay, sign up) matters far more than what they say.

Do I need an MVP to validate my idea?

Not at first. The cheapest validation happens before any code: conversations, a landing page, a fake-door test, a pre-sale. Build the MVP once you have evidence that people want the thing and will act on it — then the MVP measures how well you deliver it, not whether anyone cares.

What is the Mom Test?

The Mom Test is a way of talking to potential customers so that even your mum couldn't lie to you: ask about their real past behaviour and specific problems, not whether they'd like your idea. Avoid pitching; ask 'when did you last face this?' and 'what did you do about it?' Facts about the past predict the future; opinions about your idea don't.

When you hit the hard 20%

Build it with the founder.

Prototyping is the easy part. When real users, money, and data are on the line — security, scale, the parts you can't see are broken — that's the work. Godelian builds owned, production-grade first versions, typically for $15–30k in weeks.