Skip to the content

The AI BOSS method

What a business brain is, and how you build one

The brain is your knowledge, your rules and your record. The AI is the part that reads them.

Take the Readiness ScoreTwenty questions. About fifteen minutes. Free.

A business brain is three things you own

A chatbot is a window. The brain is what is behind it. Three things, kept together, that belong to the company.

  • What we know. The facts in your systems and the knowledge in your documents, emails and people, gathered so that they can be searched and read as one.
  • How we decide. Your rules. Who can approve what. When a customer goes on stop. The things that must be done the same way on a Tuesday as on a Friday, whoever is at the desk.
  • What we did. A record of what was asked, what was answered, what was decided and who agreed to it. Without this you do not have a brain; you have an oracle, and nobody should run a company on an oracle.

The AI model itself is not on that list. Neither is any particular screen, app or assistant. Those are how you reach the brain. They are not the brain.

The five tests

Five tests for anything that calls itself a business brain

  1. It starts from the truth. The facts come from your system of record, not from the AI's general knowledge and not from a copy somebody made last quarter. When the ledger changes, the brain's answer changes.Fail it and the brain is wrong.
  2. It shows its sources. Every answer comes with where it came from: this invoice, this email, this clause. An answer you cannot check is a rumour.Fail it and nobody will believe it.
  3. It says when it does not know. An AI left to itself will produce a confident answer to almost anything. A business brain is built so that, when the knowledge is not there, it says so. "I can find no record of that" is one of the most valuable sentences a system can produce.Fail it and one day it will mislead you badly.
  4. Rules decide, and people approve what matters. The AI may read, find, summarise and draft. It does not decide whether to pay the invoice. That is decided by a rule you wrote, which gives the same answer every time, and anything above the limit you set goes to a person.Fail it and you have handed the keys to a machine.
  5. You can leave. The knowledge, the rules and the record are held in a form you can take away. If you fell out with every supplier you have, the brain would still be yours.Fail it and you are back to renting.

The four parts of a business brain

Get these four right and it stops mattering very much which AI model you use, or which screen your people work in.

  1. A source of truth

    Your ERP, kept clean enough to trust. This is where the facts come from.

  2. Connections

    A way for data to move between the ERP and everything else you use, so the brain is fed without anyone retyping anything.

  3. A memory you own

    A store of your documents, your emails, your decisions and your know-how, held where you decide, which shows you where each answer came from.

  4. Rules and controls

    The decisions that must be made the same way every time are written down as rules. People approve what matters. And there is an off switch.

One question. One role. One hundred days.

Five steps, each with a definition of done, because a step with no definition of done never ends. Treat the day counts as a guide. What matters is the order.

  1. Step 1: Assess (Days 1 to 15)

    You do not start by buying anything. You gather your answers to the chapter exercises into one folder, then choose which question first. It matters to the business, it is asked often, and it is narrow: one role, two or three systems, one slice of data.

    Done looks like: One folder; one chosen question, written down with what a good answer contains; a named owner; and a list of who should and should not be able to ask it.

  2. Step 2: Connect (Days 15 to 40)

    Build the nervous system the question needs, and no more. Clean the slice. Build the two or three connections. Carry the permissions through. Make it fail loudly.

    Done looks like: A person can see, in one place, live facts from the ERP alongside the related documents for the cases in your slice; permissions are respected; and when you pull a cable out, somebody gets a message.

  3. Step 3: Remember (Days 40 to 65)

    Give the business its memory, for this one question. Load the documents, add the map between them, write down the lessons, and test it hard with thirty real cases and the people who do the job.

    Done looks like: For real cases, the system gives an answer with sources that the person doing the job agrees with, most of the time; it says so when it cannot; and you have a written list of why it failed on the rest.

  4. Step 4: Govern (Days 65 to 85)

    Until now the system has only answered. Before it is allowed to do anything, the controls go in: the rules as fixed logic, drafts and not deeds, limits the system enforces, a record it cannot edit, and an off switch.

    Done looks like: The rules are written, tested and signed off by the person responsible for the policy; every action is a draft that a person commits; the log shows who did what; and the off switch has been used once, on purpose, to prove that it works.

  5. Step 5: Extend (Days 85 to 100)

    Measure, honestly, including what did not improve. Listen to the people using it. Choose the second question by the same three tests, and go round the loop again.

    Done looks like: A one-page before and after for the first question; a second question chosen; and a date in the diary for the next review.