Building an AI Game Studio: Rethinking Org Charts and Token Efficiency

At the start of my journey into creating an AI-driven game development studio, my central question was: How do I build bot employees that can function like a real company and iteratively generate games over the long term?

My first step was focused on creating individual, highly skilled bot workers proficient in their specific domain tasks. However, as I began assembling this initial team of AI workers, I quickly ran into a major operational bottleneck: the org chart and tokenization.

The Tokenization Dilemma & Group Chat Overhead

Initially, I structured the team like a traditional hierarchical company. For instance, I had Sheila, the Art Director, managing sub-specialists like pixel artists and poster designers. Sheila would then report up to the project manager, who would report to me.

However, this hierarchical structure caused an unexpected issue:

• Exploding Token Consumption: The bots began creating group chats, constantly discussing and checking in with each other to solve even simple problems.
• Exponential Communication Overhead: Every extra layer resulted in bots endlessly conversing amongst themselves, burning through tokens without delivering proportional output.

It immediately brought to mind Fred Brooks’ classic software engineering book, The Mythical Man-Month. Just as adding human developers to a late software project can make it later due to communication overhead, adding more AI bot roles exponentially increased token usage and delay because everyone needed to be notified and consulted.

The Solution: A Flat Org Chart with “Pat”

To fix this, I pivoted to a flat organization structure:

1. One Central Project Manager: I created a single PM bot named Pat.
2. Direct Specialist Connections: Instead of nested managers (like having pixel artists talk to Sheila, who talks to Pat), all individual domain experts now communicate directly with Pat.
3. Streamlined Flow: Everyone reports straight to Pat, and Pat interacts directly with me.

This flat org structure dramatically reduced token utilization and eliminated unnecessary bot-to-bot chatter loops.

Current Trade-offs and Looking Ahead

While the flat org chart solved the token crisis and made the system significantly more efficient, it comes with a trade-off: a lot of the operational load now sits heavily on Pat’s shoulders.

This is just the beginning of my journey. As we start building multiple games, I’ll be testing and tweaking these systems to see if an AI-bot-operated gaming company is truly a viable, scalable model. Stay tuned for future progress updates!