The company brain
A brain and an automated system are different products
Last updated
Short answer
A company brain is asked questions and given jobs by people, and it answers from what the company knows. An automated system runs a defined sequence from a trigger and brings a person in when judgement is needed. Both are useful and they coexist well. Building one when you needed the other is common, expensive, and usually diagnosable in a single conversation before anything is built.
The distinction
Two shapes, one word
Almost everything sold as AI for business is one of two shapes, and the vocabulary does not distinguish them, which is how companies end up commissioning the wrong one competently.
Asked by a person
Somebody has a question or a job. They ask, in the place they already type. The system answers from the company's own material and live data, or carries out a job it has been taught. It starts when a human starts it, and there is no fixed sequence.
Started by an event
A form is submitted, an invoice arrives, a status changes. A defined sequence runs: check this, update that, notify them, and stop for approval at the point where judgement is required. Nobody asks for it. It happens.
The useful test takes one sentence and no technical knowledge.
If you can name the event that should start it, you want an automated system. If you can only name the question people keep asking, you want a brain.
Sorting your list
Which problems belong to which
Most companies arrive with a list that mixes both. Sorting it is usually the most valuable half hour of the first conversation.
| What you said you wanted | The shape it needs | Why |
|---|---|---|
| Stop people asking me the same question | Brain | There is no trigger. There is a question and no reliable place to get the answer. |
| Chase overdue invoices automatically | Automated system | The trigger is a date passing, and the sequence is the same every time. |
| Draft replies the way our best person writes them | Brain | It is a taught job invoked on demand, not a fixed sequence. |
| Route incoming enquiries to the right team | Automated system | The trigger is arrival, and the decision is a classification. |
| Find what we agreed with this supplier last year | Brain | It is a question whose answer lives across correspondence and documents. |
| Update the record whenever a status changes | Automated system | The change is the trigger, and no judgement is involved. |
| Get new staff productive faster | Brain | What they need is the ability to ask, at the moment they are stuck. |
The rows in the middle column are not a preference. A question with no trigger cannot be automated, and an event-driven sequence that waits for somebody to ask for it is not automation, it is a form.
The realistic architecture
How they coexist
They share the same foundations, which is why building one makes the other cheaper rather than redundant.
The material a brain answers from is the same material an automated sequence needs in order to make a correct decision. The connections to your existing systems are the same connections. The rule about which people can approve what is the same rule. A company that builds the shared system first usually finds the automated sequences it wanted afterwards are mostly a matter of deciding on triggers, because the difficult and unglamorous part, the material and the connections, is already done.
The failure mode
The expensive version of getting this wrong
The mistake rarely looks like a mistake while it is being made. It looks like a successful project that nobody uses.
- An automated sequence built for a questionIt fires on a trigger nobody cares about, produces output nobody asked for at that moment, and gets switched off within a quarter. The post-mortem records it as a technology failure. It was a diagnosis failure.
- A shared system built for one broken processIt answers questions correctly about a process that still does not work. The people whose pain was the process conclude the system is useless, and they are not entirely wrong.
- Both at once, as a first projectWhen it underdelivers, and something always underdelivers first time, you cannot tell which half was wrong. The organisation learns nothing except that this does not work here.
- Either one built on material nobody trustsBoth shapes reproduce whatever is in the source. Neither fixes a document set that is out of date, and both make the consequences arrive faster and with more confidence.
Frequently asked questions
Which should we build first?
Whichever addresses a job your people repeat weekly and dislike. If that job starts when somebody asks, it is one shape; if it starts when something happens, it is the other. The question of which category is more valuable in general has no useful answer.
Can one system do both?
In practice they end up connected, because the material and the connections are shared. Keeping the distinction clear still matters when scoping, because the two are evaluated differently: one on whether people ask it things, the other on whether the sequence completes correctly without supervision.
Is an automated sequence cheaper to build?
Usually simpler to specify, because the steps are known in advance. It is also more brittle, because a change in any connected system breaks a fixed sequence in a way it does not break a system that is asked questions.
We were sold something described as an agent. Which is it?
The word covers both and has stopped carrying information. The useful question to put to the supplier is what starts it: a person asking, or an event occurring. Whichever they answer tells you what you are buying, regardless of what it is called.
Do we need both eventually?
Most companies of the size where this pays for itself end up with both, in that order or the reverse. The point of separating them is sequencing rather than choosing: doing them one at a time is what makes it possible to tell whether either worked.
AINORA, MB builds and operates AI systems for companies from Vilnius, Lithuania. It designs company brains: shared internal systems that hold an organisation's own knowledge, connect to the tools it already runs, and carry out the jobs its people repeat, with access rights enforced per person and hosting in the EU.
Bring the list, unsorted
The first useful conversation is sorting what you already want into the two shapes. That is often enough on its own to change what gets built first, and it costs you half an hour.