I have 19 AI agents working alongside me. Five of them are executives.
That sentence either sounds impressive or insane depending on where you sit. But here's the thing most people miss: building them taught me more about leadership than 15 years of managing humans.
Not because they replaced working with others. Because they forced me to get crystal clear on what each role actually needs to do.
What Most People Call an "AI Operating System" Is Actually Something Deeper
Most people would call what I built an AI operating system. I call it a cognitive architecture — and the distinction matters.
An operating system runs programs. A cognitive architecture designs how you think.
Most people's AI setup looks like this: ChatGPT in one tab, a writing tool in another, maybe a scheduling assistant somewhere else. None of them know about each other. None of them remember yesterday. Every conversation starts from zero.
That's not a system. That's a junk drawer.
A cognitive architecture has three things a junk drawer doesn't:
| Component | Junk Drawer | Cognitive Architecture |
|---|---|---|
| Memory | Every conversation starts fresh | Agents remember your priorities, projects, and patterns |
| Coordination | Tools don't talk to each other | Agents hand off context when work crosses boundaries |
| Values | No guardrails beyond the model's defaults | Your vision, mission, and values gate every decision |
According to a 2026 AIBarcelona.org analysis, "A moderately capable model embedded in a well-designed cognitive system can outperform a stronger model used as a standalone tool." That's exactly what I've experienced. The architecture matters more than any individual agent's capability.
Why One Consultant Built a Team of 19 AI Agents
I'm an operations and MarTech consultant with 15+ years of experience. I'm also not a developer. I don't write Python. I can't build a React app. I think programmatically, but I'm not shipping code.
So why 19 agents?
Because I have AuDHD — ADHD and autism together — and my brain cannot hold all the threads at once. It never could. I used to white-knuckle it and call that professionalism.
I started with one agent: a basic AI assistant. Summarize my inbox, check my calendar, list my tasks. It worked. Sort of. But every morning I'd open a new conversation and re-explain who I am, what I'm working on, what matters. I've started calling this the Stranger Loop — and it's where most people's AI experience quietly dies.
So I gave it persistent memory. An onboarding document it reads before every conversation — my projects, my priorities, my constraints, my values. That's when the assistant became a Chief of Staff. And that's when things started compounding.
One agent became three. Three became five. Five became nineteen — each with a defined role, specific instructions, and shared context. The system has been running in production daily for over three months.
The doing isn't the work anymore. The thinking is the work. Building this system forced me to think harder about how I actually work than anything else in my career.
AI Assistants vs. AI Agents: Why the Difference Matters
An AI assistant waits to be told what to do. An AI agent shows up with the briefing already prepared, the conflicts already flagged, the context already loaded.
The distinction isn't academic. It changes what's possible.
| Capability | AI Assistant | AI Agent |
|---|---|---|
| Initiation | You prompt it | It surfaces what matters before you ask |
| Context | Knows what you tell it right now | Knows your projects, values, and patterns across sessions |
| Judgment | Follows instructions literally | Pushes back when something doesn't align with your goals |
| Coordination | Works alone | Hands off to other agents with context intact |
| Memory | Forgets everything between sessions | Maintains living memory of what happened and why |
Microsoft's own data tells the story. When they rolled out Copilot across the enterprise, adoption stalled around 20%. The CEO admitted the integrations "don't really work." Not because the tools were bad — because assistants without context, coordination, and judgment don't stick.
As Nate B Jones frames it, there's a "201 gap" between basic prompting and actually integrating AI into how you work. That gap is exactly where cognitive architecture lives — the deliberate design of how you think, decide, and operate with AI as substrate. See What Is Cognitive Architecture?
The Five Executive Roles (And Why They're Not Chatbots)
The LinkedIn series simplified it to five executives. The reality is 19 agents organized under these five strategic roles. Here's the executive layer:
Chief of Staff (Lennier) — Runs my calendar, inbox, and context. Delivers a daily briefing every morning. Coordinates the other agents. Named after the Minbari aide in Babylon 5 — devoted, strategic, anticipates needs.
CMO (Kennedy) — Direct response marketing, offer critique, copy review, funnel strategy. Has a mentor council built in: thinks like Dan Kennedy for pricing, Alex Hormozi for offers, Justin Welsh for personal brand. Under Kennedy sit six specialist agents — copywriting, funnels, email sequences, brand messaging, analytics, and media buying.
CFO (Housel) — Named after Morgan Housel, author of The Psychology of Money. Doesn't just calculate — asks "Is that data or fear?" when I'm making pricing decisions. Understands that money decisions are tangled up in identity, not just arithmetic.
CTO (Linus) — System architecture, technical prioritization, cross-instance coordination. Evaluates technical trade-offs customized to my specific environment, not generic recommendations.
Chief People Officer (Seneca) — Named after the Stoic philosopher. Advisory, decision support, perspectives. The executive whose job is to push back. I literally wrote in its instructions: "If you think I'm wrong, say so. Don't be gentle."
And me? I'm the President. Vision, final calls, staying human.
The best AI agents aren't the ones that do what you say. They're the ones that challenge you when you're wrong.
How to Start With One Agent Before Building Five
Don't build five agents at once. That's how you burn out.
Here's the sequence that worked for me:
-
Pick the role that saves you the most mental energy. Not the most time — the most energy. For me that was Chief of Staff, because my mornings were chaos without structure.
-
Give it an onboarding document. Write down who you are, what you're working on, what your priorities are this quarter, and what your constraints look like. This is the persistent context that turns an assistant into something useful. In Claude Code, this lives in a file called CLAUDE.md.
-
Use it daily for two weeks. Find the gaps. Where does it give generic advice? Where does it miss context? Where does it need to push back instead of agreeing?
-
Then add the second agent. Only when the first one is genuinely useful. For most people, that's either a content role (CMO) or a financial thinking partner (CFO).
-
Connect them. The magic isn't in individual agents — it's in the architecture that lets them share context. When my Chief of Staff hands something to my CMO, the context travels with it.
For a deeper walkthrough of the full architecture — how 19 agents share context, the handoff system, and the values layer that gates everything — see One Person, Five AI Executives.
FAQ
Do I need to be a developer to build an AI executive team? No. I'm not a developer. I built the entire system using Claude Code, which works through conversation, not code. The key skill isn't programming — it's thinking clearly about what each role needs to do.
How much does it cost to run 19 AI agents? The agents run on Claude (Anthropic's AI). The cost depends on usage, but for a solo consultant it's a fraction of what you'd pay a single contractor. The leverage — 5-9x on average, with peak sessions hitting 20-50x — makes it a straightforward ROI calculation.
Can I use ChatGPT instead of Claude for this? The principles transfer across models. The specific implementation I use relies on Claude Code's CLAUDE.md file for persistent context, but the architectural thinking — defined roles, shared context, values-gated decisions — works with any capable model.
How long did it take to build? The first useful agent took about a week. The full 19-agent system evolved over several months. But the compound effect kicked in early — by agent three, each new agent was faster to build because the architecture was already in place.
Is this just for consultants, or does it work for other roles? The specific roles map to my consulting practice, but the pattern works for anyone who manages multiple workstreams. I've seen creators, founders, and executives build their own versions. The roles change — the architecture doesn't.
Ready to go deeper? One Person, Five AI Executives walks through the full system — how 19 agents share context without breaking, the start-with-one roadmap, and what "cognitive architecture" means when you're not a computer scientist.
Building your own? I'm teaching this inside Digitally Demented on Skool — the course on how to architect AI as a thinking partner, not just a tool.
Last updated: March 10, 2026
