Your AI Workforce, Governed: What Replaced BrainRoad's AI Company
On this page
We built an AI org chart, and it worked. A CEO agent broke your goal into tasks, proposed hiring specialists, and ran the work through an issue tracker with budget caps and approval gates. Internally, it shipped real software.
Then we watched who actually used BrainRoad, and retired it.
What the org chart got right
Two things, and they were the important two.
Nothing consequential happened without a human decision on the record. Hiring an agent, raising a budget, taking a flagged action — each of those paused and waited for a person. That principle survived the retirement intact.
Every action was attributable. You could trace an output back through the task that triggered it, the agent that handled it, and the tools it used. That principle survived too.
What it got wrong
The shape. A small-business owner does not want to run a simulated company. They want one capable helper that knows their business, and they want the actual humans they work with — a partner, an office manager, a bookkeeper — to be able to see and steer what that helper is doing.
The org chart optimized for agents managing agents. The real need was people and one agent in the same room, working from the same record.
It also concentrated governance in a product feature. Approval belonged in the platform, applying to every account whether or not anyone opted into an org chart.
What replaced it
The Business Brain
Your files, notes, customer history, FAQs, quote templates, service rules, and decisions, in one private place your helper drafts from. This is the record the work happens against — not a chat history the helper synthesizes after the fact.
The review Inbox
Anything your helper wants to send, post, charge, update, or change lands here first as an editable card. You approve, edit, or decline it. Then BrainRoad’s server performs the action — not the helper. That distinction is the whole ballgame: if the agent holds the credential and sends on its own, an approval step is advice rather than enforcement.
Approvals stay on the record afterwards, attributed to whoever made them, so months later you can still see what was proposed, what changed, and who decided.
The Team room
The Company page became Team: one shared room per account where the people on your account and your BrainRoad helper work in the same place, over the same Business Brain. It is built on Buzz, an open-source project from Block released under the Apache 2.0 license, hosted and governed by BrainRoad.
Work that starts in the team room still routes through the Inbox. The team room is not a second approval queue — there is exactly one place where outward-facing actions get decided.
What this means if you were using AI Company
Your helper, your Business Brain, your agent identity, your approval history, and your billing are unchanged. The org-chart tooling, the CEO/specialist hierarchy, and the separate company workspace are gone. Your dashboard’s Company page is now Team.
If what you valued was parallel specialist agents, that capability lives in the helper runtimes themselves — OpenClaw and Hermes both support sub-agents and delegation inside your own workspace, without a second governance product on top.
The lesson worth keeping
Multi-agent structure is a means, not a product. What people pay for is a helper that knows their business, does real work, and cannot do anything outward-facing without a person’s say-so — plus a durable record of every one of those decisions.
We built the org chart to get the governance. We kept the governance and dropped the org chart.
Did retiring AI Company weaken any controls?
No. The approval model moved from a feature you opted into toward the platform itself, so it applies to every account by default. Every outward-facing action stages as an editable card in your Inbox, BrainRoad’s server executes it rather than the agent, and the decision stays on the record afterwards.
What happened to per-agent budget caps?
Model spend is governed by the API keys you supply and the cost views in your dashboard rather than by an agent-level budget ledger. You bring your own provider keys and pay those providers directly, so spend is visible and capped where the credential lives.
Can more than one person use my account?
Yes. You can invite a teammate as a delegated reviewer who reads your shared Business Brain and can edit, approve, or decline ordinary work in the Inbox. Billing, helper controls, Brain writes, and trust settings stay with the owner.
Start with the Brain, not the org chart
Bring your files, examples, FAQs, templates, and customer details. Build one reviewable workflow before you expand.
Build Your Business Brain