AI-Powered Operations
7 MINUTE READ
APR 2026
RPA follows rules. Agentic operations handle what happens when the rules break.

Robotic Process Automation was a real step forward. You defined the steps, the bot executed them. But RPA has a specific failure mode that every organization running it at scale has encountered: it breaks when something unexpected happens. A data format changes. An API returns an error. A supplier is unavailable. And then a human gets a ticket and has to fix it. IBM's 2026 operations research identifies this as the core limitation of legacy automation and the reason agentic systems are replacing it. Autonomous agents now have what IBM calls reasoning traces. They can navigate ambiguity, handle API failures through automatic retry logic, and loop back to resolve issues without generating a human ticket. The goal for 2026 is not just efficiency. It is operational resilience: systems that keep running when conditions change, not systems that stop and wait.

79%

Of executives expect AI to be a primary revenue driver by 2030, per IBM. The immediate 2026 focus is operational resilience, not future revenue potential.

40%

Reduction in manufacturing downtime through Digital Twin operations, where autonomous systems predict equipment failure and schedule their own maintenance, per IBM's Industries in the AI Era report.

Real-time

Supplier rerouting is now possible through autonomous sourcing agents that monitor global volatility, including geopolitical events and weather disruptions, and switch suppliers without human intervention.

Instant

Transaction settlement is the direction banking operations are heading. IBM's 2026 Global Outlook identifies AI agents negotiating and clearing transactions on-chain, replacing the T+2 settlement model.

Business operations are starting to be managed the way software systems are managed.IBM's 2026 theme of Observability as Code makes a specific argument that C-suite executives need to understand. Just as IT teams use code to monitor servers and define what an alert looks like, business operations teams can now use configuration files to define how KPIs are monitored and what triggers a response. Supply chain throughput. Loan approval speed. Network latency. These can all be monitored and responded to autonomously rather than manually. IBM also identifies a new category of agent for this: Auditor Agents that do nothing but watch Worker Agents to make sure they stay within compliance and budgetary guardrails. So the oversight mechanism itself is automated. C-suite executives who have spent time worrying about whether autonomous systems will go out of bounds now have a concrete answer to that question built into the architecture.
What AI-powered operations actually look like across four industries where it is moving fastest
IBM's 2026 industry operations research is specific about what is changing in each sector. These are not conceptual shifts. They are live operational models being deployed by organizations that are ahead of where most are today. Here is what each one looks like in practice.

Supply chain: Autonomous sourcing that responds to disruption before you know it is happening

IBM's Scaling Supply Chain Resilience report describes a shift to what it calls autonomous sourcing. Agents monitor global volatility signals including geopolitical developments, weather events, and shipping disruptions. When a risk is detected, they do not send an alert to a procurement team and wait. They reroute shipping or switch to an alternative supplier in real time, within the guardrails that have been defined for them. The human receives a summary of what was done and why, not a notification that something needs attention. C-suite executives managing supply chains that are still dependent on humans to spot disruptions and manually trigger responses are running a slower version of a process that can now largely run itself. The question is not whether autonomous sourcing is possible. It is how exposed the current manual model is leaving the organization when disruption happens faster than people can react.

Banking: Moving from T+2 settlement to instant settlement through on-chain agent coordination

IBM's 2026 Global Outlook for Banking identifies a specific operational shift in how transactions settle. The current T+2 model, where transactions settle two business days after execution, involves significant manual back-office coordination. IBM describes the direction as tokenized operations: moving assets to on-chain environments where AI agents can negotiate and clear transactions in real time rather than over two days. This removes a category of operational risk, counterparty exposure during the settlement window, and a category of operational cost, the manual processes involved in back-office coordination. For C-suite executives in financial services, the operational question is not whether instant settlement is coming. It is whether the institution's systems are being built to support it or whether the current infrastructure will require expensive retrofitting when it becomes the expected standard.

Manufacturing: Digital twins that predict failures and schedule their own maintenance

IBM's Industries in the AI Era report identifies Digital Twin Operations as the primary operational shift in manufacturing. A digital twin is a live simulation of physical equipment that runs in parallel with the real machine. When the simulation detects a wear pattern that indicates an upcoming failure, the autonomous system does not wait for the failure to happen. It schedules its own maintenance, coordinates with inventory to ensure parts are available, and if necessary adjusts the production schedule around it. IBM reports a 40% reduction in downtime from this approach. C-suite executives in manufacturing who are still relying on scheduled preventive maintenance or reactive repair are accepting a level of unplanned downtime that autonomous predictive maintenance can significantly reduce. The technology to do this exists now. The question is implementation sequencing.

Telcos: Intent-based networking where the goal replaces the manual configuration

IBM's Connectivity to Growth Partner research describes a shift in how telecoms manage their networks. Traditional network operations require engineers to manually configure systems to achieve specific outcomes. Intent-based networking replaces that with a different model: a human or a business system defines the goal, something like prioritize emergency services bandwidth during a major event, and the AI figures out the configuration required to achieve it and executes in real time. The human is no longer translating a business objective into technical configuration steps. They are stating the objective and the system handles the translation. For C-suite executives in telecoms, this changes what the operations team spends time on. Manual configuration becomes a smaller part of the job. Managing the intent definitions and the guardrails around them becomes a larger one.

At Marchcroft

Innovating Today,
Shaping Tomorrow

At Marchcroft, we don't just meet expectations - we exceed them.

7 in 10

Leading utilities using predictive analytics as the operational intelligence layer

Seven in ten pioneering utilities use predictive analytics to manage energy supply and demand. Predictive analytics is the input layer that makes autonomous operations reliable. Without it, agents are reacting to what has already happened. With it, agents can act on what is about to happen. Self-optimization at operational scale depends on the analytical foundation being strong enough to give agents accurate signals to act on.

67%

Managing distributed operational assets as coordinated systems

67% of optimizing utilities manage microgrids as both local services and grid-wide assets. In AI-powered operations, this is the principle behind multi-agent orchestration. Worker agents handle specific domains. Auditor agents monitor them. A coordinating layer manages them toward shared business objectives. Organizations that treat their operational systems as a coordinated whole rather than independent functions consistently outperform those managing each operation in isolation.

~65%

Using failure forecasting to guide where operational investment goes

Nearly two-thirds of utilities create asset failure forecasts to evaluate network impact before investing in fixes. Applied to business operations, this means modeling which operational processes are most likely to fail under specific conditions before those conditions occur. C-suite executives who know in advance where their operations are most brittle, whether supply chain, settlement, equipment, or network, make better decisions about where to invest in autonomous resilience than those waiting to find out from the next disruption.

01. Identify where your operations currently stop when something unexpected happens

The clearest signal that an operation is ready for agentic upgrade is that it generates human tickets when something breaks. A ticket is evidence that the system hit something it was not designed to handle and handed it back to a person. Map where those tickets are coming from across your operations. Those are the processes where legacy rule-based automation is hitting its ceiling and where agentic systems with reasoning capability would create the most immediate operational resilience. C-suite executives who review their support ticket volume by process category often find that a small number of process types are generating the majority of manual intervention work. That is where the ROI case for agentic operations is easiest to build.

02. Define your KPI monitoring requirements in the same way you define your software monitoring requirements

IBM's Observability as Code framework applies the same logic to business operations that IT teams apply to infrastructure. If a server metric crosses a threshold, a defined response triggers automatically. The equivalent for business operations is: if supply chain throughput drops below a defined level, trigger a specific autonomous response. If loan approval speed exceeds a defined threshold, alert a compliance agent. C-suite executives should work with their operations teams to define what the KPI boundaries are, what a response looks like when those boundaries are crossed, and what level of autonomous response is acceptable versus what requires human escalation. That definition exercise is the foundation of Observability as Code for business operations.

03. Build the auditor layer before you scale the worker agents

IBM's prediction that multi-agent orchestration in 2026 will include dedicated Auditor Agents addresses a real governance concern. When autonomous agents are making operational decisions at scale, the oversight mechanism cannot itself be manual. Auditor agents watch worker agents and flag when they are operating outside compliance or budgetary guardrails. C-suite executives who approve autonomous operations without an auditor layer are creating accountability gaps that are hard to audit after the fact. The sequence matters: define the guardrails, build the auditor mechanism, then scale the worker agents within that monitored environment. Organizations that build in that order have a much cleaner governance story than those who add oversight as an afterthought.

04. Plan for the transition from manual configuration to intent-based operation as a change management exercise, not just a technology one

The shift from operations teams that configure systems manually to operations teams that define intent and manage guardrails changes what those teams do every day. IBM's intent-based networking model in telecoms is a clear example: engineers who previously spent significant time on manual configuration now spend that time on different problems. That transition requires deliberate change management. Which skills remain essential? Which need to develop? How does the team's structure change when a significant portion of configuration work is automated? C-suite executives who treat this as a technology implementation project and not a workforce transition project consistently underestimate the time and effort required for the new operating model to actually take hold.

Get Access To Audit Sheet

Unlock valuable insights with our complimentary audit sheet. Streamline your processes, identify areas for improvement, and boost efficiency—all at no cost.

Download Audit Sheet
Questions C-suite executives ask us about AI-powered operations
These come up in almost every engagement where leadership teams are moving from interest in operational AI to actual decisions about where to start and how to govern it.

Q: Our RPA implementations are working well. Why would we move to agentic operations?

RPA works well for stable, high-volume processes where the inputs and outputs are predictable and the format does not change. The limitation shows up at the edges. When a data format changes unexpectedly, when an API fails, when a supplier is unavailable, or when an exception falls outside the rules the bot was given. At that point, RPA generates a ticket and waits. Agentic systems handle those edge cases through reasoning: they can navigate ambiguity, retry failed connections, and resolve issues without human intervention. If your RPA implementations are generating a low volume of exception tickets and running stable processes, the case for upgrading is not urgent. If a meaningful portion of your operations team's time is spent resolving RPA exceptions, that is the signal that the ceiling of rule-based automation has been reached.

Q: How do we maintain compliance when autonomous agents are making operational decisions?

This is the right question and the answer is architectural, not just procedural. The guardrails that define what an agent is and is not permitted to do need to be built into the system design, not added as a review step afterward. IBM's Auditor Agent model addresses exactly this: dedicated agents that do nothing but monitor worker agents and flag when they are operating outside compliance or budgetary boundaries. The audit trail for autonomous decisions also needs to be built in from the start. When an agent makes a decision, what was the reasoning trace? What data did it work from? What guardrail did it operate within? C-suite executives in regulated industries need to be able to answer those questions for a regulator, which means the logging and traceability architecture needs to be a design requirement, not an implementation afterthought.

Q: What is the realistic timeline for seeing operational impact from agentic systems?

It depends heavily on the starting point. Organizations with clean data, well-integrated systems, and clearly defined processes can typically see meaningful operational impact from agentic pilots within three to six months. The timeline extends significantly when the underlying data is fragmented, systems are not well integrated, or the processes being automated are poorly documented. IBM's finding that 79% of executives expect AI to be a primary revenue driver by 2030 reflects a realistic multi-year horizon for full-scale impact. The 2026 focus is operational resilience: reducing the failure modes in current operations rather than building entirely new capabilities. C-suite executives who start with the highest-friction, highest-ticket-volume processes in their current operations, and build agentic solutions for those specific cases, get to measurable impact faster than those trying to build comprehensive operational AI from scratch.

Latest Blogs

Marchcroft Editorial - 2026-03-31

Why RPA Breaks and What Agentic Operations Do Instead When Something Unexpected Happens

Agentic Operations

RPA

Operational Resilience

Marchcroft Editorial - 2026-03-17

Observability as Code: Managing Business KPIs the Way IT Teams Manage Servers

Observability as Code

BizOps

AI Operations

Marchcroft Editorial - 2026-03-03

Digital Twins, Autonomous Sourcing, and Instant Settlement: What AI-Powered Operations Looks Like in 2026

Digital Twins

Supply Chain

Banking Operations

View more

Want to identify where your current operations are most exposed to disruption?

Here is what working with us on AI-powered operations looks like.

Ready to Optimize Your Operations?
Let's discuss how agentic AI can transform your operational resilience and drive measurable business impact.
Consult with us

Get In Touch

+44 20 3286 8065

contactus@marchcroft.com