Write Your Own Operating Manual as a Solo Operator

Write down how you operate. Not for a team you do not have, but for the two things that actually run your portfolio when you are not paying attention: the AI agents you delegate to, and the version of you that shows up tired next Tuesday. A personal operating manual is the document that turns your judgment into rules something else can apply. Without it, every decision routes back through your live attention, and live attention is the one resource that does not scale.

I run around twenty companies alone. The reason I can is not that I hold twenty companies in my head. It is that I have externalized most of my defaults into rules, so the system already knows what I would decide in the common cases.

Why a solo operator needs a manual most

It sounds backwards. Operating manuals are for onboarding employees, and you have none. But that is exactly why you need one more, not less. In a company, institutional knowledge lives across many heads. In a solo portfolio, it all lives in one head, which means it is a single point of failure and it is completely invisible until you try to hand something off.

The moment you delegate anything to an AI agent, the gap shows. The agent needs to know your defaults: what you approve automatically, what you never approve, how you want customers spoken to, where the line is. If that lives only in your instinct, you re-explain it every session, and the delegation never really saves you anything. Written down once, it becomes context the agent can carry.

What goes in your operating manual?

Keep it to the things you actually decide the same way every time. Four sections cover most of it.

Defaults. Your standing answers to recurring situations. Inbound opportunity, default no. New infrastructure, use the standard stack. New content, brand voice rules apply. These are the same rules that cut decision fatigue, written where a machine can read them.

Guardrails. What must never happen without you: sending money, signing, publishing public claims, deleting data. This is the boundary that makes broad delegation safe, and it needs to be explicit, not assumed.

Voice and taste. How your companies sound. The specifics that make output feel like you wrote it and not a generic model. This is the part you keep closest, and writing it down is how you get leverage on it without lowering the bar.

Cadence. Your weekly and daily rhythm: when you review, when you decide, when you build. The structure that runs the portfolio regardless of mood. Mine is built around a weekly review across twenty companies, and it belongs in the manual so it survives a bad week.

How the manual powers AI delegation

This is where the document earns its keep. A written operating manual is context you feed straight into your agents. Instead of prompting an agent from scratch every time, you hand it the relevant section, and it operates by your rules by default.

The difference is large. An agent working without your manual makes reasonable-sounding decisions that are not yours, and you catch the drift only when you review. An agent working with your defaults and guardrails makes your decisions at volume, and you review exceptions. That is the gap between delegation that creates cleanup work and delegation that removes it. Platforms like Girard AI run far better when they are pointed at explicit rules than at your hope that they guess right.

Treat it as living, not carved

Your manual is wrong the day you write it, in small ways, and that is fine. The point is to make it correctable. Every time you catch yourself re-deciding something you already decided, or correcting an agent for the same thing twice, that is a missing or wrong rule. Update it.

Over time the manual becomes the real asset. It is the accumulated, externalized version of how you run things, and it is what lets you add a venture without adding proportional load, because the new venture inherits the same defaults, guardrails, and voice. That inheritance is the whole trick behind running many companies as one operator, and I made the broader case in the operator's stack. The stack is the infrastructure. The manual is the judgment. Write both down, and the system runs whether you are sharp that day or not.