If Your Company Brain Lives in the Chat, You Don’t Have One

Cyberpunk filing cabinet and open ledger in sharp focus while chat bubbles dissolve into static, with cash-flow and covenant overlays.

The new AI slide is not a chatbot. It is a company brain.

Femke Plantinga opened nine of them this week. The vendors disagree on the furniture. They do not disagree on the job. Every serious one does four things: get signals, remember, prune, and speak. That is not a product category. That is a control environment with better branding.

If you are the interim CFO walking into a PE-backed holdco, you already own three of those functions. They are called the bank feed, the close, and the pack. The interesting question is not whether to buy a brain. It is whether the fourth function — remembering — lives in a file a grown-up can find after the chat dies.

I have written before that AI which does not change Monday morning is theatre. This is the sibling test. If the model remembered it and the pack did not, it did not happen.

The chat is a scratchpad. The pack is the brain.

Most of what is being sold as a company brain is a conversational layer over a shared drive. Useful. Not memory. Memory is what survives a session reset, a staff change, and a buyer’s counsel asking what was true last March.

PE already had this argument, just with worse names. The trial balance is memory. The covenant workbook is memory. The charges register at Companies House is memory, which is why a 2006 charge that outlived the loan still counts. I made that point on the historic charge problem: the public record will be treated as true until you change it. A chatbot that “knows” the facility was repaid is not a change to the record.

So when a vendor shows you a brain that can answer questions, ask where the answer lives when the window closes. If the answer is “in the thread,” you bought a very expensive intern with amnesia.

Steal four rows. Do not build HQ.

Plantinga’s round-up is useful if you steal the table and refuse the cathedral. Four patterns earn their keep in a mid-market PE asset. The rest is headcount dressed as architecture.

1. Only store what a human meant to store.
mem0’s idea is rude and correct: memory is an explicit write, not a by-product of chatting. In finance terms, that is the difference between a journal and a hallway conversation. If a number mattered, it goes into the system of record on purpose. Models that “pick up context” will also pick up the joke, the stale forecast, and last Thursday’s working assumption that nobody recanted.

2. Facts get end dates. They do not get overwritten into fiction.
Zep / Graphiti put a clock on the graph. When a fact changes, the old one closes instead of vanishing. That is how you still answer “what did we think the EBITDA add-back was at signing?” without rewriting history. PE already does this when it is being honest: versioned packs, dated covenant cases, a debt schedule that can explain last quarter. A brain that only keeps the latest answer is a management team that shreds the old board pack.

3. Wrong answers become a fix, not a vibe.
Gorgias Cortex, in Plantinga’s telling, turns questions the system got wrong into pull requests that repair the nodes. That is the whole job of a decent close. Flux that was wrong is not a narrative problem. It is an open item. If your company brain cannot name the file that will be different tomorrow because today’s answer was wrong, it is not learning. It is repeating.

4. Nothing that hits lenders, auditors, or the board moves without a human.
Slite’s research is blunt on this: watch for stale, send the diff, wait for the owner. That is not bureaucracy. That is who goes to prison, or at least who gets the angry letter from the credit fund. I will let a model draft. I will not let it speak for the company.

Notice what I did not steal: Garry Tan’s email-into-git hobby brain, a 12,000-node markdown monastery, or a brand ontology for the marketing team. Those can be excellent for the people who built them. They are not a 100-day plan.

Map the four functions onto the holdco you actually have

Ignore the vendor map for a minute. In a typical mid-market PE asset the four functions already exist. They are just badly joined.

Signals. Bank actuals, order book, ERP, payroll, the covenant workbook, Companies House, the data room. If a brain cannot name the system of record it is reading, it is guessing with better punctuation.

Remembering. Files, not tokens. The test is ugly and fair: kill the chat. Can a new FD reconstruct the live covenant case, the open add-backs, and the three customer concentrations that actually matter? If not, you did not have memory. You had a demo.

Dreaming and pruning. This is the part everyone skips. Stale forecasts, dead SKUs, historic charges, old board actions that never closed. A brain that only accumulates is a shared drive with an LLM on top. The close is already a prune. Use it.

Speaking and searching. The pack, the lender pack, the IC memo. Speaking is not “the assistant said.” Speaking is a number a grown-up will own. Search is useless if it cannot cite the TB line, the clause, or the email that authorised the exception.

Join those four badly and you get the current fashion: a model that can write a fluent commentary on a late close. Join them well and Monday morning moves. That is still the only scoreboard I care about.

What to starve

Be rude about the rest, at least internally.

  • Chat as system of record. If the only copy of a customer concentration, a side letter, or an earn-out interpretation lives in a thread, it does not exist. File it or lose it.
  • A tenth brain. You already have ERP, a data room, a board pack, and probably three SaaS tools that each think they are the graph. Adding a “company brain” without killing something is how finance inherits the reconciliation of the assistants.
  • Memory without a clock. Latest-answer-wins is how add-backs become folklore.
  • Speaking without an owner. Auto-drafted board prose that smooths a hole in the pack. Pretty wrong is still wrong.

If a tool cannot name the system of record, the control owner, and the file that changes when it is wrong, it is a toy with an invoice. Same test as last time. Different slide.

The thirty-day test, memory edition

When I land in a PE-backed finance function I still do not start with a vendor bake-off. I start with the Monday morning stack, then I ask where the answers live:

  • What does the CEO actually ask every week, and which file is the answer in?
  • Which “everybody knows” facts are only in people’s heads — or worse, only in a chat?
  • What was true at signing that is no longer true, and can we still see the old version?
  • When the model is wrong, what artifact gets patched before the next pack?

Then we wire AI into those seams. Draft the flux. Rank the exceptions. Surface the stale. Do not let the conversation become the books. The interim job is not an audition and it is not a chatbot with a mandate. It is to make the record, the bank, and the pack tell the same story.

The point

Everyone is building a company brain because “chatbot” stopped sounding like strategy. Fine. The grown-up version was never mysterious. Get the signals from systems of record. Write down what you meant to remember. Close the facts that died. Speak only through something a director will sign.

If it only lived in the chat, it did not happen. File the fact. Then you have a brain. Until then you have a demo.

Mark Hendy is a PE-facing CFO and the founder of Tanous. Views his own.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *