What Happens When a Solo Operator Takes a Week Off

If your businesses fall apart the week you step away, you do not have businesses. You have twenty jobs. The vacation test is the cleanest audit a solo operator can run: leave for a week and see what breaks. Whatever collapses without you is a design flaw, a place where you never built a system and instead became the system. A portfolio that runs on your daily presence is not a portfolio. It is a very demanding form of employment you gave yourself.

I run around twenty companies. I can leave for a week, and the companies keep operating, because the parts that need to happen every day were built to happen without me deciding them in real time. That is not luck. It is the direct payoff of designing for absence on purpose.

Why the vacation test is worth running

You cannot see your dependencies while you are present, because your presence hides them. Every day you show up and quietly patch the gaps: you approve the thing, answer the customer, restart the process. The patching is invisible because it is constant, so you never notice how much of the operation is actually just you, plugged in, holding it together by hand.

Stepping away is the only way to make those dependencies visible. The week you leave, every gap you were silently filling reveals itself as something that breaks or stalls. That list of breakages is a map of your single points of failure, and it is far more honest than any plan, because it is the business telling you where it truly depends on you rather than where you think it does.

What should keep running without you?

The routine. Anything that must happen on a schedule and follows a rule should already be running on systems and agents, not on your live attention. Customer messages should get triaged and answered within your standards. Transactions should get categorized. Systems should be monitored, with alerts that escalate only real problems. Deploys, backups, and the boring machinery of twenty companies should not care whether you are at your desk.

If those need you daily, that is the fix list. The point of delegating decisions under guardrails, of writing down your defaults, of automating the volume, is precisely this: the operation continues because the rules continue. I run this on the same human-in-the-loop automation I use every day, just with a longer leash while I am gone. The agents keep deciding the routine by policy, and the exceptions queue for my return instead of forcing my presence.

What genuinely waits for you, and that is fine

Not everything should run without you, and pretending otherwise is its own mistake. Strategy, big irreversible decisions, the taste-level work, key relationships: these are supposed to pause. A week without you steering the strategy is not a failure. It is a week where the machine ran the routine and the judgment work waited, which is exactly right.

The skill is drawing that line before you leave. Everything reversible and rule-covered runs. Everything strategic and irreversible waits in a clearly bounded queue. This is the same division that lets me decide which venture gets attention when I am present: the routine is delegated, the judgment is mine. Stepping away just proves whether the division is real or whether you were secretly doing judgment work and routine work in the same undifferentiated blur all day.

How to build toward a portfolio that survives your absence

Treat every breakage from the test as a system to build, not a chore to resume. The week you get back, do not just clean up. Ask why each thing broke, and close that gap with a rule, an agent, or an automation, so it does not break next time. Over a few cycles, the list of things that fail without you shrinks toward zero for everything routine.

The prize is not just vacations, though those matter for lasting more than a few years at this. The prize is that a business which runs without your daily presence is a business you actually own rather than one that owns you, and it is a business you could eventually sell or hand off, because its operation lives in systems and not in your head. This is the deeper reason I keep my whole portfolio on infrastructure I control and run it on agents: ownership means the thing works when you are not touching it. Platforms like Girard AI exist to hold the routine while you are gone, so the week you step away becomes a test the business passes, not a crisis you rush home to end.