A company second brain is a shared memory that a firm's people and its AI agents read and write, organized around client records instead of one person's folders. It keeps the personal method's habits of capturing and distilling, and adds what a team needs: an owner and a source for each fact, permissions, and a rule for what stays private.
Company second brain: a memory for your team and AI agents
A company second brain is the memory a team and its AI agents share. What carries over from your personal second brain, what breaks, and what to keep private.
The Standards team
In short
What is a company second brain?
A company second brain is the memory a team and its AI agents share, so that what one adviser learns about a client is there for the next colleague and the next agent who open the file. The personal second brain, as Tiago Forte teaches it on Building a Second Brain, aims at a body of knowledge "uniquely your own", kept in a note app such as Notion or Obsidian. The company version keeps the idea of an external memory and changes who owns it: the knowledge belongs to the firm and stays when an employee leaves. The phrase now covers four things: a personal second brain, an AI second brain that adds an assistant to one person's notes, a company brain, and a brain several AI agents share as one source of truth. A company second brain joins the last two: one memory for the firm, read and written by its people and its agents alike.
In 2026 a company brain has readers a note app never had: agents that draft emails and file meeting transcripts, and that take every line they read at its word.
What carries over from a personal second brain?
Two habits of a personal second brain carry over to a company second brain as they are: you capture what you learn while it is fresh, and you distill it down to what someone else can act on. Building a Second Brain is Tiago Forte's method for keeping an external memory: CODE (capture, organize, distill, express) to process what you learn, and PARA (projects, areas, resources, archives) to file it. In an advisory firm, capture is the note after a client meeting, distill is the two lines telling a colleague what the client decided, and express is the letter or the proposal built from those lines. The step that changes is organize. PARA sorts notes by how active they are for one person, and a team has to find a fact by the client, the household or the contract it concerns, whoever wrote it down. An adviser covering for a colleague opens the household, never that colleague's Projects folder.
Keep PARA for your own work in progress. Move the facts about clients onto the client's record: the guide to building a customer database from your client spreadsheet shows how to set up one record per client, household or contract, with its documents, emails and meetings attached.
Five things that break when a team shares one brain
A personal second brain works because one person writes every note, reads every note and knows what each one means. Put ten people and a few AI agents on the same notes and five of those assumptions fail. Each failure needs a fix built into the company second brain itself:
What breaks | In your personal second brain | In a company second brain |
|---|---|---|
Ownership | You own every note | Each fact needs an author, and Slite's guide (October 2026) gives every shared note an owner and a check-in date |
Permissions | Nobody else reads your notes | A junior adviser should not read the partners' notes on pay; access follows roles and records |
Provenance | You remember where a note came from | A colleague needs the source: which meeting or which email |
Freshness | You notice your own stale notes | A stale shared note misleads everyone who reads it, so facts need an end date or a review |
Departure | The notes leave with you | The firm's knowledge has to stay; Slite names notes in personal apps leaving with their owner |
The upkeep problem gets worse at team scale. The this+that team, in its June 2026 review of team apps (which includes its own), calls it the "discipline gap": most second brains fail because capture and upkeep depend on people remembering to do them. A company brain that relies on ten people remembering goes stale wherever one of them forgets, so the capture has to come from the work itself: the meeting and the email.
Where should a company second brain live?
A company second brain can live in a shared note app, in a company wiki, in a folder of files that agents read, or on the client records themselves. Each option fits a different kind of knowledge and has its own limit for a team, as of October 2026:
Where it lives | What it fits | Where it breaks |
|---|---|---|
A shared note app or vault, such as Notion or Obsidian | Teams already writing there; this+that notes that Notion sets view, comment and edit rights per page | this+that writes that Notion and Obsidian need significant configuration before they help a team; facts are filed by page unless the team builds and maintains its own client database |
A company wiki | Processes, policies and documents people choose to publish | Pages are filed by document, not by client, and hold what someone writes up or a connected tool brings in |
A folder of markdown files that agents read, as MindStudio describes | One person and their own agents | The guide covers no permissions or per-fact authorship, and two agents writing the same file at once conflict |
The client records, with memory attached, as in Standards | Firms whose knowledge is about clients, households and contracts | You define your records first, and processes written as long documents fit a wiki better |
For an advisory firm, most of what is worth remembering is about a client: who the decision maker is, what the household decided last spring, which document is missing. That knowledge belongs on the client's record, where permissions and history already apply. Processes and policies can stay in a wiki, with a link from the record to the page that applies.
When AI agents write to the company brain, its rules apply to software too
Once AI agents write to a company second brain, ownership, permissions, provenance and freshness apply to software as well as to people. An agent drafting a client email reads the brain, and an agent filing a meeting transcript writes to it. Meta's engineering team, describing its organizational second brain in September 2026, has domain experts review each change the agent proposes to its knowledge, sent as a pull request with an audit trail, before it lands. A firm of twelve people will not staff that review, so the rules have to live in the tool. An agent sees only what the person it acts for may see, every change shows who made it, and anything irreversible waits for a human. The MindStudio guide to a markdown second brain, from June 2026, warns that two agents writing the same memory file at once conflict, which records with an owner and a history avoid.
In Standards, agents read and write the firm's records with the permissions of the person they act for. Each record keeps its history: who changed what, a colleague or an agent, and the value before. You pick how much an agent may change alone. In Manual mode, it asks for your approval before each change to your data. In Auto, the default, it changes your data without asking, and deletions and outgoing sends still wait for a person's approval by default. Claude Code, Cursor or any MCP client reaches the same records under the same permissions, as the set-up page for MCP clients describes.
Which personal notes should reach the company brain?
Facts about the firm's clients and work should reach the company second brain; instructions and preferences that belong to one person, and anything about their health, pay or private life, should stay with that person. Every team moving from personal notes to shared memory crosses this boundary, and the guides read for this article leave it to judgment. Slite recommends a "share when ready" norm, which suits a document a person chooses to publish. It does not cover what an agent learns in the background from a mailbox or a meeting, where nobody decides to share anything. A company brain fed by agents needs the boundary written down as a rule:
Shared with the team by default | Stays with the person |
|---|---|
How people and companies relate to each other | Instructions a person gives their own assistant |
The context of a client file | How a person likes to work |
Decisions taken on the file | Anything about health, pay or private life |
Standards writes this sharing rule into its memory. Memory learns from your conversations with agents, from meeting transcripts and from the important direct emails in your inbox, and it keeps one page per person, one for the workspace and one per record. The setting "Share with the team what memory learns from my private sources" is on by default. While it is on, relationships, context and decisions about the team's records reach the record's page, and instructions and preferences never do. Each person can switch it off in their preferences, and can stop memory reading their mailbox through the API. A shared memory is never more visible than the record it is about or the source it came from.
In Standards, each record has a Memories tab. Your team sees every memory about the client with its author, its day and its source, and can correct it, delete it or add one. A line a person writes or corrects is marked as theirs, and memory puts it back if a later rewrite drops it.
How a 12-person advisory firm moves from personal notes to a company brain
Take a fictional advisory firm of twelve people, where each adviser keeps client notes in their own app and the partners keep theirs in a notebook. In Standards, the move to a company second brain takes five steps, in this order, and none of them asks anyone to copy their old notes by hand:
The partners choose the records the firm works from: households, people, contracts and companies, and they agree that a client fact lives on its record, never in a personal app.
An administrator sets the roles: who reads, creates, edits or deletes each kind of record, and which partner matters stay in private records, hidden from other people and their agents.
Each adviser connects their Gmail inbox and Google Calendar and sends the recording bot to client meetings, so transcripts land on the participants' records and memory learns from them and from important emails.
Each adviser decides on sharing: they leave "Share with the team what memory learns from my private sources" on to pass relationships, context and decisions to the records, or switch it off and keep everything on their own profile.
The partners set their Default work mode to Manual, read the Memories tab of their main clients each week, correct what is wrong, and switch their conversations to Auto for routine tasks once the corrections stop.
The advisers keep their personal second brains for their own drafts, reading and ideas. A client fact, once it exists, goes onto the client's record, where colleagues and agents look first.
Questions
Before you switch tools.
Yes, if the team gives it what one person's notes never needed: an owner and a source for each fact, permissions by role and by record, and a rule for what stays private. Without those, your team stops trusting the shared note app and goes back to asking colleagues. A team second brain also has to stay current without relying on everyone's discipline, so capture should come from meetings, emails and changes to records.
A company wiki holds what people chose to write down and publish, such as processes and policies. A company second brain also holds what the firm learns while it works, such as who decided what with a client and why, and it sits on the client records themselves. AI agents read it before acting and write to it after, so every line needs an author, a date and a source.
Yes, when the brain is made of records with an owner and a history. In shared memory files, two agents writing one file at once conflict. In Standards, its own agents and Claude Code, Cursor or any MCP client read and write the same records, each under the permissions of the person it acts for. Every change shows who made it and the value before, and by default Standards' own agents wait for a person's approval before deleting or sending.
In a personal app, the notes leave with the employee, which is the loss a company second brain exists to prevent. In Standards, the facts your team enters on a client stay on the client's record after anyone leaves, and the record's history still shows who entered each one and when.
Yes, for their own work: reading notes, drafts, ideas and the way they like to work. The line to draw is between facts about the firm's clients, which belong on the records, and everything personal, which stays private. Forte's PARA system still suits personal notes. Client facts are better found on the client's record than in someone's Projects folder.
Read next
On the same subject.
Client facts on the client's record, shared with your team and its agents, never seen by more people than their source.
Show us how your advisers keep client notes today, and we will show you what that becomes in Standards.