The management issue is not whether AI will keep expanding, but how leaders will govern demand when supply is uneven. CIOs should treat infrastructure pressure as a portfolio control problem: if AI capacity becomes scarce or volatile, every new use case competes against more valuable workloads, and the organisation needs a clear method for deciding what moves first. The practical implication is that AI intake cannot remain a departmental free-for-all; it needs explicit thresholds for funding, prioritisation, and retirement.
This also changes the financial conversation. If access to AI compute becomes less predictable, the business case for each initiative should include cost sensitivity, service-level assumptions, and the value of delay. Leaders may need to separate experimental spend from operational spend, then track benefits by tier rather than aggregating AI into one investment bucket. The next question for portfolio boards is simple: which outcomes justify premium capacity, and which can wait, slow down, or move to a smaller model or a local environment?
Operating model discipline will matter more than model ambition. Organisations with central oversight can set rules for who gets access, when workloads can scale, and what happens when vendor capacity tightens. That creates trade-offs: tighter control improves resilience and budget predictability, but can frustrate business teams and slow innovation. CIOs should test whether their governance model can handle rationing without becoming bureaucratic.
Vendors should now be assessed as continuity partners, not just technology suppliers. Procurement and architecture teams need to ask how capacity is allocated during peaks, what contractual remedies exist, and whether workloads can move across regions or providers without rework. The next management question is whether current AI designs create hidden dependency on one supply path, or whether the organisation has enough portability to absorb disruption without pausing delivery.
The gap between AI investment and operational capacity
The scale of investment flowing into AI infrastructure remains enormous, with hyperscalers and AI vendors continuing to spend billions in pursuit of future compute supply. But several experts said the industry may be underestimating how difficult it is to convert capital expenditure into operational AI capacity. The challenge, several experts said, is that physical infrastructure scaled far more slowly than software demand. “Capital commitments make headlines, but power availability, permitting, grid upgrades, cooling, specialized hardware supply, and construction timelines slow real delivery,” said Linthicum. “Money is moving faster than infrastructure.” Edward Liebig, CEO and CISO of Yoink Industries and an adjunct professor at Washington University in St. Louis, emphasized that the challenge extends beyond compute availability alone. “The demand curve for AI infrastructure appears to be outpacing not only data center construction, but also power availability, cooling, interconnect scalability, and the operational integration needed to bring these environments online reliably,” he said. Yet Liebig also cautioned against treating infrastructure constraints purely as a supply problem. In his view, the pressure is exposing weaknesses in how enterprises themselves are approaching AI deployment. “What we’re beginning to see is that infrastructure constraints expose whether organizations have a disciplined AI operating strategy or simply an accumulation of disconnected AI initiatives competing for resources,” Liebig said. That distinction may become increasingly important as enterprises scale AI adoption across departments. Many organizations are simultaneously experimenting with copilots, AI-assisted workflows, analytics tools, retrieval systems, and agentic systems, often without centralized governance or operational prioritization. Liebig described the result as “AI sprawl,” where infrastructure demand grows faster than measurable business value. “The organizations most affected by AI capacity shortages may not be the ones with the least infrastructure, but the ones with the least operational discipline around AI deployment,” he said.How infrastructure pressure could surface inside enterprises
Not every expert believes enterprises are facing an immediate AI capacity crisis. Donald Farmer, futurist at Tranquilla AI, took a more measured view, arguing that many CIOs may have more time than current headlines suggest. “We expect agentic AI to be the big driver of enterprise adoption, not GenAI,” Farmer said, referencing TDWI research that shows only 31% of businesses think agentic AI adoption is happening now; 49% predict it will take 1-5 years. “So, I suspect there is still time for power production to pick up.” Farmer also pointed to improving efficiency across both models and hardware, which will lessen the compute burden. Even so, several experts agreed that constraints are likely to emerge unevenly, with mid-sized enterprises potentially facing the greatest pressure during periods of peak demand. “I suspect training runs are safe,” Farmer said. “Hyperscalers, when capacity is tight, will presumably prioritize their own first-party AI workloads and their largest enterprise customers.” Linthicum similarly framed the issue less as outright scarcity and more as intermittent instability. “The biggest risk is not that AI disappears, but that access becomes more expensive, delayed, or uneven across regions and providers,” he said. That distinction matters because many enterprise AI strategies currently assume relatively frictionless access to compute. Organizations building roadmaps around rapid experimentation, real-time inference, and always-available AI services may need to prepare for a more constrained environment than they initially anticipated. “One of the emerging risks here is that organizations may unintentionally build business processes that assume infinite AI availability and infinite inference responsiveness,” Liebig said. “Physical infrastructure realities may challenge that assumption sooner than many expect.”AI governance becomes an infrastructure issue
The prospect of constrained AI capacity is also beginning to reshape conversations around governance and prioritization. Liebig argued that enterprises focused on operational assurance and resiliency may ultimately be better positioned during periods of infrastructure pressure because they tend to expand AI more deliberately. These companies tend to prioritize operationally critical use cases first and expand incrementally once value, governance, and controls are validated. “Bounded expansion creates resilience because organizations can prioritize the AI functions that matter most when infrastructure conditions tighten,” Liebig said. That approach also changes how CIOs evaluate AI investments internally. The central question becomes less about acquiring additional AI capacity and more about determining which workloads justify priority access to constrained infrastructure. Linthicum described a similar need for operational discipline. He argued that CIOs should begin separating AI initiatives into tiers — critical, important, and experimental — so infrastructure allocation becomes intentional, rather than reactive. “Enterprises without contingency plans are the most exposed,” he said. That shift may also force organizations to become more selective about where frontier AI models are truly necessary. Farmer noted that many enterprises are already finding success with smaller, local models running on commodity hardware, particularly in environments where governance, compliance, or cost concerns make cloud dependence less attractive. “Not everything has to run on the latest and greatest model,” Farmer said.What CIOs should ask vendors now
As infrastructure constraints become more visible, experts said CIOs should also begin treating AI capacity as a resilience and continuity issue rather than simply a procurement concern. In order to get ahead of potential issues, IT leadership needs clarity into their current supply. Linthicum said enterprises need far more transparency from vendors about how capacity shortages are managed. “They should ask very directly about capacity guarantees, regional availability, queue priority, pricing volatility, failover options, and portability between environments,” he said. Farmer similarly argued that conversations should increasingly focus on operational reliability, not feature sets. Among the questions he suggested CIOs ask vendors:-
“What is your contractual commitment on capacity availability during peak windows?”
-
“If I commit to multi-year reserved capacity, what does that purchase me in terms of priority versus on-demand customers?”
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.

