High Growth Handbook
Elad Gil's reference for the specific problems of a technology company scaling from roughly fifty to several thousand people — assembled from his own operating experience and long interviews with founders and executives who have done it.
- First published
- 2018
- Publisher
- Audible
- Pages
- 349
- Shelf
- Business
- Level
- Core
- ISBN-13
- 9781732265103
Record checked against
Only one source carried a publication date for this work, so the year is uncorroborated.
Catalogue note
- Reads as
- PracticalWritten to be applied, not only understood.
- Level
- Core / BuildingAssumes general familiarity with the subject.
- Approach
- Practical
- Written for
- Founders and operators, Readers with some grounding
Saved in this browser only — no account, nothing sent anywhere. My library
Read this if
- You are starting or growing a company and want the unglamorous parts.
- You are responsible for other people's work as well as your own.
- You want something to apply, not only something to think about.
- You know roughly how the subject works and want the fuller account.
The scope, and why it is narrow
Gil deliberately skips the founding and product-market-fit stages, which are well covered elsewhere, and addresses only the hypergrowth phase — the period when a company that has found something is trying not to break while multiplying.
The problems of that phase are specific: the organisation restructures every few months, the founder's job changes fundamentally, and decisions made under pressure become permanent.
The book starts where most startup writing ends: the thing works, and now it is breaking as it grows.
Devmark’s reading — not a quotation from the book
The chief executive's changing job
His opening argument is that the role changes qualitatively at least three times during hypergrowth, and that founders usually notice one transition late.
The specific shifts he identifies are from doing, to managing doers, to managing managers, to setting context for an organisation you cannot personally observe — with the last requiring written communication and explicit decision-making frameworks that were unnecessary before.
Hiring executives
The most practically detailed chapter. Gil is direct about what goes wrong: hiring for pedigree rather than for the stage, hiring someone who has only operated at much larger scale, and hiring a functional leader before the function has a shape.
His scorecard approach — define the outcomes and the stage-specific requirements first, then assess against them — is conventional; his insistence on interviewing for the next eighteen months rather than the next five years is not, and it is the more useful instruction.
Managing the board
Unusually candid material on a topic most books avoid. Gil covers board composition as the company matures, the difference between investors who are useful at different stages, and the mechanics of removing a board member.
His framing is that the board is a resource to be managed actively rather than a body to be reported to, and that founders systematically under-use it while over-preparing for it.
Organisational structure and reorganisation
Gil treats reorganisation as a routine tool rather than an emergency measure, arguing that a company growing at hypergrowth rates will outgrow its structure every six to twelve months regardless of how well the structure was designed.
His practical guidance — announce quickly, communicate the reasoning, do not leak it slowly — is aimed at limiting the productivity cost, which he treats as unavoidable rather than preventable.
At this growth rate the structure will be wrong in six months no matter how well you design it. Plan to redo it.
Devmark’s reading — not a quotation from the book
Late-stage financing and M&A
Chapters on raising later rounds, secondary sales, and acquiring companies — the last written from the acquirer's side, which is rarer than the founder's-side account.
His acquisition guidance is notably unromantic: most acquisitions are talent or product acceleration, the integration is the hard part, and the decision should be made on whether you would build the thing anyway.
The interview format
Roughly half the book is transcribed conversations with operators — founders, executives, investors — rather than Gil's own prose.
This is the book's strength and its weakness. The interviews carry specific, hard-won detail that no framework would capture, and they are also unedited, repetitive in places, and occasionally contradict each other without the contradiction being resolved.
Where it is limited
It is narrowly about venture-backed technology companies in a particular funding environment, and much of the advice presumes access to capital, a liquid senior talent market and the option to grow headcount quickly.
Written during a long expansionary period, some of its assumptions about capital availability and hiring speed read differently now, and the book does not contemplate a company that must scale without those conditions.
Who it is for
Genuinely useful to someone currently inside the problem it describes, and close to useless otherwise. It is a reference to be consulted at the point of a specific decision — hiring a first VP, restructuring, handling a board issue — rather than read straight through.
Read cover to cover it is disjointed. Used as a lookup when a specific problem arrives, it is among the most practical books in this shelf.
What to take from it
The observation that the chief executive's job changes discontinuously, and that the transitions are noticed late, is the most portable idea.
Then the hiring instruction: interview for the next eighteen months, not for an imagined end state, because the company the candidate would be perfect for does not exist yet and may never.
What to take away
- 01The role changes discontinuouslyDoing, managing doers, managing managers, setting context — and founders notice each shift late.
- 02Hire for the next eighteen monthsThe company a big-company executive would be perfect for does not exist yet and may not.
- 03Reorganisation is routine hereAt hypergrowth the structure expires every six to twelve months however well it was designed.
- 04Manage the board, do not report to itFounders systematically over-prepare for board meetings and under-use the people in them.
- 05Use it as a lookupIt is a reference for the moment a specific decision arrives, not a book to read through.
