Business Ideas

A practical course on generating, validating, and launching business ideas that customers actually want.

Why Validate Ideas

Most startups fail not because of poor execution, but because they build something nobody wants. The cost of being wrong is high: time, money, opportunity cost. Validation reduces risk by testing assumptions before you commit.

The numbers are bleak:

• 42% of startups fail due to "no market need" (CB Insights)
• 90% of startups fail overall
• The average failed startup wastes 11 months and $50,000+
• Most failures are preventable with proper validation

Validation is not about finding yes. It is about finding truth.

Who This Is For

• First-time founders who want a structured path from idea to launch
• Side-project builders who want to test before they build
• Operators inside larger companies who need to validate new bets

Contents

Core Principles

1. Talk to Customers First, Build Second

Most founders build in isolation, then look for customers. Reverse this:

• Talk to 50-100 potential customers before writing code
• Understand their problems deeply
• Validate they will pay before building

The trap: "If I build it, they will come." They will not.

2. Fall in Love with the Problem, Not Your Solution

Your first solution is probably wrong. That is fine. Problems are durable, solutions are disposable.

Example: Slack started as a gaming company. They pivoted when they realised their internal chat tool solved a bigger problem.

3. Speed Is Your Competitive Advantage

As a small player, you can:

• Talk to customers daily
• Iterate in days, not months
• Pivot without committees
• Test ideas competitors cannot justify

Use this advantage. Big companies are slow. You are not.

4. Evidence Over Opinions

Validation requires evidence:

Counts as evidence:
  50 customer interviews
  100 email signups
  $5,000 in pre-orders

Does not count as evidence:
  "My friends think it's cool"
  "This market is huge"
  "Nobody else is doing this"

5. Kill Ideas Fast

Bad ideas do not get better with time. If validation fails:

• Do not rationalise
• Do not pivot prematurely
• Move to the next idea
• Speed of iteration matters

Rule: if you cannot validate problem-solution fit in 4-8 weeks, kill it or pivot.

The Validation Framework

Stage 1: Problem Validation (Week 1-2)

Question: does this problem exist, and do people care enough to pay?

Methods:

• Customer interviews (30-50)
• Problem surveys
• Observation studies
• Search volume research

Success criteria: 40%+ say this is a top-3 problem they would pay to solve.

Stage 2: Solution Validation (Week 3-4)

Question: does your solution actually solve the problem?

Methods:

• Solution interviews
• Smoke tests (landing pages)
• Prototypes and mockups
• Concierge MVP

Success criteria: 30%+ would use your specific solution.

Stage 3: Willingness to Pay (Week 5-6)

Question: will people actually pay?

Methods:

• Pre-sales
• Crowdfunding
• Pilot programs
• LOIs (letters of intent)

Success criteria: $10,000+ in commitments or 100+ qualified leads.

Stage 4: MVP Testing (Week 7-12)

Question: can you deliver, and will they stay?

Methods:

• Build minimum viable product
• Launch to early adopters
• Measure retention and satisfaction
• Iterate based on feedback

Success criteria: 40%+ retention after 30 days, NPS > 30.

Common Validation Mistakes

The Mom Test

When talking to customers, bad questions get bad data.

Bad: "Would you use an app that helps you stay organised?"

• Leading question
• Hypothetical
• Generic
• Gets polite lies

Good: "Tell me about the last time you struggled with organisation. What did you do?"

• Open-ended
• Specific past behaviour
• Reveals real problems
• Gets truth

The rule: ask about past behaviour and current problems, not future hypotheticals.

Quick Start Checklist

Starting validation today? Here is your first week:

[ ] Write down your idea and core assumptions
[ ] Identify your target customer (be specific)
[ ] Create a list of 100 potential customers to talk to
[ ] Write 10 interview questions (focus on problems, not solutions)
[ ] Schedule 10 customer interviews this week
[ ] Create a simple landing page describing the problem
[ ] Document findings after each interview
[ ] Look for patterns in responses
[ ] Identify your riskiest assumption
[ ] Design a test for that assumption

Success Metrics by Stage

Red Flags to Kill the Idea

Stop if you see these patterns:

• Cannot find anyone with the problem
• Problem exists but nobody is trying to solve it (probably not painful enough)
• Current solutions are "good enough"
• Cannot clearly identify who would pay
• Customers want it but will not commit to anything
• You are the only one excited about it
• Market research shows decline or saturation

Recommended Resources

Books

• The Mom Test by Rob Fitzpatrick
• The Lean Startup by Eric Ries
• Running Lean by Ash Maurya
• Sprint by Jake Knapp
• The Startup Owner's Manual by Steve Blank

Frameworks

• Lean Canvas (business model)
• Jobs to Be Done (customer needs)
• Value Proposition Canvas (product-market fit)
• Hypothesis Testing (scientific approach)

Tools

• Typeform / Google Forms (surveys)
• Calendly (scheduling interviews)
• Loom (demo videos)
• Figma (prototyping)
• Stripe (pre-orders)
• Carrd / Webflow (landing pages)

A note on confidence: the framings in this course (the Mom Test, Lean Startup, Jobs to Be Done) are tools, not laws. They work because they make you slow down and check your story against reality. Use them, then trust the customer in front of you over the framework on the page.