📖 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 →
✍️ 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
Free
Intermediate
Why we picked it
This is a concrete workshop method for exactly the ranking step in our answer. You list every desirability, viability, and feasibility assumption, then plot each one by how important it is and how much evidence you have. The top-right corner (high stakes, low evidence) is the single assumption your MVP should attack first.
From
Strategyzer (David J. Bland)
by David J. Bland
9 min read
- Split assumptions into desirability, viability, and feasibility
- Rank each by importance against how much evidence you actually have
- Test the high-stakes, low-evidence assumptions before anything else
Open
strategyzer.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
Once you know your riskiest assumption, this book tells you which experiment actually tests it. It carries 40 plus illustrated experiment types organised by cost, time, and strength of evidence, matched to whether the risk is about desirability, feasibility, or viability. It is the reference you keep on the desk so you run the cheapest test that gives real evidence, not the most impressive demo.
From
Strategyzer (Wiley)
by David J. Bland and Alexander Osterwalder
Book, around 320 pages
- Break the idea into prioritised, testable assumptions first (via assumptions mapping), then pick an experiment for the riskiest one.
- Match the experiment to the type of risk: a landing page or interview for desirability, a different test for feasibility or viability.
- Start with cheap, fast, low-evidence experiments and only invest in stronger, costlier ones as an assumption survives the early tests.
Open
strategyzer.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Ramanujam argues that putting willingness to pay at the very centre of product design, before you build, is what separates products people buy from products people merely like. He shows how to have the money conversation early instead of bolting a price on at the end. This is the discipline behind baking a price into your test from day one.
From
First Round Review
by Madhavan Ramanujam
- Test willingness to pay before you build, not after you launch
- Most companies avoid the price conversation until it is too late
- A product designed around what people will pay for is a different product
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 →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
This is the most concrete walkthrough of how to test a niche when you have nothing built yet: put up a page describing the offer and count who actually clicks or signs up. It treats a click as a behavior, not an opinion, which is exactly the difference between real demand and polite interest. It gives you the seven steps, rough benchmarks, and the ethics of an honest reveal page, so you can run it this week for almost no money.
From
kromatic.com
by Kromatic (The Real Startup Book)
~15 min read
- A click or an email is a behavioral signal, worth far more than someone saying they like the idea
- Set your success threshold and sample size before you start, so you cannot rationalize a weak result
- Be honest on the reveal page ("coming soon, join the list") so the test does not burn trust in your own niche
Open
kromatic.com →
📄 Article
✓ Link checked
Freemium
Beginner
Why we picked it
Todd Jackson studied how dozens of now-large companies validated their very first idea. The pattern that repeats: deliver the outcome by hand, talk to real users, and watch for genuine emotion. A polite 'that's cool' is a no. Strong reactions are the signal you want.
From
Lenny's Newsletter
by Todd Jackson
~15 min read
- Manual delivery beats a survey for early signal.
- Look for strong emotion, not politeness.
- Great ideas usually start from a problem you have lived.
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The cleanest distillation of the one framework that turns a customer chat into a relationship instead of a survey. The three rules (talk about their life not your idea, ask about the past not hypotheticals, and chase real commitments of time, reputation, or money) are exactly how you get an early customer to tell you what nearly stopped them from buying and who else you should talk to. Rekhi is a product leader, so the examples are operator-grade, not book-report fluff.
From
Sachin Rekhi's Blog
by Sachin Rekhi
10 min read
- Never pitch your idea in the conversation; ask how they handle the problem today and what it costs them, so praise can't lie to you.
- The strongest signal is a commitment that costs them something: a trial, an intro to a colleague, or a pre-order.
- 'Would you buy this?' teaches you nothing; 'walk me through the last time you dealt with this' surfaces the real story and the referral.
Open
sachinrekhi.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Steve Blank coined get out of the building, and this is a clean primer on why talking to customers is a search for facts your building cannot give you. It frames customer discovery as testing your assumptions against real people rather than defending a plan. A short, foundational read on why you are doing this at all.
From
Kauffman Entrepreneurs (Steve Blank)
by Steve Blank
10 min read
- Facts about your customers live outside the building, go find them
- Treat your idea as a set of hypotheses to test, not a plan to defend
- Customer discovery is a search, expect several iterations before it clicks
Open
entrepreneurship.org →
Why we picked it
This is the essay that named the problem: an MVP quietly pushes you to build a whole product when what you actually need is to test one thing. Higham makes the case for the Riskiest Assumption Test (RAT), building only enough to learn whether your single biggest unknown holds. It is the sharpest starting point for deciding what to test instead of what to build.
From
HackerNoon
by Rik Higham
8 min read
- An MVP is not really a product, it is a way to test whether you have found a problem worth solving, so treat it as a test, not a launch.
- Find your largest unknown and build only what is needed to test it, nothing more.
- The goal is to maximise the rate of learning by minimising the time to try things, so pick the assumption that would kill the idea if it were wrong.
Open
medium.com →
📄 Article
Free
Intermediate
Why we picked it
Maurya gives you a repeatable way to rank risk instead of guessing at it. He points you at the universal early risks (do these customers have the problem, is the pain worth paying for, can you reach them) and shows why founders mis-prioritise and waste months. This is the how-to behind the 'rank by how fatal and how uncertain' step in our answer.
From
LEANSTACK blog (Ash Maurya)
by Ash Maurya
10 min read
- Tackle what is riskiest, not what is easiest or most fun to build
- Early on, problem, willingness to pay, and channel risks are near universal
- Intuition alone is a poor guide; talk through your risks with advisors and analogs
Open
blog.leanstack.com →
Why we picked it
The book that gave the world 'MVP', 'build-measure-learn', and 'validated learning'. It reframes a startup as a series of experiments, not a bet, the mental model everything else in this category builds on.
From
theleanstartup.com
by Eric Ries
~330 pages
- Progress = validated learning, not features shipped.
- Build the minimum that produces a real learning loop.
- Decide pivot-or-persevere on evidence, on a schedule.
Open
theleanstartup.com →
Why we picked it
A step by step process for taking an idea to something people want without building the wrong product first. Maurya's mantra, love the problem not your solution, keeps your first MVP focused on testing risk rather than shipping features. Practical if you want interview scripts and a repeatable order of experiments instead of theory.
From
Ash Maurya (O'Reilly)
by Ash Maurya
~336 pages
- Rank your assumptions and test the riskiest one first
- Love the problem, not your solution
- A one page model beats a long plan for an early idea
Open
oreilly.com →
