MVP: how to validate an idea in 4 weeks

An MVP isn't "a weaker version of the product". It's the smallest experiment that proves or kills a hypothesis.

The right hypothesis

Before writing a line of code, write:

"I believe [type of customer] will pay [amount] for [solution] because [pain]."

If you can't fill it in, you're not ready.

4-week timeline

Week 1 — Interviews

• 10 conversations with potential customers
• No demos, just questions about the problem
• Look for patterns, not validation

Week 2 — Prototype

• Figma + a landing page
• A 60-second video
• Still no real code

Week 3 — Pre-sale

• Show to 20 qualified people
• Ask for commitment: credit card or contract
• 3 real yeses > 100 likes

Week 4 — Minimal build

• Only the flow paying customers need
• Manual backend is OK (Wizard of Oz)
• Ship to the first customer in production

Signals you're on track

• Customers pay before the product exists
• They ask for specific features (not generic)
• They complain when the product fails

Stop signals

• "Interesting, but..." from everyone
• They ask for a discount before seeing value
• Nobody refers others

An MVP isn't there to impress. It's there to learn faster than the competition.