The Single Point of Failure in a Solo Portfolio

The strongest argument against running twenty companies alone is simple: I am the single point of failure. If I am unavailable, the portfolio waits. If I am wrong about something foundational, I am wrong everywhere it reaches. A team has redundancy that I do not. This is the real objection, not a strawman, and I am not going to wave it away. What I can do is be honest about the actual shape of the risk, show what bounds it, and explain why I take the rest on purpose.

Most solo operators either ignore this risk or let it scare them into hiring prematurely. Both are wrong. The right move is to size it correctly, reduce what can be reduced, and accept what is left as the price of the structure.

Name the risk precisely

The single point of failure is really two different risks that get lumped together. The first is availability: if I am sick, offline, or gone, no one else can act. The second is judgment: because every venture runs on my decisions, a wrong foundational call propagates to all of them at once. These are different problems with different answers.

The availability risk is about time. The judgment risk is about correctness. Conflating them leads to bad fixes, like hiring a team to solve an availability problem when the team actually makes the judgment problem worse by diluting the standard, which I argued in why I don't hire a team. Size each one separately and the response gets sharper.

Written systems bound the availability risk

The availability risk is the more manageable one, and the tool against it is writing everything down. A portfolio held in my head fails the moment I am unavailable. A portfolio held in written systems degrades gracefully instead, because the state exists outside me.

Every open thread, every current state, every next action lives in writing, which is the entire point of the never drop a thread system. If I disappear for a week, the ventures do not lose their state. They pause with everything documented, ready to resume. That does not eliminate the availability risk, but it converts a catastrophe into a delay, and a delay is survivable where a catastrophe is not.

Automation absorbs the routine load

The second bound is that the routine operations do not actually require me minute to minute. Agents and code carry the operational middle, so a large share of each company keeps running whether or not I am at the desk. Support gets answered, monitoring keeps watching, scheduled work keeps shipping.

This shrinks the surface area where my absence matters. I am the single point of failure for judgment and design, not for the day-to-day execution, because the execution is handled by agents that run across the portfolio. The more of the routine that automation absorbs, the smaller the blast radius of me being gone. Tools like Girard AI are what let the operation keep breathing without my constant presence.

The judgment risk is the one I actually carry

The availability risk can be bounded. The judgment risk cannot, not really, and I am honest that it is the sharp edge of this structure. Because every venture inherits my decisions through the shared foundation, a wrong foundational call is wrong everywhere at once. The same leverage that lets one fix reach twenty companies lets one mistake reach them too.

I do not have a clever escape from this. What I have is the discipline to make foundational calls slowly and reversibly, and to govern the highest-stakes actions personally. The leverage cuts both ways and I accept that it does. The alternative, spreading judgment across a team, trades this concentrated risk for a diluted standard, and for a portfolio whose value is one consistent standard that is a worse trade, not a better one.

Why I accept what is left

After the bounding, a residual single-point-of-failure risk remains, and I take it on purpose because the thing it buys is worth more than the thing it costs. A portfolio whose entire value is one consistent standard is better held by one person who refuses to dilute it than by a team that gradually would. The concentration that creates the risk is the same concentration that creates the value.

That is the trade, stated plainly. If your priority is resilience above all, a solo portfolio is the wrong structure and you should build a team. If your priority is a standard held uniformly across every venture, the single point of failure is the cost of getting it, and it is a cost I pay with open eyes. You can see what that bet holds together at Girard Media.