The Mom Test

On this pageWhat I like
What I like about this book
It is short, blunt and fixes the most expensive mistake in early sales: asking people whether they like your idea. Fitzpatrick admits he made these mistakes himself, which makes the rules easier to trust. I'd read it before your next customer call, because the rules are simple enough to remember in the middle of a conversation.
Why read it
It teaches you to ask about customers' lives, so you collect facts and commitments instead of polite compliments.
The problem it solves
Customer conversations feel useful when they are not. You describe your idea, the other person says it sounds great, and you leave believing you have evidence. Fitzpatrick's point is that you have almost none. A compliment costs the other person nothing, so it tells you nothing, and a few of them add up to a false positive that pushes you to spend more money, time and team energy on something nobody wants.
His fix is not to find more honest people. It is to change your questions, so that even someone who loves you cannot mislead you by being kind.
What changes in how you work
You stop pitching first. Instead you ask about the other person's life: what they did the last time the problem came up, what it cost them, what they already pay for and what else they tried. You learn to hear the answer too. Someone who has never looked for a solution, and will not introduce you to anyone, has told you something, however much they praise the idea.
You also change what you count as a result. After a product or sales meeting you ask whether anything moved forward. If you left with a compliment or a vague promise to talk later, the meeting failed, and you plan the next one differently.
When to read it, and when not to
Read it before you build anything, before you hire someone to run discovery calls and before you launch a new service. It takes an afternoon and costs less than one bad product decision. It is also the fix if your pipeline is full of friendly people who never buy.
It is less useful once you have a large base of paying customers and a way to test ideas with data, because your own numbers will teach you more. It is also a book about early learning from a small number of conversations, not about surveys or large samples. And do not read the three rules as a reason to hide your product for ever: Fitzpatrick says plainly that you do need to mention what you are building and ask for money. The mistake is doing it too soon.
How it connects to running and growing a business
Every customer conversation produces decisions: build this, drop that, aim at this segment, charge this much. The quality of those decisions depends on the quality of what you heard. Fitzpatrick insists on writing notes with exact quotes, listing your three biggest questions before each meeting and reviewing the notes with the team afterwards, so that the learning is not stuck in one head. That gives you a record you can return to: what you believed before, what you heard, and what you decided because of it.
The same habits make a playbook. A fixed set of questions, a fixed note format and a fixed ask at the end can be taught to a colleague, reviewed after each call and improved over time. That is how a skill that lives in one person turns into work the whole company does the same way.
Who it's for
Key take-aways
Book summary
Fitzpatrick argues that most customer conversations go wrong because of how the founder asks, not because customers are dishonest. If you describe your idea and ask for an opinion, you collect compliments, guesses and promises, and you walk away thinking you have evidence. His answer is a small set of rules, which he calls the Mom Test, that make it hard for anyone, even someone who loves you, to mislead you. It is a short, practical handbook for people who need to learn about customers quickly and cheaply, and it is written for people who find the whole process awkward.
Why another book on talking and selling?
He opens with his own failure. His first company, Habit, spent three years building social advertising technology, and he later realised that his months of customer conversations had been done wrongly. Bad conversations, he says, are worse than useless because they convince you that you are on the right path. He presents himself as an introverted techie rather than a natural salesperson, which is why the book is a how-to and not a theory text. He is also clear about scope: the book covers talking to customers, not the whole of Customer Development.
The Mom Test
The core chapter shows the same chat with a mother twice, about a cookbook app for the iPad. In the first the son asks loaded questions, gets a polite yes and takes it as validation. In the second he asks about her life: what she does on the tablet, what she did last, how she finds apps and where the cookbooks on her shelf came from. He learns that she hears about apps from the Sunday paper and that cookbooks mostly arrive as presents, which are real facts about reaching and selling to people like her. It worked because she never heard the idea. Three rules follow: talk about their life instead of your idea, ask about specifics in the past instead of generics or opinions about the future, and talk less and listen more.
Good question / bad question
A short chapter lets you grade a list of questions before reading his verdicts. Asking whether something is a good idea is an awful question, because only the market can tell you and opinions are worthless. Asking whether someone would buy, or how much they would pay, fails for the same reason: anything about the future is over-optimistic, and a number only makes it feel rigorous. The good questions are about the present and the past. How do they handle it now, what does it cost them, what else have they tried, why do they bother, what are the implications, and can they talk you through the last time it happened? He also suggests asking where the money comes from in a business sale, who else you should talk to and whether there is anything you should have asked. The split is clean: they own the problem, and you own the solution.
Avoiding bad data
Bad data comes in three kinds: compliments, fluff (generalities, hypotheticals and the future) and ideas, meaning feature requests. It produces false negatives, but more dangerously false positives. Three moves put a conversation back on track. Deflect compliments, anchor fluff by asking for the last specific time something happened, and dig beneath ideas to find the motivation behind them. He also names two habits that invite bad data. One is seeking approval, including what he calls the Pathos Problem, where exposing your ego makes people protect you with kind words. The other is being pitchy. As he puts it, "Compliments are the fool's gold of customer learning: shiny, distracting, and entirely worthless."
Asking important questions
Once you avoid biasing questions you can drift into harmless trivia. Fitzpatrick tells you to ask the question that could destroy your current idea, and to be frightened by at least one question in every conversation. Two thought experiments help you find it: imagine the company has failed and ask why, then imagine it a huge success and ask what had to be true. He wants you to welcome bad news, since spending a few conversations to learn you are on a dead end is far cheaper than spending your savings on the first idea. A lukewarm reaction tells you more than excited praise, so do not pitch harder to win people round. He also warns against zooming in on details before you know the problem matters, and against mistaking market risk for product risk.
Keeping it casual
Steve Blank's approach of three separate meetings is hard to arrange and costs far more calendar time than the meeting itself. Fitzpatrick prefers casual chats: when you meet someone at a conference or in a cafe, go straight to your most important question. He calls the habit of forcing every chance to learn into a calendar block the meeting anti-pattern. Early conversations can take five to fifteen minutes, and formal, structured meetings make people stiff and more likely to give polite answers. His guide is to give as little information about your idea as possible while still steering the talk somewhere useful.
Commitment and advancement
Once you have something to show, compliments come back, so you ask for commitments. Commitment means the other person gives up something they value, and advancement means they move to the next step of your real sales process. He says no meeting simply goes well: it either succeeds or fails. You lose it when you leave with a compliment or a stalling line, and you win it when you leave with a commitment. The currencies are time, such as a trial or a next meeting with clear goals, reputation, such as an introduction to a boss or a public testimonial, and cash, such as a pre-order or deposit. Friendly prospects who never buy are zombie leads, and you fix them by giving a concrete chance to say yes or no. In his words, "If you don't know what happens next after a product or sales meeting, the meeting was pointless."
Finding conversations
Cold outreach is hard, and its aim is to stop having cold conversations: treat people's time with respect, and they turn into warm introductions. He suggests going to people through cold calls, events and giving talks, bringing people to you through landing pages and meetups, and creating warm introductions through industry advisors, professors and investors. In early meetings he suggests looking for advisors, not customers, which changes your mindset and removes the needy feel.
Choosing your customers
Startups drown rather than starve, because they have too many options. A fuzzy segment gives you mixed feedback, no way to prove yourself wrong and no clear next step. The big companies began narrow: Google helped PhD students find obscure code, and eBay helped people trade collectables. He teaches customer slicing: take a broad group and keep asking who exactly and where you can find them, until you can name a segment you can walk up to, such as non-native English speaking PhD students reached through a university admissions office.
Running the process
Even good questions fail without a process around them. Before a meeting, agree your three big questions with the team, decide which commitment you will push for and write down your best guesses about what the person cares about. After it, review the notes together so that the learning is on paper and not only in one head. He describes how he became a learning bottleneck himself and his CTO quit. Everyone making big decisions should attend some meetings, two people is the best number, with one talking and one taking notes, and you cannot outsource customer learning to a hired hand. Write exact quotes in quotation marks and add your own symbols as shorthand.
Conclusion and cheatsheet
He admits he still asks dumb questions and slipped into pitch mode the day before writing. Most bad conversations can be fixed, and failure is forgivable. The closing story, Hack it, is about a personal trainer who was told that the police might make a good customer. While a workshop debated how to validate the idea, he simply phoned them and booked a trial session within twenty minutes. A process is useful, but sometimes you can pick up the phone. The cheatsheet lists the skills, the common mistakes and the steps before, during and after a meeting.
What to do with it
- Write down your three biggest questions before your next customer conversation, including the one that scares you.
- Rewrite your standard questions so each asks about the past or present in the other person's own life, and remove any that mention your idea or ask for a future promise.
- End every conversation with a clear ask for a commitment, such as time, an introduction or money, and record whether you got it.
- Take notes with exact quotes, and review them with your team soon afterwards.
- Narrow your target segment until you can say where to find ten of those people this week.



