Mom Test

The Mom Test Framework

Framework for customer conversations that won't lead you astray, based on a fundamental truth: everyone is lying to you -- not maliciously, but because you're asking the wrong questions. The Mom Test provides rules for asking questions so good that even your mom can't lie to you.

Core Principle

Good customer conversations are about their life, not your idea. The moment you mention what you're building, people switch from sharing truth to performing politeness. Talk about their problems, their lives, and their existing behavior instead of pitching, and ask about specifics in the past, not hypotheticals about the future. Above all, talk less and listen more.

Scoring

Goal: 10/10. Rate customer conversations 0-10 against the principles below: a 10/10 focuses entirely on the customer's life and past behavior, with no leading, no pitching, and clear commitment signals. Always state the current score and the specific improvements needed to reach 10/10.

Framework Sections

1. The Mom Test Rules

Core concept: Three rules that make it impossible for even your most supportive loved ones to give you false validation, shifting conversations from opinion-gathering to fact-finding.

Why it works: People are unreliable predictors of their own future behavior, so opinions are worthless. Past behavior is the only reliable data and can genuinely inform product decisions.

Key insights:

• Rule 1: Talk about their life, not your idea -- never mention your solution until the end, if at all
• Rule 2: Ask about specifics in the past, not generics or hypotheticals about the future
• Rule 3: Talk less, listen more -- aim for them to speak 80% of the time
• A question fails the Mom Test if the answer is always "yes" regardless of whether the business will succeed
• Good questions could potentially destroy your currently imagined business

Product applications:

Copy patterns:

• "Tell me about the last time you..."
• "How are you dealing with that currently?"
• "What else have you tried?"

Ethical boundary: Never weaponize someone's honest answers against them -- using vulnerability data to manipulate sales crosses the line.

See: references/question-patterns.md for good vs bad question examples, the three rules in depth, and formulation exercises.

2. Good vs Bad Questions

Core concept: Most interview questions are broken because they ask people to predict the future, evaluate hypothetical products, or confirm your assumptions. Good questions anchor in observable past behavior and extract concrete facts.

Why it works: Asking "would you buy this?" is like asking "will you go to the gym next week?" -- the answer is always yes, the follow-through rarely there. Behavior that already happened can't be rationalized away.

Key insights:

• Bad: "Do you think it's a good idea?" -- always gets a yes
• Bad: "Would you buy a product that does X?" / "How much would you pay?" -- hypothetical, anchored to please you
• Good: "How are you dealing with this problem today?" -- reveals actual behavior
• Good: "What have you tried before and why did you stop?" -- reveals past decisions
• Good: "Where does the money come from for solutions like this?" -- reveals real budgets
• The scariest questions -- ones with the power to change what you're building -- produce the most useful data

Product applications:

Copy patterns:

• "What's the hardest part about [doing this thing]?"
• "How often does this come up?"
• "Talk me through the last time this happened"

Ethical boundary: Never use leading or loaded questions that anchor the respondent toward your desired answer -- your job is to learn, not to sell.

3. Avoiding Compliments and Opinions

Core concept: Three types of bad data feel like progress but actively mislead: compliments ("That's a great idea!"), fluff (hypotheticals, maybes, future promises), and ideas (feature requests disconnected from real problems). Deflecting these and digging for truth is the core skill.

Why it works: Compliments are the fool's gold of customer development -- they feel amazing but contain zero information about whether anyone will pay or use the product. Only specifics about real past behavior and genuine commitments provide signal.

Key insights:

• Compliments: deflect immediately and return to concrete facts about how they handle the problem today
• Fluff: generic claims ("I usually," "I always," "I would never") are worthless without a specific instance
• Ideas: dig into the motivation behind every feature request -- what's driving it, when they last needed it
• Fishing for compliments ("Don't you think this would be useful?") is unconscious validation-seeking
• Symptom of a bad conversation: you walk away feeling great but with no concrete facts or commitments

Product applications:

Copy patterns:

• "Thanks, but to make sure I'm not wasting your time -- what does your current process look like?"
• "When you say you'd 'definitely' use this, what would you stop using?"
• "That's a great feature idea -- what problem would it solve for you specifically?"

Ethical boundary: Deflecting compliments is about getting to truth, not pressuring someone into a sale.

See: references/avoiding-bad-data.md for the three bad-data types and deflection scripts.

4. Commitment and Advancement

Core concept: The currency of a customer conversation is commitment, not compliments. End every conversation with a clear advance toward adoption or a clear rejection -- the worst outcome is a "zombie lead" who is polite but never commits.

Why it works: Saying "I'd definitely buy that" costs nothing; offering an intro, a deposit, or a pilot invests something real. Commitment closes the dangerous gap between what people say and what they do.

Key insights:

• Commitment currencies: time (meeting, trial), reputation (intro, testimonial), money (deposit, pre-order, letter of intent)
• Advancing moves the relationship toward a sale; spinning wheels produces pleasant, useless meetings
• Know your "ask" before the meeting -- the minimum commitment that proves this is real
• A "no" is more valuable than a "maybe" -- you can learn from it and move on
• If they won't give you their time, they definitely won't give you their money

Product applications:

Copy patterns:

• "Who else should I talk to about this?"
• "Would you be willing to try a prototype next week?"
• "If I built this, would you be willing to pilot it for 30 days?"

Ethical boundary: Separate real interest from politeness -- never pressure people into commitments they'll regret.

See: references/commitment-advancement.md for commitment currencies and pushing for advancement.

5. Finding Conversations

Core concept: The best customer conversations happen casually -- warm intros, industry events, online communities, coffee. Formal "customer interview" framing triggers performance mode; casual framing produces honest data.

Why it works: "Can I interview you about your problems?" makes people polished and guarded; "I'm trying to learn about the industry -- can I buy you coffee?" makes them open up. The framing determines the quality of the data.

Key insights:

• Cold outreach: keep it short, lead with their expertise, don't pitch
• Warm intros are the best source -- one well-connected advisor can open dozens of doors
• Go where customers already gather: industry events, meetups, online communities (participate genuinely first)
• "I'm trying to learn" beats "I'm doing customer research"
• Use the five-part structure for getting meetings: vision / framing / weakness / pedestal / ask

Product applications:

Copy patterns:

• "I'm researching how [industry] handles [problem] -- could I learn from your experience over a 15-minute coffee?"
• "[Mutual contact] suggested I talk to you because you know a lot about [area]"
• "I'm not trying to sell anything -- I'm just trying to understand the space"

Ethical boundary: Never disguise a sales call as a learning conversation -- if you already have a product and are selling, be transparent.

See: references/finding-conversations.md for cold vs warm approaches and keeping it casual.

6. Processing and Learning

Core concept: Conversations are only useful if processed: distill raw notes into beliefs, update them regularly, and share with your team. Without a system you'll cherry-pick quotes that confirm your biases.

Why it works: Memory is biased toward recent and emotionally charged information, so teams selectively remember confirming data. Processing as a team prevents any one person's bias from dominating the narrative.

Key insights:

• Take notes during or immediately after -- never rely on memory
• Separate facts (what they said and did) from interpretations (what you think it means)
• Share raw notes with your team, not filtered summaries
• Update your three key beliefs after each batch: the problem, the customer segment, the solution
• Stop talking and start building when conversations start repeating
• Use a simple spreadsheet: who, date, key quotes, facts, commitments, belief changes

Product applications:

Copy patterns:

• "Our current belief is X -- here's what confirms it and what challenges it"
• "We've heard this from N of M people -- is that enough signal?"
• "Time to stop talking and build -- conversations are repeating"

Ethical boundary: Never selectively quote conversations to justify a predetermined conclusion -- honest processing means accepting uncomfortable truths.

See: references/processing-learning.md for note-taking systems and knowing when to stop talking.

Common Mistakes

Quick Diagnostic

Reference Files

• question-patterns.md: Good vs bad question examples, the three rules in depth, question formulation exercises
• commitment-advancement.md: Commitment currencies, advancing vs spinning wheels, how to push for commitment
• avoiding-bad-data.md: Compliments, fluff, ideas -- the three types of bad data and how to deflect them
• finding-conversations.md: Where to find people, cold vs warm approaches, keeping conversations casual
• processing-learning.md: Note-taking, team sharing, updating beliefs, knowing when to stop talking
• case-studies.md: Realistic scenarios showing Mom Test principles applied to SaaS, consumer, B2B, and marketplace contexts

Further Reading

This skill is based on Rob Fitzpatrick's Mom Test methodology:

• *"The Mom Test: How to Talk to Customers & Learn if Your Business is a Good Idea When Everyone is Lying to You"* by Rob Fitzpatrick

About the Author

Rob Fitzpatrick is an entrepreneur and educator who founded multiple venture-backed startups and learned the hard way that most customer conversations produce misleading feedback. The Mom Test (2013) distills his evidence-based approach, has been translated into 20+ languages, and is required reading at accelerators including Y Combinator and Techstars. He also wrote The Workshop Survival Guide and Write Useful Books.

Avoiding Bad Data: Compliments, Fluff, and Ideas

Bad data is worse than no data because it gives you false confidence. You build the wrong thing, launch to crickets, and can't figure out what went wrong because "everyone said they loved it." This reference covers the three types of bad data, how to recognize them in real-time, and specific techniques for deflecting each type back to useful information.

The Three Types of Bad Data

Type 1: Compliments

Compliments are the most common and most dangerous form of bad data. They feel amazing in the moment and are completely worthless for decision-making.

What compliments sound like:

• "That's a really cool idea!"
• "I can definitely see myself using that."
• "You guys are going to crush it."
• "This is exactly what the market needs."
• "I love it. When can I get it?"
• "You're solving a real problem."
• "My team would love this."

Why compliments are dangerous: Compliments contain zero information about whether someone will change their behavior, pay money, or use your product. They're a social reflex -- the same way you say "I'm good" when someone asks how you are. People compliment you because:

• They want to be supportive
• Saying "bad idea" feels cruel
• They haven't thought about it deeply enough to have a real opinion
• They want the conversation to end pleasantly

How to deflect compliments:

The golden rule: Every time you receive a compliment, convert it into a question about their life and past behavior.

Type 2: Fluff

Fluff is vague, generic, or hypothetical talk that sounds informative but carries no real-world weight. It's the verbal equivalent of empty calories.

Three sub-types of fluff:

Generic Claims

• "I usually..." (without a specific instance)
• "I always..." (really? always?)
• "I never..." (provably false in most cases)
• "We generally..." (who, specifically? when?)

Deflection: "Can you give me a specific example of the last time that happened?"

Hypothetical Promises

• "I would definitely..." (but you haven't)
• "If you built that, I'd..." (future tense = fiction)
• "I think I'd probably..." (double hedging)
• "That would be worth at least $X to me" (imaginary money)

Deflection: "You mentioned you'd pay $X. What's the most you've actually paid for a tool like this?"

Future-Tense Predictions

• "Next quarter, we're planning to..."
• "We'll probably need something like this soon"
• "I'm going to start looking for a solution"
• "That's on our roadmap for later this year"

Deflection: "When did you first realize this was a problem? What have you done about it so far?"

The fluff test: If you can't assign a date, a dollar amount, or a specific event to what they said, it's fluff. Dig until you hit concrete ground.

Type 3: Ideas (Unsolicited Feature Requests)

When people understand what you're building, they start designing your product for you. This feels collaborative and exciting, but it's usually misleading because they're solving an imagined version of the problem.

What idea-giving sounds like:

• "You should totally add [feature]"
• "It would be amazing if it could also [function]"
• "Have you thought about integrating with [tool]?"
• "What if it also did [tangentially related thing]?"
• "The real killer feature would be [thing they thought of in the last 30 seconds]"

Why ideas are dangerous: Feature requests are solutions, not problems. When someone says "you should add a chat feature," you don't know:

• What problem they're trying to solve
• Whether they've actually experienced that problem
• Whether they'd use the feature if you built it
• Whether this is a deal-breaker or a nice-to-have

How to deflect ideas back to problems:

The idea deflection formula: 1. Acknowledge: "That's an interesting idea." 2. Record: Write it down (shows respect). 3. Dig: "What's driving that? Tell me about the last time you needed something like that."

The Approval-Seeking Trap

The most subtle form of bad data collection is when you unconsciously seek validation instead of information. This happens when:

You're Fishing for Compliments Without Realizing It

Signs you're fishing:

• You describe the idea in glowing terms before asking questions
• You lead with the solution and then ask "what do you think?"
• You show excitement and energy that makes disagreement feel rude
• You ask leading questions: "Don't you think it would be better if...?"
• You share your vision for 10 minutes, then ask a token question

Signs you're genuinely learning:

• You haven't mentioned your idea yet and they're doing most of the talking
• You're asking about their problems, not your solution
• You're comfortable with silence after a question
• You're genuinely curious about answers that might kill your idea
• You're taking notes on what they say, not on how they react to your pitch

The Pitch-Creep Problem

Pitch-creep happens when a learning conversation gradually becomes a sales pitch. It usually follows this pattern:

1. You start with good questions about their problems (learning mode) 2. They describe a problem you can solve (excitement builds) 3. You say "Actually, that's exactly what we're building!" (pitch mode activated) 4. The rest of the conversation is about your solution (learning stops) 5. They say "That sounds great!" (compliment received) 6. You leave feeling validated (but you learned nothing new after step 2)

How to prevent pitch-creep:

• Set a rule: no pitching until the last 5 minutes
• Bring a partner who kicks you under the table when you start pitching
• Write "SHUT UP" on the top of your notepad
• Practice the phrase: "That's really helpful context. Can you tell me more about [their problem]?"

The "Would You Buy" Trap

"Would you buy this?" is the single most popular and most useless question in customer development. Here's why:

The scenario: You describe your product. You ask "would you buy this?" They say "yes." You feel great.

The reality: Of course they said yes. Saying "no" to your face would be uncomfortable. They're not lying -- in this hypothetical moment, they genuinely believe they would. But this belief has no predictive power because:

• They haven't felt the pain of actually parting with money
• They haven't compared your solution to alternatives
• They haven't considered whether this is a top priority
• They haven't thought about the switching cost from their current workflow
• They're answering in a context of social pressure (you're sitting right there)

What to ask instead:

Real-Time Bad Data Detection

During a conversation, monitor for these warning signs:

Conversation Quality Scorecard

Running score interpretation:

• Positive score: You're learning. Keep going.
• Zero or negative: You've drifted into bad data territory. Reset with a behavior question.

Recovery Phrases

When you realize you're in bad data territory, use these phrases to reset:

• "I appreciate the encouragement. To make sure we get this right -- can you walk me through how you dealt with this last week?"
• "That's helpful. Let me back up -- tell me about the last time this problem actually cost you time or money."
• "I want to make sure I'm not just hearing what I want to hear. What would make this NOT work for you?"
• "Let's put my idea aside for a second. What's the biggest headache in your [relevant area] right now?"
• "I hear you saying you'd use this. Help me understand -- what would you stop doing if you started using something like this?"

The Post-Conversation Gut Check

After every conversation, ask yourself these five questions:

1. Did I learn any new facts I didn't know before? If no, you were probably collecting compliments.

2. Can I summarize what I learned without mentioning my product? If no, the conversation was about your idea, not their life.

3. Did anything surprise me or challenge my assumptions? If no, you were probably asking leading questions.

4. Did they give a concrete commitment? If no, you may have a zombie lead.

5. Would my co-founder learn something new from these notes? If no, the notes contain opinions rather than facts.

If you answer "no" to three or more of these questions, the conversation produced bad data. Don't count it as validation. Learn from the mistake and adjust your approach for the next conversation.

The Emotional Cost of Good Conversations

Good conversations are uncomfortable. You will hear things like:

• "I don't think I'd actually pay for that."
• "That's not really a problem for me."
• "I already have a solution that works fine."
• "I don't think this is a priority."

These responses feel bad in the moment but are enormously valuable. A painful truth heard early saves you months of building the wrong thing. The emotional cost of a hard conversation is tiny compared to the cost of building a product nobody wants.

Reframe: A conversation that kills a bad idea is the most valuable conversation you'll ever have. It just saved you a year of your life.

Case Studies: The Mom Test in Action

Four realistic scenarios showing Mom Test principles applied to different startup contexts. Each case study follows a founder through bad conversations, identifies what went wrong, and shows how applying The Mom Test produces genuinely useful data.

Table of Contents

1. Case Study 1: TaskFlow (B2B SaaS -- Project Management) 2. Case Study 2: FreshPlate (Consumer App -- Meal Planning) 3. Case Study 3: SupplyLink (B2B -- Marketplace for Wholesale Suppliers) 4. Case Study 4: StudyBuddy (Marketplace -- Peer Tutoring) 5. Patterns Across All Four Cases

---

Case Study 1: TaskFlow (B2B SaaS -- Project Management)

The Idea

Alex is building TaskFlow, a project management tool designed specifically for marketing agencies. He believes agencies struggle with tracking campaigns across multiple clients and need a dedicated tool.

The Bad Conversations

Alex meets with Maria, who runs a 15-person digital marketing agency.

Alex: "I'm building a project management tool specifically for marketing agencies. We'd have campaign tracking, client dashboards, and deadline management all in one place. What do you think?"

Maria: "That sounds amazing! We're always struggling with keeping track of everything. I'd love something built for agencies."

Alex: "Would you pay $50 per user per month for something like this?"

Maria: "Absolutely. That's totally reasonable for the time it would save us."

Alex leaves feeling validated. Score: 0/10.

What Went Wrong

The Mom Test Conversation (Redo)

Alex: "I'm trying to understand how agencies manage their project workflow. Can you walk me through how a typical campaign goes from kickoff to delivery?"

Maria: "Sure. So when a new client comes in, we create a folder in Google Drive, set up a Slack channel, and our PM creates tasks in Asana. Reporting goes through a custom spreadsheet we built."

Alex: "You mentioned Asana. How's that working for you?"

Maria: "Honestly, it's fine for task tracking. The real problem is the reporting. My team spends about 6 hours every week manually pulling data from Google Analytics, Facebook Ads, and Asana into a spreadsheet to create client reports. It's brutal."

Alex: "6 hours per week -- is that one person or spread across the team?"

Maria: "That's our ops manager. She hates it. She threatened to quit over it last month, actually."

Alex: "Have you tried anything to fix this?"

Maria: "We looked at some reporting tools. Tried Databox for a while. Paid about $200 a month. But it couldn't pull from Asana, so we still had to do half of it manually. We cancelled after 3 months."

Alex: "If you had to rank your top 3 operational headaches, where does reporting fall?"

Maria: "Number one, no question. Client management is fine. Project tracking is fine. Reporting is killing us."

What Alex Actually Learned

• The problem isn't project management -- it's reporting
• They already pay for Asana and are satisfied with task tracking
• They previously paid $200/month for a reporting solution (real willingness to pay)
• The pain is acute enough that someone nearly quit over it
• The specific gap is cross-platform data aggregation (analytics + ads + task tool)
• This completely changes what Alex should build

The Commitment Test

Alex: "This is really helpful. Based on what I'm hearing from you and others, we're exploring automated reporting that pulls from multiple sources. If I had a prototype in 3 weeks, would you be willing to test it with one client for a week?"

Maria: "Absolutely. Can you have it pull from Google Analytics and Asana? Those are the two most painful ones."

Result: Concrete commitment (time + access to real data). This is advancement, not spinning wheels.

---

Case Study 2: FreshPlate (Consumer App -- Meal Planning)

The Idea

Jordan is building FreshPlate, a meal planning app that generates weekly grocery lists based on dietary preferences. She believes busy parents want help planning healthy meals.

The Bad Conversations

Jordan talks to her friend Dave, a father of two.

Jordan: "I'm building a meal planning app for busy parents. You pick your dietary preferences, it generates a weekly meal plan with recipes, and it creates a grocery list. Does that sound like something you'd use?"

Dave: "Oh wow, that would be incredible. We never know what to make for dinner. We always end up getting takeout."

Jordan: "How much would you pay for something like this?"

Dave: "I don't know... maybe $10 a month? $15? It would save so much time."

Jordan: "Would you sign up for a beta?"

Dave: "For sure! Send me the link."

Score: 1/10. Jordan got one small signal (they get takeout often) but buried it under bad questions.

The Mom Test Conversation (Redo)

Jordan: "I'm curious about how your family handles dinner on weeknights. What happened last night?"

Dave: "Last night... honestly, we ordered pizza. Again. Third time this week."

Jordan: "What did you do the other nights?"

Dave: "Monday I think we made pasta -- just spaghetti with sauce from a jar. Tuesday we had leftover pizza. It's been a rough week."

Jordan: "Is this a typical week or unusual?"

Dave: "Pretty typical, honestly. We cook maybe two real meals a week. The rest is takeout or scrambled eggs."

Jordan: "Have you tried anything to cook more? Meal kits, apps, anything?"

Dave: "We did Blue Apron for about three months. It was $80 a week. The food was great but honestly, the cooking still took 45 minutes to an hour, and by the time we get home from work, feed the kids a snack, and do homework... we just don't have the energy."

Jordan: "What happened when you cancelled Blue Apron?"

Dave: "We said we'd start meal planning on Sundays. Bought a whiteboard for the fridge and everything. That lasted maybe two weeks. The whiteboard's been blank for six months."

Jordan: "So the problem isn't knowing what to cook -- it's having the energy to actually cook it?"

Dave: "Yeah, exactly. We have a folder full of recipes we'll never make. The issue isn't ideas. It's that cooking takes too long when you're exhausted."

What Jordan Actually Learned

• The problem isn't meal planning -- it's cooking time and energy
• They already have recipes and even tried planning (the whiteboard)
• Blue Apron proved they'll pay $80/week but failed on the time dimension
• The real competition isn't other apps -- it's takeout ($15-30 per night, multiple times per week)
• A meal planning app doesn't solve the core problem (which is energy/time after work)
• The real opportunity might be pre-prepped ingredients or 15-minute meals, not planning

The Pivot Signal

Jordan's conversations reveal that 8 out of 12 parents describe the same pattern: they know what they should cook, they have recipes, they even buy ingredients -- but they're too exhausted by 6pm to actually cook. A meal planning app solves a problem that doesn't exist for this segment. The actual product might need to be something completely different.

---

Case Study 3: SupplyLink (B2B -- Marketplace for Wholesale Suppliers)

The Idea

Priya is building SupplyLink, a marketplace connecting small retailers with wholesale suppliers. She believes small store owners struggle to find reliable suppliers and get competitive pricing.

The Bad Conversations

Priya visits a small boutique gift shop and talks to the owner, Tom.

Priya: "I'm building a platform that helps small retailers find wholesale suppliers with competitive pricing. Would that be useful for you?"

Tom: "Oh definitely. Finding good suppliers is such a pain."

Priya: "What if you could compare prices from multiple suppliers in one place?"

Tom: "That would be a game-changer. I'd use that for sure."

Score: 0/10. Classic Mom Test failures. Tom said what Priya wanted to hear.

The Mom Test Conversation (Redo)

Priya: "I'm trying to understand how small retailers source their products. Can you walk me through how you chose your current suppliers?"

Tom: "Most of them I've been working with for years. My candle supplier -- I met her at a trade show in 2019. My jewelry line is from a friend of a friend. The stationery is from a company I found on Faire."

Priya: "When was the last time you actually looked for a new supplier?"

Tom: "Hmm. Probably eight months ago. I wanted to add home decor. I went to AmericasMart in Atlanta."

Priya: "How did that go?"

Tom: "It was fine. Found two new vendors. But honestly, the real problem isn't finding suppliers -- it's minimum order quantities. I found amazing ceramics from this one artist, but her minimum was 200 units. I can't carry 200 of anything. My store is 800 square feet."

Priya: "Do other store owners you know have the same issue?"

Tom: "Every small store owner I know. The suppliers want big orders, and we want small batches to test what sells. It's a constant tension."

Priya: "Have you ever tried to negotiate lower minimums?"

Tom: "All the time. Usually doesn't work. Sometimes I'll go in with another store owner and split an order, but that's a logistical headache -- coordinating, splitting the delivery, fronting the money."

Priya: "How often do you do that split-order thing?"

Tom: "Maybe 3-4 times a year. It's worth it when the product is great, but I've stopped doing it with anyone I don't trust completely because one time a co-buyer flaked and I was stuck with $3,000 of products I couldn't move."

What Priya Actually Learned

• Discovery isn't the core problem -- relationships and trade shows work
• Minimum order quantities are the real pain point
• Store owners already informally solve this (cooperative buying) but it's risky and hard to coordinate
• There's existing spending (trade show attendance, shared orders) that validates willingness to invest
• The real product might be a cooperative buying platform, not a supplier discovery marketplace
• Trust and reliability between co-buyers is a critical factor

The Commitment Test

Priya: "I'm exploring ways to make cooperative buying less risky for small retailers. If I built something that matched stores for shared orders with payment protection, would you try it with your next order?"

Tom: "That's actually interesting. My next order is in about six weeks. If you have something by then, I'd try it. Can I give you my email?"

Result: Specific timeline (six weeks), specific use case (his next order), and proactive offer of contact info. Real interest.

---

Case Study 4: StudyBuddy (Marketplace -- Peer Tutoring)

The Idea

Kenji is building StudyBuddy, a marketplace connecting college students who need help in courses with peers who recently aced those same courses. He believes students prefer peer tutoring over professional tutoring because it's more relatable and affordable.

The Bad Conversations

Kenji surveys 50 students online with the question: "Would you pay $15/hour for peer tutoring from a student who got an A in your course?" 82% said yes.

Score: 1/10. Hypothetical survey data from a self-selected sample. Completely unreliable.

The Mom Test Conversations

Kenji sits in the university library and approaches students who look like they're struggling.

Conversation 1: Lin (Organic Chemistry student)

Kenji: "You look like you're deep into something intense. What are you studying?"

Lin: "Orgo. I have a midterm Friday and I'm panicking."

Kenji: "Have you tried getting any help?"

Lin: "I went to the TA's office hours twice. It's packed -- like 30 people in a tiny room. You can't even ask a question. I tried watching YouTube videos but Professor Stevens teaches it differently, so the methods don't match up."

Kenji: "Have you tried a tutor?"

Lin: "I looked into it. The university tutoring center is free but you have to book a week in advance and it's group sessions. I looked at Wyzant but it's like $40-60 an hour. I can't afford that."

Kenji: "What did you end up doing?"

Lin: "I texted my friend Sarah who took this class last semester and asked her to explain chapter 5. She came over for an hour. It was honestly the most helpful thing I've done all semester."

Kenji: "Did you pay her?"

Lin: "No, she's my friend. But I felt bad about it. I bought her lunch."

Conversation 2: Marcus (Computer Science student)

Kenji: "How's your semester going?"

Marcus: "Honestly, terrible. I'm failing Data Structures. I've never failed anything before."

Kenji: "What have you tried?"

Marcus: "I go to every lecture, take notes, do the homework. But when I sit down for the exams, I blank. I think I understand it but then I can't apply it."

Kenji: "Have you talked to the professor?"

Marcus: "I went to office hours once. It was awkward. He kind of made me feel stupid for not getting it. I haven't gone back."

Kenji: "Have you tried studying with anyone?"

Marcus: "I tried a study group with people from class, but honestly, none of us know what we're doing, so it's the blind leading the blind. What I really need is someone who actually understands this stuff and can explain it in normal language, not professor-speak."

Kenji: "What would that look like ideally?"

Marcus: "Someone who took this exact class, with this exact professor, and got an A. They'd know the exam format, which topics to focus on, what the professor actually cares about. That's worth way more than a random tutor who's great at CS but doesn't know this class."

What Kenji Actually Learned

• The hypothesis is validated: students do want peer help from people who took their exact course
• The existing alternatives (TA office hours, tutoring center, Wyzant, study groups) all fail for specific reasons
• Students already do this informally (Lin asked her friend) -- the behavior exists
• Price sensitivity is real: $40-60/hour is too expensive, but $15-20/hour might work
• The key value proposition isn't "peer tutoring" generically -- it's course-specific and professor-specific knowledge
• The matching algorithm needs to match by course + professor + semester, not just subject area

The Commitment Test

Kenji (to Lin): "What if I could connect you with someone who got an A in Stevens's Orgo class last semester, for $15 an hour? Would you want a session before your midterm?"

Lin: "Yes. Can you actually do that? I'd want to meet tomorrow if possible."

Kenji (to Marcus): "If I find someone who aced Data Structures with your professor last semester, would you pay $15 for an hour with them this week?"

Marcus: "I'd do two hours. Seriously. When can we set this up?"

Result: Both students want it now, urgently, and are willing to pay. This is a strong signal. Kenji's next step is to find the supply side -- recent A students willing to tutor for $15/hour.

---

Patterns Across All Four Cases

1. The Stated Problem Is Rarely the Real Problem

• TaskFlow: "Project management" was fine; reporting was the real pain
• FreshPlate: "Meal planning" wasn't the issue; energy and cooking time were
• SupplyLink: "Finding suppliers" was manageable; minimum order quantities were the blocker
• StudyBuddy: "Tutoring" is too generic; course-specific peer knowledge is the real value

2. Past Behavior Reveals More Than Opinions

In every case, asking about what people have already done (Blue Apron subscription, co-buying attempts, asking a friend for help) produced more reliable data than any hypothetical question could.

3. Existing Spending Validates Willingness to Pay

Every case revealed existing spending on the problem: $200/month for Databox, $80/week for Blue Apron, trade show attendance, buying a friend lunch. These are real data points for pricing.

4. Commitment Separates Real Interest from Politeness

In the good conversations, concrete commitments emerged naturally: test a prototype in 3 weeks, try cooperative buying on the next order, book a session this week. These are the signals that matter.

5. The Biggest Risk Is Building the Wrong Thing

In three of four cases, the original product idea would have missed the mark. Mom Test conversations saved months of building by revealing the true problem early.

Commitment and Advancement

The most dangerous lie in customer development is "That sounds great -- keep me posted." It feels like progress but is actually a polite dismissal. This reference covers how to distinguish real interest from empty enthusiasm, the three commitment currencies, and how to design conversations that end with clear advances.

The Core Problem: Compliments vs Commitments

Compliments are free. Saying "great idea" costs nothing. Real interest always costs something -- time, reputation, or money. If someone won't invest any of these three currencies, they're not a real customer. They're being polite.

The Spectrum from Worthless to Valuable

Worthless                                                        Valuable
   |                                                                |
   "Cool idea"  →  "Keep me posted"  →  "I'll try it"  →  "Here's a deposit"
   "Love it"    →  "Send me info"    →  "Meet my boss"  →  "Letter of intent"
   "Sounds great" → "Let me think"   →  "Pilot program"  → "Pre-order payment"

The left side costs nothing. The right side costs something real. Your job is to push every conversation as far right as possible -- not to close a sale, but to test whether interest is real.

The Three Commitment Currencies

1. Time Commitment

Time is the easiest currency to ask for and the first test of real interest. If someone won't give you 15 more minutes, they won't give you their money.

Escalation ladder:

How to ask for time commitments:

• "Would you be up for a 15-minute demo next week?"
• "We're running a small pilot -- it's 30 days, minimal setup. Would you be interested?"
• "I'd love to show you a prototype. Can we book 20 minutes next Thursday?"
• "We're hosting a workshop on this topic. Would you attend?"

Red flags:

• "Sure, just email me" (with no specific date/time = probably won't happen)
• "Maybe next month" (indefinite postponement = not interested)
• Cancels or reschedules repeatedly (actions reveal true priority)

2. Reputation Commitment

When someone risks their professional reputation by connecting you to their network, they're investing social capital. This is a stronger signal than time because it costs them something irreversible -- if your product is bad, they look bad.

Escalation ladder:

How to ask for reputation commitments:

• "Who else on your team deals with this problem? Could you introduce me?"
• "You mentioned your VP is frustrated by this -- would you be comfortable connecting us?"
• "If we build this, would you be willing to be one of our first case studies?"
• "Do you know 2-3 other people who struggle with this? Would you mind introducing me?"

Red flags:

• "I know someone, but let me think about it" (never follows up)
• Offers a general referral but won't make a specific intro
• Introduces you but adds caveats that undermine credibility

3. Money Commitment

The ultimate test. Money is the most reliable signal because it is the most costly. If someone pays you -- even a small amount -- they are a real customer, not just a fan.

Escalation ladder:

How to ask for money commitments:

• "We're offering early access at 40% off for our first 10 customers. Would you want one of those spots?"
• "Would you be willing to put down a $100 refundable deposit to lock in your place?"
• "We're validating demand -- if we build this, would you pre-order at $X?"
• "Can I send you a letter of intent for a pilot? No obligation, but it helps us prioritize."

Red flags:

• "I'd definitely pay for that" (without actually paying -- classic Mom Test failure)
• "Let me check with my team" (stalling without a deadline)
• Agrees to a price but won't sign anything or provide payment info

Advancement vs Spinning Wheels

What Advancement Looks Like

Every conversation should move the relationship forward. If you can't point to a concrete next step with a specific date, you're spinning your wheels.

Clear advances:

• They agree to a follow-up meeting with a specific date and time in the calendar
• They introduce you to someone specific via email (not "I'll mention you sometime")
• They sign up for a pilot, trial, or beta program with a start date
• They provide a deposit, pre-order, or letter of intent
• They give you access to their data, system, or team for testing

Spinning wheels (feels like progress but isn't):

• "Let's stay in touch" (no specific next step)
• "Send me more info" (they'll never read it)
• "We should grab coffee sometime" (no date)
• "I'll forward this to my colleague" (rarely happens without an intro email)
• "Come back when you have a prototype" (delay tactic with no commitment)

The Advance Planning Framework

Before every conversation, decide what advance you want. Have three levels ready:

If you can't get even the minimum ask, the conversation has given you important data: this person (or segment) isn't a real customer.

Designing the End of a Conversation

The last two minutes of every conversation should follow this pattern:

Step 1: Summarize What You Learned

"So if I understand correctly, your biggest challenge is [X], you've tried [Y] and [Z] but neither worked because [reason], and you're currently spending [amount] on this problem."

This does three things:

• Confirms your understanding
• Shows you were listening
• Gives them a chance to correct or add details

Step 2: Share Your Vision (Briefly)

Now -- and only now -- you can share what you're building. Keep it to 30 seconds.

"Based on what you've told me and what I'm hearing from others, we're building [one sentence description]."

Step 3: Make the Ask

"Would you be willing to [specific commitment with a specific date]?"

If they say no or hesitate, that's valuable data. Don't push harder -- instead, ask:

• "What would need to be true for this to be a priority?"
• "Is there someone else who might be a better fit for this?"
• "What's holding you back?"

Step 4: Set the Exact Next Step

Never end with "I'll follow up." End with:

• "I'll email you Tuesday with the prototype link, and we'll do a 15-minute walkthrough Thursday at 2pm."
• "You'll intro me to Sarah by end of week, and I'll reach out to schedule a call."

Commitment by Stage

Different stages of your business require different commitment asks:

Idea Stage (No Product Yet)

• Ask for: Problem validation and intros
• Good signals: "Yes, this is a real problem. Talk to my colleague Sarah -- she deals with this daily."
• Bad signals: "Sounds interesting, keep me posted."

Prototype Stage (Something to Show)

• Ask for: Time to test and feedback on specifics
• Good signals: "Can I try this right now? When will it be ready?"
• Bad signals: "Looks great!" (with no follow-up action)

Beta Stage (Working Product)

• Ask for: Pilot commitments, letters of intent, deposits
• Good signals: "We'd like to run a 30-day pilot with our sales team."
• Bad signals: "Definitely send me the link when it launches."

Launch Stage (Ready to Sell)

• Ask for: Purchase, annual contract, referrals
• Good signals: "Here's our PO number."
• Bad signals: "We need to think about it." (after months of conversation)

The Zombie Lead Problem

Zombie leads are the most dangerous outcome of bad customer conversations. They're people who:

• Keep taking your meetings
• Keep saying nice things
• Keep promising they'll buy "when it's ready"
• Never actually commit anything of value

How to identify zombie leads: 1. Count the number of meetings you've had with them 2. Count the concrete commitments they've made 3. If meetings > 3 and commitments = 0, you have a zombie

How to cure zombie leads:

• Force a clear yes or no: "We need to decide by Friday whether to include you in the pilot. Are you in or out?"
• Set a deadline: "We're closing early access spots next week. Would you like to lock one in?"
• Ask directly: "We've met three times and I really value your input. To move forward, I need [specific commitment]. Is that something you can do?"

A "no" from a zombie is a gift -- it frees you to focus on real prospects.

Tracking Commitments

Use a simple spreadsheet to track every conversation:

The "commitment kept" column is the most important one. Over time, it reveals who your real customers are and which segments are full of zombie leads.

Finding Conversations

The hardest part of customer development isn't knowing what to ask -- it's finding people to ask. This reference covers where to find your target customers, how to approach them, and how to keep conversations casual enough to produce honest answers.

The Framing Problem

How you frame a conversation determines the quality of data you receive. Compare:

Key insight: The less formal the conversation, the more honest the data. The best customer conversations don't feel like interviews at all.

Seven Channels for Finding Conversations

1. Warm Introductions

The highest-quality channel. A warm intro from a mutual contact starts the conversation with trust already established.

How to build an intro network:

• Tell everyone you know what you're exploring (not what you're building)
• Ask: "Do you know anyone who deals with [problem area]? I'd love to learn from them."
• Be specific: "I'm looking for [role] at [company type] who [relevant behavior]"
• Make it easy: offer to write the intro email for them

The intro email formula:

Subject: Intro -- [Your Name] <> [Their Name] re: [topic]

[Contact Name] -- meet [Your Name], who's researching how
[industry/role] handles [problem area]. I thought you'd be a
great person for them to learn from.

[Your Name] -- [Contact Name] is [one sentence on their expertise].

I'll let you two take it from here!

Volume target: Ask 10 people for intros. Expect 3-5 to follow through. Each intro should produce 1-2 additional referrals, creating a snowball effect.

2. Industry Events and Conferences

Go where your customers already gather. The conversations happen naturally.

Types of events:

• Industry conferences (large, diverse, good for initial exploration)
• Local meetups (smaller, more intimate, better for deeper conversations)
• Trade shows (good for B2B, especially supply-side conversations)
• Workshops and seminars (people come to learn, which means they're aware of problems)
• Online communities with meetups (Reddit, Discord, Slack groups)

How to approach people at events:

• Don't pitch. Don't hand out business cards unprompted.
• Open with genuine curiosity: "What brings you to this event?"
• Ask about their work: "What's the biggest challenge you're facing in [area]?"
• Share your interest: "I've been exploring [space] -- what should I know?"
• Follow up within 24 hours with a specific reference to your conversation

Event preparation checklist:

• [ ] Identify 5-10 people you'd like to meet (check speaker list, attendee list)
• [ ] Prepare 3 open-ended questions about their work
• [ ] Bring a notebook, not business cards
• [ ] Set a goal: have 5 substantive conversations
• [ ] Plan follow-up within 24 hours

3. Cold Outreach

Cold emails and messages work if you lead with their expertise, not your needs.

The cold outreach formula:

Subject: Quick question about [specific thing they know about]

Hi [Name],

I saw your [talk/post/article] about [specific topic].
I'm exploring [problem area] and trying to understand
how [their role/industry] handles it.

Would you have 15 minutes for a quick call this week?
I'm not selling anything -- just trying to learn from
people who know this space.

Best,
[Name]

Key principles for cold outreach:

• Keep it under 5 sentences
• Reference something specific about them (not a generic template)
• Be transparent: you're learning, not selling
• Ask for 15 minutes, not 30 or 60
• Provide a clear reason why you're reaching out to them specifically
• Follow up once after 3-5 days, then stop

Response rates by channel:

4. Landing Pages and Signups

Create a simple page that describes the problem (not the solution) and collect emails from people who resonate.

How to use landing pages for conversations: 1. Describe the problem in your target customer's language 2. Add a signup: "We're exploring solutions -- want to help shape what we build?" 3. When someone signs up, email them within 24 hours: "Thanks for signing up. I'd love to learn more about how you handle [problem]. Do you have 15 minutes this week?" 4. These are your warmest leads -- they self-selected by caring about the problem

Landing page copy principles:

• Lead with the problem, not the solution
• Use language from your initial conversations (mirror their words)
• Don't promise a product -- promise involvement in shaping one
• Include a short survey (3-5 questions) to pre-qualify

5. Online Communities

Participate genuinely in communities where your target customers hang out.

Where to look:

• Reddit subreddits related to the problem space
• Industry-specific Slack groups
• Discord servers
• Facebook groups (especially for consumer products)
• Hacker News (for developer/startup audiences)
• Specialized forums (e.g., Indie Hackers, Product Hunt discussions)

How to participate without being slimy:

• Join 4-6 weeks before you start asking questions
• Contribute value first: answer questions, share relevant resources
• When you do ask, be transparent: "I'm exploring [problem area] and would love to hear how people here handle it"
• Never pitch in a community. Ever. Even if someone asks you to.
• DM people who post about relevant problems: "I saw your post about [problem]. I'm researching this area -- would you mind telling me more?"

6. Advisors as a Channel

Formalize relationships with well-connected people who can open doors at scale.

What makes a good advisor for conversations:

• They know 50+ people in your target customer segment
• They're respected in the community (their intro carries weight)
• They understand what you're trying to learn (so they can make relevant intros)
• They have a genuine interest in your success

How to structure an advisor relationship for conversations:

• Be explicit: "I don't need strategy advice. I need introductions to [specific type of person]."
• Set expectations: "Would you be able to make 3-5 introductions over the next month?"
• Make it easy: provide them with a one-sentence description of who you want to meet and a template intro email
• Give them credit: "Sarah introduced us, and she mentioned you're the expert on [thing]"

The advisor pipeline: 1. Identify 5-10 well-connected people in your space 2. Approach them honestly: "I'm trying to learn about [problem]. You know everyone in this space. Can I buy you coffee?" 3. If the coffee goes well: "Would you be open to being an informal advisor? Mainly, I'd love your help making introductions." 4. Formalize if appropriate (advisory shares, compensation)

7. Customer-Adjacent Roles

When you can't easily reach end customers, talk to people who serve them.

Who to talk to:

• Consultants who advise your target customers
• Sales reps who sell to your target segment
• Customer support agents who hear complaints daily
• Industry analysts who study the market
• Journalists who cover the space

Why this works: These people talk to hundreds of your potential customers. They have pattern-matched the common problems, objections, and buying behaviors. One conversation with a consultant can compress what would take 20 customer interviews.

How to approach customer-adjacent roles:

• "You work with dozens of [type of company]. What's the most common problem you see them struggling with?"
• "When companies in [industry] buy new tools, what's the typical process?"
• "What are the top 3 complaints you hear from your clients?"

Keeping Conversations Casual

The Vision/Framing/Weakness/Pedestal/Ask Framework

A five-part structure for getting meetings that produce honest conversations:

1. Vision (one sentence) "I'm exploring how small businesses handle their bookkeeping."

2. Framing (set expectations) "I'm not selling anything. I'm just talking to people who deal with this to understand the space."

3. Weakness (show vulnerability) "I'm an engineer, so I don't know much about the accounting side. I'm trying not to build something stupid."

4. Pedestal (elevate them) "You've been doing this for 10 years, so you'd know better than anyone."

5. Ask (specific and small) "Would you have 15 minutes for a quick chat? Coffee's on me."

Rules for Keeping It Casual

1. Never use a clipboard or formal survey. Use a small notebook or your phone's notes app. 2. Don't record without permission. And know that recording changes behavior. 3. Meet in their territory. Their office, their favorite coffee shop, their coworking space. 4. Start with rapport. Talk about something other than your topic for the first 2-3 minutes. 5. Don't ask all your questions. Ask 3-5 important ones, not a 20-question script. 6. Let the conversation flow. Follow interesting tangents. Your best insights will come from unexpected directions. 7. End naturally. Don't abruptly end at exactly 15 minutes. Let the conversation wind down organically (but respect their time). 8. Follow up with value. Send them an article, a connection, or a thank-you note. Not a pitch deck.

How Many Conversations Do You Need?

Convergence Theory

You don't need hundreds of conversations. You need enough to see patterns.

Rule of thumb by stage:

When to Stop and Build

Stop talking when:

• You can predict what the next person will say
• Multiple people describe the same problem in the same way
• You've received concrete commitments (not just compliments)
• You have a clear picture of the problem, the customer, and the existing alternatives
• You're procrastinating on building by scheduling more conversations

Warning: "Just one more conversation" can become a form of procrastination. If you're past saturation and still not building, you might be using conversations to avoid the risk of building something real.

Processing and Learning

Customer conversations generate raw material. Without a system for processing that material, you'll unconsciously cherry-pick the data that confirms your existing beliefs and ignore the signals that challenge them. This reference covers note-taking, team sharing, belief updating, and knowing when to stop talking.

Note-Taking During Conversations

What to Capture

Take notes on facts and commitments, not opinions and feelings. Your notes should be useful to someone who wasn't in the room.

Capture these:

Don't waste space on these:

Note-Taking Systems

The Two-Column Method

Divide your notebook page (or document) into two columns:

This separation is critical because it prevents you from conflating what you observed with what you think it means. Raw data is permanent; interpretations are hypotheses that should be tested.

The Shorthand System

During fast conversations, use shorthand symbols to tag important moments:

Example note with shorthand:

Sara, VP Ops at Acme Corp, Jan 15

"" "I spend my entire Friday doing reports that nobody reads" :(
! She didn't know her company paid for Tableau ($1,200/mo) $
"" "If someone could just email me the 3 numbers that matter, I'd be so happy"
X She doesn't want a dashboard (contradicts our assumption)
-> Agreed to 20-min demo next Wed 2pm
? Who else on her team does reports? Ask next time

When to Take Notes

During the conversation:

• Jot quick keywords and quotes
• Don't let note-taking disrupt the flow
• Say "That's really interesting, let me write that down" if you need a moment
• A small notebook is less intimidating than a laptop

Immediately after the conversation (within 5 minutes):

• Expand your shorthand into full sentences
• Add context you remember but didn't write down
• Separate facts from interpretations (two-column method)
• Rate the conversation quality: did you learn new facts or just collect compliments?

Never rely on memory alone. After 24 hours, you'll have lost or distorted most of the details. After a week, you'll remember only what confirms your existing beliefs.

Processing with Your Team

The Weekly Customer Learning Session

Set aside 30-60 minutes per week to review conversations as a team. This is the single most important ritual in customer development.

Agenda:

1. Raw Data Review (20 minutes)

• Each team member shares their conversation notes (facts and quotes only)
• No interpretation yet -- just the raw data
• Other team members ask clarifying questions

2. Pattern Identification (15 minutes)

• What themes are repeating across conversations?
• What problems come up most frequently?
• What surprised us?
• What contradicted our assumptions?

3. Belief Update (15 minutes)

• Review and update the team's three core beliefs (see below)
• Document what evidence supports or challenges each belief
• Decide whether any beliefs need to change

4. Next Actions (10 minutes)

• Who do we need to talk to next?
• What questions should we add or remove?
• Are we ready to stop talking and start building?

Why Team Processing Matters

Individual processing is biased. Every person unconsciously filters information through their own lens:

• Engineers focus on technical feasibility, not customer pain
• Designers remember the UX complaints, not the business model signals
• Founders remember the validation, not the contradictions
• Salespeople remember the "yeses," not the hesitation

When the whole team processes raw data together, these biases partially cancel out. The group sees patterns that individuals miss.

Rules for Team Processing

1. Share raw notes, not filtered summaries. Saying "I talked to Sara and she liked the idea" is useless. Sharing Sara's exact quotes is useful. 2. No hierarchy in interpretation. The founder's interpretation isn't more valid than the intern's. Evidence decides. 3. Celebrate surprising data. When someone brings a conversation that challenges the team's beliefs, that's the most valuable contribution. Don't shoot the messenger. 4. Distinguish between "interesting" and "actionable." Some facts are fascinating but don't change what you should build. Focus on data that has decision-making power.

The Three Core Beliefs

At any point in customer development, your team should be able to articulate three beliefs:

Belief 1: The Problem

"We believe that [customer segment] struggles with [specific problem] because [root cause]."

Example: "We believe that freelance designers struggle with invoicing because they use generic tools that don't account for project-based billing and revision cycles."

Belief 2: The Customer Segment

"We believe that the people who care most about this problem are [specific description] who [observable characteristic]."

Example: "We believe that the people who care most are solo freelance designers earning $50-150K who manage 5-15 clients simultaneously."

Belief 3: The Solution Direction

"We believe that the right solution [approach] because [evidence from conversations]."

Example: "We believe the right solution integrates invoicing with project milestones because 7 of 10 designers told us their biggest pain is tracking which revision rounds are billable."

Updating Beliefs

After each batch of conversations, review each belief:

When to update a belief:

• 3+ conversations provide contradictory evidence
• A new pattern emerges that your current belief can't explain
• You discover that a different customer segment cares more than your current target

When to abandon a belief:

• Majority of conversations contradict it
• You can't find anyone who exhibits the problem
• Everyone who has the problem already has a satisfactory solution

Organizing Customer Data

The Conversation Spreadsheet

Maintain a central spreadsheet (or Notion database, or Airtable) with one row per conversation:

Tagging and Filtering

As your conversation count grows, you'll need to filter by:

• Customer segment: Which type of person said this?
• Problem area: Which problem does this relate to?
• Signal strength: How strong was the evidence? (fact/commitment > opinion/fluff)
• Recency: When was this collected? Old data may be stale.

Quantifying Qualitative Data

While customer conversations are qualitative, you can and should count patterns:

Knowing When to Stop Talking

Signs You've Talked Enough

1. Convergence: The last 3-5 conversations didn't teach you anything new. You can predict what the next person will say. 2. Clear problem: You can describe the problem in the customer's own words, and multiple customers have confirmed it. 3. Clear segment: You know exactly who has this problem most acutely and can describe them specifically. 4. Existing spending: You've confirmed that people are already spending time or money on this problem. 5. Commitments collected: You have concrete commitments (time, reputation, or money) from real potential customers.

Signs You Haven't Talked Enough

1. Every conversation surprises you: You're still discovering the problem space. 2. Segment unclear: You can't describe your ideal customer specifically. 3. No commitments: Nobody has invested time, reputation, or money -- only compliments. 4. Contradictory data: Different conversations point in completely different directions. 5. You're guessing: Your three core beliefs are assumptions, not evidence-based conclusions.

The Conversation-to-Action Transition

When you've hit convergence, make the transition explicit:

Team exercise: The "Stop Talking" Decision 1. Review all conversations from the last 2-4 weeks. 2. For each of your three core beliefs, count supporting vs contradicting evidence. 3. Ask: "If we build based on what we know now, what's our biggest remaining risk?" 4. If the risk can be addressed by more conversations, keep talking. 5. If the risk can only be addressed by building something, stop talking and build.

The dangerous middle ground: Teams often get stuck in an infinite loop of conversations because talking is less scary than building. If your conversations are no longer producing new insights, you're procrastinating. Ship something and learn from real usage.

Anti-Patterns in Processing

Question Patterns: The Three Rules in Depth

Mastering The Mom Test comes down to asking better questions. This reference covers the three core rules, provides extensive examples of good vs bad questions, and includes exercises for building the skill.

The Three Rules

Rule 1: Talk About Their Life, Not Your Idea

The moment you mention your idea, the conversation shifts from honest sharing to polite performance. People don't want to hurt your feelings, so they'll nod and smile no matter what you describe. The fix: keep the entire conversation about them.

What this looks like in practice:

Key principle: If you can replace your product name with any competitor's name and the question still works, it's a bad question. Good questions are product-agnostic.

Rule 2: Ask About Specifics in the Past

Generics ("I usually...") and hypotheticals ("I would...") are unreliable. People reconstruct memories to fit narratives and predict futures based on ideal-self behavior, not actual behavior. Specific past events are facts -- they happened, and the details reveal real patterns.

What this looks like in practice:

Anchor phrases that force specificity:

• "Tell me about the last time..."
• "Walk me through..."
• "Can you give me a specific example of..."
• "When did that last happen?"
• "What exactly did you do?"

Rule 3: Talk Less, Listen More

If you're talking more than 20% of the time, you're doing it wrong. Every minute you spend talking is a minute you're not learning. Silence is a powerful tool -- when you stop talking, people fill the gap with details they wouldn't have volunteered.

Practical techniques for talking less:

• Ask the question, then wait. Count to ten silently if you must.
• When they finish an answer, don't immediately respond. Wait 3-5 seconds. They'll often add the most valuable insight as an afterthought.
• Use minimal encouragers: "Mm-hmm," "Go on," "Tell me more about that"
• Avoid the urge to relate with your own experience ("Oh yeah, I do that too!")
• Never finish their sentences, even if you think you know what they'll say
• If you catch yourself about to pitch, bite your tongue and ask another question

The Question Hierarchy

Not all good questions are equal. Here's a hierarchy from most to least informative:

Tier 1: Behavior Questions (Most Reliable)

These reveal what people actually do. Behavior doesn't lie.

• "Walk me through what you did the last time this came up."
• "What did you try first? And after that?"
• "How much time did you spend on it?"
• "What did you end up doing?"
• "Did you pay for anything? How much?"

Tier 2: Problem Questions (Very Reliable)

These reveal pain points tied to real events.

• "What's the hardest part about [doing this thing]?"
• "Why was that hard?"
• "What didn't work about the solutions you tried?"
• "When you couldn't solve it, what happened? What was the consequence?"
• "How often does this actually come up?"

Tier 3: Motivation Questions (Reliable with Care)

These reveal why people do what they do, but require anchoring to specific events.

• "Why did you choose that particular tool?"
• "What made you switch from [old thing] to [new thing]?"
• "What were you hoping would happen?"
• "What finally pushed you to look for a solution?"

Tier 4: Worldview Questions (Handle with Care)

These reveal beliefs and values, but are easily influenced by how you ask.

• "How do you think about [problem area] in general?"
• "What matters most to you when choosing a tool for this?"
• "What would have to be true for you to change how you do this?"

Tier 5: Hypothetical Questions (Least Reliable -- Avoid)

These predict future behavior and are almost always wrong.

• "Would you use..." -- AVOID
• "Would you pay..." -- AVOID
• "How much would you pay..." -- AVOID
• "Do you think you'd..." -- AVOID

Domain-Specific Question Banks

For SaaS Products

Understanding current workflow:

• "Walk me through how your team handles [process] from start to finish."
• "What tools are involved? How do they connect?"
• "Where does information get lost or duplicated?"
• "How long does the whole process take? Where are the bottlenecks?"

Understanding buying behavior:

• "Who approved the budget for your current tool?"
• "How long did it take from 'we need something' to 'we're paying for it'?"
• "What would make you switch away from what you're using now?"
• "Have you tried switching tools before? What happened?"

For Consumer Apps

Understanding behavior patterns:

• "What's the first app you open in the morning? Why?"
• "When you're bored on the train, what do you do?"
• "The last time you had [problem], what did you pull out your phone to do?"
• "What apps have you deleted recently? Why?"

Understanding willingness to pay:

• "What subscription apps do you currently pay for?"
• "What made those worth paying for?"
• "Have you ever started paying for an app you previously used for free? What changed?"

For Marketplaces

Supply side:

• "How do you currently find customers/clients?"
• "What's the most effective channel? Why?"
• "How much do you spend on acquiring a new customer?"
• "What's the most frustrating part of finding new business?"

Demand side:

• "How did you find your current [service provider]?"
• "What made you choose them over others?"
• "What would make you switch to someone new?"
• "When was the last time you needed this and couldn't find it?"

Question Formulation Exercises

Exercise 1: The Idea Purge

Take your product idea and write down 10 questions you want to ask potential customers. Now go through each one and remove any mention of your product, solution, or idea. Reframe each question to be about their life and past behavior.

Example:

• Before: "Would you use an AI tool that writes emails for you?"
• After: "Walk me through how you handled your email this morning. How long did it take? What was annoying about it?"

Exercise 2: The Specificity Drill

Take any generic question and add specificity anchors until it references a concrete past event.

Example progression: 1. "Do you have trouble managing your finances?" (generic -- bad) 2. "How do you manage your finances?" (better, but still generic) 3. "Walk me through how you paid your bills last month." (specific past event -- good) 4. "Last month, was there a bill that surprised you? What happened?" (specific + emotional anchor -- great)

Exercise 3: The Deflection Practice

Have a partner pitch you ideas and practice deflecting to useful questions.

Partner says: "I'm building an app that reminds you to drink water." You respond: "Interesting. Do you personally have trouble staying hydrated? When was the last time you felt dehydrated? What happened? Have you tried any solutions? What worked and what didn't?"

Exercise 4: The Scary Question List

Write down the five questions you're most afraid to ask because the answers might invalidate your idea. These are exactly the questions you must ask first.

Examples of scary questions:

• "Have you actually tried to solve this, or do you just complain about it?"
• "You said you'd pay for this -- can I take a deposit right now?"
• "Why haven't you already bought one of the existing solutions?"
• "Is this actually a top-three priority for you, or more of a nice-to-have?"
• "If I gave you this for free right now, would you actually set it up this week?"

Common Mistakes in Questioning

Signal vs Noise Cheat Sheet