Layer two · the company brain
Policies in SharePoint. Customer information in systems. Processes living in people's heads. Reports nobody can find. Before AI is genuinely useful — and long before that, actually — a business needs a trustworthy way to reach what it already knows.
Two connected ideas
They are usually treated as separate projects owned by separate people. They are more useful managed together, because most real questions need both.
Approved documents, policies, procedures and knowledge, organised so that both people and AI can find the current version — and so that what is out of scope stays out of scope.
Structured business data connected and surfaced so that reporting and analysis are trusted rather than quietly rebuilt in a spreadsheet by whoever needed it most recently.
How it fits together
The company brain is not a place people visit. It is the layer that makes an answer possible — whether the person asking is using a search box, a report or Company Jarvis.
Each layer depends on the one beneath it. That is why permissions and identity belong at the bottom of the diagram rather than as a feature near the top: an access rule invented at the answer layer is not an access rule, it is a hope.
Asking questions, writing things, making decisions.
Through whichever front door suits
One familiar front door — optional, and not the only way in.
Approved knowledge and selected actions
Managed, permission-aware knowledge and data from approved sources.
Drawn from what you approve
How we work
We do not build one central database holding a duplicate of your entire estate. The recipe is specific to each organisation, and what stays out is designed as deliberately as what goes in. Copying everything somewhere new is how a knowledge problem becomes a security problem.
Source permissions are preserved, or an agreed equivalent control is put in place where the chosen platform enforces access differently. Where a platform cannot support what you need, we say so at design time rather than after go-live.
Every meaningful source has a person who owns it and a view on how current it is. Knowledge without an owner drifts, and drifted knowledge is worse than no knowledge, because people still believe it.
Managed, not delivered once
A knowledge foundation is not a project that finishes. Policies change, teams reorganise, systems get replaced and somebody always saves a second copy.
Under a managed service we keep the sources current and correctly permissioned, retire what has been superseded, watch what people are failing to find, and feed that back into what gets curated next.
Which of these apply depends entirely on your estate. A business running everything in Microsoft 365 needs a different answer from one with a decade of line-of-business systems, and we would rather scope that honestly than sell a standard package.
Start with a real question
That question tells us more about your knowledge foundation than an audit would. Start there, and we will work out what actually needs organising — and whether an AI front door on top of it would earn its place.