📖 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
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 →
📖 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
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
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
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
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
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 →
📖 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
Graham wrote this after watching hundreds of early companies fail, so the failure patterns are observed, not theorized. Two of his mistakes go straight at trend-chasing: the derivative idea (building an imitation of whatever is hot) and the marginal niche (picking a weak market to dodge competition), both of which trace back to his root failure, not making something users actually want. It is a good starting point for pressure-testing whether you are building on a trend or just following one.
From
YC Startup Library
by Paul Graham
~20 min read
- Copying a hot company (a derivative idea) is a top killer: real startups usually start from a problem the founder personally felt, not from a trend to ride.
- Chasing an obscure corner to avoid competition is its own trap, you can only dodge competitors by dodging good ideas.
- Every mistake funnels back to one test: are real users demonstrably choosing what you built?
Open
ycombinator.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Press is one of the easiest excuses to relaunch that founders under-use, and this guide teaches you to treat it as ongoing relationship-building with reporters rather than a one-time pitch saved for a big round or milestone. It pairs well with your short answer, since if you build a few real reporter relationships, every meaningful update becomes a small, low-effort story you can pitch.
From
Y Combinator (YC Startup Library)
by Y Combinator
- Treat press like business development: build reporter relationships before you need them.
- Warm introductions beat cold pitches, and that pipeline takes ongoing work, not a one-time push.
- Small, real updates are pitchable once you already have the relationship in place.
Open
ycombinator.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Figma spent years building quietly before a genuinely coordinated launch, and this piece walks through how that transition was actually planned and executed. It is the clearest real-world playbook for the moment your co-founder is imagining, useful once you both agree you have reached it, since a big launch done well still takes deliberate groundwork.
From
First Round Review
by First Round Review
20 min read
- Years of quiet building can precede a launch without wasting the moment
- A coordinated launch works best when the product is already proven internally
- Plan the emergence from quiet mode as carefully as the quiet period itself
Open
review.firstround.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Slack iterated privately with a small team for months, using what they learned to earn a preview release that then turned into real press momentum. It is a concrete example of exactly the sequencing your short answer argues for: quiet first, coordinated push once there is something worth the one shot. Read it with your co-founder as a shared case study instead of two competing opinions.
From
First Round Review
by First Round Review
20 min read
- Private iteration with real users came well before any public announcement
- The preview release, not a hard launch, was the actual turning point
- Press attention followed proof of a working product, it did not create it
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 →
