Own practice · three businesses
A multi-brand agent operating system
Three businesses operated from one system, with brand separation enforced by architecture instead of by remembering.
Stack
- Claude Code
- MCP servers
- Custom Skills
- Scheduled agents
- Persistent memory
- 3
- businesses I run on the systems I design
The problem
Running three businesses from a single desk, with content, client deliverables, task triage and reporting all competing for the same hours.
Context switching was the real cost, not the work itself.
The approach
Built an agent operating system on Claude Code rather than buying another tool.
Custom Skills encode each repeatable deliverable with its own rules and brand voice, so the output is consistent regardless of when it runs.
An MCP integration manages the task boards for all three businesses with a single daily triage pass, fed by a universal capture inbox. Scheduled agents run the recurring reporting without being asked.
Persistent file-based memory keeps brand separation enforced, so one business’s voice and offers never leak into another’s deliverable.
The result
Three businesses operated from one system.
This is also the reference build behind the client work: the same patterns — skills for repeatable deliverables, MCP for the systems of record, scheduled runs for the recurring work — are what get implemented inside client operations.
You are not the test case.