The Board
One structure for the whole business.
Every business runs a different shape. A sole trader is not a small version of a company, and a company is not a sole trader with more people. The Board fits all three, because the rule underneath it is the same one every time.
The idea
It mirrors the business you already have
The Board is an operating model, not another piece of software your team has to learn. It does not ask you to restructure anything. It takes the org chart you already run, owner at the centre, leads over their arms, admins keeping branches moving, and adds one layer underneath each branch: an AI agent with the right skills and the right connections for that branch, and nothing more.
This is not an AI takeover play. The point is making AI simple for everyday people, taking stress off the menial tasks, not removing jobs from the equation. People stay in every decision, and the system adapts to each person's comfort with computers rather than expecting them to adapt to it.
The rule
A layer exists only where a person already does that job
Where nobody does that job, its scope merges upward, and never silently. That is the whole model. The three shapes below are what the rule produces at three different sizes.
A branch is a function of your business, not a team of people. One person can stand in four branches. That is why this still works when the business is one person.
The whole board
Pick your shape, then pick any branch
Branch names, skills and connectors on this page are examples. The shapes are examples too: they are drawn to show how the rule behaves at three sizes, not copied from three real businesses. Select a shape, then a branch, to see its people, its skills and its connectors.
Chairs occupied: CEO, Branch Managers
Nobody runs several branches yet, so the Arm Lead chair stays empty and its scope sits with the owner. This is the smallest size where it matters who can see whose work, because the warehouse and the front desk are now different people.
Branch ManagerOperations
Branch ManagerCustomer side
The human line runs between every branch and its agent. Nothing the agent produces reaches a customer without a person approving it first.
Warehouse branch, wired
The people
- Admin
- Storeperson
- Dispatch lead
Each one has a profile: role, tools, tasks, comfort with computers.
Skills it runs
- Weekly report
- Quote drafter
- Quote red team
- File completeness check
- Meeting prep
- New starter answers
Named in your team's words, built once, run the same way every time.
Connectors
- Inventory systemread only
- Supplier inboxread only
- Team calendarread only
- Accounts exportread only
Write access only by your written request, per system.
Who sees what
Two fences, and only one of them depends on your size
The scope fence. An agent cannot reach a system outside its branch. The sales agent cannot see warehouse systems, at any size, including when the business is one person. This is wiring, not policy, and it is enforced in the build rather than on the honour system.
The visibility ladder. Which people can see whose work. This one only exists where the chairs are occupied. In a one person business there is nobody to keep apart, so we do not pretend otherwise and we do not sell it to you.
Enforced in the wiring, not on the honour system.
Layer by layer
The five layers that are always there
- 01CEOthe owner's chair
The centre of the model. Sets direction, sees the whole board, and has final say on anything that leaves the business. The structure exists so this chair gets a clear view without chasing ten people for it.
- 02Brancha function you already run
Sales. Marketing. Help desk. Warehouse. Accounts. A branch is a function of the business, not a team of people, which is why one person can stand in four of them. The model does not invent branches, it mirrors the subsections your business already has, in your own words.
- 03AI Agentone per branch
Each branch gets exactly one. It knows the branch's people through their profiles, speaks the branch's language, and takes the menial load: drafting, checking, summarising, preparing. It works underneath the people, never instead of them.
- 04Skillstrained procedures
The specific jobs an agent has been trained to run: draft the weekly report, argue against a quote before it goes out, check a job file against your own checklist. Built once, named in your team's words, run the same way every time.
- 05Connectorswired to that branch only
The wiring into the branch's real systems: inventory, email, calendars, accounts. Each connector belongs to its branch, so the sales agent cannot see warehouse systems. Every connection starts read only. Write access is a separate decision, made by you, in writing.
The two layers that come and go
- emptyArm Leadruns several branches
- occupiedBranch Managerruns one or two
Named for what they govern, not for a job title, because your business already has its own words for these people. Lead developer, operations manager, GM, foreman, supervisor: all Arm Leads in this model. Where nobody does the job, the chair is empty and its scope sits with the chair above.
The right people, the right tools
The system knows who it is working with
Before any agent goes near a branch, every person in it gets a short profile. Not surveillance, a working introduction: who they are, what they do, which tools they touch, and how comfortable they are with computers. A power user gets shortcuts, someone newer to this gets patience and plain language.
What this person is responsible for, in the team's own words.
The systems they actually touch day to day, so the agent meets them where they work.
The recurring jobs on their plate, which decides which skills their branch gets.
How they like to work with computers. The agent adapts its depth to match.
Principles
The rules the whole structure obeys
Every piece exists to take stress off real tasks. If it does not, it does not ship.
Smart systems streamline the workflow. People stay the voice, the judgement and the signature.
The structure adapts to different computer skill levels rather than expecting people to catch up to it.
Skills and connectors are matched per branch and per person, never issued as a blanket.
Output reads human because a human approved it, not because the AI is hidden.
The model is built to remove stress from tasks, not people from payroll.
How it lands
One stage at a time, each stage earns the next
The structure never arrives as a big bang. It rolls out on a five stage ladder with a stop condition on every stage. If a stage does not earn its keep, the rollout stops there and you have still bought something whole.
- Stage 0
The diagnostic
Map the branches, the people, the tools and the tasks. Stands alone and is worth having even if nothing else follows.
stop if: no clear wins found - Stage 1
Foundations and pilot
Accounts set up properly, policies on, one branch picked, volunteers only.
stop if: the pilot team does not want it - Stage 2
Shared knowledge
The business's own knowledge goes in, with one named curator keeping it honest.
stop if: answers are not being verified - Stage 3
Power users and connections
Skills built in your words. Connectors wired to real systems, read only.
stop if: time saved is not named out loud - Stage 4
Writes and self sufficiency
Write access where you have approved it in writing. Your team runs it without didodot in the room.
stop if: approval habits slip
Guard rails
What the structure will not do
It never contacts your customers
No automation ever messages a customer. Anything customer facing is a draft, and a person sends it or bins it.
It never writes without written permission
Every connection starts read only. Write access to any system is a separate decision you make in writing, per system.
It never certifies
The checking skills flag gaps against your own checklists. They refuse to declare a file complete or audit ready. For a regulated business, that refusal is the feature.
Your data stays yours
Organisation accounts with managed policy and audit logging. Your data is not used to train anyone's models, and what stays out of the system entirely is decided with you at stage 0.
Scope never moves without you saying so
If someone leaves and their branches roll up to whoever is above them, that is a conversation and a written confirmation, not a background change. Nobody inherits access to something they did not ask for.