Stage 1: Problem Proof — Proof Engine

Confirm a real, recurring problem exists for a specific group before spending anything else.

What you're proving

A specific group of people have a recurring, painful problem they would pay to solve — and that you haven't invented it for them.

Evidence threshold

5+ unprompted confirmations from your target audience, describing the problem in their own words.

Strong signals

• They describe the problem without you naming it first
• They've already tried other solutions and failed
• They can name the cost: time lost, money wasted, stress caused
• They ask if you've built something yet

Weak signals

• "That sounds cool"
• "I'd probably use that"
• Vague agreement without specifics
• Interest from people who don't match your target audience

Failure modes

• Interviewing friends who are too polite to say no
• Confusing excitement for evidence
• Describing your solution before listening for the problem
• Treating a survey with 50 responses as proof if the questions were leading

Lesson: You are not looking for approval

The goal of this stage is not to validate your idea — it's to find out if the problem is real and painful enough to change behavior. Ask about past behavior, not future intent. 'What did you do the last time this happened?' is worth more than 'Would you pay for a solution?'

Case study: Airbnb: Proof in the field

Before building anything, Airbnb's founders walked the streets of New York talking to strangers about renting out space in their homes. They weren't pitching — they were listening. They found that the problem (affordable short-term accommodation for hosts and guests alike) was real, recurring, and painful. That fieldwork shaped every early decision.

Action

Post in 3 subreddits relevant to your audience. Ask about their biggest frustration with [your problem area]. Do not mention your solution. Count how many responses describe the same pain.

Resources for this stage

• How to Run a Problem Interview Without Sounding Like a Researcher (media) — A step-by-step guide to having natural conversations that reveal real pain — not polished feedback.
• Complaint Mining: How to Use Reddit as a Research Lab (media) — The exact search patterns and thread types that surface high-signal complaints in any niche.
• The Observation Audit: Finding $10k Problems in "Boring" Industries (media) — How to step outside the developer bubble to spot manual inefficiencies in retail, logistics, and specialized services.
• The JTBD Blueprint: Why Customers "Hire" Your Solution (media) — A guide to the Jobs-to-be-Done framework to uncover the deeper functional and emotional progress users are trying to make.
• Calculating the "Cost of Doing Nothing": Quantifying Pain into Dollars (media) — How to move beyond 'it's a problem' to proving it costs the user exactly $X or Y hours per month.
• The Manual Trail: How to Map Workarounds and Concierge MVPs (media) — Identify high-signal manual workarounds like complex spreadsheets and old hardware as proof of a market gap.
• The Job Map™: Deconstructing the Workflow to Find Hidden Friction (media) — Stop looking at the user — look at the underlying process to find gaps that current software and manual tools miss.
• Hiring and Firing: Using the "Switch Interview" to Predict Adoption (media) — Beyond the Mom Test — uncovering the psychological forces that determine whether a user will actually fire their current workaround to hire your product.
• Opportunity Scoring: Turning Subjective Pain into a Data-Driven Strategy (media) — Moving from gut feeling to a mathematical formula that identifies which parts of a problem are most ripe for disruption.
• The Observation Audit: How StageTimer Found a $10k Problem in a Boring Industry (case-study) — How Lucas Hermann skipped the survey and watched a professional struggle with subpar tools — then built a profitable product in 72 hours.
• The Niche Pivot: How CloudSync Pro Escaped an Oversaturated Market (case-study) — Sarah Chen started with 'better project management software' — then found a specific niche signal that saved her two years and made her $1.2M ARR.
• The Reddit Engagement Loop: How Buildpad Hit 100 Users in Two Weeks (case-study) — A solo builder used a feedback-exchange strategy on Reddit to run 10–15 deep validation interviews in one week — then built to $7,300/mo.
• The False Positive Trap: What an 89% Survey Score Actually Means (case-study) — A founder surveyed 500 people, got 89% saying they 'definitely need it,' spent $100k building — and launched to 12 signups and $45 in revenue.
• Google Trends: Quantifying Market Urgency (tool) — See whether demand for your idea is growing or shrinking — free, instant, and essential for spotting seasonal patterns and emerging markets.
• Answer Socrates: Mining the "Natural Language" Long Tail (tool) — Uncover the exact questions real people type into search engines — revealing the specific frustrations hidden in 'how do I' and 'why is X so hard' queries.
• Preuve AI: Evidence-Based Idea Scanning (tool) — Scans 40+ sources — Reddit, Product Hunt, review platforms — to find evidence of problem pain and demand signals in under 60 seconds.
• Notion Interview Workspace: Organizing the Chaos (tool) — Free structured templates for tracking customer discovery calls and defining your ICP — so interview insights don't get lost in scattered notes.
• PainOnSocial: Reddit Pain Pattern Analysis (tool) — AI-powered analysis of Reddit conversations that scores frustrations by frequency and intensity — so you can prioritize which problems are most worth solving.
• User Interview & Discovery Workspace (template) — A centralized hub to plan, schedule, and summarize discovery calls — with structured sections for consent, observation notes, and post-interview summaries.
• 5 Ws Problem Framing Framework (template) — A methodical breakdown that forces you to define the unmet need clearly — moving from a vague idea to a specific, testable problem statement using Who, What, When, Where, and Why.
• Jobs-to-be-Done (JTBD) Analysis Builder (template) — A workspace that shifts your thinking from product features to the job a user is trying to accomplish — includes a Job Statement builder and a database for functional, emotional, and social needs.
• Universal Job Map Canvas (template) — A Miro canvas that deconstructs the customer's job into 8 solution-agnostic steps — identifying exactly where hidden friction and unmet needs live within a complex workflow.
• JTBD Hypothesis Canvas (template) — A strategic alignment tool for scoping the entire job landscape before field research — identifies the job performer, their aspirations, and the contextual factors that influence how effectively the job gets done.
• The 'Polite Praise' False Positive (warning) — The most dangerous data you can collect is a compliment. 'That sounds great!' is a polite way to end a conversation — not evidence of demand.
• The 'Developer Bubble' Trap (warning) — Building tools for other developers is a comfortable default — and a crowded market where users expect everything to be free and will often build their own version instead of paying for yours.
• The 'Vitamin vs. Painkiller' Error (warning) — A problem is only a business if it's a painkiller — urgent, frequent, and costly. If your idea is just annoying or nice-to-have, you'll fight for every sale.
• The Single-Cause Fallacy & Signal Noise (warning) — Simplifying early feedback down to one metric while ignoring broader misalignments — or trusting early adopter signals as proof of mass-market need — will send you in the wrong direction.
• Ignoring 'Switching Forces' (warning) — You can validate a burning problem, but if the anxiety or habit forces are too strong, the user will never adopt your solution — no matter how well it works.
• Moonshots Podcast — Episode 42: Eric Ries, The Lean Startup (media · podcast) — Eric Ries breaks down the core ideas behind the Lean Startup — validated learning, the build-measure-learn loop, and why most startups fail by building before they've proven demand.
• Moonshots Podcast — Lean Startup (media · podcast) — A focused Moonshots episode on the Lean Startup methodology — covering the minimum viable product concept, pivot vs. persevere decisions, and how to structure early-stage experimentation.
• The Eric Ries Show (media · podcast) — Eric Ries in long-form conversation with founders and operators — exploring how lean principles translate to real company decisions, product strategy, and organizational design.
• Problem Solved with Jeff Guenther and Alex Moskovich (media · podcast) — A podcast dedicated to problem-first thinking — each episode works through a specific business problem, exploring how to identify the root cause before reaching for solutions.
• Customer Discovery — How to Build a Startup (media · youtube) — Steve Blank's Udacity lecture on the customer discovery process — the foundational step in the Customer Development methodology that comes before any product building.
• How to Do Customer Discovery to Validate Your Startup Assumptions (media · youtube) — A practical walkthrough of running customer discovery interviews to test your core assumptions — covering question design, avoiding leading questions, and interpreting what you hear.
• Using Customer Discovery to Validate Your Product, with Pete Kazanjy (media · youtube) — Pete Kazanjy (Atrium) on using customer discovery to validate whether your product is solving the right problem before investing in a full build — with specific techniques for B2B founders.
• How to Validate Your Startup with Customers Before Building (media · youtube) — A concise, structured walkthrough of the pre-build validation process — covering how to find interviewees, what to ask, and how to turn raw conversations into a go/no-go decision.

Get the AI pack for Stage 1 →