Why your data infrastructure — not your AI model — will determine whether Agentic AI scales

Nearly all the business media coverage of AI focuses on the eye-popping sums being deployed into data center infrastructure that drives the “compute” coveted by leaders in the AI industry. That “compute” provides the raw processing power required to train, build, and run AI systems. Think of it as the engine behind the technology. The tech community is expected to invest more than $750 billion into data centers this year alone. Estimates for total cumulative spend on the humming warehouses reach over $7 trillion by 2030. Such mind-boggling numbers and the circular financing arrangements to drum up the necessary capital have understandably generated a lot of buzz about a potential bubble comparable to the dot-com bubble.

Recommended Video

The development of data centers is a must if we want to capture the productivity gains that AI promises. Overinvestment, though, could not only have a chilling effect on the rapid integration into the global economy but also lead to a calamitous outcome for financial markets. All the vigorous debate is warranted. However, not enough attention is paid to the other kind of infrastructure required to scale AI for highly productive, enterprise-agentic deployments—data infrastructure. Data and databases must be organized, checked for accuracy, and made easily accessible so that an AI agent can both locate a specific data point and use it to complete actual tasks across myriad systems without constant supervision.

Agentic AI has increasingly attracted attention over the past year, and for good reason. Systems that can reason, plan, and execute across complex enterprise workflows represent a genuine shift in what software can do. But the enthusiasm has outrun the evidence. Two-thirds of enterprises have experimented with AI agents, yet fewer than one in ten have scaled them to the point that they measurably change the cost base, revenues, or earnings. The public conversation remains fixated on what these systems can do in demonstrations, not on the conditions required to deploy them at scale.

The gap matters because agentic systems are not an incremental extension of prior AI. When AI drafts an email or helps write code, internal data barely matters. An agentic system, by contrast, does not just answer a question about an invoice—it locates the invoice in the Enterprise Resource Planning (ERP) system, matches it against the purchase order in procurement, and triggers payment, all without human direction. Its usefulness depends entirely on reaching across the systems where enterprise data actually lives. That is the central difficulty, and it is largely an infrastructure problem.

Agentic AI pilots obscure this. They succeed precisely because they are contained: a narrow, clean slice of data, a single system, and none of the integration complexity that characterizes real enterprise environments. When organizations move from pilot to deployment, the containment breaks, and the agentic system encounters data held across platforms, maintained by different teams, governed by different standards, and often unable to communicate consistently with one another. What looked like a capability problem is revealed to be a data infrastructure problem—a failure of accessible, consistent, and usable data across systems—and no amount of model improvement will solve it. Eighty percent of companies cite data limitations as the primary obstacle to scaling AI, a figure that has proven stubborn even as the models themselves have leaped forward.

The organizations best positioned to move past the pilot phase are not those with the most advanced tools but those who built the infrastructure to support them before needing it. What follows examines why that infrastructure is so consistently underestimated, how readiness varies across sectors, and what firms and policymakers need to do differently.

Why Data Infrastructure Is the Binding Constraint

The data dependency of Agentic AI is obvious. What is less obvious and frequently neglected is cross-system operability—the capacity of platforms built on different architectures and governed by different standards to communicate reliably enough to carry an autonomous decision from start to finish. Data infrastructure, in this sense, is less about storage than about translation.

The distinction is compounded by the fact that most enterprise systems were never built to be spoken to by other systems in the first place. Procurement, clinical, billing, and network management tools were each designed to excel within their own domains, not to interoperate across them. Companies, then, cannot simply layer Agentic AI on top of their existing infrastructure; they must first complete the lower-profile work of standardizing data across systems. Without that foundation, even the most capable AI model has nothing coherent on which to act.

Industries encounter this challenge in different forms. In real estate and financial services, workflows involve sensitive personal a