The Mom Test — Rob Fitzpatrick

Notes by Nicholas Tickle, October 2025. Read this each time you begin the customer interview process.

The Mom Test is named after the core principle: ask questions so grounded in specifics that even your mum can't give you a false positive.

When to Do Customer Interviews

Two phases: ideation (testing your hypothesis) and product (testing the early or advanced product). Customer validation is needed at every step.

First, decide whether your idea has more product risk or customer/market risk:

Product risk — Can I build it? Can I grow it?
Customer/market risk — Do they want it? Will they pay for it? Are there enough of them?

Video games are pure product risk. If you have heavy product risk, you won't be able to prove much through conversations alone.

How Long to Spend

Spend a week, maybe two, on customer interviews. Get your bearings, then give people something to commit to.

Choosing Who to Interview

Start somewhere very specific. Make an incredible product for one person.
An industry expert can give you a taxonomy of the industry — a much better starting point.
When feedback is all over the map, you can't extract value. Keep slicing into better and better subsets.
There must be a clear physical or digital location where you can find your segment.
Find segments that are the most profitable, easy to reach, and personally rewarding. Big emphasis on being around customers you enjoy.
You have too broad a segment if you're talking to everyone.
Be wary of buying processes that have overlooked some stakeholders.
Don't only talk to the most senior people you can find.

Where to Find People

For B2B: find out who controls the budget and who approves payments.
Start cold, but convert every conversation into a warm referral.
Every place you go is an opportunity for a conversation — not an interview, a conversation. People love talking about their problems.
Immerse yourself where potential customers are.
Organise a meetup — bring the customers to you.
Teach: conferences, workshops, online videos, blogging, free consulting, office hours. A big blog following makes lining up conversations trivial.
Use advisors (small equity stake) for a fresh batch of intros.
Top-tier investors are excellent for B2B cold intros.
You can find anyone you need if you ask a couple of times.

How Many Meetings

Keep talking until you stop hearing new information.
If you've done more than 10 conversations and results are still all over the map, your segment is too vague.
Have enough meetings to understand the customer: goals, frustrations, what they've tried, how they currently cope.

Setting Up the Meeting

If you don't have anything to sell, it's unclear what the meeting is for — so frame it carefully.
If you don't know why you're there, it becomes a sales meeting by default. Bad: you're not ready, the customer closes up, you become the subject instead of them.
People don't want to be interviewed. They want to help.
The point of cold outreach is to stop needing it. Invest in warm intros.
Don't go looking for customers. Go looking for industry and customer advisors.

The framing formula:

Element	What to say
Vision	You're an entrepreneur trying to solve horrible problem X or fix stagnant industry Z. Don't mention the idea.
Framing	Mention what stage you're at — if true, that you don't have anything to sell.
Weakness	Name the specific problem you're looking for answers on. This clarifies you're not wasting their time.
Pedestal	Show why they in particular can help.
Ask	Explicitly ask for help.

Meeting Format

Prefer in-person. Use whatever works, but start face-to-face.
Length: generally 30 minutes; you can usually get what you need in 10–15. Industry deep-dives may take an hour.
Two people: one talks, one takes notes. The note-taker can jump in and fix bad questions.

What to Talk About

Talk about their life, not your idea. Avoiding mentioning your idea automatically produces better questions.
Ask about specifics in the past, not generics or opinions about the future.
Talk less, listen more.
When you do it right, they won't even know you have an idea.
You're shooting blind until you understand their goals.

The Three Big Scary Questions

Before every conversation, identify the questions you've been avoiding — the ones whose answers could completely change or disprove your business. You should be terrified of at least one question you ask in every conversation.

How to find them: imagine the company failed — why? Imagine it succeeded hugely — what had to be true?

Good Questions to Ask

Don't try to ask all of these. Conversation needs to flow.

Understanding current behaviour:

Ask them to show you how they currently solve the problem. Which parts do they love and hate?
Which tools or processes did they try before settling on this one?
Are they actively searching for something better? If so, what's the sticking point? If not, why not?
Where are they losing money with their current tools?
Is there a budget for newer tools? How much does it currently cost to solve this?
"Talk me through what happened the last time problem X came up."
"Have they even cared enough to Google it?"

Digging into motivations:

"Why do you bother?" — why even care about this problem?
"What are the implications of that?" — distinguishes must-solve problems from mild annoyances.
"What else have you tried?"
"What would your dream product do?" — only useful with good follow-up. Understand why they want each feature.
"When was the last time that happened?" — anchor to a concrete past example.

Emotional signal probes:

"Tell me more about that."
"What seems to really bug you — I bet there's a story there."
"What makes it so awful?"
"What are your big goals and focuses right now?"

Commitment and readiness:

If you're far enough along, ask for money. People stop lying when you ask for money.
"Where does the money come from?" / "Who approves the purchases?"
"Do you know anyone else I should talk to?" — end every conversation with this.
"Is there anything else I should have asked?" — gives them a chance to fix your line of questioning.

Bad Questions to Avoid

"Do you think this is a good idea?"
"Would you buy a product that did X?"
"How much would you pay for X?"
"Would you pay X for a product that did Y?" — never ask about hypothetical future behaviour.
"Would you ever...?" / "Do you usually...?" / "Might you...?" — answers are worthless.
Any approval-seeking question. Even "be honest" doesn't work — people still pull their punches.

When you ask generic questions, people describe who they want to be, not who they actually are.

Questions for Feature Requests (Later Stage)

When someone requests a feature:

"Why do you want that?"
"What would that let you do?"
"How are you coping without it?"
"Should we push back the launch to add that, or can it come later?"
"How would that fit into your day?"

Your job is to understand the motivation behind the request, not to obey it.

Preparing for the Meeting

With your team, decide on 3 big learning goals. Update as questions evolve. Have a list for each customer type.
Decide on ideal next steps and commitments you want from this person.
Make best guesses about what they care about.
If something can be answered by desk research, do that first.
Spend an hour preparing — don't waste weeks.
Skip questions you already have solid data on.
The whole founding team must be involved in customer conversations in some way. Sit down together to prep — both business and product need to be represented.

Feedback: What's Valuable and What Isn't

The right signals

Learning who controls the budget and approves purchases (B2B).
They give you a list of other people to speak to.
Learning someone is a non-customer is valuable data.
Lukewarm responses ("umm, not sure" / "that's pretty neat") are honest. There's more information in a "meh" than a "wow!" You can't build a business on lukewarm.
A meeting succeeds when it ends with a commitment to advance.

Wrong signals (worthless)

Opinions — worthless, except from industry experts who've built very similar businesses.
Compliments — we crave validation and mistake compliments for data. "That's so cool." / "Let me know when it launches." / "Don't call me, I'll call you."
Ideas and feature requests — understand them, but don't obey them.
Fluff — generics, hypotheticals, and future-tense statements.
- Generic: "I usually", "I always", "I never"
- Future: "I would", "I will"
- Hypothetical: "I might", "I could"
- The world's most deadly fluff: "I would definitely buy that."

If they don't care enough about solving the problem today, they won't care about your solution tomorrow.

Signs of Real Commitment

The goal is to ask for something they'll think twice about giving you — to put them to a decision.

Type	Examples
Time	Clear next meeting with known goals; feedback on wireframes; non-trivial product trial
Reputation	Intro to peers, team, or decision-maker; public testimonial or case study
Financial	Letter of intent; pre-order; deposit

The more they give up, the more you can trust their signal. If you've hit a real problem, they'll jump at the chance to get early access.

During the Meeting

Grab the reins at the start or they'll start drilling you on your idea.
Repeat the framing from your email/intro. If someone made the introduction, use them as an authority.
Don't pitch. If you slip into pitch mode, apologise and redirect.
If they ask what you're working on, promise to tell them at the end.
Talk less. The more you talk, the worse you're doing.
Deflect compliments — they're almost certainly not being straight with you.
Don't zoom in on a specific problem too quickly before you understand the broader context.
Keep it casual. A quick chat beats a long formal meeting.
Write down exact quotes in quotation marks — useful for marketing, pitch decks, investor conversations.
Capture any strong emotion and dig into it.

What to note:

Emotions (excited, angry, embarrassed?)
Pain or problem
Goal or job-to-be-done
Obstacles they face
Current workarounds
Background context
Feature requests or purchasing criteria
Budget, purchasing process
Names of people they mention — ask for intros at the end
Follow-up tasks and next steps

Ending the Meeting

If you don't know what happens next, the meeting was pointless.
Give them a clear chance to either commit or reject — this gets you out of the friend-zone and identifies real leads.
A meeting that's going nowhere can often be saved by pushing for a commitment while you're being brushed off with a compliment.

After the Meeting

If notes during the meeting were rude, write them up immediately after.
Review notes and key quotes with the whole founding team promptly — learning must be shared.
Transfer notes to permanent storage.
Update your beliefs and plans.
Decide on the next 3 big questions.
Evaluate how you could improve — customer conversations are a skill worth developing.

Results of a good meeting:

Facts — what do they do, why do they do it.
Commitment — they give up something they value: time, reputation, or money.
Advancement — they move to the next step in your funnel, closer to a sale.

Signs You're Not Taking This Seriously

You're talking more than they are.
They complimented your idea.
You told them the idea and have no next steps.
You don't have notes, or aren't using them.
You got an unexpected answer and didn't update your thinking.
You weren't scared of any of the questions you asked.
You aren't sure what you were trying to learn.

Pricing Note

Price your product in terms of value to the customer, not cost to you. If they're currently spending £100,000 on the problem, you shouldn't be having a £100 conversation.

Rules of Thumb

Opinions are worthless.
Anything involving the future is an over-optimistic lie.
People will lie to you if they think it's what you want to hear.
People know what their problems are, but not how to solve them.
You're shooting blind until you understand their goals.
Some problems don't actually matter.
Watching someone do a task shows where the problems really are — not where the customer thinks they are.
If they haven't looked for a solution already, they won't look for yours.
People stop lying when you ask them for money.
While it's rare for someone to tell you what they'll pay, they'll often show you what it's worth.
Compliments are the fool's gold of customer learning: shiny, distracting, and worthless.
Ideas and feature requests should be understood, but not obeyed.
Anyone will say your idea is great if you're annoying enough about it.
The more you're talking, the worse you're doing.
You should be terrified of at least one question you ask in every conversation.
There's more information in a "meh" than a "wow!" You can't build a business on a lukewarm response.
Start broad; don't zoom in until you've found a strong signal.
You always need a list of three big questions.
If it feels like they're doing you a favour by talking to you, it's too formal.
Rejection is not failure.
It's not a real lead until you've given them a concrete chance to reject you.
In early sales, the real goal is learning. Revenue is a side-effect.
Keep having conversations until you stop hearing new things.
If you aren't finding consistent problems and goals, your segment isn't specific enough.
If you don't know what you're trying to learn, don't have the conversation.
Notes are useless if you don't look at them.