How to Read This Book by Stage

The right chapter depends on the stage of the company. A founder choosing an idea does not need the same reading path as a founder preparing for diligence or scaling a team.

Use this page as a stage-based reading path.

Quick stage diagnosis

Use this before choosing chapters.

If this is true	Your likely stage	Main work
You have an idea but cannot name 30 reachable prospects	Idea	Sharpen customer and access.
You can name prospects but have weak evidence of pain	Validation	Run discovery and artifact review.
Pain is real but the first product is unclear	MVP	Define riskiest assumption and first value moment.
Users/customers try it but do not repeat	Product-market fit search	Fix activation, retention, value, segment, or promise.
Customers buy only through founder effort	First customers	Learn sales motion before delegating.
One segment and channel are starting to repeat	Repeatable GTM	Improve metrics, onboarding, support, and sales process.
Hiring and spend are increasing	Scaling	Strengthen operating rhythm, culture, cash discipline, and management.
Cash, retention, or founder energy is failing	Survival/pivot/shutdown	Preserve options and make a responsible decision.

When two rows feel true, read the earlier stage first. Earlier-stage mistakes become expensive later.

Idea stage

Main question: Is this worth exploring?

Read:

Action: Write three problem hypotheses and speak to people who live with the problem.

Ignore for now: incorporation details, investor decks, full product architecture, hiring plans, and brand polish. At idea stage, the main job is to find a painful enough problem and a reachable enough customer.

Useful output before moving on:

Output	Minimum quality bar
Problem hypothesis	Specific customer, trigger, workaround, cost, and evidence needed.
Prospect list	At least 30 reachable people or companies in the target segment.
Risk map	Customer, problem, payment, channel, delivery, and founder-market risks named.
Kill/continue rule	Written before emotional attachment takes over.

Validation stage

Main question: Is there real pain and willingness to act?

Read:

Action: Run enough conversations to find repeated patterns, not just polite encouragement.

Stage gate: do not move to MVP because people said “sounds useful.” Move when you can describe the customer’s current workaround, trigger, cost of the problem, decision maker, and reason they might act now.

Evidence to collect:

Evidence	Why it matters
Recent customer story	Proves the problem is not theoretical.
Workflow artifact	Shows what actually happens, not what people summarize.
Current spend or time cost	Reveals seriousness.
Buyer path	Prevents building for a user who cannot approve change.
Willingness to act	Intro, pilot, paid diagnostic, data share, or decision meeting.

MVP stage

Main question: What should we build first?

Read:

Action: Define the riskiest assumption and build only what tests it.

Ignore for now: nice-to-have integrations, admin dashboards, perfect onboarding, and every edge case. If the MVP does not test a risk, it is probably scope creep.

Useful output before moving on:

Output	Minimum quality bar
MVP scope	Must-build list is shorter than not-now list.
Success metric	One primary signal tied to first value or payment.
Manual layer	Named honestly, with time per customer tracked.
Review date	Set before building starts.

First customers stage

Main question: Can we sell and deliver value?

Read:

Action: Build a weekly sales rhythm: prospect, call, follow up, learn, close, deliver.

Stage gate: before hiring sales or spending heavily on marketing, founders should be able to explain who buys, why they buy, what blocks the deal, how long it takes, what price is believable, and what promise the product can keep.

Useful output before moving on:

Output	Minimum quality bar
ICP	Narrow enough that outreach, demo, pricing, and onboarding feel specific.
Sales notes	Buyer, pain, urgency, objection, next step, and decision process captured.
Pilot/proposal	Scope, success criteria, price, owner, timeline, and decision meeting written.
Delivery notes	First value delivered without heroic hidden work, or hidden work is measured.

Fundraising stage

Main question: Should we raise, and what proof supports the round?

Read:

Action: Write the milestone the round unlocks before polishing the deck.

Stage gate: raise because capital can create a stronger company, not because a deck can hide weak proof.

Useful output before investor outreach:

Output	Minimum quality bar
Investor memo	Clear customer, problem, evidence, risk, use of funds, and milestone.
Deck	Understandable without founder narration.
CRM	Investors sorted by thesis fit, intro path, status, and next action.
Data room	Cap table, financials, customer proof, legal/compliance basics, and product notes organized.
Walk-away terms	Founder understands what terms or investor behavior are unacceptable.

Hiring stage

Main question: Which role unlocks the company now?

Read:

Action: Write the scorecard before sourcing candidates.

Stage gate: hire only when the role removes a repeated company constraint and the founder can explain the first 30 days clearly.

Useful output before making an offer:

Output	Minimum quality bar
Role scorecard	Outcomes, skills, traits, and disqualifiers written.
Work test	Resembles actual work and respects candidate time.
Reference plan	Questions reveal strengths, risks, integrity, pressure behavior, and management needs.
30/60/90 plan	First outcomes and feedback rhythm are clear before joining.

Scaling stage

Main question: What is repeatable enough to grow?

Read:

Action: Identify the one growth loop that already has evidence before scaling spend.

Stage gate: scale only what is repeatable enough to survive more volume. Scaling a broken onboarding, weak retention, poor margin, or founder-only sales motion makes problems louder.

Useful output:

Output	Minimum quality bar
Stage metrics	Activation, retention, revenue quality, CAC/payback, gross margin, and runway visible by segment where relevant.
Operating cadence	Weekly review, decision log, monthly metrics, and owner accountability working.
Hiring plan	Roles mapped to constraints, not vanity org chart.
Customer success rhythm	Onboarding, support, renewal, expansion, and churn reasons tracked.

Survival, pivot, or shutdown stage

Main question: What is the responsible next move?

Read:

Action: Make the decision while options still exist.

Useful output:

Output	Minimum quality bar
Cash forecast	13-week view of cash, collections, payroll, vendors, taxes/advisors, and closing balance.
Options memo	Continue, narrow, pivot, cut burn, raise bridge, sell assets, acquihire, shutdown, or restart evaluated honestly.
Stakeholder map	Employees, customers, investors, vendors, advisors, family, and data/access obligations listed.
Founder recovery plan	Treated as real, not as an afterthought.

What stage are you really in?

Founders often name the stage they want to be in, not the stage the evidence supports. Use this table when the team is confused.

If you are saying…	You may actually be in…	Check this
”We need to scale.”	First customers or PMF search	Are customers retaining, referring, expanding, or buying without heavy founder effort?
”We need a marketer.”	Customer discovery	Do you know the exact customer language, trigger, objection, and promise?
”We need an investor deck.”	Validation	What proof would make the round believable beyond a story?
”We need more features.”	MVP	Which assumption will each feature test?
”We need a sales head.”	Founder-led sales	Have founders personally learned the buying process?
”We need to pivot.”	Survival	Is the issue weak problem, wrong customer, bad channel, poor retention, cash pressure, or founder energy?

When in doubt, move one stage earlier and collect better evidence. Startups usually suffer less from moving too slowly through theory and more from moving too quickly past reality.

One-week reading plan

Use this when the book feels large.

Day	Task
Monday	Name your real stage and write the current decision.
Tuesday	Read two chapters tied to that decision.
Wednesday	Run one playbook or fill one template.
Thursday	Talk to a customer, prospect, investor, candidate, advisor, or team member connected to the decision.
Friday	Review evidence and write continue/change/stop.
Weekend	Rest or read one adjacent chapter only if it helps next week’s decision.

This book should create a weekly operating rhythm, not a reading backlog.

Stage-specific anti-goals

At each stage, know what not to optimize yet.

Stage	Do not optimize yet
Idea	Brand, full product, incorporation ceremony, investor deck, complex financial model.
Discovery	Pitching, surveys, broad personas, solution demos, vanity landing pages.
Validation	Feature depth, automation, expensive design, hiring, broad marketing.
MVP	Perfect architecture, admin polish, every edge case, scale infrastructure.
First customers	Delegated sales, paid growth, enterprise process, broad customer segments.
Fundraising	Valuation theater before milestone clarity and evidence.
Hiring	Culture slogans before role clarity, scorecard, onboarding, and management time.
Scaling	More spend before retention, unit economics, onboarding, support, and cash discipline.
Survival	Hopeful growth projects before cash, options, stakeholder communication, and decision windows.

Anti-goals are liberating. They protect founder attention from work that feels mature but is premature.

Stage review script

Use this script in a founder meeting:

What stage are we in based on evidence, not aspiration?
What proof gate have we passed?
What proof gate have we not passed?
Which current work belongs to a later stage?
Which earlier-stage work are we avoiding?
What is the single action this week that would improve the evidence?

The answer should fit on one page. If it needs a long explanation, the stage is probably unclear.

The evidence bar by stage

Use this table to decide whether you are ready to move forward or whether you need another learning cycle.

Stage	Weak evidence	Stronger evidence
Idea	Friends, trends, founder excitement, online comments.	Reachable prospects, repeated pain, current workaround, strong founder-market fit.
Discovery	”This sounds useful” conversations.	Recent stories, artifacts, current spend, urgency, buyer/user map.
Validation	Signups, likes, vague LOIs, free trials.	Paid pilots, deposits, data access, decision meetings, repeated usage, credible referrals.
MVP	Completed feature list.	First value reached, learning captured, manual work measured, scope reduced.
First customers	One-off custom deals.	Similar customers buying or piloting through a similar motion.
PMF search	Revenue from many unrelated customers.	Retention, expansion, referrals, sales pull, support load improving in one segment.
Growth	More traffic or leads.	Repeatable channel, clear unit economics, onboarding capacity, retention by segment.
Scale	More headcount and meetings.	Leaders own outcomes, metrics are trusted, cash is controlled, customers remain healthy.
Survival	Hope, one pending deal, or investor optimism.	Written options, cash forecast, stakeholder plan, hard decision date.

If your evidence is weak, read earlier-stage chapters. This is not going backward. It is rebuilding the floor before adding another floor.

30/60/90-day reading and doing cycle

Do not try to read the whole book like a course. Use it to run the company.

Timeframe	Founder work	Book use	Output
First 30 days	Diagnose current stage, customer, product, cash, and founder constraints.	Read the stage route, run one playbook, fill one template.	One-page diagnosis and one evidence sprint.
Days 31-60	Act on the biggest uncertainty.	Read only chapters tied to the decision.	Customer calls, sales tests, product changes, pricing test, hiring scorecard, or cash plan.
Days 61-90	Turn learning into a decision.	Use templates to write the decision and next operating rhythm.	Continue, narrow, pivot, hire, raise, cut burn, or double down.

The goal is not completion. The goal is better decisions. Reading without changing behavior is entertainment.

How much to read before acting

Founders often use reading as a socially acceptable way to delay uncomfortable work. Use this rule:

Situation	Read	Then act
You are unsure who the customer is	One idea chapter and one discovery chapter.	Make a prospect list and book interviews.
You are unsure what to build	MVP and product discovery.	Write the riskiest assumption and cut scope.
Sales calls are weak	Founder-led sales and discovery calls.	Run five real calls using notes and next steps.
Fundraising feels confusing	Funding paths and investor readiness.	Write the milestone and investor memo before deck polish.
Team is overloaded	Founder operating system and early hiring.	Write the bottleneck and role scorecard.
Cash is stressful	Runway and burn, finance templates, survival pages.	Build a 13-week cash view.

Read enough to improve the next action. Then do the action.

Team reading protocol

When a chapter is relevant to the whole team, do not assign it as passive homework. Turn it into a working session.

Step	How to run it
1	Pick one chapter tied to a real decision.
2	Ask each person to mark one sentence they agree with and one they disagree with.
3	Spend 10 minutes listing current evidence.
4	Spend 10 minutes listing missing evidence.
5	Decide one change to make this week.
6	Assign owner, date, and success signal.

This keeps the book from becoming advice everyone nods at and nobody operationalizes.