📖 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 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 →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
The definitive essay on where good ideas come from: notice problems you personally have, don't force it. Use it as the lens for judging whether your idea is a real problem or a solution in search of one.
From
paulgraham.com
by Paul Graham
~20 min read
- Live in the future and build what's missing.
- The best ideas look like bad ideas at first (schleps and hard-to-explain).
- Start with problems you have, in a domain you actually know.
Open
paulgraham.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
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
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 →
📖 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 →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
Savoia, who led early Google AdWords, argues most ideas fail because nobody wanted them, and teaches pretotyping: cheap experiments that generate your own data on real demand before you build. You get concrete tactics like the fake-door and the mechanical-turk test, plus a way to demand skin-in-the-game commitment rather than opinions. Practical for anyone who wants a test that can prove them wrong.
From
Alberto Savoia
by Alberto Savoia
~250 pages
- Collect your own data on real behaviour instead of trusting opinions
- Pretotype the idea to test demand before you build a prototype
- Measure commitments like a signup or a payment, not verbal enthusiasm
Open
albertosavoia.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
DoorDash started as PaloAltoDelivery.com, a static page with a phone number and no app, delivering orders by hand. This is the founder telling how that scrappy test proved demand before any product got built. A concrete reminder that a landing page plus manual fulfillment can validate a billion dollar idea.
From
Stanley Tang (DoorDash co-founder)
by Stanley Tang
10 min read
- A simple page and a phone number tested real demand in a day.
- The founders delivered the first orders themselves to learn the job.
- Word of mouth on a fake looking MVP was the signal to build for real.
Open
stanleytang.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 →
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
This is the founder essay that made the case for validating before you build, from the person who did it with Buffer. Gascoigne frames the no-code or landing page MVP not as a shortcut to a product, but as a way to learn whether anyone actually wants the thing, which is exactly the stance this question takes. His honest point is that 120 signups plus real conversations taught him more than any polished build would have.
From
Medium (Joel Gascoigne, co-founder of Buffer)
by Joel Gascoigne
- The goal of a no-code or landing page MVP is validated learning, not vanity signups: talk to the people who respond, do not just count emails.
- Anything can be your MVP as long as you are genuinely testing demand before committing to a full build.
- Buffer got only 120 signups in seven weeks, but the direct conversations proved real interest and led to paying customers at launch.
Open
medium.com →
