Validation Without an MVP: 9 Tests That Beat Building
Stop building MVPs. Here are 9 validation tests that prove demand before you write a line of code.
The MVP is no longer the starting line
For years, founders were told the same thing:
“Build an MVP as fast as possible and see what happens.”
That advice made sense when building was slow and expensive.
It doesn’t anymore.
-
In 2025, AI can generate:
- landing pages in minutes
- prototypes in hours
- production-quality code in days
Which means the MVP is no longer a validation tool. It’s a cost center.
The real question isn’t:
“Can we build this?”
It’s:
“Should we?”
The modern validation mistake
Most founders still use MVPs to answer questions that should have been answered before code existed:
- Does anyone care?
- Who is this really for?
- Will they change behavior?
- Will they pay?
By the time the MVP answers those questions, you’ve already paid the price.
Strong founders now validate upstream — where learning is cheaper and signals are clearer.
What validation is actually for
Validation isn’t about confidence. It’s about reducing risk.
-
Specifically:
- market risk (is the problem real?)
- customer risk (do the right people care?)
- pricing risk (is value recognized?)
- urgency risk (why now?)
You don’t need an MVP to test those.
You need experiments.
The Forge validation ladder
Before building anything, every idea should climb this ladder:
- Curiosity → “That’s interesting”
- Intent → “I’d look into this”
- Commitment → “I’ll act or pay”
MVPs often stop at curiosity.
The tests below are designed to reach commitment without code.
The 9 tests that beat building
1. The Problem Interview Test
What it tests: Pain, frequency, severity
Talk to people before pitching anything.
Pass condition:
- They describe the problem without prompting
- They already have workarounds
- They sound frustrated, not hypothetical
Fail condition:
- Polite interest
- Future talk
- “That would be nice”
2. The Replacement Test
What it tests: Competitive gravity
Ask:
“What do you use today instead?”
If the answer is:
- spreadsheets
- internal hacks
- manual processes
You may have an opening.
If the answer is:
- “Nothing really”
- “It’s not a big deal”
You don’t.
3. The Fake Door Test
What it tests: Message-to-action conversion
Create a landing page that pretends the product exists.
But don’t stop at signups.
Pass condition:
- People take a meaningful next step
- They book time, apply, or ask questions
Fail condition:
- Emails only
- No follow-up engagement
4. The Pricing Reaction Test
What it tests: Value perception
Show pricing early — even if it’s wrong.
Ask:
“If this solved the problem, would £X/month be reasonable?”
Watch reactions:
- Calm acceptance = signal
- Objections = insight
- Evasion = warning
5. The Time Commitment Test
What it tests: Priority
Ask users to:
- join a pilot
- attend a session
- review a mock flow
Time is more honest than words.
If they won’t give 15 minutes, they won’t give money later.
6. The Manual Concierge Test
What it tests: Outcome value Deliver the result by hand:- reports
- recommendations
- workflows
7. The Data Friction Test
What it tests: Real usage readiness Ask users to upload:- real data
- real credentials
- real examples
8. The Referral Test
What it tests: Natural pull Ask:If they proactively introduce others, you’re onto something. If they hesitate, the pain may not be strong enough.“Who else has this problem?”
9. The Pre-Payment Test
What it tests: Truth You don’t need Stripe on day one. You can simply say:One yes here outweighs 100 signups.“We’re taking early customers at a discounted rate.”
When you’ve earned the right to build
You’re ready to build when:- at least one test hit commitment
- you know exactly who it’s for
- you understand why existing solutions fail
- users pull you forward instead of you pushing them
