You Cannot Automate Your Way Out of a Mess You Built Yourself

Why agentic AI is the final exam for every process you never bothered to fix

Organisations everywhere are racing to deploy AI. The pitch decks are beautiful. The business cases look solid. The enthusiasm is real. The strategy houses make slide decks like crazy. Yet… Somewhere between the boardroom presentation and actual production, something breaks.

Spoiler: it was already broken before AI arrived.

The fundamental problem is not AI. The fundamental problem is that people assume AI is a cure. It is not. AI is an amplifier. When you amplify broken, you get broken faster. You get broken at scale. You get broken automatically, around the clock, without anyone pressing a button. And it will cost you a crazy amount of money.

REPEAT: AI does not fix broken processes. AI executes them at speed.

The seductive lie of automation

There is a persistent myth in enterprise transformation. The myth says: once we automate this, things will get better. Efficiency will rise. Errors will drop. People will be freed up for higher value work.  Well, dream on.

This myth survived mainframes, ERP rollouts, and RPA deployments. Now it survives AI. Each wave makes the same promise. Each wave exposes the same underlying problem. The process was never clean. The data was never structured. The definitions were never agreed upon. And internal politics are a killer on top of that.

AI is the latest in a long story of technological promises. It is also the hardest test so far, because agentic AI does not just execute a defined task. It reasons, it decides, it acts. Give it a broken starting point and it reasons its way into a very confident wrong answer. Give it ambiguous inputs and it makes a choice, any choice, and presents it as fact.

That is not an AI problem. That is your problem dressed up in a language model.

And here is the uncomfortable truth: most organisations are not ready. Not because the technology is immature. Because the organisation is immature. The processes, the governance, the shared understanding of what things actually mean inside the enterprise. That is where the gap sits. Process minded organizing is more then just having a process; it is living it.

What systemic thinking actually means

Most organisations lose the plot here. They think about systems as technology stacks. A CRM, an ERP, a procurement platform, a contract management system. Those are tools. They are not systems in the meaningful sense.

A system, in the real sense, is a set of interacting elements working toward a purpose. Your organisation is a system. Your supply chain is a system. Your customer relationship is a system. Every one of those systems sits inside a larger ecosystem, with its own rules, pressures, and feedback loops.

Systemic thinking means you start by understanding how things actually connect before you change anything. Not how they are supposed to connect on paper. How they actually connect in practice. Who talks to whom. Where information actually flows. Where it gets stuck. Where decisions actually happen versus where the process map says they happen.

The difference between the map and the territory is where most transformation projects die. Teams design for the map. They deploy into the territory. They discover the gap too late, too expensively, with a consultant standing nearby saying it can be fixed in phase two.

Systemic thinking closes that gap before the project starts. It is not theoretical. It is operational discipline. Without it, you are building on sand.

The ecosystem is not optional

Your organisation does not operate in isolation. It is part of supplier ecosystems. Regulatory ecosystems. Customer relationship ecosystems. Industry ecosystems. Every one of those external systems imposes requirements, constraints, and expectations on how your internal processes need to work.

When you design your processes, and then your technology stack on top of those processes, you need to design with the ecosystem in mind. Not just your internal needs. The entire connected web of obligations and interactions.

This matters enormously for AI. An agentic AI making procurement decisions without understanding supplier relationship constraints is a liability. An AI managing contracts without knowing the regulatory context is a compliance risk. An AI supporting customer interactions without awareness of the full relationship history is, frankly, an embarrassment.

External systems are not just constraints. They are information sources. They define what good looks like. They define what legal looks like. They define what the customer actually expects. Your AI needs to be designed with those definitions in mind from day one, not as an afterthought in the final sprint.

The ecosystem is not background noise. The ecosystem is the context in which your AI either adds value or causes damage.

The language problem nobody talks about

Here is the part that kills more AI projects than any technology failure ever does. Organisations do not speak a common language.

The word "value" means seventeen different things across seventeen different departments. Finance calculates value. Procurement negotiates value. Sales promises value. Operations delivers value. Legal protects value. None of them is wrong. None of them is the same.

Risk is even worse. Risk is a container word. People throw everything into it. Financial risk, reputational risk, delivery risk, compliance risk, relationship risk. When someone says "we need to manage risk", what do they actually mean? Reduce probability of loss? Protect contractual position? Ensure regulatory compliance? All of the above?

Now imagine feeding that ambiguity into an AI model. The model processes the word "risk" based on patterns in its training data. But your "risk" is enterprise-specific. Your "risk" sits inside your specific industry context, your specific contractual framework, your specific organisational culture.

Without a uniform language model, meaning a shared, agreed, documented definition of every key term in your enterprise context, AI does not know what it is actually talking about. And neither do you, although you have been pretending otherwise for years.

This is not a technology problem. This is a governance problem. It requires humans to sit in a room and agree on what things mean. It requires that agreement to be written down, maintained, updated, and used. Every team. Every process. Every AI deployment.

That work is unglamorous. That work is absolutely essential.

Rules of engagement: who decides what

Every process has implicit rules. Someone decides. Someone approves. Someone escalates. Someone is accountable when things go wrong. These rules of engagement exist in every organisation. The question is whether they are explicit or whether they live only in the heads of experienced people.

When those rules live only in heads, they die when people leave. They vary when different people apply them. They create inconsistency, dispute, and friction. That is a serious problem in any process. It is a catastrophic problem in an AI-driven process.

Agentic AI needs clear rules of engagement. Not vague guidelines. Not general principles. Clear, documented, tested rules that define what the AI does, what the AI does not do, when it escalates, who it escalates to, and what happens when an edge case appears.

If your rules of engagement are unclear for humans, they are unworkable for AI. Full stop.

Writing those rules forces a conversation that most organisations have never had. It forces agreement on authority. On accountability. On what good looks like. That conversation is uncomfortable. It is also the conversation that separates AI that works from AI that causes expensive problems at impressive speed.

Technology fits your systemics. Not the other way around.

This is the part that frustrates every vendor in the room. It is still the truth.

Technology is a tool. Tools serve purposes. Purposes exist inside processes. Processes exist inside systems. Systems exist inside ecosystems. That is the sequence. The only logical sequence.

What happens in practice? A vendor demonstrates an impressive platform. The demo looks clean. The use case looks familiar. Leadership gets excited. The purchase happens. Then the implementation team arrives and discovers that the process the tool was designed for does not resemble the process the organisation actually runs.

Now a choice appears. Change the process to fit the tool. Or configure the tool to match the process. Most organisations choose the first because it is faster. They call it standardisation. It is not standardisation. It is cutting corners while calling them corners.

The right sequence: understand your systems first. Document your processes. Define your language. Specify your rules. Then select and configure technology that fits that foundation. This takes longer upfront. It saves enormous time and money downstream. It is the only foundation on which agentic AI actually delivers what the business case promised.

When the rubber meets the road

Here is the punchline. It is not funny, even with a smile.

Your business case for agentic AI looks fantastic. The ROI calculation is impressive. The efficiency gains are real on paper. The competitive argument is sound. The board approves. The budget is allocated. The project starts.

Then the rubber meets the road.

The AI encounters a process that nobody documented properly. It hits a term nobody defined consistently. It faces a decision nobody specified. It acts on data that means three different things in three different systems. It escalates to a workflow that exists in a diagram but not in reality.

The output is wrong. Or inconsistent. Or legally exposed. Or embarrassingly poor quality at a speed that is genuinely impressive.

The problem is not the AI. The problem was always the foundation.

No systemic thinking means no coherent process. No coherent process means no clean inputs. No clean inputs means no reliable AI. No reliable AI means your business case is worthless the moment it is tested in real conditions. That is not a future risk. That is the current reality of most enterprise AI projects today.

The projects that succeed share one characteristic: someone did the hard foundational work first. Someone mapped the systems. Someone agreed on the language. Someone documented the rules. Someone ensured the technology served the process, not the other way around.

The organisations that skip that work are not deploying AI. They are deploying expensive confusion at scale.

Fix the foundation. Define the language. Document the rules. Deploy the AI.

In that order. Every time.

Arjen van Berkum 

The Borders Have Moved, and Leadership Has Not Yet Caught Up

This is a story about a potential Greek tragedy waiting to unfold. I analyses some causes, adresses some elements but in the end it is a call to action for leaders. 

For decades, the working assumption inside most organizations was simple and  comfortable. You managed what was inside the walls of the shop. You set the targets, you built teams to execute, you monitor performance against internal metrics. As long as the internal machinery ran well, you could make a credible argument that you were doing a great job. That assumption is now genuinely dangerous, not because the world became more complicated overnight, but because leadership in many organizations still operates as if those walls are intact and sovereign and therefore not an issue. Dream on!

The borders of organizational responsibility have expanded, shifted, and in some cases dissolved altogether. The pace at which this has happened has far outrun the capacity of traditional leadership information models to keep up, yet this is not yet part of the average leadership MBA. What happens at the edge of your supply chain, at the boundary between your organization and the world it operates in, matters just as much as what happens in your boardroom. I might argue that matters considerably more because you are freaky dependent on others.

The supply chain conversation has for too long been treated as a logistics and procurement problem, something appropriately handed to operational staff and monitored through a spreadsheet dashboard with a convenient traffic light system. Senior leadership glanced at delivery lead times and unit costs, occasionally panicked when a key supplier went under, and considered that sufficient oversight. That era is over. What sits beyond the organizational boundary is no longer a set of transactional relationships that can be managed at comfortable arm's length. It is a web of interconnected risks, each one capable of transmitting shock waves into the core of your business in ways that cannot be absorbed by a revised procurement policy or a hastily scheduled supplier review meeting. The complexity is not the problem. The problem is that most leadership structures were never designed to see it. So stop treating procurement as a cost savings center.

Consider what that actually means. ESG risk alone has fundamentally rewritten what leadership must understand about its supply base. Regulations such as the Corporate Sustainability Due Diligence Directive in Europe are not aspirational guidelines for organizations that care about optics. They carry legal weight, and they require organizations to demonstrate that they know what is happening not just with their direct suppliers but several tiers deep into those suppliers' own supply chains. If a company three steps removed from your organization is using labor practices that violate basic standards, or sourcing materials through channels that create environmental liability, the reputational and legal exposure can land at your door regardless of how many layers of contract separate you. The contract you signed with your immediate supplier does not insulate you from that liability. In many jurisdictions and under many emerging regulatory frameworks, it actually defines the extent of your responsibility.

Geopolitical risk has become similarly impossible to quarantine in a separate analysis function. The tensions between major trading blocs, the fragility of certain raw material supply lines, the imposition of tariffs and export controls with minimal notice, these are not abstract macroeconomic concerns for economists to debate at industry events. They are realities that determine whether your production capacity holds next quarter and at what cost structure. When a critical component becomes suddenly unavailable because of a diplomatic deterioration between countries that had no geopolitical relevance to your business model three years ago, the question leadership will face is why no one was tracking that exposure. The honest answer, in most organizations, is that nobody was structurally responsible for it, because the governance model was built for a more predictable world.

Client default risk is another dimension that tends to get parked in the finance function and treated as a credit management problem, largely disconnected from the commercial relationship management function. But client default is rarely an isolated financial event. It is usually the downstream effect of a chain of deteriorating conditions, sector stress, regulatory pressure on the client's own business model, shifts in their customer base, contractual obligations they can no longer fulfil, and leadership changes that affect strategic direction. When you look at client default through the combined view of contract management and account health over time, you start seeing the warning signals earlier. The problem is that those signals are typically scattered across separate functions that do not share a common information architecture or reporting rhythm, which means by the time any coherent pattern is visible to anyone with the authority to act, the situation is already genuinely difficult to recover from.

Regulatory pressure deserves particular attention because its velocity has increased to a degree that most compliance functions were not designed to handle. Governments and supranational bodies are legislating at pace, and the intersection of those regulations with existing commercial contracts is becoming a specialist discipline in its own right. Standard contract terms that were entirely adequate two years ago may now create compliance exposure that neither party anticipated when they signed. Leadership cannot be expected to read and synthesize every regulatory development across every jurisdiction in which they operate, but they absolutely can and should be expected to have a governance structure that surfaces the contractual and commercial implications of those developments before they materialize as a problem rather than after the damage is already visible.

This is precisely where the information challenge for leadership lives, and where almost all organizations are genuinely failing. The answer is not to add more reports to an already overloaded inbox, more dashboards, more data without interpretation. The answer is aggregation, standardizing, crossfunctional and coherence. Leadership needs to understand the total picture of organizational exposure and performance across the entire commercial relationship lifecycle, on both sides of the equation. And that requires something that most organizations have still not properly built or invested in seriously: a connected information architecture that draws from delivery performance, contract management, relationship health, sector dynamics, and portfolio strategy into a single coherent view that enables decisions to be made with appropriate context and appropriate speed. The absence of that architecture is not a technical problem. It is a governance problem, and ultimately a leadership problem.

Contracts sit at the foundation it is worth being clear about that. They are the legal and operational recordings of every commercial commitment the organization has made or received. They define what is owed, when, under what conditions and with what consequences when those conditions are not met. Ignoring them therefore treating them as administrative (usually pdf in an inbox) artifacts after signature, is one of the most expensive habits organizations maintain yet fail to see. Contracts alone are not sufficient for leadership-level insight, and they were never meant to be. They need to be read in combination with the relational, financial, and strategic layers that surround them. A contract with a financially stressed client in a sector under regulatory pressure in a geopolitically unstable region carries a fundamentally different risk profile than a contract with identical commercial terms in a stable context. Leadership needs to see that difference structurally, not infer it from instinct.

On the sales side of the business the chain runs from delivery through contract management to account management, through sector management and into product and portfolio management. It describes a continuum of commercial stewardship and continuity. Each function holds a piece of the picture. Delivery knows what is actually happening operationally. Contract management knows the legal and financial commitments and whether they are being honoured. Account management understands the relationship health and the client's evolving intent. Sector management reads the market dynamics that affect the client base as a whole. Product and portfolio management shapes what the organization offers and where it is positioned strategically. When these functions share information and operate within a common information architecture, leadership gets a coherent view of commercial performance and risk that allows them to act rather than react.

On the buying side, the structure is remarkably similar. The chain runs from delivery through contract management through supplier management through category management and into product and portfolio management on the procurement side. The same continuum, the same logic, the same fundamental need for aggregation and coherence at the top. It is about Supplier health, contractual compliance, category dynamics, and portfolio positioning. They all feed into the same question that leadership must be able to answer clearly: do we know what our obligations and exposures are across our supply base, and are we managing them with the same intelligence and discipline we apply to our customer base?

The symmetry here is striking yet largely unacknowledged in the way most organizations are structured. The governance architecture that would make a sales operation genuinely world-class is structurally identical to the architecture that would make a procurement and supply operation genuinely world-class. The information flows required, the governance mechanisms needed, the skill profiles demanded, the quality of leadership attention both sides need to perform at a peak level. All of it mirrors the other.

This all makes it worth asking a question that I will leave with you. The answer says more about organizational culture and inherited assumptions than any strategy document ever will. Why is it that in most organizations, the sales side is substantially better resourced, better governed, better led, and better remunerated than the buying side? If the architecture is the same, if the risks are comparable in magnitude, if the organizational need for genuine competence on both sides is equivalent, where exactly does that persistent imbalance come from? And what does your answer reveal about what your organization actually values?

In the age of AI and Ecosystems ignoring this will lead to the end of your organization, so better act now.

The Ecosystem Is Not a Buzzword. It Is a Mirror. 

Open any business publication from the last five years and the word "ecosystem" appears on almost every page. Consultancy organizations go crazy on it. Strategy decks are full of it. Keynote speakers build entire narratives around it. Advisors charge premium rates to map it. But, when you ask executives what their ecosystem actually looks like, who the key players are, what the agreements look like that hold it together, and how performance across that network is being managed, the answers become uncomfortable.

That gap, between the word and the reality, is exactly what makes "ecosystem" so interesting right now.

What the Word Actually Means

An ecosystem, stemming from biology, describes a community of organisms that depend on each other and on their shared environment to survive and thrive. Nothing operates in isolation. Everything is connected. When one element changes, the rest of the system responds.

In business, the term describes the same. Your organisation is not standalone. It is a node in a network of suppliers, partners, contractors, technology providers, distributors, regulators, and customers. These relationships are not optional extras bolted onto your core business; they are the business. Remove any significant node and the whole network underperforms or collapses. This is also why I am so surprised that this is not enterprise risk number one.

The reason this matters a bit more now than it did ten years ago is not because the concept is new. It is because the consequences of mismanaging that network are now visible freaky fast and scale that organisations can no longer absorb this quietly.

The Irony Nobody Talks About

Here is where things get strange. The language around ecosystems carries a tone of discovery, as if we are collectively realising for the first time that businesses depend on other businesses. But this has been true since the industrial revolution.

From the moment organisations began to specialise, they began to depend. Ford needed steel suppliers. Steel suppliers needed coal. Coal operations needed rail. Rail needed legal agreements. Every step in the chain was governed by some form of contract. Division of labour, the organising principle of the industrial age, is by definition a statement that we cannot and should not do everything ourselves.

So why, in 2026, are we treating this as a revelation?

The honest answer is that for most of the last century, the complexity was manageable. Supply chains were long, but they were relatively stable. Partners were few and known. Agreements were renegotiated slowly. The consequences of poor contract management were real but absorbed over time. There was always another quarter, another fiscal year, another renegotiation window.

That window has closed.The age of complacency is gone. Welcome to the age of AI and Ecosystems.

Contract Management: The Foundation That Was Treated as a Footnote

Against that backdrop, consider the role of contract management. Every agreement in an ecosystem, every partnership, every outsourcing arrangement, every procurement deal, every service level commitment, is formalised in a contract. The contract is the document that translates strategy into objectives into obligations. It is where "we will work together" becomes "here is what we will deliver, by when, under these conditions, with these consequences."

Contract management is, in that sense, the operational layer of every ecosystem. It is the mechanism through which intentions become accountable commitments and where commitments drives realization of the objectives.

Yet, for decades, organisations treated it as an administrative afterthought. How bizarre.

Contracts were filed after signature. Obligations were tracked informally, if at all. Performance data was scattered across departments. Renewals were missed or handled reactively. The people responsible for managing contracts were often buried in legal or procurement functions with insufficient authority, insufficient tooling, and insufficient recognition of the strategic role they played or they even sat in the dungeons, tucked away as a low end function.

Research consistently shows that poor contract management costs organisations between five and nine percent of contract value annually. For large enterprises with complex supplier networks, that number translates into hundreds of millions of euros sitting on the table, not because the contracts are bad, but because nobody is actively managing them. Yet still executives don’t seem to get it.

Where the Neglect Came From

The undervaluation of contract management did not happen by accident. It was the result of a set of assumptions that made sense in a simpler operating environment and became liabilities as that environment changed.

The first assumption was that legal teams owned contract risk. As long as the contract was well-drafted, the job was done. This confused the quality of the document with the quality of the execution. A well-drafted contract that nobody monitors is a well-drafted statement of intent.

The second assumption was that procurement owned commercial performance. Procurement teams focused rightly on securing good terms before signature. But the handoff after signature was rarely clean, and the responsibility for tracking whether those terms were being honoured fell into no clear ownership.

The third assumption was that ERP systems and finance reporting would catch the gaps. They did not. ERP systems track transactions. They do not track obligations. Finance reports revenue and cost. They do not report on whether a supplier delivered to specification, whether a milestone was met, or whether a risk clause was triggered.

The result of these three assumptions operating together was a function that was fragmented, underresourced, and invisible to leadership. Contract management sat (and still usually sits) in the gap between legal, procurement, and operations, with pieces of the function living in all three and being fully owned by none. Contracts, touched by everyone, but owned by nobody.

The Wake-Up Call Arrives in Two Forms

The shift happening now comes from two directions at once.

The first is capital. Venture capital is flowing into the contract management technology space at a rate that would have been unimaginable a decade ago. Investors are betting that organisations will pay serious money for platforms that bring visibility, compliance, and performance tracking to their contract portfolios. That bet is already paying off. The market is growing fast, and the incumbents in adjacent spaces, legal tech, procurement platforms, ERP providers, are all moving aggressively to capture this territory.

Where capital flows, attention follows. Contract management is no longer a niche concern for specialist practitioners. It is now a recognised business priority with budget, board-level visibility, and a growing talent market to match. And being the wizard in this field I should know.

The second driver is shock. The past six years delivered a sequence of systemic disruptions that would have seemed implausible as a single scenario. A global pandemic, followed by supply chain collapse, followed by geopolitical fragmentation, followed by inflationary spikes, followed by an AI transformation that is rewriting the assumptions behind entire job categories and business models.

What organisations are now accepting is that this is not a sequence of isolated shocks. It is a new operating environment. Instability is the baseline. The question is no longer how to recover from disruption. The question is how to build organisations that perform during disruption, and that means knowing exactly who your partners are, what they are committed to delivering, and whether they are delivering it.

Contract management is central to that capability.

The Party After Signature Solves Nothing

There is a ritual that happens in organisations after a major deal is signed. The teams gather, champagne is poured, and the contract is filed away. Everyone celebrates the close. That celebration is a lie, it is fun, it is important but it is step 1.

The signature does not deliver the outcome. The signature creates the legal framework within which the outcome is supposed to be delivered. What happens after the signature, the active management of obligations, milestones, performance indicators, risk triggers, and relationship dynamics, that is where value is created or destroyed. That’s where objectives are realized.

Organisations that understand this shift their definition of success. A signed contract is a starting line, not a finish line. The work begins the moment the ink dries, and the document transcends the PDF stage.

Process Is the Answer Nobody Wants to Hear

The enthusiasm around AI and agentic workforces is genuine and warranted. Intelligent agents are already taking on research tasks, compliance checks, contract analysis, obligation extraction, and performance monitoring at a speed no human team can match. This is not science fiction. It is production software that organisations are deploying today. Out of the box. Ready to go.

But here is the problem. You cannot automate a process that does not exist, or worse, automate a bad process and you simply produce bad outcomes faster.

Most organisations that are now turning their attention to contract management find the same thing when they look honestly at their current state. The processes are mediocre at best. Ownership is unclear. Responsibilities overlap or fall into gaps. There are no standard task definitions, no consistent role assignments, no agreed handoffs between legal, commercial, procurement, finance, and operations.

Before you deploy a single agent, you need to answer a set of foundational questions. What are the processes that govern the contract lifecycle in your organisation? Who owns each stage? What are the discrete tasks within each stage? Which roles are responsible for which tasks? Which decisions require human judgment and which are rules-based and therefore automatable?

This is business architecture work. It is less glamorous than deploying AI. It takes longer. It requires organisations to look honestly at current-state processes that are often poorly documented, inconsistently applied, and politically sensitive to change.

But without this foundation, any investment in automation produces shallow gains. You speed up the broken parts. You scale the inconsistencies. You embed the gaps into your digital infrastructure.

The Right Sequence

The approach that actually works starts with process and people.

Map the contract lifecycle end to end. Define the tasks. Create a uniform language. Assign ownership. Identify where the work is manual and why. Separate the tasks that require judgment, relationship management, commercial intuition, and contextual knowledge from the tasks that are procedural, data-dependent, and repeatable.

Then build the capability model. Train the people responsible for contract management in the methodology and the skills their role requires. Create clarity on accountability. Give the function the organisational standing it deserves given the strategic importance of what it manages.

Then, and only then, introduce automation and agentic tools into the parts of the process where they add genuine value without creating new risks.

This sequence is not a quick fix. It is a multi-year programme in most large organisations, not a three-month deployment. But the organisations that commit to it build something that no amount of technology spending alone can buy. They build a contract management capability that is resilient, scalable, and genuinely aligned with the ecosystem they operate in.

The Ecosystem Demands This

The ecosystem is not a metaphor for ambition; it is a description of reality. Your organisation is interdependent with dozens or hundreds of other organisations. The agreements that define those interdependencies are contracts. The capability that manages those agreements is contract management.

The shocks will continue. The complexity will increase. The partners in your ecosystem will face their own pressures and those pressures will arrive at your door through the contracts you share.

The organisations that survive this environment are not the ones that sign the best contracts. They are the ones that manage them best, across every stage of the lifecycle, with clear processes, capable people, and the right tools supporting them.

Start with the process. Start with the people. The rest follows.

____________________________________________________________

Arjen van Berkum is a key contributor to CATS CM and is globally regarded as one of the top voices and wizards in post-award contract management. He works with organisations to build the processes, capabilities, and structures that make contract management a strategic asset.

The Blended Workforce: Why Agentic AI Is Not Just Another Tool

By Arjen van Berkum

Rethinking the Paradigm

There is an almost standard pattern in how organisations respond to technological discontinuity. A new technology emerges, early adopters integrate it into existing workflows, leadership issues a press release declaring commitment to innovation, and then the organisation waits to see what happens next. This pattern has repeated itself with the internet, with cloud computing, with mobile platforms. It is repeating itself now with artificial intelligence, and for most organisations it will produce the same outcome it always has: late adoption, competitive disadvantage, and a scramble to catch up.

The difference this time is that the gap between those who understand the shift and those who do not will be catastrophic. Agentic AI is not another tool to be absorbed into an existing workflow or process. It is a fundamental reorientation of how work is structured, how information is gathered and processed, how decisions are made, and ultimately how leadership functions. To treat it as anything less is to misread the nature of the transformation entirely and will lead to abysmal failliure.

The Architecture of the Blended Workforce

The concept of the blended workforce is already out there, but its implications are rarely examined with the attention they demand. A blended workforce is not simply a team that uses AI-powered software, although I see that a lot…. It is a structural reorganisation of labour in which human cognitive capacity and machine processing capacity are allocated according to comparative advantage of each. Humans will increasingly own the domains of oversight, ethical judgement, relationship management, and strategic direction. These tasks are not easy to automate, the real question is however should they be... The difficulty is precisely what drives human value. The responsibility, the ambiguity, the relational complexity and the moral weight of consequential decisions are features of human work, not inefficiencies to be optimized away. But it does require reskilling.

What shifts is everything adjacent to those domains. The gathering of intelligence, the processing of data, the execution of micro-tasks, the monitoring of systems, the aggregation of signals from disparate sources and the generation of actionable summaries all move into the domain of the machine. And critically, not into a single monolithic AI system, but into swarms of micro-bots, each performing a discrete, well-defined task, orchestrated together to produce composite outputs of significant intelligence and value. This is the architectural reality that most organisations have not yet internalised.

Micro-Tasks, Orchestration and the End of the API

The implications for systems architects are profound and underappreciated. Traditionally, enterprise technology design has been dominated by the logic of the platform: identify functional requirements, select a platform, integrate it with adjacent systems through defined APIs, and manage the resulting complexity. This logic is being superseded. Agentic AI systems do not route information through predefined endpoints. They navigate, interrogate, and synthesise information across systems dynamically, without explicit integration logic for every possible connection. The micro-bot does not need a pre-built integration. It needs a task, a set of rules, access to relevant environments, and the capacity to reason about how to fulfil its objective.

For architects, this represents a conceptual shift. The question is no longer simply what the landscape looks like and how the systems connect. The question becomes: what are the micro-tasks that constitute our total operational activity, and which of those are candidates for agentic automation? Answering this requires decomposing complex processes into their atomic constituent actions, assessing which require human judgement and which do not, and designing orchestration logic that governs how agents collaborate, sequence activities, and escalate when necessary. The end of the API as the primary integration mechanism is not science fiction. It is, in emerging form, already here. It is also the end of the architects that are technology lovers, however it is the rise of the process owner.

The Platform of Platforms Era and Contract Management

We are living in the age of the platform of platforms. The most sophisticated enterprise adopters have already moved past the question of which individual system to use. They are building meta-architectures, layers of orchestration that sit above existing systems and coordinate activity across them through intelligent agents rather than rigid integration code. The speed differential between organisations operating with this architecture and those still locked in the traditional model is already visible and will become decisive.

Contract management illustrates the stakes clearly. The post-award management of contracts, the discipline concerned with ensuring that what was agreed is actually realised, has historically suffered from fragmentation and information deficit. It is now shifting towards “did we realize what we wanted to realize”. From buying or selling to meeting objectives. A typical senior contracts manager operates in an environment where information about performance, supplier behaviour, risk, change events and compliance is scattered across CLM platforms, ERP systems, supplier portals, communication tools, financial systems, and spreadsheets. Synthesising this into a coherent picture requires significant manual effort, is invariably out of date, and is rarely available at the speed required for proactive decision-making. A swarm of micro-bots continuously processing information across that ecosystem produces instead a living, real-time intelligence picture. It surfaces anomalies, flags risk concentrations, identifies emerging disputes before they escalate, and monitors performance against commitments without waiting for a quarterly review. The conversation about who is to blame, a retrospective exercise in attributing fault after value has already been lost, becomes unnecessary because the conditions that give rise to it are detected and addressed earlier (finally we can go really pro-active). And critically, the backend systems do not need to change. The legacy ERP, the incumbent CLM, the procurement platform acquired five years ago can remain. Agentic AI acts as an intelligent intermediary, funnelling information from existing systems rather than replacing them.

The Employee Experience

There is a dimension of this transformation that is easily underestimated: the experience of the individual employee. Consider the administrative friction embedded in the daily working life of a contracts professional. Document retrieval, status updates, approval workflows, data entry across multiple systems, version control, stakeholder notifications: the cumulative burden is extraordinary. The PDF that must be printed, completed by hand, scanned, and emailed back is not merely an inconvenience. It is a symbol of how far the current architecture of work is from what it could be. Agentic AI replaces this friction with an interaction model in which the employee communicates intent and the machine executes, leaving human cognitive energy for the judgements, relationships, and strategic thinking that genuinely require it. Employees gain clarity: not a vague sense of what they probably need to do, but a precise, contextualised understanding of where their attention adds the most value. This will require significant reskilling of the current workforce. 

The Risks That Demand Honest Accounting

It would be not very cool to present this vision without confronting the risks, and those risks are very substantial. The most fundamental is process quality. Agentic systems execute against the logic of the processes they are built on. Poorly designed, incomplete, or internally contradictory processes are not corrected by AI; they are amplified and propagated rapidly at scale. Organisations that deploy agents without first achieving process clarity will not merely fail to realise benefits. They will generate new categories of operational risk. And lets be honest, who has its processes really in order?

Data integrity is of fundamental importance. Corrupt, outdated, incomplete or biased data produces corrupted, outdated, incomplete and biased outputs. A senior leader relying on an AI-generated risk dashboard built on poor data is making decisions based on a sophisticated confabulation. The third risk concerns cost sustainability. The economics of AI appear compelling today, but the trajectory is not guaranteed. Emerging tokenisation of inference capacity, combined with the already significant environmental costs of large-scale AI computation in terms of both energy and water consumption, introduces real uncertainty about long-term cost structures and ethical costs. Organisations committing to agentic architectures must model scenarios in which AI compute costs are substantially higher than they are today, and build business cases that are robust under those assumptions.

The Skills That Actually Matter

There is a widespread assumption that the critical future skill in an AI-intensive environment is the ability to prompt effectively. This is insufficient. Prompting is a technique. What is needed is understanding. The professionals who will thrive in blended workforces are those who understand the journeys (and thus processes) that key stakeholders undertake: the customer journey, the supplier journey, the employee journey. They understand where those journeys encounter friction, where they are vulnerable to disruption, where system shocks originate, and where dependencies create fragility. They understand how to design audit mechanisms, checks and balances, and governance structures for systems in which much of the execution is automated and how to embed human oversight as a genuine control point rather than a formality.

Regulatory pressure will grow. Legislation governing AI in consequential decision-making is a matter of when, not whether. It will require organisations to reproduce the reasoning behind AI-assisted decisions, demonstrate that human oversight was substantive, and retain the evidence required for audit. The data storage implications alone are substantial and largely unplanned for. The future professional in contract management or procurement is not a prompt engineer. They are a systems thinker who understands human and machine behaviour equally well, can design for resilience, and can distinguish between a process that looks efficient and one that is genuinely robust.

Augmented Intelligence and the Imperative to Act

The framing that best captures what is at stake is the distinction between Artificial Intelligence and Augmented Intelligence. Artificial Intelligence, as a concept, positions the machine as the primary agent and the human as an observer. Augmented Intelligence inverts this: the human remains the primary agent, the bearer of purpose, judgement and accountability, and the machine extends the scope and quality of what that human can achieve. This distinction is not just semantic. It shapes how agents are designed, how people are prepared, and how success is measured. An organisation building for Augmented Intelligence measures not how many tasks have been automated but how much better its people are able to do what only people can do.

The final question is whether senior leadership will engage with this agenda with the urgency it requires or whether they will wait. Waiting is a choice with consequences. The organisations already building agentic architectures, already decomposing their processes into micro-tasks, already thinking in platform-of-platforms terms, are acquiring capabilities that compound over time. A press release announcing that the organisation will do AI is not a strategy. A proof-of-concept that never scales is not a transformation. What is required is the mindset of the startup applied to the resources of the enterprise: dream big, start small, act fast, and learn from both the failures and the successes. The blended workforce is not a future state. It is an something that is starting to spring to life now, and the window in which early action creates durable advantage is here....

Arjen van Berkum is the contract management wizard and entrepreneur, speaker, teacher and conceptually creates work for CATS CM, specializing in post-award contract management best practices, organisational design, and the integration of intelligent systems into complex commercial environments.