What Entrepreneurs Can Learn from Big Friendship
Building a company tends to swallow every spare hour, and the friendships that come with no deadline and no invoice are often the first thing quietly set aside. Big Friendship argues that a close, long-term friendship deserves the same deliberate investment as any other major relationship in your life, not whatever attention is left over once the business is fed. For founders, that means treating friendship as infrastructure worth maintaining on purpose, not a reward that arrives once the company stabilizes. The strain of divergent schedules, incomes, and risk between founders and the friends who live outside that world makes the book's ideas about asymmetry and repair especially useful.
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
Making room for friendship amid the founder grind
A founder cancels dinner with a close friend for eight months running during a fundraising push, telling himself each time that this is temporary, until the friend simply stops calling to reschedule.
Block one recurring, protected slot on the calendar for a specific friend, and treat any request to move it with the same reluctance you would apply to moving a board meeting.
When success and struggle pull two lives apart
After one friend's company succeeds and the other's quietly folds, both people avoid the subject, one out of guilt and the other out of pride, and the friendship goes quiet rather than through one uncomfortable conversation.
Name the gap plainly in a single conversation, and ask directly what would make spending time together feel comfortable for both people now, rather than guessing.
Repairing what the hustle interrupted
A founder snaps at a close friend during a brutal launch week, then lets months of silence stand in for an apology that neither person ever actually offers.
Write a specific message naming what happened and what it likely cost the other person, without folding it into an explanation of how busy the week was.
Friendship as a choice you keep making, not a founding story
A founding story can make a friendship feel automatically permanent, as though shared early struggle guarantees the bond holds no matter what changes later. It does not. The founder who keeps a friendship through an acquisition, a failure, or a slow pivot into an unrelated career is the one who keeps choosing that person, season after season, rather than coasting on how things used to be. Treating friendship as an ongoing decision, not a settled fact from year one, is what makes the earlier effort worth sustaining at all.
For a founder, the instinct is to solve friendship strain the way you would solve a product problem, by throwing more time or a bigger gesture at it. Resist that instinct. If a friendship carries both an unresolved asymmetry, like a growing income gap, and an unrepaired rupture, like a canceled trip that never got discussed, address the rupture first in a short, direct conversation before proposing a big reunion trip or a new standing call. Piling fresh investment onto an unaddressed hurt tends to read as managing the relationship rather than actually repairing it.
Name one thing, honestly
- Which friendship have you been treating as something that will simply keep until the company settles down, and is that actually true? - Is there a financial or lifestyle gap with a friend that you have been managing mostly by avoiding certain topics or plans? - What is one conversation about a strained or ruptured friendship you have been postponing in favor of work that felt more urgent?
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
Write a specific message naming what happened and what it likely cost the other person, without folding it into an explanation of how busy the week was.