Cadence Beats Hours: Scheduling a Solo Portfolio

The person who runs twenty companies alone does not win on hours. There are not enough of them, and burning more just moves the collapse forward a few weeks. You win on cadence: a fixed rhythm that touches every venture on a schedule, so nothing depends on you feeling motivated on a given morning. Motivation is a bad input. Cadence is a reliable one.

Hours are a resource you deplete. Cadence is a machine you build once and then feed. That difference is the entire case for how I schedule a solo portfolio.

Why hours are the wrong unit

Measuring a solo operation in hours worked is how you end up doing the wrong twelve hours. Effort feels like progress and often is not. You can spend a full day heads-down and touch one company while the other nineteen quietly drift, and the day will still feel productive because you were tired at the end.

Tired is not an outcome. The unit that matters is whether each venture got the attention its stage requires, on time, this week. A young venture needs a heavy weekly push. A stable one needs a light check. When you schedule by hours you give the loudest company all of them. When you schedule by cadence you give each company the dose it actually needs, which I broke down in how to run a portfolio of companies solo.

Set a cadence per venture, not per task

The core move is assigning each company a touch frequency and holding it. Some ventures get a real block every week. Some get a checkpoint every two weeks. A few dormant ones get a monthly look to confirm nothing is on fire. The frequency is a decision I make deliberately, not a reaction to whoever emailed last.

This is what keeps a solo portfolio from becoming pure reaction. Without a set cadence, urgency decides your calendar, and urgency is almost never the same as importance. The venture that is quietly compounding never sends an urgent email, so it gets starved by the one that does. A fixed cadence protects the quiet compounders, and those are usually the ones worth the most.

Batch by layer to kill switching cost

Cadence works best when I batch across companies by the kind of work instead of bouncing between companies by the clock. A content morning is content for several ventures back to back. A deploy afternoon is shipping across whatever is ready. A review block is every open thread in one pass.

The reason is switching cost. Moving between companies is cheap when the work is the same shape, because the tools and the headspace stay loaded. Moving between kinds of work is where the real tax lives. Batching by layer means I pay the setup cost once and reuse it across the portfolio, which is only possible because the ventures share one governed foundation. Shared plumbing is what lets a content block or a deploy block span many companies at once.

Protect the cadence from the emergency

The hardest part is not building the rhythm. It is defending it when something is on fire. Every real emergency is an argument to abandon the schedule, and if you abandon it every time, you do not have a schedule, you have a to-do list that lies about being one.

So I hold the cadence through most fires. A genuine outage jumps the queue, of course. But "this feels urgent" is not an outage, and most things that feel urgent are just recent. I let them wait for their scheduled block. The portfolio survives a two-day delay on almost everything. It does not survive me abandoning the system that keeps twenty companies from colliding.

What cadence actually buys

The payoff is predictability, for the ventures and for me. Every company knows when its turn comes, so nothing rots waiting for attention it will never randomly receive. And I get to stop carrying the anxious sense that I am forgetting something, because the rhythm already accounts for all of it.

That calm is not a luxury. It is what lets one person hold this without the quality sliding. Grinding harder scales for a month. Cadence scales for years, which is the timescale a portfolio is actually built on. You can see the ventures the rhythm holds together at Girard Media, and the automation side of the cadence at Girard AI.