I used to read 50 books a year. Now I read maybe 12. But I read the right 12 differently.
That confession usually surprises people. Founders expect their coach to hand them a massive reading list — a stack of business books and biographies and "must-reads" that'll take eighteen months to get through. I did that for years. I'd finish a book on a Tuesday and start another on Wednesday. I treated reading like cardio: more reps, better results.
It didn't work that way. Most of what I read evaporated within weeks. I could reference book titles at dinner parties, but when a founder was sitting across from me in crisis — staring at a co-founder departure or a failed product launch or a body that wouldn't stop running hot — I wasn't reaching for the fifty books I'd speed-read. I was reaching for the same handful. Over and over.
So I stopped reading widely and started reading deeply. One book at a time. Pen in hand. A single question for each chapter: What changes in my practice if this idea is true?
The twelve books below aren't a "best of" list. They're the books that actually changed how I work with founders. I've organized them not by genre or popularity, but by the problem they solve — because that's how founders actually need information. You don't pick up a book because it's famous. You pick it up because something's broken and you need it fixed.
For Identity Work
Most founder problems that look like strategy problems are actually identity problems. The CEO who can't stop micromanaging. The founder who keeps hiring people just like themselves. The leader who built a $3M company but panics every time they try to cross $5M. These aren't tactical failures. They're identity architecture problems — the person's internal operating system can't run the software the next stage requires.
These three books gave me the vocabulary and the framework to work on that layer.
1. "The Body Keeps the Score" — Bessel van der Kolk
This book rewired how I think about founder behavior under stress. Van der Kolk's work on how trauma lives in the body — not just the mind — explained a pattern I kept seeing in coaching sessions: founders who understood exactly what they should do but physically couldn't do it. Their nervous systems were running old programs. The CEO who froze during board meetings wasn't lacking confidence. Her body was replaying a pattern from decades earlier.
What changed in my practice: I stopped treating every founder problem as a thinking problem. Now, when a client gets stuck, my first question isn't "What are you thinking?" It's "What are you feeling in your body right now?" That one shift has been worth more than any strategy framework I've ever learned.
Best for: Founders in the $3M-$10M range who've hit a ceiling they can't think their way past. If you've read all the business books and you're still stuck, the block probably isn't intellectual.
2. "Letting Go" — David Hawkins
Hawkins gives you a method for processing emotions that doesn't require years of therapy or a meditation retreat. The core technique is simple — feel the feeling without attaching a story to it, and let it pass through. Most founders have never been taught this. They either suppress emotions ("I don't have time to feel this") or get consumed by them ("Everything is falling apart"). Hawkins gives you the middle path.
What changed in my practice: I started teaching founders emotional processing as a performance skill, not a wellness activity. The speed at which a founder can process a bad quarter, a failed hire, or a personal setback directly correlates with how fast they recover and make good decisions again. This book gave me the protocol.
Best for: Founders carrying emotional weight from a rough stretch — a failed raise, a co-founder split, a product that didn't land. Read this before the weight calcifies into cynicism.
3. "Man's Search for Meaning" — Viktor Frankl
I know this book shows up on every list. I don't care. Frankl's core idea — that you can't control what happens to you but you can control the meaning you assign to it — is the single most important concept in founder psychology. I've watched it save companies. Not metaphorically. Actually save them.
What changed in my practice: When a founder comes to me after a catastrophic quarter, I don't start with damage control. I start with meaning. "What does this experience make possible that wasn't possible before?" That question — which comes directly from Frankl — has pulled founders out of spirals that were about to take down their teams, their marriages, and their health.
Best for: Every founder, at every stage. But especially anyone going through the specific hell of watching something they built start to break. Read the first half. Then read it again.
For Business Architecture
Identity work without business structure is therapy. Business structure without identity work is consulting. You need both. These three books shaped how I think about the actual machine of a company — and why so many founders accidentally build a machine that eats them alive.
4. "The E-Myth Revisited" — Michael Gerber
Gerber's distinction between working in your business and working on your business sounds obvious until you realize that 90% of the founders I coach are trapped in the first category. They're the best technician in the company. They can't leave for a week without everything degrading. They've built a job, not a business — and the job is killing them.
What changed in my practice: I started using the "franchise prototype" concept with every founder I work with. Even if they never plan to franchise, the exercise of asking "Could someone else run this without you?" reveals every structural weakness in the company. It's the fastest diagnostic I've found. If the answer is no, we know exactly where to start.
Best for: Founders between $1M and $5M who feel indispensable. That feeling isn't a badge of honor — it's a warning sign. This book explains why.
5. "Good to Great" — Jim Collins
Everyone remembers the hedgehog concept and the flywheel. Fine. Those are useful. But the part of Collins's work that changed my coaching was his description of Level 5 Leadership — the paradox of personal humility combined with fierce professional will. That's an identity shift, not a management technique. You can't "hack" your way into it. You have to actually become a different kind of person.
What changed in my practice: I started framing leadership development as identity development. When a founder says "I need to be a better leader," I don't give them a communication framework. I ask them who they'd need to become for that kind of leadership to feel natural. Collins showed me that great leadership isn't a skill you add. It's a version of yourself you grow into.
Best for: Founders who've proven they can build something but sense that the next stage requires a fundamentally different version of themselves. Usually the $5M-$15M transition.
6. "The Hard Thing About Hard Things" — Ben Horowitz
Every other business book tells you what to do when things go right. Horowitz wrote the book about what to do when things go wrong — and he wrote it with the kind of raw honesty that most business authors are too polished to attempt. The layoff chapters. The "going to war" chapters. The sections about making decisions with no good options. This is the book I hand to founders when they're in the thick of it.
What changed in my practice: I stopped pretending that founder life has clean answers. Horowitz gave me permission — and the language — to sit with a founder in genuine ambiguity and say "There's no good move here. Let's find the least bad one." That honesty builds more trust in ten minutes than six months of positive-thinking coaching.
Best for: Founders currently in crisis. Don't read this when things are good. Save it for the moment when everything's on fire and you need to hear from someone who's been through the same fire and came out the other side.
For Decision-Making
A founder's company is a reflection of their decisions. Not their vision. Not their hustle. Their decisions. The quality of thinking that goes into a hundred small choices per week is what separates the founder at $10M from the founder stuck at $2M. These three books shaped how I think about thinking itself.
7. "Thinking, Fast and Slow" — Daniel Kahneman
Kahneman's System 1 / System 2 framework — fast intuitive thinking versus slow deliberate thinking — is the most practically useful model of human cognition I've ever encountered. Most founders are running System 1 all day. They're making rapid, intuitive calls about hiring, product, pricing, and partnerships without ever slowing down to check whether their intuition is actually calibrated for the decision they're making.
What changed in my practice: I built a decision architecture protocol that sorts founder decisions into System 1 and System 2 categories. Small reversible choices? Go fast. Large irreversible ones — hiring a VP, choosing a market, pricing strategy? Force System 2. This one framework has probably saved my clients more money than any other single concept.
Best for: Founders making rapid decisions they later regret. If you've ever looked at a choice six months later and thought "What was I thinking?" — you weren't thinking. You were reacting. This book explains the difference.
8. "The Almanack of Naval Ravikant" — Eric Jorgenson
This isn't a traditional book. It's a compiled collection of Naval's thinking on wealth, judgment, and specific knowledge. But the density of useful ideas per page is higher than almost anything else I've read. Naval's framework on specific knowledge — the idea that your unique combination of skills, interests, and experience creates a form of knowledge that can't be trained and can't be competed away — became central to how I coach founders on positioning.
What changed in my practice: I started asking every founder: "What do you know that almost nobody else knows, because of the specific life you've lived?" That question — pulled directly from Naval's thinking — has helped dozens of founders find their actual competitive edge. Not the one on their pitch deck. The real one.
Best for: Founders who feel like they're competing in a crowded market. The market isn't as crowded as you think — you just haven't identified what makes your perspective irreplaceable yet.
9. "Antifragile" — Nassim Taleb
Taleb's central concept — that some systems don't just survive stress, they get stronger from it — fundamentally changed how I think about building companies. Most founders build fragile systems. They optimize for efficiency, which means any shock breaks them. Taleb argues you should build systems that benefit from disorder. Applied to a startup, this means designing your company so that market shifts, team changes, and unexpected challenges actually make you better.
What changed in my practice: I stopped helping founders build "resilient" companies and started helping them build antifragile ones. The difference is massive. Resilient means you survive the hit. Antifragile means the hit reveals an opportunity you wouldn't have seen otherwise. I now run every founder's business model through an antifragility audit: "If X goes wrong, does this company get weaker or stronger?"
Best for: Founders who've been through one serious disruption and want to make sure the next one doesn't just not kill them — it makes them dangerous.
A note on how to read these: Don't read all twelve. Pick the section that matches your current problem. Read one book from that section. Finish it. Write down the one idea that changes how you operate. Install that idea into your weekly practice. Then — and only then — pick up the next one. Reading without installation is entertainment. Reading with installation is growth.
For Performance & Recovery
This section is the one founders skip. They'll read every business and psychology book on this list, then treat their body like it's an afterthought. I used to do the same thing. Then I watched enough founders flame out — not from bad strategy, but from depleted biology — that I couldn't ignore this category anymore. Your body isn't separate from your business. It's the infrastructure your business runs on.
10. "Breath" — James Nestor
Nestor spent years investigating the science of how we breathe — and how badly most of us do it. The book is half science journalism, half personal experiment, and it's genuinely riveting. But the reason it changed my coaching is practical: breathwork is the single fastest tool I've found for shifting a founder's nervous system state. Faster than meditation. Faster than exercise. Faster than anything except pharmaceutical intervention.
What changed in my practice: I now start every coaching engagement with breathwork. Not as a warm-up. As a diagnostic. How a founder breathes under stress tells me more about their operating state than thirty minutes of conversation. Nestor's work gave me the science to back up what I was already seeing in practice.
Best for: Every founder, immediately. But especially founders who describe themselves as "always on" or who can't wind down at night. Your breathing pattern is probably locked in a stress configuration, and you've been running that way so long you think it's normal.
11. "Why We Sleep" — Matthew Walker
This book should be required reading for every human alive, but especially for founders — because founders are the worst sleepers on the planet, and they're proud of it. Walker's research is devastating. Sleep deprivation doesn't just make you tired. It destroys your decision-making, your emotional regulation, your creativity, and your ability to read other people accurately. In other words, it wrecks every skill a founder needs most.
What changed in my practice: I made sleep the first intervention in my recovery protocol, not the last. Before we touch strategy, before we talk about delegation or hiring — how are you sleeping? If the answer is "five or six hours," we're not doing anything else until that changes. I've watched founder performance improve 30-40% from sleep optimization alone, with zero changes to their business strategy.
Best for: Founders who wear sleep deprivation as a badge. You're not tough. You're impaired. Walker's data will make that impossible to deny.
12. "Atomic Habits" — James Clear
I saved this one for last because it ties the entire list together. Clear's framework — that lasting behavior change comes from identity shifts, not willpower — is the closest thing to a unifying theory of everything I teach. When a founder says "I want to exercise more," that's a goal. When a founder says "I'm the kind of person who moves their body every day," that's an identity shift. The second one sticks. The first one lasts until February.
What changed in my practice: Clear's identity-based model became the backbone of my 90-Day Protocol. Every habit we install, every system we build, every behavior change we attempt — it starts with the question "Who are you becoming?" not "What are you doing?" This book gave me the cleanest articulation of something I'd been circling around for years: that performance is an identity problem, and habits are how identity gets expressed in daily life.
Best for: Founders who've tried to change their behavior and failed. Not because they lack discipline — because they were trying to change actions without changing the identity those actions come from. Read this alongside "Letting Go" by Hawkins, and you'll have both the emotional processing tool and the habit installation system.
The Reading Rule I Give Every Founder
When a founder asks me "What should I read?" I don't give them this list. I ask them one question first: "What's the problem you're trying to solve right now?"
If they can't answer that clearly, we don't start with books. We start with clarity. Because a book without a question is just pages. A book that answers a specific, burning, personal question is a weapon.
Twelve books. Four categories. One rule: don't read more. Read right.
And if you're not sure which category your problem falls into — if you're not even sure what the problem is, just that something feels stuck — that's not a reading problem. That's a coaching conversation. The kind where someone who's seen your pattern before can name it in fifteen minutes flat.
That's what the 90-Day Protocol is built for. Not more information. Better installation.