Not hustle. Compounding.
Leadership systems, operating rhythm, and the tools underneath them
Most leadership content treats effort as linear: work harder, get more done. What actually scales is different. Decisions and systems that keep paying off long after the day they were made, so next month's output doesn't cost the same hours as this month's did.
This pillar has two layers on purpose. The why is the system: leadership decisions, delegation, what to build once instead of repeating. The how is tactical: the tools and operating rhythm that make those systems survive a normal week. Same pillar, so the two never read like separate blogs about the same thing.
What this pillar covers
Four threads, one argument: compounding beats volume
Leadership Systems
Delegation, decisions made once instead of weekly, and org design that takes the founder out of the loop rather than making them faster inside it.
Operating Rhythm
The actual cadence: what gets reviewed, when, and by whom. Which loops run weekly, which run monthly, and which exist only to catch the things nobody owns.
Tools & Stack
The agentic and AI tooling I actually run day to day, including the fleet of always-on agents doing routine work — plus what I tried and dropped.
Company + Body
Running a company and an endurance build on the same calendar. Periodization, deload weeks, and treating attention as a budget rather than a virtue.
Latest
Written from how the work actually runs, not how it should
The Delegation Ledger: What I Stopped Doing This Year
A first-person inventory of work I moved off my own plate — to people, to automation, to AI agents. What each handoff cost up front, and which ones quietly came back.
Read it → Tools & StackAn Executive's Week on an AI Agent Fleet
What day-to-day operations look like when a large share of routine work runs on always-on agents: what gets delegated, what stays human, and the supervision rhythm that keeps it honest.
Read it → Company + BodyTraining Load as a Management System
Deload weeks, one hard focus per block, and measuring load instead of output. What periodization taught me about running a company, mapped onto an executive calendar.
Read it → Leadership SystemsThe 10 Most Popular Destinations for Virtual EAs
Where support talent actually gets sourced, and why the choice comes down to which hours the work has to happen in, not just cost.
Read it →Every other data-backed section on this site — the commit lanes, the training load, the weight and body-fat charts — runs on real logged data, not narrative. This pillar will work the same way once there's something real to show. Nothing here is backfilled or estimated. The chart goes live when the tracking does.
Building the same kind of system?
If you're trying to get a company to run without you in every loop, that's the work I do as a fractional CTO and AI strategy advisor.