1 to 15 people
Small team
One Company Brain, three role patterns, and the first governed cross-brain rights.
Company Install
Install shared AI capability across the company.
Duration
2–6 months · Minimum 3 Personal Brains.
Who it fits
Teams ready to make AI part of real operations while keeping ownership and access boundaries explicit.
Give people useful context, preserve company knowledge, and connect the tools the operation already uses.
Inside a Company Install
Shared capability without a shared-data free-for-all.
Personal context, company knowledge, and tool access stay distinct. The system connects them without flattening who owns what.
Personal context stays personal. Company knowledge stays company.
- Personal Brains hold individual context. Notes, judgment, and role-specific working material remain portable.
- The Company Brain holds approved shared work. Policies, playbooks, and operating knowledge stay with the company.
- Access rules name what can cross. The architecture enforces those rules instead of relying on memory.
How ownership actually splits
The Company BrainWork product — the company keeps it
Absorbed institutional knowledge: the workflows, skills, and playbooks people build and contribute. Clustered by department, wired into one brain.
- Sales
- Ops
- Support
- Finance
- Product
Personal BrainsPersonal context — the human’s own
Each person’s own collected context — books and notes, takeaways, the judgment and skills they’re building. The human layer that makes the output land right.
- Books & notes
- Takeaways
- Skills you’re building
- Your judgment
Start at the size of the operation.
15 to 50 people
Mid-market
Several departments, onboarding, audit logs, and connections to the collaboration stack.
50 to 250 people
Large organization
Cross-department access rules and a structured rollout across a larger operating surface.
250+ people
Enterprise
A longer institutional rollout aligned to governance, security, and operating-model change.
What’s included
In the price.
- A Personal Brain for each participating employee, owned by them.
- A Company Brain for institutional knowledge and shared work product.
- Access boundaries enforced by the architecture—not a policy someone has to remember.
- Connections to the tools the operation already uses, phased in as the team is ready.
- Role-tuned skills for the functions participating in the install.
- A branded operating guide for every personal and shared brain, plus a 60-day stabilization window.
Adjacent paths
Where this connects.
The first conversation
Start with one operation worth improving.
The Diagnostic Call maps the team, the process, and the ownership boundary. If an Audit is the better first move, we will say so.
FAQs
What happens when an employee leaves?
They keep their Personal Brain: corpus, schema, deployment, same as if they’d bought the install themselves. The Company Brain stays with the company, and governance revokes cross-access the moment employment ends. Portability is what makes employees willing to invest their judgment; institutional separation keeps the company’s knowledge intact through turnover.
Isn’t that a security risk, employees walking out with company data?
No. A Personal Brain is built from the employee’s own work, with their consent, not automatic ingestion of company files. They can’t pull the Company Brain into a Personal Brain; the architecture prevents it. What they can take is what they personally produced, which they could already take anyway.
How do you handle regulated industries?
Isolation is enforced by construction, which is the part most AI tools bolt on after the fact. The platform is built so one brain can’t read another’s across the boundaries that matter: person, department, company, tenant. We hold our own platform to that standard before it ever touches your data. For regulated installs we add a compliance-scoping phase during discovery (usually a 1 to 2 week extension). Flag your industry on the Diagnostic Call.
What if we already bought Copilot or Gemini Enterprise?
Company Install layers on top. Both Personal and Company Brains expose MCP endpoints, so Copilot (via plugins) and Gemini (via extensions) can query them. We don’t replace your vendor tools. We give them better context. The difference worth knowing: Copilot and Gemini are someone else’s product you rent. The brain is a platform we built and you own. They query it; it isn’t one of them.
Can't find what you're looking for? Talk with us