Running Four Ventures on One Operating System
Project Summary
I run several companies at once, so I designed the operating layer that holds them together. Each venture gets its own workspace, inbox and task lists, and all of them roll up to one chief-of-staff process where AI triages, drafts and delegates, and I make the calls.
One workspace per venture
Instead of one giant workspace where every company's context bleeds together, each venture gets its own AI project with its own instructions, and a matching folder structure on my machine. Everything rolls up to a single chief-of-staff process, so I hold how the pieces coordinate, not every piece.
Lists by who does the work
Task lists are organized by executor, not by status: what's happening now in each venture, build requests, what we're waiting on, and a build list for the software. Software tasks get captured as tasks and then executed in Claude Code. It runs across four business accounts through one connector.
A standup that runs itself
Every weekday at 7 AM, a scheduled task triages four inboxes by urgency, drafts replies for real business and personal mail only, files the reports, and rolls it all into one brief alongside what's due that day.
Skills as reusable systems
Repeated work becomes a packaged skill: a production web stack setup across eight services, a seven-stage sales pipeline for a property management company, and a market scout for research and lead generation. Each one turns a process into something any session can run the same way twice.
More Examples
