✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
This is the essay that forces the honest question underneath your idea: are you building a growth company or a good small business, because they are different DNA and require different lives. Graham is blunt that a barbershop is not a startup no matter how new it is, and that clarity helps you choose on purpose instead of drifting. There is nothing wrong with either path, but you should pick the one you actually want before you spend years on it.
From
Paul Graham
by Paul Graham
~20 min read
- A startup is defined by fast growth, not by being new or funded, so a business that cannot grow fast is a different (and often fine) choice, just not a startup.
- Growth needs two things at once: something many people want, and a way to reach them at scale, if either is missing the idea caps out as a niche.
- Deciding whether your idea can grow beyond a niche is really deciding what kind of company, and what kind of years, you are signing up for.
Open
paulgraham.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 →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
The original, primary source where the RICE framework was introduced, cite this, not the SEO reposts. The clearest way to compare hard-to-compare feature ideas.
From
Intercom Blog
by Sean McBride
~12 min read
- Score = (Reach x Impact x Confidence) / Effort.
- Forces you to quantify confidence and expose low-confidence pet projects.
- Comparable scores let you rank features objectively.
Open
intercom.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Des Traynor makes the case that "no" is the product strategy, and that adding a feature for one loud customer quietly costs every other user. It gives you language to defend a tight v1 against constant requests. Short, sharp, and directly about the discipline of cutting.
From
Intercom (Des Traynor)
by Des Traynor
~8 min read
- A cohesive product with clear boundaries beats a pile of tangential features.
- Every feature you add has an ongoing cost, not just a one-time build cost.
- No single customer request is worth more than a coherent product.
Open
intercom.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
Cutler names the exact trap your short answer warns about: shipping feature after feature while nobody measures whether any of them worked. The twelve signs are a mirror you can hold up to your own week. Sign one is the whole point: teams that never measure impact and treat shipping itself as the win.
From
Cutle.fish
by John Cutler
- Not measuring the impact of what you ship is the top warning sign
- Success theater around launches replaces honest talk about impact
- Constant feature churn without learning is the default failure mode
Open
cutle.fish →
📄 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
This is the warning label for treating every customer request as a build order. Chen shows how a team can keep shipping requested features, keep honouring the letter of promises, and still slowly die because none of it moves the business. It sharpens the short answer's point that exciting or requested does not equal important.
From
andrewchen.com
by Andrew Chen
- Building every requested feature can still lead nowhere
- Ask why behind a request before you commit to building it
- Honouring promises literally is not the same as growing
Open
andrewchen.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
Intermediate
Why we picked it
The full book behind the essay, for when you want the system and not just the idea. It gives you the language of outcomes over outputs so you can defend a no to your team and your customers with something concrete. Worth it if requests are piling up faster than you can reason about them.
From
Melissa Perri (O'Reilly)
by Melissa Perri
200 pages
- Tie every build decision to a measurable customer or business outcome
- Say no to work that only adds output without moving an outcome
- Set up the org so outcomes, not feature counts, decide priority
Open
amazon.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
The definitive manifesto for building a 'calm company', remote-friendly, sustainable, and free of chronic overwork, from a team that's lived it for two decades. Essential for founders designing culture and operations.
From
37signals
by Jason Fried & David Heinemeier Hansson
~232 pages
- Sustained output comes from calm and focus, not permanent crunch
- Default to async, protect deep work, and kill the always-on expectation
- Reasonable hours and a livable pace are a competitive advantage, not a weakness
Open
amazon.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Kano gives you a vocabulary for why exciting features can mislead you: delighters add satisfaction, but missing basics (reliability, honouring what you promised) actively create anger. It shows that a broken basic hurts more than a shiny delighter helps. That is the model behind treating reliability as non negotiable and exciting as optional.
From
Interaction Design Foundation
by Interaction Design Foundation
- Basic expectations, when broken, cause outsized anger
- Exciting delighters add satisfaction but never cover a broken basic
- Reliability is a must have, not a nice to have
Open
interaction-design.org →
📄 Article
✓ Link checked
Free
Advanced
Why we picked it
Google's error budget is the most rigorous version of the one third rule: define how much unreliability you can tolerate, and when you blow past it, new feature work stops until reliability recovers. It gives you an objective trigger for when to drop the exciting build and pay down reliability. Even a rough version of this keeps promises from silently rotting.
From
Google SRE Book
by Google SRE Team
- Set an explicit budget for how much unreliability you accept
- When the budget is spent, feature work pauses for reliability
- A shared budget ends the endless features versus stability argument
Open
sre.google →
📖 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
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
Intermediate
Why we picked it
Cagan draws the line between teams measured by output (features shipped) and teams measured by outcomes (problems solved). If you keep defaulting to the exciting build, this explains the mindset shift that stops it. It reinforces judging bugs, promises, and new work by the result they produce rather than how exciting they feel to build.
From
Silicon Valley Product Group (SVPG)
by Marty Cagan
- Measure the team by outcomes solved, not features shipped
- A roadmap of features handed down breeds the wrong incentives
- Being empowered to solve the problem beats being told what to build
Open
svpg.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
This is the canonical source for the claim that the customers you already have are far cheaper to keep than the ones a shiny feature might win. Gallo lays out the retention economics, including how acquiring a new customer can cost many times more than keeping an existing one. It gives you hard numbers to justify protecting reliability and promises over the exciting build.
From
Harvard Business Review
by Amy Gallo
- Winning a new customer can cost five to twenty five times retention
- Small gains in retention drive outsized gains in profit
- The cheapest growth is not losing the customers you already have
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 →
