Solution Validation

Testing if your specific solution actually solves the problem, before building the full product.

The Critical Distinction

Problem validation: is the problem real?

Solution validation: does YOUR solution work?

Many real problems have failed solutions. You need both.

The Solution Validation Mindset

Most founders:

1. Have a solution in mind
2. Build it for months
3. Show it to customers
4. Realise it does not solve the problem

Better approach:

1. Validate the problem exists
2. Test multiple solutions cheaply
3. Build what customers actually want
4. Launch quickly, iterate fast

The insight: your first solution idea is probably wrong. Test assumptions before committing.

The Riskiest Assumption Test

Before building anything, identify your riskiest assumptions.

Framework:

1. List all assumptions about your solution
2. Rate each by: (Risk if wrong) × (Certainty you are right)
3. Test the highest-scoring assumptions first

Example: meal planning app

Test #1: will people cook our recipes? Highest score, so most important to validate.

Solution Validation Methods

Level 1: Fake It (Cheapest, Fastest)

Goal: test demand before building anything.

Landing Page Test

What: create a page describing your solution. Drive traffic. Measure signups.

How:

1. Write compelling copy (problem + solution)
2. Add email signup form
3. Set success metric (5% conversion)
4. Buy ads or post in communities ($100-500)
5. Measure results in 1-2 weeks

Example copy:

Headline: "Meal planning in 2 minutes, not 2 hours"
Subhead:  "Weekly meal plans personalised to your taste, dietary
           needs, and schedule"
CTA:      "Join the waitlist"

Success criteria:

• 5%+ conversion: strong interest
• 2-5%: medium interest
• under 2%: weak interest

Cost: $200 (domain, hosting, ads). Time: 1-2 days. What you learn: will people even want this?

Smoke Test

What: advertise a product that does not exist. See who clicks "buy."

How:

1. Create an ad with your value prop
2. Link to a simple page with a "buy" button
3. On click: "Thanks for your interest. We're launching in X weeks."
4. Collect email
5. Measure click-through and purchase intent

Example:

• Facebook ad: "Finally, healthy meal planning that takes 2 minutes"
• Landing page: $10/month, "Start free trial"
• After click: waitlist form

Success criteria:

• 2%+ click "buy": validated
• 1-2%: maybe
• under 1%: not interested

Cost: $300 (ads). Time: 2-3 days. What you learn: will people pay?

Concierge MVP

What: manually deliver your solution to a few customers.

How:

1. Find 5-10 early customers
2. Charge them (even a small amount)
3. Do everything manually behind the scenes
4. Learn what actually solves their problem
5. Automate only what works

Example: meal planning

• Customer signs up for $20
• You manually create their meal plan
• You build the grocery list by hand
• You send it via email
• You adjust based on feedback

Success criteria:

• They use it
• They are willing to pay
• They refer others
• You understand what they need

Cost: $0-100. Time: 1-2 weeks per customer. What you learn: what actually solves the problem?

Level 2: Prototype It (Medium Cost, Speed)

Goal: test if the experience resonates.

Clickable Prototype

What: a fake app or website that looks real but has no backend.

Tools:

• Figma (design + prototype)
• InVision (interactive mockups)
• Marvel (simple prototypes)

How:

1. Design key screens
2. Link them together
3. Share with 20-30 users
4. Watch them use it (do not help)
5. Interview after

What to test:

• Can they complete core tasks?
• Is the flow intuitive?
• Do they understand the value?
• What confuses them?

Cost: $0 (tools are free). Time: 3-5 days. What you learn: is the UX right?

Wizard of Oz MVP

What: looks automated but you are doing it manually.

Example:

• User thinks AI is generating meal plans
• You are actually doing it by hand
• User cannot tell the difference
• You learn if the output is valuable

How:

1. Build a simple frontend
2. Fake the automation
3. Fulfil requests manually
4. Measure satisfaction
5. Only automate what works

Success criteria:

• 4+ star rating
• Users would pay for this
• Clear what features matter
• You understand the workflow

Cost: $500-2,000 (simple frontend). Time: 1-2 weeks. What you learn: is the output valuable?

Level 3: Build a Minimum MVP (Higher Cost)

Goal: test with a real, functioning product (minimal features).

The Single-Feature MVP

What: build one core feature really well.

Rule: if you are embarrassed by v1, you launched too late.

Example: project management tool

Do not build:

• Task management
• Time tracking
• File sharing
• Reporting
• Integrations
• Mobile apps
• Gantt charts

Do build:

• Create task
• Assign to person
• Mark complete
• That's it.

Why it works:

• Launches in 2-4 weeks
• Tests core value proposition
• Gets real feedback fast
• Cheap to build

When to use: after validating with prototypes or fake tests.

Technical Prototype

What: prove technical feasibility of the hard part.

When you need it:

• Complex algorithm
• New technology
• Integration challenges
• Performance concerns

Example:

• Question: "Can we actually match recipes to preferences?"
• Build the matching algorithm
• Test with real data
• Ignore UI, payments, and so on

Cost: 1-4 weeks of dev time. What you learn: is this technically possible?

The Solution Interview

After showing prototype or MVP:

Structure (45 minutes)

1. Context (5 min)

   • Remind them of the problem
   • "Remember you said [problem was painful]?"

2. Show solution (10 min)

   • Demo your prototype or MVP
   • Let them try it (if possible)
   • Do not explain too much. See if they get it.

3. Open feedback (20 min)

   • "What do you think?"
   • "Would this solve your problem?"
   • "What is missing?"
   • "What is confusing?"
   • "What would you change?"

4. Prioritisation (5 min)

   • "What is most important?"
   • "What could we skip?"
   • "What would make this a must-have?"

5. Commitment test (5 min)

   • "If we launched this next month at $X, would you buy?"
   • "Would you refer others?"
   • "Can we follow up for beta testing?"

What You Are Listening For

Strong signals:

"When can I get this?"
"How much does it cost?"
"Can I sign up now?"
"This solves my exact problem"
They describe specific use cases
They spot problems you didn't think of

Weak signals:

"This is interesting"
"I like it" (generic)
Lots of feature requests
"I'd need to see more"
Cannot articulate how they'd use it

Red flags:

"I'm not sure I'd use this"
"Current solution works fine"
"Too complicated"
"Doesn't really solve my problem"
They don't understand it
Confused about value prop

The Five-Second Test

Goal: can people understand your value proposition instantly?

How:

1. Show your landing page or product for 5 seconds
2. Hide it
3. Ask: "What does this product do?"

Success:

• They can explain it accurately
• They mention the key benefit
• They identify the target user

Failure:

• "I'm not sure"
• Wrong understanding
• Focus on features, not benefits

Fix: simplify your message.

Measuring Solution Validation

Qualitative Signals

After 20 solution interviews:

Quantitative Signals

For landing pages and fake tests:

Iterating Based on Feedback

Pattern Recognition

After 20+ interviews, look for:

1. Consistent confusion. If 40%+ confused about same thing, fix immediately. Example: "I thought it did X not Y."
2. Missing features. If 60%+ mention same gap, add to roadmap. Example: "I need to integrate with Slack."
3. Wrong solution. If 50%+ say it does not solve the problem, pivot. Example: "This is nice but doesn't address my real issue."
4. Wrong segment. If only a subset loves it, focus on them. Example: freelancers love it, agencies do not care.

The Pivot Decision

Pivot when:

• 50%+ say solution does not address the problem
• You keep explaining and they still do not get it
• Features they want are a completely different product
• A different segment is way more excited

Iterate when:

• Core value is clear but needs refinement
• Missing features that make sense
• UX issues but the concept is right
• Pricing concerns

Kill when:

• You cannot get anyone excited
• Problem was not as painful as you thought
• Solution does not actually work
• Better alternatives exist

The Iteration Loop

Test -> Measure -> Learn -> Adjust -> Test

Week 1: show prototype to 10 people
Week 2: fix top 3 issues
Week 3: test with 10 new people
Week 4: fix next issues
Repeat until 60%+ would buy

Common Mistakes

Mistake 1: Building Too Much

Bad:  "Build the full product, then test"
Good: "Test the core idea with a landing page first"

Cost of mistake: 3-6 months wasted, $50K+ burned.

Mistake 2: Ignoring Negative Feedback

Bad:  "They just don't get our vision"
Good: "If they don't get it, we need to change it"

Reality: customers are always right about their problems, often wrong about solutions.

Mistake 3: Testing With Wrong People

Bad:  Showing to friends, family, non-customers
Good: Testing with target customers who have the problem

Mistake 4: Feature Creep

Bad:  "Just one more feature before testing"
Good: "Test with minimum, add based on feedback"

The MVP rule: if you are not embarrassed, you waited too long.

Mistake 5: Explaining Too Much

Bad:  Walking them through every feature
Good: Watching them struggle (that's the data)

If they need explanation to understand it, it is not clear enough.

Mistake 6: Taking All Feedback Equally

Bad: treating all feedback the same.

Good: weighting feedback by:

• How much they have the problem
• Whether they would actually pay
• How well they fit target segment

The Solution Validation Checklist

[ ] Tested riskiest assumptions first
[ ] Ran landing page test (if applicable)
[ ] Built clickable prototype or concierge MVP
[ ] Conducted 20+ solution interviews
[ ] 60%+ say solution would solve problem
[ ] 30%+ would pay at target price
[ ] Clear on what features are must-haves
[ ] Iterated based on feedback
[ ] Five-second test passes
[ ] No major confusion about value prop
[ ] Identified segment that loves it most
[ ] Got beta tester commitments
[ ] Documented findings and learnings
[ ] Decided: build, pivot, or kill

Red Flags

Kill or pivot if:

Solution does not solve the problem.

• Persistent feedback that it misses the mark
• Need to explain it extensively
• "Nice but not what I need"

Too complex to build or use.

• Would take 12+ months to build
• Requires specialised expertise you do not have
• Users find it confusing

Wrong approach.

• A different solution would work better
• Competitor already nails this
• Market wants different approach

Cannot validate quickly.

• Cannot test without building everything
• Need 12-month sales cycle to validate
• Dependencies outside your control

Moving to Business Model Validation

If solution validation succeeded, you now know:

• Your solution solves the problem
• Target customers understand it
• 30%+ would pay
• What features are essential
• Where you need to improve

Resources

Prototyping tools:

• Figma (design + prototype)
• Webflow (functional websites)
• Bubble (no-code apps)
• Loom (demo videos)
• Canva (marketing materials)

Testing tools:

• Maze (prototype testing)
• UserTesting (user feedback)
• Hotjar (heatmaps, recordings)
• Typeform (surveys)

Books:

• The Lean Startup by Eric Ries
• Sprint by Jake Knapp
• Don't Make Me Think by Steve Krug

Next Steps

Continue to 05-business-model.md to check the unit economics, pricing, and acquisition channels that turn a working solution into a working business.