The idea

What a second brain for a company is

Your company already knows almost everything it needs. That knowledge sits in heads, inboxes and scattered files, where no tool can read it. A second brain for a company is one connected map of it: every client, deal, person, figure and service gets one page, and pages link the way the facts link in real life. It belongs to the company, on the company’s storage.

What does “second brain” mean when the owner is a company, not a person?

It means a record. Not notes, and not a chat history: a structured set of pages, one per thing the company deals with, each carrying the facts that are true about it and the document each fact came from. The originals are kept exactly as they arrived. The pages are written and rewritten from them, so a figure never floats free of its source.

Is this the same as Building a Second Brain?

No. Building a Second Brain is a method for organising one person’s notes. This is a record of a company: its decisions, numbers, clients and services, owned by the company, kept current by software, readable by everyone who needs it. The phrase is shared; the thing is not.

Where does a company’s knowledge sit today?

In people’s heads, in email, in chat, in drives nobody has tidied since the last reorganisation, and in a CRM that was true in March. The AI the company has bought reads none of it, which is why its answers are generic. It has nothing to read.

What are the three parts, and why none of them works alone?

A base nobody maintains goes stale in a month. Agents with nothing to write into produce noise. A dashboard over an untrusted base is a decorated guess. Installed together, each keeps the other two honest.

What can a company ask its second brain?

Seventeen questions, from a lookup to the ones nobody in the company can answer today. The last two tiers are the argument for the thing: they cannot be answered while the records live in heads and mail.

Look up
Reconcile
Notice
Investigate
Decide

What does “every fact names its source” mean in practice?

Each figure on a page carries the document it was read from and the person who approved it. When two sources disagree, the page says so instead of picking one quietly. When a fact goes stale, the agent flags it rather than letting it stand. This is the same discipline a regulator or an auditor expects of a tokenized asset’s record, applied to the company itself.

What is it not?

It is not a migration: the systems you have keep running. It is not custom software: it is a structure, agents and a dashboard, developed for this one organization. And it is not a licence: there is nothing to renew and nothing to be locked into.

What would an auditor make of it?

The first question an auditor asks is whether the company can show where a number came from. A second brain answers that on every page. It was built for businesses that get audited, by someone whose other work is building records that regulators accept. How the work runs describes what actually happens; the questions before you start answer the rest.