How to Catch Burnout Early as a Solo Operator

By the time burnout feels like burnout, you are already two weeks late. So I stopped waiting for the feeling. I watch the operational symptoms instead. When I run twenty companies alone, burnout does not announce itself as exhaustion. It shows up first as small, boring failures in how I work. My inbox backs up. I stop closing loops. I reread the same email three times. Those signals arrive well before the crash, and they are easy to measure if you know to look.

What burnout looks like before you feel it

The first symptom is always latency. Not mine emotionally, my response latency. When I am healthy, a thread gets an answer inside a day. When I am sliding toward burnout, threads sit. Two days. Four days. I tell myself I am busy. I am not busy. I am avoiding decisions because deciding costs more energy than I have.

The second symptom is rework. I start redoing things I already finished because I cannot trust that I did them right the first time. That distrust is the tell. A rested operator ships and moves on. A depleted one circles back.

The third is a shrinking radius of attention. I stop thinking about any company more than one week out. Everything becomes reactive. If you have read which venture gets attention today, you know I run on deliberate rotation. When burnout hits, that rotation collapses into whatever is on fire. That collapse is the alarm.

The three metrics I actually track

I do not journal my feelings. I track three numbers, because numbers do not lie to me the way I lie to myself.

Open threads older than 48 hours. If that count climbs above ten across the portfolio, something is wrong with me, not with the work. The work did not get harder. My capacity dropped.

Days since my last deep-work block. I protect one block a day, the way I described in protect one deep work block a day. When I have not had one in four days, I am running on interruption fuel. That never lasts.

Decisions deferred. I keep a short list of decisions I have punted. When it grows faster than I clear it, I am not managing a portfolio anymore. I am dodging it.

Why solo burnout is different

An employee who burns out has a manager, a team, and slack in the system. Nobody catches me. The whole point of running lean is that there is no bench. That is the trade, and I took it on purpose, but it means I am the single point of failure. I wrote about that risk in single point of failure solo portfolio. Burnout is how that failure actually arrives. Not a dramatic collapse. A slow degradation where I keep showing up and doing worse work until something breaks.

The other difference is that I cannot delegate my way out mid-crash. Hiring takes weeks. Onboarding takes longer. The tools that keep the load survivable have to already be in place. I lean hard on automation and agents inside my stack at girardai.com precisely so that a bad week does not become a bad quarter. The agents keep running the routine work while I recover.

What I do when the symptoms appear

I cut scope before I cut sleep. The instinct is to grind harder. That is exactly backwards. When the three numbers move against me, I declare a maintenance week. Every company drops to keep-the-lights-on mode. No new features. No new bets. I clear the deferred decisions, answer the stale threads, and get one real day off.

Then I ask which company caused the overload. Usually one venture is eating a disproportionate share of my attention, and it is not paying it back. That company either gets a fix, gets simplified, or gets a hard conversation about whether it stays. I covered that call in when to kill a portfolio company.

The point is that burnout is not a character flaw and it is not inevitable. It is a lagging indicator with leading signals. Watch the latency, the rework, and the shrinking horizon. Track the three numbers. When they move, act before the feeling arrives. Running twenty companies solo is sustainable, but only if you treat your own capacity as the scarcest resource in the portfolio, because it is.