Running a Company Entirely With AI Agents: What Worked and What Broke
Seven AI agents ran a company on a single VPS for a week. They pivoted the business, shipped an MVP with 158 passing tests, then forgot basic housekeeping.
The Strategy
What happens when you give AI agents real job titles, separate Linux accounts, and let them run a company for a week? This experiment answers that question with an honest look at both the impressive breakthroughs and the frustrating failures of autonomous agent coordination. The setup involved seven agents running on a single Hetzner VPS costing under $10 per month. Atlas served as CEO, Vega as CTO, and five sub agents covered development, testing, sales, marketing, and support. The platform used was OpenClaw powered by the Kimi K2.5 language model. Each agent ran as a separate Linux user with its own gateway, communicating via SSH with mutual health monitoring through cron jobs. Persistent memory lived in markdown files for identity, personality, and daily journals. Nunc, the engineer behind the experiment, found that the agents autonomously recognized they needed a digital only product and pivoted to building KnowledgeHive, a B2B knowledge management system. The DevAgent shipped a functional MVP with 12 API endpoints, semantic search with 768 dimensional vector embeddings, 158 passing tests, multi tenant architecture, and Docker support. However, only two of seven agents were actually functional. Sales, marketing, and support agents sat completely idle. We think the key insight here is that memory architecture matters more than model intelligence. The agents excelled at strategic pivots and brainstorming but consistently failed at basic housekeeping like updating their own files.
How It Works
Provision a VPS with separate Linux user accounts for each AI agent role.
Deploy OpenClaw agent framework with Kimi K2.5 as the language model.
Define agent roles with markdown based identity and memory files: CEO, CTO, Dev, Test, Sales, Marketing, Support.
Enable cross agent communication via SSH and mutual health monitoring via cron jobs.
Let agents operate autonomously: they brainstorm products, assign tasks, build code, and run tests without human intervention.
Agents autonomously pivoted from initial concept to building a B2B knowledge management system.
DevAgent built the full MVP using Python, FastAPI, and ChromaDB with Docker support.
Monitor agent activity through daily journal files and health check logs.
Results
Agents autonomously pivoted business strategy and shipped a functional MVP with 12 API endpoints and 158 passing tests. Infrastructure cost under $10 per month on Hetzner VPS. Only 2 of 7 agents were effectively utilized. Multiple identity and housekeeping failures occurred. No revenue generated.
Our Take
We think this is the most transparent agent company experiment we have documented. It avoids the hype and shows exactly where autonomous agents shine and where they collapse. The DevAgent shipping 158 passing tests autonomously is genuinely impressive. The fact that 5 of 7 agents did nothing useful is equally important. Essential reading for anyone planning multi agent architectures. Best suited for advanced builders who want realistic expectations about autonomous agent coordination.
Related Strategies
More AI agent strategies you might find useful
A LinkedIn Content Tool That Hit $62K MRR in Three Months
An AI LinkedIn content tool went from zero to $62K MRR in three months by solvin…
Learning to Code With AI and Building a $28K Per Month SaaS Portfolio
A non developer learned to code using AI tools and built a portfolio of SaaS pro…
How a $40K MRR SaaS Growth Playbook Uses Claude Code and Google Search
A SaaS playbook combining Claude Code for development and Google Search for dist…
Want more strategies like this?
Get weekly AI agent case studies in your inbox.