Foundations
How to explain an AI employee to your board
Tobiloba Odejinmi · 8 Jan 2026 · 6 min · 1,305 words
Direct answer
Explain an AI employee as a named worker on one written process. Give the board a cost, an owner, a log, a miss rate, and a human gate. Do not explain it as a platform or a headcount story: they need the public downside and the person who picks up the phone, and if you cannot say that in five minutes you are not ready.
- Use worker language, not product language.
- Show one process and a kill switch, not a catalog of tools.
- Put cost next to the person who still sits the gate.
- Answer law and miss replay before anyone asks.
How do you explain an AI employee to a board?
You explain a hire. Not a vision. A hire has a name, a job, a manager, and a way to fire them. 'We are adopting agents' is a vision. 'We hired a worker on replacement requests, Amina owns the rejects, we can turn it off' is a hire.
I have sat across from people who write large cheques. They get bored when you talk about models. They wake up when you talk about cost, downtime, and whether one person can explain the system. That was true when we sold Insurpass. It is true when the system includes an AI employee.
Keep the metaphor boring on purpose. Employee is already a stretch. Do not add 'digital workforce' or a cartoon org chart. Stretching the metaphor is how you inherit HR questions you cannot answer.
What slide do they actually need?
One page. Process name. Volume per week. What the worker does. What it must not do. Owner. Backup. Cost for the first workflow. Date you will show miss rate.
A second page only if they ask how this compares to a chatbot, a copilot, or RPA. Three sentences. Chatbot answers. Copilot helps a person type. RPA clicks a stable path. This hire finishes a case or stops. Then sit down.
Do not bring a survey as the reason. BCG's 2026 numbers are useful in the appendix. 30 percent in workflows. Half without clear governance. 61 percent who think half their job moves in three years. Use those to show you are not chasing a crowd. Use them only if someone says 'everyone is doing this'. Everyone is not.
How do you talk about cost without a fantasy ROI?
Show the hours on the first pass today. Show the cost of the worker. Show the cost of the person who remains on the gate. The saving is hours if the miss rate stays inside a number you wrote down. If you cannot write the number, you cannot write the saving.
I charge $5k for one workflow, $7.5k for the week, and $15k and up for several. That is a project cost, not a fairy-tale multiple. Your ongoing cost is usage plus the rota. Boards understand projects. They should be suspicious of multiples invented in a deck.
If a member wants a five-year NPV, give them a one-quarter experiment and a kill switch. You can do NPV after you have a miss rate. Doing it before is fiction with a discount rate.
How do you talk about risk and law?
List the closes the worker is forbidden to take. Money out. Medical language. Legal letters. Hiring decisions. Credit decisions. Say who takes those. Say how fast.
If anyone wants AI on recruiting, tell them the law did not step aside. NYC Local Law 144. EU AI Act high-risk for recruitment. Civil rights law with no AI exemption. That is enough. You do not need to perform a seminar. You need to show you will not be the case study.
IBM's 9 percent Frontier Firm figure is a useful cold shower if the room is giddy. Human-led, agent-operated is rare. You are not behind if you are careful. You are behind if you have no owner.
- Forbidden closes, written.
- Owner and backup, named.
- Log that can replay a complaint.
- Off switch that one person can use.
What will they ask that you must answer in one sentence?
What happens if it is wrong? A person takes the case from a file, not a chat dump, and we correct it before the next batch.
What happens if the vendor dies? We still have the SOP, the log, and the off switch. The pile returns to people. We have done that drill.
What happens if this works? We add a second adjacent process. We do not buy a platform on the same day. We do not announce a headcount freeze on the same day.
If you need a paragraph for any of those, you are not ready. Write the sentence. If you cannot, the work is not a board topic yet. It is a homework topic.
What should you refuse to promise?
That the company will run itself. That the 61 percent who expect half their job to move are a plan. That governance will appear after the pilot. That hiring law is someone else's problem. That you need this because a competitor posted a screenshot.
Promise a smaller pile on one process, a miss review, and a date. That is a promise you can keep or fail in public. Boards can live with a fail they can see. They cannot live with a story that had no owner.
If you want help turning that into a week of work instead of a quarter of slides, the offer is one process. I will tell you if the process is not real. That sentence is also useful in a board pack.
Print the one-pager the night before. If you cannot print it because it is still a deck of twenty, you are not explaining a hire. You are explaining a wish. Stay home and cut the deck.
Who should speak in the room?
The owner of the process, not only the person who likes AI. Boards can smell a champion with no queue. Let the person who already takes the angry call say what the worker will and will not do. Their voice is the risk answer.
Engineering can speak to the log and the off switch. Finance can speak to the project cost and the rota cost. If those two people have not met, do not schedule the board slot. The meeting will become a vocabulary class.
I would not send a vendor to present the hire. Vendors present platforms. You are presenting one worker. If a director wants a vendor later, fine. First they need your sentence about the pile.
After the meeting, send the one-pager again with the date you will return with a miss rate. Silence after a yes is how projects swell. A dated return is how they stay one process.
Questions people ask
How do I explain an AI employee to my board?
Say it is a worker hired for one process. It takes a queue, follows a policy, writes a log, and escalates. Then show cost, owner, and what happens when it is wrong.
What will the board ask first?
What it costs, what it replaces, and what the downside is if it is wrong. Have those three answers without a second slide.
Should I promise headcount savings?
Promise a smaller first-pass pile and a named reviewer. If you promise fewer people before you have a miss rate, you are selling a hope. Boards remember hope when it fails.
How do I talk about risk without killing the project?
Name the gates. Name the off switch. Name the law that already applies if you touch hiring or credit. Risk that is specific sounds like management. Risk that is vague sounds like you did not look.
Do I need a vendor comparison?
Not in the first meeting. You need a process. Vendors are how you avoid talking about the pile. Bring a vendor when the SOP exists.
Written by
Tobiloba Odejinmi
Head of Engineering at 10mg Health. I have run engineering at Zeeh Africa and sold Insurpass and Shopl. I still write the code. If you have one process that still runs on people copying things, we can look at it in thirty minutes.
