Every resource founders actually use, in one library.

What founders use most, ranked by how many answers lean on it.

1. A short investor essay arguing for shipping internal betas to your team on a regular weekly basis to keep momentum. It... Medium Essay · ~7 min read · Starting Up Development Cadence Megan Quinn
2. Traynor's cupcake metaphor says your first version should be small but whole and enjoyable, a real cupcake rather than a slice... Des Traynor, Intercom Blog Article · 5 min read · Starting Up Start with a cupcake Des Traynor
3. The Kano model separates must-be features (whose absence causes real anger) from delighters (whose absence nobody notices yet).... Wikipedia Article · 10 min read · Starting Up Kano Model Wikipedia
4. Traynor explains how Intercom stopped sorting feedback by what was said and started sorting it by the job the customer was... Jobs-to-be-Done Radio Podcast · Starting Up Des Traynor on Jobs-to-be-Done & Intercom Des Traynor
5. A hands on walkthrough of the unglamorous middle step, putting every piece of feedback in one place, tagging it, and rolling it... Intercom Article · Starting Up Customer feedback strategy: How to collect, analyze, and take action Intercom
6. Traynor describes finding fit by looking for clusters of demand, groups of customers pulling for the same underlying thing,... Underscore VC Article · Starting Up How Intercom Uses Clusters of Demand to Find Product-Market Fit Des Traynor
7. Fried makes the case for saying no to most requests and letting them pile up, so only the ones that keep recurring earn... Intercom Podcast · Starting Up Basecamp's Jason Fried on product strategy Jason Fried
8. Gilad's work is about ranking ideas by the strength of the evidence behind them, not by who shouted loudest. His Confidence... itamargilad.com Book · Starting Up Evidence-Guided: Creating High Impact Products in the Face of Uncertainty Itamar Gilad
9. Kano gives you a vocabulary for why exciting features can mislead you: delighters add satisfaction, but missing basics... Interaction Design Foundation Article · Starting Up The Kano Model Interaction Design Foundation
10. Google's error budget is the most rigorous version of the one third rule: define how much unreliability you can tolerate, and... Google SRE Book Article · Starting Up Embracing Risk (Error Budgets) Google SRE Team
11. Cagan draws the line between teams measured by output (features shipped) and teams measured by outcomes (problems solved). If... Silicon Valley Product Group (SVPG) Article · Starting Up Product vs Feature Teams Marty Cagan
12. The 37signals team makes the case for doing fewer things extremely well rather than many things adequately. It is the audio... REWORK by 37signals Podcast · ~25 min · Starting Up Build Half a Product, Not a Half-Assed Product Jason Fried and David Heinemeier Hansson
13. Cagan draws the line between discovery (figuring out what is worth building) and delivery (building it), and argues most waste... Silicon Valley Product Group Article · ~12 min read · Starting Up Product Discovery Marty Cagan
14. A raw, honest founder account of using building as a way to avoid the scarier work of selling and talking to strangers. It puts... Indie Hackers Thread · ~8 min read · Starting Up I've been building for months and made $0. The honest psychological reason. Indie Hackers
15. The talk version of the same idea, covering product scope, feature creep, and how products lose relevance when they try to do... Business of Software Video · 45 min · Starting Up Product Strategy (BoS talk) Des Traynor
16. A practical checklist drawn from many product leaders on the exact question of when a feature has earned its removal. It gives... Lenny's Newsletter Article · 10 min read · Starting Up When to sunset a feature Lenny Rachitsky
17. A product team's honest account of the ongoing cost every shipped feature adds to engineering, design, support, and the next... HubSpot Product Blog Article · 7 min read · Starting Up On Killing It by Killing Features Daria Marmer
18. This treats unshipping as a craft with real upside, not just cleanup, and shows how to use usage data to decide what goes. It... Mixpanel Article · 9 min read · Starting Up The art of removing features and products Neil Rahilly
19. Written for solo and small-team founders, this makes the case that saying no and removing features is a survival advantage when... The Bootstrapped Founder Essay · 10 min read · Starting Up The Power of Omission: Killing Features for Fun and Profit Arvid Kahl
20. The step-by-step operational side of your question: once you have decided to kill a feature, how do you actually retire it... Product Teacher Article · 9 min read · Starting Up How to Deprecate a Feature Clement Kao
21. This gives you the simple two-axis map (how many people use a feature, and how often) that turns a gut feeling into a picture... Intercom Article · 6 min read · Starting Up Prioritising Features: Who'll Use It and How Often (the Feature Audit) Des Traynor
22. A short, practical answer on how to actually decline feature requests and keep the product lean, including their line that you... Signal v. Noise Article · 5 min read · Starting Up Ask 37signals: How do you say no? Jason Fried
23. A practical playbook for the part founders fear most: removing a feature while keeping the few users who relied on it on your... airfocus Article · 9 min read · Starting Up How to kill product features without losing customers Andrei Tiburca
24. A practical piece on the exact failure mode where each big customer gets their own custom feature and the product fragments... The Startup (Kit Merker) Essay · 8 min read · Starting Up How to Avoid the Per-Customer Feature Trap Kit Merker

Show the next 24