What is a company brain?

A company brain is the one place where what your business knows is written down in a form that you and your AI tools can both read: your clients, your money, your plans, your decisions and the reasons behind them. For a one-person business, the simplest version that works is a single folder of plain markdown files with a consistent structure.

That is the whole idea. The rest of this guide covers why it matters now, what goes in one, and how to build it yourself.

Why a business of one needs one now

A company of fifty writes things down because it has to. A new hire can’t read the founder’s mind, so there is a wiki, a CRM and a shared drive.

A company of one never had to. You were the wiki. That held until AI tools arrived, because an AI agent is a new hire who starts from zero every morning. Every chat, every tool and every account knows only what you paste into it, so you explain your clients, your prices and your tone again, and then again.

A company brain is the fix. You write the business down once, where every tool can read it.

What goes in it

Start with the concrete things your business runs on:

• Clients and projects. One file per client and one per project, with the status, the contacts and what was agreed.
• Money. Invoices, subscriptions, what you’re owed and what you owe.
• Plans. This quarter’s priorities, the launch you’re preparing, the goals you track.
• Decisions. What you decided and why, so you (or an agent) don’t reopen it next month.
• How you work. Your offers, your prices, your voice, the steps you repeat.
• The life around the business. Health, family, learning. It belongs in the same place because it competes for the same hours, but it stays separate, for a reason covered below.

Three properties that make it work

A pile of notes isn’t a company brain. Three properties turn one into the other.

1. Structure. Every file says what it is. A client note is typed as a client and an invoice as an invoice, and each carries a few fields at the top: its type, its tags and a one-line description. A person or an AI agent can tell what a file is before reading a word of it. The open standard for this is OKF, the Open Knowledge Format that Google Cloud published in 2026 (what OKF is).

2. Ownership. The files are plain text on a disk you control. Any editor opens them and any AI can read them, and no company closing its doors can lock you out. Leaving a tool is copying a folder.

3. Scope. An AI agent should see what its job needs and nothing else. The agent that chases your invoices needs clients and money; it doesn’t need your journal. Tags do this better than folders, because a file can sit wherever it makes sense to you and still be inside or outside an agent’s reach.

How to build one yourself

A weekend is enough for a first version.

1. Make one folder. Inside it, a few folders by area, not by app: Clients, Projects, Money, Plans, Notes, Life.

2. Write one file per thing. One file per client. A meeting is its own file that links to the client. Small files are easier to find and to keep current, for you and for an agent.

3. Put a short block of fields at the top of every file. For example:

   ---
   type: Client
   description: Design partner since March. Monthly retainer, invoices net 30.
   tags: [Client, Business]
   ---
   

4. Write a context file at the root. One page on who you serve, what you sell, how you work and what matters this month. It’s the file every AI reads first (how to write it).

5. Tidy it every week. Twenty minutes: file the loose notes, update the fields, close what’s finished.

Step five is where most of these folders die. It works for a month. Then a busy week lands, the tidy gets skipped, and the folder turns back into a pile you have to read to use. The folder was the right idea. The upkeep is the part that doesn’t survive a busy month.

Where Oknola fits

Oknola is that folder with the tending done for you. You write, and Oknola types, tags and files what lands in it, keeps the structure from rotting while you work, and hands an AI agent only the tags you allow. The files stay plain markdown on your disk, so leaving is still copying a folder.

I run my own business from this structure, in a folder of about 34,000 files. What is available today is on the roadmap, and the demo shows the rest working on sample data.

Questions people ask

Is a company brain the same as a second brain?

They overlap. A second brain usually means your personal notes and ideas. A company brain holds the business itself, its clients, money and decisions, in a shape an AI agent can work with. In a business of one they live side by side, which is why keeping them separate matters.

Do I need special software?

No. A folder of markdown files and any text editor is enough to start. Software earns its place with the upkeep: filing, tagging and keeping the structure true while you’re busy.

Can ChatGPT or Claude read it?

Agents that work on files, such as Claude Code, Codex or Cursor, read a folder directly: open them in it and ask. Chat apps can be given the context file. The same folder serves all of them.

Is it safe to let an AI read my business files?

It is when you decide the scope. Give an agent the files its job needs and nothing more, keep private notes out of its reach, and prefer tools where every change lands as plain text you can inspect and undo.