Source systems keep factual ownership
Your existing documents, project tools, CRM, finance records, and conversations remain where they belong. The context layer points back to the right source instead of creating a competing copy of the truth.
Company Brain / shared operating context
A Company Brain for AI agents and teams.
A Company Brain gives people and AI agents a governed operational context layer between an organisation’s systems of record and the work they need to do. It brings approved facts, operating rules, decisions, and workflows into view without creating another source of truth.
Starting workflows
Choose the live work to improve first.
Each workflow is a bounded 30-day implementation. Open a workflow to see the output, source boundary, technology role, human review, and day-30 decision point. From there, the one application records the workflow you chose.
Workflow 01
Client Commitment Radar
A weekly, source-linked account brief for commitments, decisions, risks, owners, and the next check.
For an active client account where missed context becomes a delivery problem.
See the workflowWorkflow 02
Proposal/RFP Evidence Desk
A cited evidence pack that makes the approved material, open gaps, and owner questions visible before drafting.
For teams with at least three live proposals or RFPs in the next 30 days.
See the workflowWorkflow 03
Client Onboarding & Handover Desk
A current transition brief that gives the next owner commitments, open questions, sources, and next checks.
For a live client onboarding or handover where context cannot stay in one person’s head.
See the workflowThe problem
What is a Company Brain for AI agents?
The latest brief may live in one place, a decision that changed direction in another, and the person who knows why may be unavailable. A polished AI draft from partial material makes the gap harder to spot, not easier to resolve.
A Company Brain gives agents the right context for a job, shows where it came from, names what remains uncertain, and leaves the next action with an owner.
The layer
A navigable layer. Not a giant prompt or a document dump.
The system guides a request toward only the instruction and source detail it needs. That keeps the context relevant, inspectable, and easier to maintain as the work changes.
Operating rules make work repeatable
A defined workflow names the inputs, decision rules, checks, output format, and the point where a person remains accountable.
Permissions and freshness travel with the work
Each source or derived claim carries an owner, intended audience, freshness expectation, and allowed use so an answer does not quietly widen access or rely on stale material.
Outputs leave a usable trail
The result can show its sources, open questions, relevant trade-offs, owner, and next check. That makes the work inspectable and easier to improve.
Evidence standard
Shared context, not shared access.
People and agents stay in sync when a claim carries its source, status, permission, and decision boundary with it. That is more useful than a pasted document or a confident sentence.
Source
What record or approved material supports this?
Currentness
When was it last checked, and what may have changed?
Authority
Is this a fact, a cited view, or a working inference?
Use
Who may rely on it, for what purpose, and where must a person decide?
One source, three roles
Keep the record, the context, and the decision in their proper place.
| Layer | Job | Stays accountable |
|---|---|---|
| Systems of record | Maintain the facts and their updates. | The owner of the source. |
| Company Brain | Route an approved request to the right context and workflow. | The workflow and its governance rules. |
| People | Judge trade-offs, approve consequential work, and act. | The named decision maker or owner. |
How a team starts
Build around work that already has consequences.
A serious context layer earns trust through a bounded implementation cycle, not a company-wide migration or a generic chat interface.
- 1
Define the operating question
Choose a decision, handover, update, or deliverable where the cost of reconstructing context is visible. Set a baseline and a success threshold before adding tools.
- 2
Map approved evidence and authority
Record which system owns each fact, who maintains it, how current it needs to be, which audience may use it, and what stays restricted.
- 3
Configure the working path
Write the topic instructions, decision rules, source checks, output standard, and human control point required for that one workflow.
- 4
Validate with real work
Test normal and failure cases in the field. Improve the smallest layer responsible: source coverage, definition, routing, workflow step, or review check.
Shared work
A Company Brain is a second brain for shared work.
A personal Second Brain helps an individual carry useful context into their work. A Company Brain makes the team context usable by people and agents while preserving authority and access boundaries.
| Context | Job | What it holds |
|---|---|---|
| Personal Second Brain | Helps one person recover their own context and move their work forward. | Individual notes, memories, decisions, and workflows. |
| Company Brain | Helps a team and its AI agents work from governed shared context. | Approved team sources, access rules, decision history, and accountable workflows. |
Build on this
Practical resources for the work around the layer.
These guides cover the working practices that make a Company Brain maintainable once the first workflow is in use.
Context Engineering Guide
The five layers behind instructions, memory, MCP, skills, and hooks. Use it to turn a source map into context that an AI can use deliberately.
AI Work Cycle
A practical loop for planning, doing, reviewing, triaging, and learning. Use it to place a quality check inside the workflow, not after the fact.
Second Brain Setup Health Check
A diagnostic for an existing AI setup. Use it to find missing instructions, weak memory, and context that has stopped being useful.
Boundaries
Useful context needs clear limits.
- No replacement for your CRM, project tool, Drive, or finance system.
- No flat repository loaded into every model prompt.
- No autonomous action across sensitive systems without an approved workflow and human control point.
- No assumption that personal and restricted context belongs in one shared namespace.
Questions
Company Brain, in practice.
What is a Company Brain for AI agents?
A Company Brain is a governed operational context layer between an organisation’s systems of record and the AI tools its people use. It gives an AI agent the approved facts, operating rules, decisions, and workflow detail relevant to a request, without turning the layer into another system of record.
How do people and AI agents stay in sync?
They work from the same governed context, not the same unrestricted data. A Company Brain routes a request to approved sources, instructions, and decision history while keeping access, freshness, and review boundaries visible.
Is a Company Brain an AI knowledge base?
A knowledge base can store useful material. A Company Brain adds source ownership, currentness, allowed use, workflow rules, and review points. It is the operating context around a knowledge base, not a flat repository copied into every prompt.
Does a Company Brain replace our existing tools?
No. Systems such as project management, CRM, finance, documents, and messaging remain the sources of record. The Company Brain helps people and AI work from the right approved context across them.
What is the relationship between Company Brain and Team Brain?
Company Brain is for governed context across approved sources, teams, and AI agents. Team Brain is a separate focused offer for one team and one recurring workflow.
Where should a team start?
Start with one recurring decision or deliverable where the team repeatedly rebuilds context. Define the approved sources, their owners, access boundaries, review point, and the outcome that should be traceable.
Company Brain starting point
Start with the work that is already live.
Choose a workflow first. Its page shows the concrete output and boundary. The application then records that choice, checks fit and source rights, and only accepted applicants receive a private Factory checkout link.
Working with one team and one recurring workflow? Explore Team Brain.