Solo Operator vs Small Team: Which Runs a Portfolio
Solo operator vs small team for running a portfolio of companies: a real comparison of speed, consistency, coordination cost, and where each structure actually wins.
If you are going to run a portfolio of companies, you face one structural choice early: do it as a solo operator, or build a small team. Most people assume the team wins because more hands means more output. For a portfolio whose value is one consistent standard, that assumption is wrong. The team wins on raw throughput and loses on the thing that actually makes the portfolio worth anything. This is a real comparison, not a solo victory lap, because the answer genuinely depends on what you are building.
Here is how the two structures compare on the dimensions that decide it.
Speed: the team wins any single week
Start with the obvious. On any given week, a small team out-produces one person. Five people can push five ventures forward at once where I can push two or three. If the metric is how much moves this week, the team wins and it is not close.
But single-week throughput is the wrong metric for a portfolio, which is built on a timescale of years, not weeks. The question is not who moves fastest in a sprint. It is who holds a coherent standard across twenty companies over a long time. The team's speed advantage is real and also mostly irrelevant to the thing that determines whether the portfolio is valuable. I make the fuller case in why solo beats a team for this.
Consistency: the solo operator wins decisively
This is where it flips. The value of my portfolio is that every venture meets the same bar: the software does not lie, does not do damage, behaves the same way. That bar is a judgment call, and one person makes it the same way every time.
A team fractures the standard. Five people hold five slightly different definitions of good enough, and the effective standard becomes their average, which drifts down over time. Not through carelessness, just through the unavoidable variance of multiple humans exercising taste. For a portfolio where consistency is the product, that dilution is not a minor cost. It is the whole game lost. The solo operator wins consistency decisively, because consistency and a single decision-maker are the same thing.
Coordination cost: the solo operator wins
Every person you add creates communication overhead that grows faster than headcount. Two people, one link. Five people, ten links. Keeping everyone aligned is real work that produces nothing on its own, and it scales badly. Alone, that cost is zero: no standups, no handoffs, no context transfer.
This is why the team's speed advantage is smaller than it looks on paper. A chunk of the extra output gets eaten by the overhead of coordinating it. The solo operator spends none of it, which is part of how one person keeps pace at all. It only works because the ventures share a single foundation, so there is nothing to coordinate across companies in the first place.
Resilience: the team wins, and it is real
Here is the honest mark against solo. A team has redundancy. Someone is out, someone else covers. A solo operator is a single point of failure with no backup. If I am unavailable, the portfolio waits. If I am wrong about the foundation, I am wrong everywhere.
That is a genuine advantage for the team and I do not wave it away. It is the strongest argument against my structure. My answer is that the risk is bounded by written systems and automation rather than eliminated, and that I accept the exposure as the price of the consistency I get in return. But if resilience is your top priority, the team is the correct call and you should make it.
The verdict depends on what you are building
The comparison resolves cleanly once you name the goal. If the value is throughput and the work is genuinely parallel, build the team. If the value is one consistent standard held across many ventures, go solo, because a team dilutes exactly the thing that makes it valuable and a single operator does not.
For me the goal is the standard, so the choice is solo, and the resilience cost is one I take on purpose. Your goal might be different, and then your answer should be too. The mistake is not picking either structure. It is picking one without knowing which thing you are actually optimizing for. You can see what the solo bet produces at Girard Media and across the ventures at Girard AI.