FTFuture Technology
SOFTWARE

Why AI Agents Are the New Enterprise Software Layer, and What That Means for IT

· 3 min read · By Nath Connell

Key takeaways

  • NVIDIA's Agent Toolkit has expanded to include Omniverse, PhysicsNeMo, and CUDA-X libraries in rapid succession, establishing a modular agent-plus-tools architecture
  • AI agent workloads require IT teams to think about GPU capacity planning, API rate limiting, and autonomous decision audit logging, all capabilities most enterprise IT is not yet set up for
  • The mid-market gap between large tech companies deploying agents in production and smaller firms still in pilot phase is primarily an infrastructure and skills gap, not a capability gap

The phrase "agentic AI" has been floating around for a couple of years now, but 2026 is the year it started meaning something concrete in enterprise settings. The evidence is accumulating in the form of actual product announcements, real deployments, and, importantly, real infrastructure choices being made by companies that would previously have been buying SaaS subscriptions and calling it a day.

NVIDIA's rapid expansion of its Agent Toolkit is one of the clearest signals. In the space of a few months, the toolkit has grown to include Omniverse libraries for 3D simulation, PhysicsNeMo for physics-informed modelling, and CUDA-X for domain-specific computing. The pattern is unmistakable: NVIDIA is building a modular platform where AI agents act as the orchestration layer, calling specialised tools to handle specific tasks rather than trying to be a single system that knows everything.

Why This Architecture Makes Sense

The tool-using agent model is compelling precisely because it mirrors how skilled human workers actually operate. A structural engineer does not keep the entirety of materials science in their head. They know when to open a simulation tool, when to consult a specification document, and when to run a calculation. An AI agent that can do the same thing, calling PhysicsNeMo to simulate stress on a component, querying a database for material properties, and returning a recommendation, is far more useful than a general-purpose language model that tries to reason through the whole problem from first principles.

This is also why the debate about whether large language models are "really intelligent" is becoming less relevant in enterprise contexts. The question is not whether the model can reason like a human. The question is whether the agent system gets the job done reliably. And increasingly, the answer for well-scoped engineering and analytical tasks is yes.

The Infrastructure Implications

For IT departments, the shift to agentic AI creates a genuinely new set of infrastructure concerns. Traditional SaaS applications have predictable compute profiles: users log in, interact with a web app, and the backend does some processing. AI agents are fundamentally different. They spin up compute on demand, call multiple APIs in sequence, run inference jobs that can be compute-intensive and unpredictable in duration, and may operate continuously rather than in response to human requests.

The future, in 3 minutes a day. The biggest tech story explained every morning, free. Get the briefing →

This means IT teams need to think about AI agent workloads the way they think about batch processing jobs, not web applications. GPU capacity planning, API rate limiting, data access controls, and audit logging for autonomous decisions all become live concerns that most enterprise IT functions are not yet set up to handle well.

The security implications are significant too. An AI agent with access to simulation tools, databases, and code execution environments is a high-privilege entity. If an agent can be manipulated through prompt injection or compromised through a vulnerable tool it calls, the blast radius could be substantial. This is a problem the security industry is only beginning to grapple with seriously.

What Enterprises Are Actually Doing

The honest picture is mixed. Large technology companies and well-resourced research institutions are deploying agentic AI in production settings with real results. The mid-market and smaller enterprises are mostly still in the experimentation phase, running pilots and proof-of-concept projects that have not yet translated into operational workflows.

The gap between these groups is largely an infrastructure and skills gap rather than a capability gap. The tools exist. The challenge is having the compute infrastructure to run agents at scale, the engineering talent to build and maintain agent workflows, and the organisational maturity to define what tasks agents should and should not be authorised to perform autonomously.

The companies that close that gap in the next two years are likely to have a meaningful productivity advantage over those that treat agentic AI as something to evaluate later. The window for careful, unhurried experimentation is shorter than it looks.

Get the briefing, free

The biggest tech story, explained in 3 minutes every weekday. Choose your briefings →

Free. No spam. Unsubscribe in one click.