The Agentic Enterprise
Agent demonstrations finish in a minute. Enterprise work waits days for approvals, crosses several systems and needs someone to answer for the outcome. This five-part series explains what changes when agents do real work across an organisation: why durable state comes before ownership of any long-running process, why delegating between agents never delegates accountability, why an HR service agent is mostly an integration project, why a capability architecture beats an AI logo landscape, and what belongs in an agent toolkit. One fictional South African food manufacturer, Karoo Mills, carries the examples, and every figure is illustrative.
5 articles
- Part 1An agent without durable state cannot own a long-running processMost agent demos finish in a minute. Real business processes wait days for approvals, cut-off dates and other people. Part 1 of The Agentic Enterprise explains why an agent that keeps its progress only in memory cannot own that kind of work, and what checkpoints, thread identity and resumable steps change.10 min read
- Part 2Delegation does not remove accountability: multi-agent systems in the enterpriseSplitting one agent into an orchestrator and several specialists can make each part simpler. It also creates handoffs, and every handoff is a place where context is lost, authority widens or nobody owns the outcome. Part 2 of The Agentic Enterprise sets out the accountability chain a multi-agent design needs.6 min read
- Part 3An HR service agent is an integration projectAn employee asks about leave on WhatsApp and gets a correct, personal answer in seconds. Behind that answer sit a messaging channel, identity verification, a policy library, the HR system, a case system and a route to a person. Part 3 of The Agentic Enterprise shows where the real work in an HR agent lies.6 min read
- Part 4Capability architecture, not another AI logo landscapeAI ecosystem maps arrange hundreds of product logos into categories. They are useful for noticing what exists and nearly useless for deciding what an organisation needs. Part 4 of The Agentic Enterprise replaces the logo map with a capability map that names jobs, dependencies, status and owners.6 min read
- Part 5What belongs in an agent toolkit, and what should stay optionalAgent tooling changes monthly, and lists of essential frameworks, memory stores and browser tools age quickly. Part 5 of The Agentic Enterprise separates the few capabilities every production agent needs from the ones that must earn their place, and gives a five-gate test for adding anything new.5 min read
Working through any of this in your own organisation?
These articles come out of delivery work rather than theory. If the problems in this series look familiar, a short scoping conversation is usually the quickest way to work out what is worth doing first.
Talk to CloudNala