📖 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
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 →
📖 Book
✓ Link checked
Free
Beginner
Why we picked it
Free to read online, with chapters like "Build Less" and "Half, Not Half-Assed" that name your exact trap. It argues that cutting scope is a feature, and that the version with fewer things done well beats the bloated one. A fast, opinionated read you can skim straight to the chapters that sting.
From
Basecamp / 37signals
by Jason Fried, David Heinemeier Hansson (37signals)
Free online, ~4 hr
- Build half a product, not a half-built product.
- Every feature you add is one more thing to maintain and explain.
- Deliberately underdo the competition on scope.
Open
basecamp.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 →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Beck, a foundational voice in software, adds useful nuance about what minimal really means and why teams so often get it wrong. His argument that you rarely know the right minimal product up front, so start smaller, guards against building too much under the MVP label. A thoughtful counterweight when your MVP is quietly growing into a full product.
From
Tidy First (Kent Beck)
by Kent Beck
~1,000 words
- You usually do not know the true minimal product in advance
- When in doubt, start smaller than feels comfortable
- Minimal is defined by the learning you need, not the roadmap
Open
newsletter.kentbeck.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Cohen names the perfectionist's core bug: maximizing every decision when good enough would do. He gives you a rule for when to chase the best answer (rare, high stakes, hard to reverse) and when to just pick and move (almost everything else). If polishing is your default setting, this gives you both permission and a filter.
From
A Smart Bear
by Jason Cohen
12 min read
- Reserve maximizing for slow, expensive, one-way decisions.
- Set a "good enough" bar in advance and stop when you hit it.
- Perfectionism is a strength that quietly becomes a tax.
Open
longform.asmartbear.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
For the refactoring half of your question, Fowler explains why building for imagined future needs usually costs more than it saves. He carefully separates real over-engineering from healthy refactoring, so you can tell craft from gold-plating in your own codebase. A precise, engineer-to-engineer read.
From
martinfowler.com
by Martin Fowler
10 min read
- Do not build capability for a future you have not validated.
- Presumptive features carry build, carry, and repair costs.
- Refactoring for changeability is fine, speculative features are not.
Open
martinfowler.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
Beginner
Why we picked it
Altman's condensed operating manual for founders, including sharp guidance on focus, spending your time on what only you can do, and prioritization. Primary source, endlessly re-read.
From
playbook.samaltman.com
by Sam Altman
long
- A founder's job narrows to a few things: set the vision, hire well, and don't run out of money
- Focus and intensity beat breadth, do a few things extremely well
- Momentum and growth are the founder's core responsibilities
- Protect your time for the highest-leverage work only you can do
Open
playbook.samaltman.com →
✍️ Essay
✓ Link checked
Free
Advanced
Why we picked it
Doshi names the IKEA effect, how you overvalue what you built simply because you built it, which is the quiet engine behind gold-plating. It pushes you toward judgment about what matters over the reflex to keep improving your own creation. Best for the founder who suspects attachment, not need, is driving the polish.
From
Shreyas Doshi (Substack)
by Shreyas Doshi
12 min read
- You overvalue what you build, so discount your own certainty.
- More features and polish are not the same as more impact.
- Judgment about what to skip beats effort spent building.
Open
shreyasdoshi.substack.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 →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
Your short answer says polishing is often fear of the market's verdict, and this is the book about exactly that fear, which Pressfield calls Resistance. It is not a startup book, but it names the emotional reason you refactor instead of ship better than any tactical guide can. Short, blunt, and uncomfortably accurate.
From
stevenpressfield.com
by Steven Pressfield
190 pages
- Procrastination often disguises itself as more preparation.
- The closer you get to shipping, the louder the fear.
- Naming the fear is how you get past it.
Open
stevenpressfield.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 →
