📖 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
A short, free primer straight from the person who coined the term, useful when someone on your team thinks an MVP just means a cheap version of the full product. It clarifies that an MVP can be as small as a landing page or a manual service as long as it produces real learning. Read it to reset the definition before you scope anything.
From
Lean Startup Co.
by Eric Ries
~8 min read
- An MVP is about learning, not about a smaller product
- It can be a page, a video, or a manual service
- Customers must take a real action for the test to count
Open
leanstartup.co →
✍️ 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
The father of customer development argues that your plan survives contact with reality only after you leave your desk and test it on real people. It is the antidote to spending months building against untested guesses. Pair it with The Mom Test to keep your scope honest.
From
steveblank.com
by Steve Blank
10 min read
- Every assumption behind your MVP is a guess until you test it outside
- Facts about customers live in the field, not in your building
- Validate the problem before you invest weeks in the solution
Open
steveblank.com →
📖 Book
✓ Link checked
Free
Intermediate
Why we picked it
This chapter is the clearest argument for our claim that a long timeline means your scope is wrong. Basecamp starts with a fixed time budget (the appetite) and cuts the design to fit, instead of estimating a fixed scope and watching time balloon. If your MVP keeps slipping, this gives you the mental model to fix it.
From
Basecamp / 37signals
by Ryan Singer
15 min read
- Fix the time and vary the scope, not the other way around
- An appetite starts with a number and ends with a design
- A deadline that cannot move forces the hard cuts for you
Open
basecamp.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
A dense list of hard won lessons, several of which land directly on speed and iteration as a startup's main edge over big companies. Altman argues you should ship, get to product market fit, and evolve the plan rather than perfect it in advance. Quick to read and easy to return to.
From
Sam Altman
by Sam Altman
8 min read
- Speed is one of your few real advantages, so protect it
- Seek product market fit by shipping, not by planning in detail
- Expect to rewrite your plan as you learn from users
Open
blog.samaltman.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 →
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 →
Why we picked it
Drew Houston validated Dropbox with a three minute demo video before building the hard sync engine, and the waitlist jumped from 5,000 to 75,000. It is a vivid reminder that sometimes the fastest MVP is not code at all. Useful when the real product would take months but you can test demand in days.
From
YourStory
by YourStory
7 min read
- A demo or video can test demand before you build the product
- Validate that people want it before committing engineering months
- The smallest MVP is whatever proves the core hypothesis fastest
Open
yourstory.com →
📄 Article
Free
Intermediate
Why we picked it
The author of Running Lean tackles the exact trap in our short answer: founders confuse a wrong timeline with a wrong scope. He gives a way to find the smallest version that still delivers on your promise. Read it when you cannot tell what to cut.
From
Ash Maurya (Lean Stack)
by Ash Maurya
9 min read
- Define your MVP by the smallest promise you can keep
- Explicitly list what you will not build to protect the timeline
- Right minimum means enough to learn, not enough to impress
Open
medium.com →
