What Entrepreneurs Can Learn from Too Good to Leave, Too Bad to Stay
Priya sat in her car outside the co-working space, laptop open, invoice unsent. She'd built her business through eighteen months of no revenue while her partner covered the bills, and lately she couldn't tell if the tightness in her chest was about the business or about him. Late nights felt like evidence for leaving; quiet Sundays felt like evidence for staying. She kept telling her sister things were "fine, I guess." Tonight, instead of opening the laptop, she wrote down the real question she'd been avoiding: not "are we fine," but what had actually changed since the business started.
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
Naming the real strain behind "I don't know"
Vague dissatisfaction is a founder's occupational hazard, and it shows up at home too. Instead of asking "should I stay," name the specific pattern: resentment over your hours, a slow drift into not telling each other what's happening, a broken trust never repaired, or simply wanting different lives now. Each needs a different response, and none get truer by staying vague. Treat this like a stalled deal: find the actual blocker before proposing a fix, since solving the wrong problem burns a relationship the same way it burns a quarter.
Founders sometimes mistake business exhaustion for relationship exhaustion and blame the wrong source for months.
Write one sentence naming the specific pattern behind your doubt, separate from any sentence about money or workload.
Testing the relationship against evidence, not this week's mood
You wouldn't greenlight a product from one user's bad day, so don't judge years of partnership by this week's argument. Look at real signals over real time: does effort flow both directions, does your partner ask about the business with curiosity or resigned tolerance, has anyone actually tried to change the thing that hurts. Founders are disciplined about pattern recognition in metrics; apply that discipline here instead of trusting whichever story today's stress hands you.
A founder mid-fundraise can mistake temporary unavailability for permanent disconnection.
Track one concrete signal, like follow-through on a stated need, across the next four weeks the way you'd track a KPI.
Sorting a fixable strain from a real mismatch
Some strain is a scaling problem: two people who love each other haven't built systems for founder hours yet, and real effort closes that gap. Other strain resembles a market mismatch: two decent people who want structurally different lives, where effort doesn't change the fundamentals. Neither situation makes either person wrong. The test isn't how painful it feels now but whether named efforts have moved anything over a defined stretch, the way you'd judge a struggling feature worth another sprint or a quiet retirement.
Sunk cost thinking keeps founders funding a mismatch because quitting feels like a second failure.
Name one concrete change each of you would make, then check back in eight weeks for real evidence.
Deciding and building forward, whichever way it goes
Once the pattern is named and tested, make the call and treat it as settled for now, the way you'd ship a decision after a strategy review rather than relitigate it weekly. Staying well means one real structural change on the calendar, not just relief the conversation is over. Leaving well means giving the transition the same planning rigor as a pivot, letting the urge to prove yourself again wait until your footing is steadier.
Naming the real question can clash with testing patterns over time: founders want an answer today, but honest signals often surface only across a full business cycle. Rushing the diagnosis to match your urgency can produce a false answer that collapses under the next hard quarter. Hold both by setting a defined window, a quarter is reasonable, while writing down your working hypothesis now so the waiting has direction instead of becoming avoidance.
Name one thing, honestly
- What specific pattern, not mood, has been driving your uncertainty? - If the business vanished tomorrow, what would you still be unsure about? - What single piece of evidence would actually change your mind?
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
Name one concrete change each of you would make, then check back in eight weeks for real evidence.