📖 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
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 →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
This is the canonical source of the ship-ugly-first idea, the LinkedIn co-founder's own essay behind the line about being embarrassed by your first version. For a solo dev deciding how much to build into a referral program before shipping, this is the judgment call at the heart of the question, launch the rough version and let real usage tell you what to add. Hoffman also draws the line on where ship-fast should not apply, which keeps it honest rather than a slogan.
From
LinkedIn
by Reid Hoffman
About a 6 minute read
- Ship the version you are slightly embarrassed by, because real user behavior teaches you what to build far faster than internal guessing
- Embarrassing is not the same as harmful: launching fast does not excuse things that alienate users or create real risk
- Speed compounds: earlier feedback means earlier iteration, which matters more than polishing features nobody has asked for yet
Open
linkedin.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Blank invented the get out of the building idea, and here he makes the sharpest version of the case: until you test your assumptions outside your own head, your plan is just creative writing. It reframes research as something you do in the field with customers, not at your desk. A short, blunt push to stop planning and go listen.
From
steveblank.com
by Steve Blank
~8 min read
- Untested assumptions are guesses dressed up as a plan
- Real learning happens outside the building, with customers
- Search for a business model before you execute one
Open
steveblank.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Bezos separates decisions into one way doors you cannot undo and two way doors you can walk back through. Deciding to build a scrappy first version is almost always a two way door, so it does not need endless research to de risk it. This one page reframes the fear that keeps you researching as usually unfounded.
From
Amazon shareholder letter (Jeff Bezos)
by Jeff Bezos
~6 min read (relevant section)
- Most early decisions are reversible, so make them fast
- Reserve slow careful analysis for the truly irreversible calls
- Treating reversible choices as high stakes causes needless delay
Open
s2.q4cdn.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
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
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 →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
A punchy, contrarian classic on building a lean, sane, profitable company from the founders of Basecamp. It's the antidote to hustle-culture folklore about how startups must operate.
From
37signals
by Jason Fried & David Heinemeier Hansson
~288 pages
- Small teams, less process, and shipping beat planning theatre
- Say no to most things and protect focus
- You can build a great company without following the standard playbook
Open
amazon.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
From the Google Ventures team, this shows how to go from a fuzzy idea to a tested prototype in a single week. The core move is building a realistic facade in a day and watching users try it, which is exactly the prevent-wrong-code loop the short answer describes. It gives a founder a concrete process, not just a pep talk.
From
Jake Knapp (jakeknapp.com)
by Jake Knapp, John Zeratsky, Braden Kowitz
Approx. 275 pages
- A convincing prototype takes a day, not a sprint of engineering
- Test with five real users before committing to a build
- Deciding fast on paper is cheaper than deciding in code
Open
jakeknapp.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Amazon's trick is to write the customer facing press release and FAQ before building anything, which forces you to describe the experience in the customer's words first. That is the same discipline our answer asks for: start from what the user does and gets, not the machinery. The FAQ section is a natural place to list what you are deliberately not doing in version one.
From
Working Backwards (Colin Bryar and Bill Carr)
by Colin Bryar and Bill Carr
12 min read
- Describe the finished experience from the customer's side first
- Iterating on a document is far cheaper than iterating on code
- The FAQ forces you to answer the hard scope questions up front
Open
workingbackwards.com →
📖 Book
✓ Link checked
Free
Intermediate
Why we picked it
Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary source, free in full. The antidote to over-planning your roadmap.
From
Basecamp / 37signals
by Ryan Singer
free online book
- Work in short cycles with a cool-down between them.
- Fix time, vary scope, use 'appetites,' not estimates.
- Make bets, not plans; no runaway backlog.
Open
basecamp.com →
📄 Article
✓ Link checked
India
Free
Beginner
Why we picked it
Concrete stories of Indian founders who went to where their customers were before building, like Shiprocket's founder travelling across pin codes and hosting seller meetups to understand pain points. It makes the go where the problem lives advice tangible in an Indian setting. Good for seeing what standing where your customers already are actually looks like on the ground here.
From
Penguin Random House India
10 min read
- Indian founders validated by physically going to where their customers worked
- Meetups and direct conversations surfaced the real pain points
- Validate the problem first, a strong problem beats a clever idea
Open
penguin.co.in →
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
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 →
