📖 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
A side-by-side of both methods that makes clear why you use bottom-up as your primary number and top-down only as a rough check. That distinction is exactly what protects you when the top-down Indian data is thin. Read it to decide which method to lead with in your deck.
From
Waveup
by Waveup
14 min read
- Bottom-up is defensible, top-down is only a directional check
- Use both and reconcile them against each other
- Lead with the method your data can actually support
Open
waveup.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
The definitive essay on where good ideas come from: notice problems you personally have, don't force it. Use it as the lens for judging whether your idea is a real problem or a solution in search of one.
From
paulgraham.com
by Paul Graham
~20 min read
- Live in the future and build what's missing.
- The best ideas look like bad ideas at first (schleps and hard-to-explain).
- Start with problems you have, in a domain you actually know.
Open
paulgraham.com →
✍️ 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
Intermediate
Why we picked it
This is the guide for the check-in itself: what to actually say when you sit down. Perel names the three things co-founder fights are secretly about (power, closeness, recognition) so you stop arguing about the surface and address the real thing directly. Her concrete rules (keep an argument under 10 seconds then pause, swap 'always/never' for 'in this moment it feels like', address one problem at a time, never assassinate character) are exactly the disagreement-muscle drills you run when stakes are low so they hold when stakes are high.
From
First Round Review
by Esther Perel (via First Round Review)
20 min read
- Most co-founder fights are misdiagnosed: they are about power, recognition, or feeling sidelined, not the strategy you are nominally arguing over, so say 'I feel sidelined' instead of blaming.
- Fight cleanly with mechanical rules: one issue at a time, arguments capped at ten seconds before a pause, no 'always/never', acknowledge and validate before you rebut.
- Proactive maintenance beats crisis repair; keep a running list of what you appreciate in your co-founder and consider a coach as a neutral third party for accountability.
Open
review.firstround.com →
📄 Article
✓ Link checked
Freemium
Beginner
Why we picked it
Sometimes the two ideas are a proxy for a deeper problem: you have no agreed way to make a call when you disagree. This HBR piece treats disagreement as a skill and pushes you to set decision rules in advance, including who gets the final say on which kinds of calls, so a single stuck choice does not calcify into resentment. It is short and pairs well with a disagree and commit rule: back one idea for a defined window with pre-agreed metrics, then review.
From
Harvard Business Review
by Evelyn Nam
~8 min read
- Decide ahead of time who owns which decisions, so a deadlock has a built-in tiebreaker instead of grinding to a halt.
- Commit to one direction for a set period with clear metrics, then revisit, rather than relitigating it every week.
- Unresolved founder conflict is a leading reason startups fail, so treating this as urgent is warranted, not dramatic.
Open
hbr.org →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
This is the primary source, not a blog summary of it, and it does both jobs your answer needs in about two pages: the one-way vs two-way door distinction and 'disagree and commit', in Bezos's own words. Read the section titled 'High-Velocity Decision Making' and steal three lines verbatim for your team: decide most things at 70 percent of the information you wish you had, treat reversible calls as two-way doors an owner walks back through, and 'I disagree and commit' is a real, sincere yes after being heard, not a shrug.
From
Amazon (aboutamazon.com)
by Jeff Bezos
12 min read
- Sort every decision into one-way doors (irreversible, deliberate slowly) vs two-way doors (reversible, decide fast); the failure mode is running the slow process on the fast decisions
- Decide at ~70 percent of the information you want; waiting for 90 percent means you are being slow, and being slow is more expensive than being wrong when you course-correct well
- 'Disagree and commit' is a two-way street: the owner voices real conviction, the team is genuinely heard, then everyone commits out loud, so consensus is never the bar
Open
aboutamazon.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Your short answer tells founders to design the cheapest test that would move one of them, and this is the clearest write-up of exactly that method. It shows how to isolate the single riskiest assumption behind a disagreement and disprove it with the smallest possible experiment, well before building anything. The Airbnb example makes it concrete and repeatable.
From
ModelThinkers
by ModelThinkers
10 min read
- Isolate the one assumption whose failure would sink the case
- Test it the cheapest, fastest way that could disprove it
- State up front what result would change your mind
Open
modelthinkers.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Consumer PMF advice does not map cleanly onto B2B, where deals are few, considered, and slow, which describes many Indian startups selling to businesses. This guide covers the specific signals that matter when you have ten design partners instead of ten thousand users. Read it if the 40 percent survey feels awkward for your low-volume, high-value product.
From
Lenny's Newsletter
by Lenny Rachitsky
~3,000 words
- In B2B, renewal and expansion are your retention signal, not daily use
- A handful of paying, referring customers can confirm fit
- Watch whether sales gets easier and cycles get shorter over time
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Iskold reduces market size to a single honest formula, number of customers times revenue per customer, and warns against padding decks with irrelevant giant TAM figures. It is a fast way to force both cofounders onto the same bottom-up basis, so you are comparing the same two or three inputs rather than talking past each other. Practical, opinionated, and short enough to read together in one sitting.
From
Startup Hacks (Alex Iskold)
by Alex Iskold
12 min read
- Market size equals number of customers times revenue per customer
- Build it bottom-up rather than borrowing a huge industry figure
- Disagreements collapse onto a few shared inputs once the formula is explicit
Open
startuphacks.vc →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
Thiel pushes you to look for ideas hidden in plain sight by asking what important truth very few people agree with you on. It is a strong counterweight to chasing crowded, obvious spaces, and it sharpens your instinct for problems others are overlooking. Read it for the questions it forces you to ask, more than the answers.
From
Peter Thiel and Blake Masters
by Peter Thiel and Blake Masters
About 220 pages
- Look for a truth that few people agree with you on
- Building something genuinely new beats copying what works
- The best problems are often the ones others dismiss
Open
amazon.com →
✍️ Essay
✓ Link checked
Free
Advanced
Why we picked it
Before you sweat which side to seed, Gurley helps you judge whether your marketplace is even structurally worth building. He lays out ten factors (fragmentation, frequency, payment flow, network effects) that separate marketplaces that snowball from ones that stay empty. It is the investor lens on why some two sided ideas never reach liquidity no matter how hard you push.
From
Above the Crowd
by Bill Gurley
20 min read
- Great marketplaces enhance a market, they do not just aggregate it
- High fragmentation on both sides makes a marketplace more defensible
- Being in the payment flow is far stronger than sitting outside it
Open
abovethecrowd.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Blank's core rule is that there are no facts inside your building, so a disagreement resolved at your desk is not really resolved. His customer discovery method gives you the scientific loop of stating a hypothesis, testing it with real customers, and validating, invalidating, or modifying it. That loop is the machine that turns a stubborn cofounder argument into evidence.
From
Steve Blank
by Steve Blank
varies
- Treat each side's belief as a hypothesis to test outside the building
- Design an experiment, collect data, then validate or kill the belief
- Founders themselves must run the customer conversations
Open
steveblank.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
Beginner
Why we picked it
Written from an early-stage investor's chair, this walks the calculation with examples and is blunt that a bottom-up build beats a share-of-TAM guess. Antler backs pre-seed founders, so the advice is calibrated to exactly the stage you are at. Useful for seeing how a fund wants the number presented.
From
Antler
by Akshat Agarwal
- Early-stage investors prefer a bottom-up build over a share of TAM
- Worked examples show each of the three numbers being derived
- Present the assumptions so the number can be stress-tested
Open
antler.co →
