What Entrepreneurs Can Learn from The Second Mountain
Priya sold her logistics startup for enough money that she never had to work again. She had spent nine years chasing the acquisition: the term sheet, the press release, the wire transfer. Six months later she was renovating a kitchen she didn't need, fielding calls from other founders asking how she "did it," and dreading the question, because she no longer had a clean answer. The exit was supposed to be the summit. Instead she'd reached the top of a hill and could suddenly see taller ones she hadn't noticed while climbing. What was the company actually supposed to have been for?
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
The exit that doesn't answer the question
Reaching a funding milestone, an acquisition, or simple profitability can produce the exact flatness David Brooks describes at the first mountain's summit: real accomplishment paired with a hollow aftertaste. The instinct is to fix that flatness with the next venture, larger and faster. Brooks's alternative is to treat the flatness as data: external validation was never going to be sufficient, because it was never the actual target. Noticing this before the next cap table lets a founder ask what the company was in service of, rather than restarting the loop at higher stakes.
Some founders genuinely love building for its own sake, and treating that satisfaction as suspect can curdle into self-doubt.
After any milestone, write one paragraph naming who was actually served, not just what metric moved.
Building something worth the sacrifice
A startup becomes a vocation rather than a vehicle when it's chosen because it addresses a problem the founder feels obligated to solve, not only because the market rewards it. Brooks's distinction between a job and a calling maps onto the difference between chasing category leadership and building because people genuinely need the thing. That reframe doesn't reduce ambition; it gives ambition a destination beyond the next valuation mark, which matters most in the slow years when only purpose keeps the team going.
Mission language can become a tool for extracting unpaid overtime from employees who don't share the founder's stakes.
Write one sentence answering "who is worse off if this fails" and test roadmap decisions against it.
The co-founder and team as the second mountain
Founders often treat their spouse, co-founders, and early team as inputs to the venture, not as relationships with their own claim on commitment. Brooks argues that depth comes from staying inside a relationship through hard seasons, not from optimizing for the easiest initial fit. A company's culture is a community in his sense, and it deepens the way a marriage does: people choosing to stay and repair rather than replace whenever friction appears.
Some founding partnerships are genuinely mismatched, and loyalty talk can trap people in relationships that should end.
Before every difficult co-founder conversation, ask what staying and repairing would require, not just whether replacing is easier.
A compass beyond the cap table
Founders need some framework larger than the business to judge decisions when profit and principle conflict, whether a faith tradition, a secular ethic, or a personally assembled set of commitments. David Brooks describes his own path through Christianity, but is explicit that many roads lead to the same grounded seriousness. What matters is having some anchor, religious or not, that outranks the term sheet when the two disagree.
Vocation and relational depth pull against each other constantly in startup life: the calling that justifies the company also justifies missing the anniversary dinner. Brooks doesn't resolve this tension so much as insist both sides are real and neither should be quietly sacrificed to the other indefinitely. A founder can hold both by treating relational commitments as fixed constraints the business is built around, not as flexible variables absorbing whatever time is left over.
Name one thing, honestly
- If the company disappeared tomorrow, what would you still owe the people around you? - Are you chasing the next milestone because it matters, or because the last one didn't satisfy? - What would it look like to protect one relationship as fiercely as the roadmap?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Before every difficult co-founder conversation, ask what staying and repairing would require, not just whether replacing is easier.