Quit or push

It breaks at 3am. The struggle produces a state: sleepless, catastrophizing, everything gray. Decisions made inside that state are made by the state, not by you. Horowitz's rule, and this page's first law: never decide in the 3am version of yourself. The call gets made cold, on a chosen date, by a rested decider, or it isn't a call.

And it breaks by staying one question. "Should I quit" sounds like a single decision. It's three decisions wearing one sentence, and they have different answers, usually on the same day.

1. Check the state before the question. Are you sleeping? Is this the week after the worst week? If yes: forced delay. Two weeks, sleep and movement mandatory, no irreversible conversations. The feeling is real and it will still be there in two weeks; the decision deserves a functioning decider.

One thing overrides the delay: an actual health event. Justin Welsh's stop-condition is the documented standard here. A panic attack on the highway that ends in a 911 call is data, not weakness. He read it as data, and look carefully at what he actually quit: the SVP job at PatientPop. The vehicle. He kept the game, rebuilt as a solopreneur on his own clock, and passed $10M cumulative revenue by his own accounting. The body voted; he counted the vote and changed vehicles. That's the pattern to hold onto: a 911-grade signal quits the pace immediately, and everything else gets decided later, cold.

2. Split the call three ways. Quitting the mission, quitting the vehicle, and quitting the pace are different calls:

• The mission: do you still want the destination at all, the ownership, the building, the game itself? This is the rarest true quit.
• The vehicle: this company, this model, this role. Vehicles are replaceable, and swapping one is pivot territory, with clean hands.
• The pace: the hours, the load, the solo weight. Quitting the pace looks like an ops hire, ended retainers, a calmer structure, a smaller goal held longer.

Most "should I quit" is vehicle or pace wearing mission language. Answer the smallest honest version first, because quitting the whole game when the honest answer was an ops hire is the most expensive misdiagnosis in this book.

3. Give health its veto. Price every currency like any other call, then apply this call's special rule: the health currency holds veto power, because it's the one currency where the worst case is uninsurable. Money reverses. Reputation rebuilds. Identity re-forms, slowly, but it re-forms. A cardiac event doesn't negotiate. If pushing on crosses the health ruin line, the pace quits today, whatever else stays.

4. Move the decision to a cold moment. Annie Duke's finding from the poker record: quitting on time usually feels like quitting too early. Sit with that sentence, because it means the feeling of prematurity is not evidence against quitting; it may be what on time feels like. So take the decision out of hot moments entirely. Write kill criteria while you're cold: a number and a date. "If MRR is under X on June 1, I wind it down." When the date arrives you're reading a gauge, not relitigating a feeling at whatever temperature the week happens to be.

5. Break ties against the status quo. If you've done all of it and you're still genuinely stuck, Naval's tie-break: when you truly can't decide, the answer to "keep everything exactly as it is" is no. Ambivalence that survives a full workup is information. Something changes: pace, vehicle, or mission. Pick the smallest change that's honest, and date it.

• Deciding at 3am, or in the week after the worst week. The state isn't you.
• The recurring Tuesday quit fantasy treated as venting. If it recurs, run the split. Fantasies with a schedule are data.
• Identity doing the deciding. "Who am I without this" is a real question, and it deserves a real answer, but it doesn't get to keep you sick while you avoid asking it.
• Comparing your inside to someone else's outside. The struggle is universal and mostly unposted.
• Quitting the whole game when the honest answer was an ops hire.
• Renegotiating the tripwire the week it fires. That's the hot state overruling the cold one, which is backwards, and it converts your kill criteria from instrument to decoration.

Founder, four years into a services-heavy SaaS. $45k MRR, flat. Opens with "I think I'm done." State check: four hours of sleep for two weeks, and an ER visit last month for chest pain that turned out to be panic. That's a 911-grade signal, so the pace quits immediately: two retainers ended that week, a contractor absorbs delivery, and the big decision defers 14 days with sleep mandatory. Cold again, the split runs. Mission: he still wants to own his time and build products. Alive. Vehicle: the services arm is what he dreads; the product side he'd work on for free. Pace: already amputated. So it was never mission. Kill criteria, written cold: productize onboarding, exit the last retainer by March 1, and if product MRR is under $30k by September 1, sell or wind down. Memo written, wire set.

Eight months later: $38k product MRR, sleeping, September wire quiet. What he quit was the pace and the worst half of the vehicle. The game stayed. That's what most true answers to this question look like: smaller than the question felt.