The Hybrid Intelligent Enterprise.
AI agents and people in one team, under one set of rules. Hybrid here means AI and people. Not office and home. Not hybrid cloud.
The definition
A company where AI and people work together as first-class citizens.
Both do the work. Both make decisions. Either one can hand a task or a decision to the other, in both directions, as long as they say why and how. Together they make better decisions, faster.
- One named ownerEvery task and decision has one owner, AI or person. Never "the system".
- Work moves both waysAI can pass a decision to a person. A person can pass one back to AI.
- Both reasons are keptWhoever passes work says why. Both notes are stored side by side.
- Authority is earnedA limit widens only when the record proves it should.
- No one checks their own workMaker and checker are never the same teammate.
- High-risk calls escalateTo a manager, then to leadership. Nothing is lost.
Five things an Intelligent Enterprise is not
One score cannot rate a company that makes thousands of different decisions a day.
Agents with no named owner are sprawl, not intelligence.
AI and people sit on the same org chart, in the same kinds of roles.
A vendor governs the agents on its own stack.
A policy is where governance starts.
AI on the org chart
Seven questions. Seven answers.
Next to your people. Same roles, same rules. Try the mix below: any seat can be an AI agent or a person.
The agent prepares the case. Your person makes the call and writes why. A separate audit agent checks the decision against your rules.
Where does AI sit on your org chart?
Inside a team, next to your people. Every team has several roles: doing the work, deciding and checking. Any role can be an AI agent or a person. AI drafts and a person refines. A person does the work and AI checks it. One AI agent checks another.
How does AI earn its place?
Like a new employee. It learns your processes and history, not the vendor's defaults. A teammate checks every task at first, and both record why. It earns authority one task at a time, only when its track record earns it.
What goes into AI's job description?
The same six things as your people's: responsibilities, decision rights, handoffs, escalation, limits and checks. Who checks my work? Never me.
Who does AI report to?
The same chain and rules as your people. Escalation goes by complexity and impact: team member, then manager, then senior leaders. Cost is estimated before every task, with a limit no member can exceed.
What does the org chart remember?
Every decision, with its reason, in one place in your environment. It records the work, not surveillance of people. Early on it feels like extra effort. Over time it becomes your enterprise memory.
What changes when AI is on the org chart?
Nothing is lost at handover. No one checks their own work. Every decision and reason is recorded. Cost is known before the work. Memory stays through every change of vendor.
What kind of platform should run this team?
One built for the whole team, not one agent. Vendor neutral. In your environment. No lock-in. The same rules for agents you buy, agents you build and your people.
Governance
One set of rules for AI and people, on your side.
Every member has a job description
Every decision has one named owner, never "the system". No one checks their own work. Authority is earned through a track record, one task at a time.
What the job needs. Nothing more.
Which systems each role can use, what it can do in each (view, create, change or approve) and which data it can see. Every AI agent gets its own login, with the access of its role, not of the person who set it up.
Named people, limits, and memory
Escalation to named people by complexity and impact. Cost estimated before the work runs, with a limit. Every task and decision recorded with the reasons of AI and people, unchanged and open to your auditors.
- 03Senior leadersAbove 2.5M
The largest or riskiest calls. Nothing is lost on the way up.
- 02ManagerUp to 2.5M
Higher value or more complex, as your rule sets out.
Reply within 4 hours · silence is never a yes - 01Team memberUp to 200K
The named person for this kind of case. Routine exceptions stop here.
Above this limit · passed up with the reason
- Refunds above 50K need a person
- No agent sees payroll
- Approves alone up to 200K
- Asks Priya Nair above that
- Never changes a scheme
Discover every agent
You can't govern what you can't see.
LeafCraft connects to your ecosystem and finds every agent you run: the ones vendors shipped inside your software and the ones your teams built. Then each one gets an owner, comes under your rules, or is removed.
How to put it in place
Eight steps. One process at a time.
This is how we run it with every customer, one process at a time.
- Name one senior owner for the rulesWith the CIO, the business head and risk at the table. The owner reports to the board. Not IT alone.
- Pick one processMark each role as an AI agent, bought or built, or a person.
- Write the job descriptionsGive every role a checker and an escalation path. Give every decision one named owner.
- Set access per roleSystems, actions and data. Start narrow. Remove access the day a role or agent ends.
- Set cost limits before work runsPer role and per task, charged to a business budget.
- Start the record on day oneEvery task, decision, handoff and access change, with the reasons of AI and people.
- Widen authority only when the record earns itNarrow it when the record shows mistakes. When a rule is broken: pause, escalate, and record why.
- Review against the record on a fixed scheduleKeep your rules and record in a layer you own, independent of any one vendor.
Your 5-point check
Is AI really on your org chart?
Tick the ones your company has today. Then pick one process and ask: which step is missing, and what is stopping it?
Tick each one you can answer yes to today.
Talk through your gapsEight steps to close the gapsRent the capability. Own the judgement.
Not how much AI. Who decides, and who checks. Let's look at one of your processes together.