004 · AI leaders · 1 November 2026
We automated the office, not the factory
Almost every conversation about AI in manufacturing is about the factory floor. At my company the floor already worked, and the bottleneck was the office, with me in the middle of it.
Almost every conversation about AI in manufacturing is a conversation about the floor. Machine vision, predictive maintenance, robots that pick things up. My company makes industrial displays. For us, the floor was already the part that worked.
What did not work was everything around it. A quote waiting for someone to write it. A supplier confirmation sitting unread for two days. Four separate threads, each needing the same person to look at it before anything could move.
That person was me. In a company this size, every message goes through the founder. Every handoff passes through one head, and that head has a fixed number of hours in it. You can hire your way around the problem, slowly and expensively. Or you can change the shape of the office.
We did not automate the factory. We automated the office.
The shape
Office work is now done by a team of AI executives. Each holds a domain the way a director would: sales, finance, production coordination, operations, marketing and monitoring. Above them sits a chief of staff role. It chairs a weekly meeting and keeps the whole thing pointed in one direction.
They are not chatbots. Each role wakes at set intervals, works through its own queue of pending work, acts and stops. If something comes in from outside, whether a memo from another role, a task assigned to it or an answer it was waiting for, it wakes at once. Silence is an acceptable outcome. A role that wakes to an empty queue goes back to sleep.
Four shared pieces hold it together. We built all of them ourselves.
- A message channel. Every message has an author and nothing is lost.
- A decision gate for people. When a role needs a decision only a person can make, it files a structured question. The answer goes straight back into that role’s queue and the work moves on. One topic per question. We learned that rule the hard way.
- A shared task board. Any AI executive can move a card forward with evidence attached. Only a person marks a card as done. That checkpoint does not bend.
- A calendar that gives time discipline: what is due, what wakes when, what is late.
On top of it all sits a written constitution, ratified by the owner. It says which decisions the AI executives make on their own and which stay with people. Without a document like that, agents quietly fill the gap with whatever their instructions vaguely implied. A person then ends up settling edge cases forever.
What actually changed
On an ordinary weekday morning, before anyone had sat down at a desk, three separate loops opened and closed inside the team without any person relaying anything between them. One of them: on the shop floor, someone confirmed an incoming goods check on a card. The production role woke, read the confirmation, logged it, closed the card and moved on.
That is the first value of the whole arrangement. It is smaller and more boring than the usual pitch. My attention is no longer the transport layer. Work that used to wait for someone to read a message and pass it on now gets done while that someone is asleep.
Second, the team began to extend itself. Without being asked, the roles built a review of European public procurement notices. It runs twice a day and sends matching tenders straight to the sales role. Dozens of improvements like these have come in, from almost every role.
The third change turned out to matter most. Every message, every move on the board and every answered question carries a timestamp and an author. That is not a rule anyone has to remember. It is a property of the system. You cannot have an undocumented conversation on a channel that writes everything down.
And the limits hold. No AI executive moves money. No AI executive hires anyone. Nothing leaves the company unless a person sends it or clearly approves it. Those limits are built into the tools, not written into instructions in the hope that they are followed. A limit that exists only in an instruction is not a limit.
What it cost
A piece like this is worthless if it only contains the parts that make us look good.
One night the whole team went silent for eleven hours. A shared authentication token expired and nobody had scheduled its renewal. Every role failed at the same moment, in the same way. I noticed the next morning and re-authenticated by hand. It was the ordinary gap that appears when a system grows faster than its checklist.
And the first version had to be thrown away. It was made of thirty-odd hand-copied services that drifted apart the moment anyone fixed something in one of them. The current platform exists because the first one could no longer be maintained. That is not a footnote. It is the real cost of getting here.
Whether the shape fits you
Our solution cannot be copied, because it is wired into our own systems and our own mess. The shape can.
It fits a company where a small number of people carry a disproportionate share of the decisions. Where most of the daily work is coordination, not decision-making. And where one person’s calendar is the real limit on how fast anything moves.
The interesting decision was never which model to point at the inbox. The interesting decision was which decisions we were willing to hand over, and which we were not.
If you want to try it, I think four things are non-negotiable. A written constitution. A real message channel. A decision gate that is not email. And the discipline to say no when the AI executives should not be the ones deciding.
Next