📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The single best thing ever written on customer conversations. It teaches you to ask about the customer's life and past behaviour, not your idea, so you can't be lied to. If a founder reads one thing before talking to a single customer, it's this.
From
momtestbook.com
by Rob Fitzpatrick
~130 pages
- Talk about their life, not your idea.
- Ask about specifics in the past, not opinions about the future.
- 'That's so cool, I'd totally buy it' is a compliment, not data, dig for commitment and evidence.
Open
momtestbook.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The most-quoted primary source on why founders should launch fast and iterate, short, canonical, and from the co-founder of YC. Read it when you're tempted to keep polishing before launch.
From
paulgraham.com
by Paul Graham
~8 min read
- Launch fast, you haven't really started until you launch.
- Most ideas appear in the implementing, so ship to learn.
- Make a few users love you rather than many ambivalent.
Open
paulgraham.com →
📖 Book
✓ Link checked
Paid
Advanced
Why we picked it
The book that coined get out of the building and launched the customer development movement. Blank's core claim is that a startup searches for a business model rather than executes one, so your early job is to test hypotheses against real customers before you scale anything. It is heavier than The Mom Test, but it gives you the full framework for validating a market before you build for it.
From
Wiley
by Steve Blank
- Startups search for a business model, they do not just execute a plan
- Test your riskiest assumptions with real customers before committing to build
- Customer discovery and validation come before you spend on customer creation
Open
wiley.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
The standard modern playbook for keeping discovery continuous so roadmap decisions stay grounded in real customer input, not one-off research. Exactly what founders need to stay close to users while shipping.
From
Product Talk
by Teresa Torres
~240 pages
- Start from a clear desired outcome.
- Interview customers weekly to surface opportunities.
- Use an opportunity solution tree to visualize and align your decisions.
Open
producttalk.org →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
If you are selling to companies rather than consumers, this is the specific playbook. Four concrete ways founders got signal before building, from doing the job by hand for one customer to interviewing dozens of potential users first.
From
Lenny's Newsletter
by Lenny Rachitsky
~12 min read
- Do the job by hand for one real customer before automating.
- Interview a wide set of potential users before committing.
- B2B signal looks different from consumer signal.
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
To say no to the right requests you need feedback you can trust, and this shows how to get it by watching customers rather than just taking their asks. It reinforces that observing the struggle tells you more than the feature name they hand you. Practical field technique for separating a stated want from a real need.
From
First Round Review
by Michael Sippey
12 min read
- Watch what customers do, not only what they ask for
- Get close to the actual struggle to find the real problem
- Stated requests are a starting point for questions, not a spec
Open
review.firstround.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Turns the vague feeling of product-market fit into a number you can move. Ask users how they would feel if they could no longer use the product, then track the share who say 'very disappointed'. Under 40 percent means keep working. A test you can run on an idea long before you scale it.
From
First Round Review
by Rahul Vohra
~20 min read
- The 40 percent 'very disappointed' benchmark for product-market fit.
- Segment to your high-expectation customers and build for them.
- Make the fit score a metric you improve quarter by quarter.
Open
review.firstround.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Ash Maurya, author of Running Lean, argues you can always find how a customer solves a job today, and that existing workaround is your evidence. The piece gives you the switching forces (push, pull, inertia, friction) to read whether the pain is urgent enough that someone would actually change and pay. It is a concrete, interview ready way to separate a real painkiller from a vitamin.
From
LEANFoundry
by Ash Maurya
About a 10 minute read
- Every job already has an existing alternative (even a spreadsheet or a manual hack); if you cannot find one, the problem may not be real.
- How hard the current workaround is, and what would make someone abandon it, tells you the true urgency and willingness to pay.
- Pull the problem out of the customer's actual recent story rather than asking them to predict future behavior.
Open
leanfoundry.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
The essay that put 'product-market fit' into the startup vocabulary. Read it for the gut-level description of what PMF feels like when it's happening vs when it isn't, the intuition behind the metrics.
From
pmarchive.com
by Marc Andreessen
~15 min read
- Market matters most; a great market pulls product out of a startup.
- You can feel PMF, customers buy as fast as you can ship.
- Before PMF, do whatever it takes to get there; nothing else counts.
Open
pmarchive.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Steve Blank's argument for searching for a business model before building one, the get out of the building philosophy in short form. It contrasts the old write a plan and build in secret approach with testing hypotheses on real customers. A crisp, credible piece to send anyone who thinks planning can substitute for talking to people.
From
Harvard Business Review
by Steve Blank
15 min read
- No business plan survives first contact with customers.
- Get out of the building and test your assumptions with real buyers.
- Favor experiments and customer feedback over elaborate up front plans.
Open
hbr.org →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
The honest answer to 'how many' is not a magic number, it is saturation: you keep going until new interviews stop teaching you anything new. This piece explains that idea plainly and gives a workable starting point (begin with about 5 to 6, then continue until the themes stop shifting), which is exactly the judgment call a founder is trying to make. Treat it as a rule of thumb to sanity-check your gut, not a quota to hit.
From
Nielsen Norman Group (nngroup.com)
by Maria Rosala
~10 min read
- Saturation is the real stopping rule: when the same jobs and pains keep repeating and fresh interviews add nothing, you can trust the pattern.
- Start small (roughly 5 to 6) for a focused, similar group, and add more the moment answers start diverging.
- The number depends on how varied your customers are and how broad your question is, so a wildly mixed audience needs more conversations than a narrow one.
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Lemkin lays out a specific, staged interview count for B2B SaaS founders: the first five to map the space, the next five to confirm patterns, and interviews eleven through twenty to sharpen your pitch and thesis. It is opinionated and specific in a way that is genuinely useful as a starting benchmark, while still leaving room for your own judgment about when patterns repeat. Use it as a concrete checkpoint if you are building for business buyers.
From
SaaStr
by Jason Lemkin
~10 min read
- Your first five interviews are mostly about understanding the white space, not validating a solution.
- By interview ten, real patterns in customer pain should start repeating across conversations.
- Interviews eleven through twenty are for sharpening your pitch and thesis, not discovering new problems.
Open
saastr.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The origin text for the modern MVP and validated-learning vocabulary every founder now uses. Read it for the mental model that a startup is a series of experiments, not a single bet.
From
theleanstartup.com
by Eric Ries
~330 pages
- Progress = validated learning, not features shipped.
- Run the Build-Measure-Learn loop as fast as you can.
- An MVP is a learning tool, not a cheap product.
Open
theleanstartup.com →
📄 Article
✓ Link checked
India
Freemium
Beginner
Why we picked it
Zerodha built one of India's most used products with a tiny team and a stubborn focus on simplicity over polish. Kamath's view that complexity is a bug backs up the idea that you need clear thinking, not heavy design. A grounded Indian example of how much (and how little) design a founder really needs.
From
Inc42
by Inc42
15 minute read
- Radical simplicity beats feature-heavy, over-designed products
- A small team can build a category leader by keeping it clear
- Clarity of thought matters more than visual sophistication
Open
inc42.com →
Why we picked it
Most founders either stop at two chats with friendly users or interview forever and never ship. Seaman, a UX researcher, gives you a concrete starting formula (begin at 5, add more for complex domains, multiply by personas) and a clear stop signal: when interviews start repeating and stop teaching you anything new, that is saturation and it is time to move. It reframes the real question from a magic number to noticing when you have stopped learning.
From
Medium
by Mitchel Seaman
About a 10 minute read
- Start around 5 interviews per persona and add more only if the domain is genuinely complex or the users vary a lot.
- The point to stop is saturation: when new conversations mostly echo what you already heard, more interviews are wasted time.
- There is no single correct number, so treat any count as a planning tool, not a target to hit before you are allowed to build.
Open
medium.com →
Why we picked it
The permission slip to recruit users by hand, do things manually, and deliver 'insanely great' experiences to your first few customers. The cheapest, most honest way to validate demand is to go get it one person at a time.
From
paulgraham.com
by Paul Graham
~15 min read
- Recruit your first users manually, don't wait for them to come.
- A tiny group of users who love you beats a big group who like you.
- Manual, unscalable effort early is a feature, not a failure.
Open
paulgraham.com →
Why we picked it
A short, practical field guide to customer discovery: who to talk to, how to find them, and how many. Pairs perfectly with The Mom Test, Fitzpatrick teaches the questions, Constable teaches the logistics.
From
talkingtohumans.com
by Giff Constable
~80 pages (free PDF available)
- Decide who you need to learn from before you start.
- Recruiting interviewees is a skill, scripts and channels included.
- Get out of the building; patterns emerge faster than you expect.
Open
talkingtohumans.com →
