The AI Brain Is the Foundation. Everything Else Is a Use Case
Why we start every AI build with the brain: a live layer that connects your company's documents, systems and decisions, with access rules that control who sees what.
Before we build an AI solution, we study the client's systems, their data and the use case they want. Across a number of clients, we have run into the same wall.
Clients store data in several systems and the quality varies, and the use case needs to draw on that data across those systems. Starting from the use case turns each project into intensive, custom work.
I came to AI after years leading transformation at banks including Goldman Sachs and Barclays. At Codefully, across many AI projects, I see the same pattern repeat: systems work in silos, and the dots between them stay unconnected.
Our answer is to start with the brain. An AI brain is a live layer that connects your company's documents, systems and decisions, with access rules that control who sees what.
The AI brain explained
Max has spent close to seven years building AI solutions and works on the team behind Brainfully, our AI brain. He describes an AI brain as your company's library.
"An AI brain is like your company's library."
A company keeps documents in Google Drive, SharePoint and other folders, along with calendars, meetings and long email threads. The brain pulls that material into one place on top of the company. You can ask it what the team agreed in a meeting a month ago, or what a document says.
I define the brain by what it connects. It joins data and intelligence in one layer, links to your systems, and lives and breathes as your teams work and progress.
The brain follows role-based access. Max explains that a company has communications, marketing, development and sales teams, and each team needs different information. A developer has no need to see a new sales prospect until the deal becomes real. The company website is open to the team, while a colleague's email stays private. Each person reaches the information their role requires.
I see an AI brain as the easiest way to put the people and the systems of a company on the same page.
Technical bids · Advice for junior staff · Workflow automation
Memory · Retrieval · Captured decisions · Role-based access
Google Workspace · Microsoft 365 · Email · Meetings · Documents
The market is moving towards the AI brain
The large AI vendors are building the same idea into their products. ChatGPT's company knowledge connects to tools including Slack, SharePoint, Google Drive and GitHub. Claude's enterprise search covers Slack, Microsoft 365 and Google Workspace. In February 2026, OpenAI announced Frontier for a limited set of customers, with a shared business context and agent memory.
Gartner expects organisations to abandon 60% of AI projects through 2026 because the data under those projects is not ready for AI.
Our client work points the same way. Before a use case could run, we needed access to the data, we needed that data to be good, and we needed a connection to several systems. Building each use case from scratch made each project intensive and custom.
So we built an intelligent layer that connects to those systems and covers teams, people, departments and documents. With that layer at the base, we build AI solutions that pay back for the company and raise efficiency and productivity.
The AI brain in two levels
Access to information
Teams keep documents in different places, formats and access points. An AI brain adds intelligence on top, so people find the right information at the right time in a fast, organised way.
Action
At level two the brain acts on what it knows. It understands the data, makes decisions and looks across the organisation, so people can act in ways they could not without it.
A fire and safety consultancy spends over 100 hours a month on technical bids. Each bid asks 300 to 500 questions, and the team maps hundreds of pages of technical specifications into the answers. With a brain built on that documentation, we can complete the same work in close to 10% of the time, which saves the team a considerable amount of effort.
An education consultancy relies on senior consultants with niche knowledge. A brain that takes in calls, case information, meeting notes, conversations and the reasoning behind decisions lets junior staff ask it for advice as they would ask a senior colleague. The senior consultants answer fewer routine questions.
Three things that decide whether an AI brain works
Record the reasons behind decisions
An employee who leaves hands over to a successor in a knowledge transfer session. The successor learns which projects are live, which systems matter and how the team works. An AI needs the same handover. Max puts it this way: AI runs on data, and the data you feed it decides what you get back.
Give an AI the situation and the outcome without the decision, and it fills the gap with a guess. The guess may hold or it may fail, and the team finds out after someone acts on it. A brain that captures the decision gives the AI the reasoning along with the result. Foundation Capital's Jaya Gupta and Ashu Garg call that missing record a decision trace.
You do not need ten years of history. Build a pipeline that records the important decisions as people make them, and focus on the decisions that shape current work.
Good data was the first requirement we met on client projects. A decision counts as data, and a brain that lives alongside the team gives the team a place to capture it.
Ask: does the brain keep the reasoning behind each decision, or does it keep the result?
Combine memory and retrieval
Developers train a language model up to a fixed point, and it stops learning after that. Max calls the trained model a snapshot, and each conversation starts from that frozen state. The context window holds the text the model keeps in view during a conversation. The best current models offer a window of one million tokens. In Max's experience, efficiency holds up to 500,000 tokens, and answer quality degrades past that point. Chroma tested 18 leading models and found that reliability falls as the input grows.
Two or three extra documents use up much of the window. The real work is deciding what the AI sees:
- The software sends the relevant part of a document and leaves out the rest of the file.
- It stores the key points of older conversations and retrieves them on request.
- It tracks which conversation relates to which document and records when the subject changes.
The AI does not do this by itself. Engineers build it around the model in software, and Max says the architecture becomes complex.
The two halves are hard to join. Some tools improve long-term memory but cannot retrieve from your documents. Others use retrieval augmented generation (RAG) to search documents, and their memory stays weak. Microsoft Research found that baseline RAG struggles to connect the dots across separate documents. A brain needs memory and retrieval in one system.
My requirement for the brain is that it keeps pace with teams as they work. That requires memory of last week's conversation and retrieval of a contract from last year.
Ask: can the vendor show the information the AI receives for each question, and who selects it?
Keep the knowledge current
A brain stays useful while its knowledge stays true. A tool that copies a document into its own store falls behind the original: edit a spreadsheet in Google Workspace, and the copy keeps answering from the old version until someone uploads the new one. A brain reads the live source, so it needs the rights to your Google Workspace or Microsoft tenant.
Data rot is the second risk. A company collects a large amount of information over time, and without curation the useful data ends up beside garbage. Max's first step against data rot is to let people review what the brain captured and correct it.
That is why I describe the layer as a living one. It follows teams, people, departments and documents as they change.
Ask: does the brain read the live file or a copy, and can my team correct what it holds?
AI brain vs ChatGPT and Claude
ChatGPT and Claude find documents. ChatGPT's company knowledge answers with citations and respects each user's existing permissions. Claude's enterprise search runs live searches across your connected tools. They differ in memory.
| Option | Finds documents | Memory (October 2026) |
|---|---|---|
| ChatGPT company knowledge | Yes, with citations, within each user's existing permissions | Shared projects have their own private memory. Business memory belongs to each user's account. |
| Claude enterprise search | Yes, through live searches of Slack, Microsoft 365 and Google Workspace | Memory on Team and Enterprise belongs to each member, with a separate memory for each project. Owners decide whether to switch it on. |
| A company AI brain | Yes | Built to hold one memory for the company |
Anthropic's documentation says Claude's enterprise search makes live calls to your connected tools and does not index that data. Both vendors document memory that belongs to a user or a project. Neither documents a single memory for the company in these products. OpenAI's Frontier, a separate platform, describes a shared business context and agent memory, and it launched for a limited set of customers.
Max sees the gap in design. These models serve a general audience, and a memory system tuned to one client does not suit another. Our team builds a brain around one company and tunes it to how that company works.
Ask: does each option record decisions, and can your people see and correct what it holds?
Brainfully, Codefully's AI brain
Our team builds Brainfully on live data and tunes it for specific industries.
- →Combines long-term memory and document retrieval in one system, so it answers from the live source.
- →Connects to your Google Workspace or Microsoft tenant with the rights to read current information, so an edit appears in the brain without an upload.
- →Follows role-based access, so each person reaches the information their role requires.
Next for Brainfully
Brainfully will write wiki-style summaries of the information it holds. Employees read the summaries and request corrections, and admins edit them. If a summary describes how one person works, the admin asks that person to confirm it, because that person knows the work. This process is our first step against data rot.
On top of the brain we build agents for your company. Max compares this to Salesforce: one general system that each customer configures to its requirements. The brain is the general layer, and the agents do the specific jobs, such as automating part of a workflow or supporting a decision. In my view the brain sits at the base and the agents sit on top of it.
Start with the AI brain
I believe small and large organisations should bring in an AI brain. It puts people and systems on the same page. Systems that work in silos leave the dots between them unconnected, and an AI brain connects those dots in a short time and lets people connect them. With data and intelligence at the centre, a team gets more done with less effort.
Start with the brain, and build your use cases on top of it. If you are considering an AI brain for your company, get in touch at brainfully.ai before we launch Brainfully.
Sources
- Gartner: Lack of AI-ready data puts AI projects at risk
- Jaya Gupta and Ashu Garg, Foundation Capital: AI's trillion-dollar opportunity, context graphs
- Microsoft Research: GraphRAG
- Chroma: Context Rot
- OpenAI: Company knowledge
- OpenAI: Shared projects
- OpenAI: Introducing OpenAI Frontier
- Anthropic: Enterprise search
- Anthropic: Claude memory
Want this in your business?
If building an AI brain that connects your documents, systems and decisions, so every AI use case starts from good, shared data is something you're facing, it's exactly what we build in our Cross-functional system work.
Frequently asked questions
What is an AI brain?
An AI brain is a live layer that connects a company's documents, systems and decisions in one place, with role-based access rules that control who sees what. People and AI agents can ask it questions and act on what it knows.
Why start with an AI brain instead of a use case?
Most use cases need good data drawn from several systems. Building that access from scratch for each use case makes every project intensive and custom. A brain built once at the base lets each new use case reuse the same connected, curated data.
How is an AI brain different from ChatGPT or Claude enterprise search?
ChatGPT and Claude can find documents across connected tools, but their documented memory belongs to a user or a project. A company AI brain is built to hold one memory for the whole company, including the reasoning behind decisions.
How do you stop an AI brain going out of date?
Read the live source rather than a copy, so edits appear without re-uploading, and let people review and correct what the brain has captured to prevent data rot.
How does Codefully do this?
We deliver this as Cross-functional system. An AI operating layer across teams and tools — with an AI Audit-led rollout.
