What Entrepreneurs Can Learn from The Course of Love
A founder spends months refining her startup's onboarding flow, treating every dip in signups as data, never as a verdict on the company. She runs the numbers, tries a new variant, and waits calmly for the next result, the same way she has for three years. At home, a tense dinner with her partner, a canceled plan, a short answer about money, lands very differently. It feels like a verdict, not something to iterate on. She lies awake replaying the evening, wondering if the friction means they picked the wrong life together, the way she'd never wonder if one bad week of metrics meant she'd picked the wrong business. Why does the same ordinary friction at home feel like proof something has already, quietly, failed?
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
Product-market fit doesn't mean the friction stops, and neither does a good relationship
Founders learn that finding product-market fit doesn't end the work; it changes what the work is. Yet many assume the opposite about relationships: that the right partner should end the friction. De Botton argues this popular myth, that romantic love sustains itself once you find the right person, turns ordinary disagreement into a false alarm. A founder who would never read a rough sprint as proof the company is broken can still read a rough month at home that way.
A partner's contempt or unkindness should never be waved off as ordinary friction to push through.
Name one recent friction point aloud as expected in a serious relationship, not evidence something is wrong.
Your co-founder or partner won't reach a final version, and shouldn't have to
Entrepreneurs know a co-founder relationship is never fully mapped; new information about a partner's judgment surfaces years in. De Botton argues the same of a spouse: a partner stays permanently somewhat unknown and disappoints you in small, ordinary ways, not because you chose badly but because full transparency between two people isn't possible. Founders who accept that ambiguity in a business partner can extend the same maturity home, dropping the search for someone who will finally stop mildly frustrating them.
Never tolerate a partner's persistent cruelty or dishonesty as simply unknowability.
Next time your partner does something puzzling, ask a genuine question instead of assuming why.
Treat a fight like a bug report, not a referendum on the whole relationship
Good founders know a customer complaint about a button is rarely about the button; it points to deeper confusion in the product. De Botton makes the same case for conflict: an argument about a forgotten errand is often really about feeling unseen, and complaints framed as accusations are a poor substitute for stating a need directly. Founders who investigate a ticket's root cause often stop at home, reacting to tone rather than the need beneath it.
If the pattern is contempt or blame with no willingness to name a need, the issue is unhealthy.
In your next disagreement, pause and ask what your partner actually needs, in one specific sentence.
A marriage needs the same iteration cycle you'd never skip in the business
No founder expects a company to run itself after launch; growth requires continuous iteration long after the excitement fades. De Botton frames love the same way, not a feeling that exists or doesn't, but an active skill built through patience and effort sustained over years. A founder who schedules retrospectives for the business but never a check-in with a partner applies a growth mindset everywhere except the relationship that needs it most.
These ideas can pull against each other. Accepting ordinary disappointment can excuse skipping a hard conversation a real complaint deserves, especially for a founder used to moving past low-priority fires. Treating the relationship as a project to iterate on can also tip into over-optimizing a partner like a funnel. The discipline is knowing when friction is ordinary texture, and when it is a real need deserving direct attention.
Name one thing, honestly
- Where have you read normal friction as proof you chose the wrong partner? - What need have you expected your partner to guess instead of stating directly? - If your relationship got the attention you give your business, what would change this month?
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
In your next disagreement, pause and ask what your partner actually needs, in one specific sentence.