Two stories about governments and AI, published hours apart, point in opposite directions. In the UK, Prime Minister Andy Burnham has abolished the Department for Science, Innovation, and Technology outright, and elevated AI Minister Kanishka Narayan — who also oversees the AI Safety Institute — to a full seat at cabinet. In the US, an Army CIO memo reinstates limits on how many AI tokens Army personnel can use, even as internal documents show the Department of Defense’s own Ask Sage tool has access to 100 million tokens through an annual “enterprise pack.”

The cloud versus on-premises debate has settled into a more nuanced position than its early framing suggested. The argument that all workloads should move to cloud and that on-premises infrastructure would become obsolete was oversimplified. The organizations that moved all workloads to cloud and discovered that certain workload categories are more expensive to run in cloud than on-premises have been quietly repatriating those workloads for several years.

The current reality is a hybrid infrastructure landscape where the economic decision about where to run a workload depends on its specific characteristics — compute intensity, data volume, access patterns, regulatory requirements, and predictability — rather than on a blanket preference for either delivery model. Server hardware investment in this context requires the same rigor as any capital investment: a specific business case for the specific workloads that the hardware will run.

The IT budget allocation problem is structural, not mathematical. Organizations that spend the right total amount on IT frequently allocate it incorrectly across the four functional areas — run the business, grow the business, transform the business, and maintain the infrastructure that enables all three — producing technology environments that are simultaneously overspent in some areas and critically underfunded in others.

The allocation pattern that is most common and most damaging is heavy spending on new software and technology initiatives with insufficient investment in the support, security, and infrastructure maintenance that determines whether those investments function reliably. An organization that spends aggressively on digital transformation while deferring network infrastructure refresh, understaffing the helpdesk, and running security with inadequate tooling has not made a strategic trade-off. It has made an accounting error that looks like a strategic choice.

Network infrastructure occupies an unusual position in enterprise IT budget conversations. It is essential — nothing in the technology stack works without it — and invisible when functioning correctly. The invisibility is the problem. Network hardware that is approaching or past its end-of-support date, running firmware that has not been updated in years, and operating at utilization levels for which it was not designed accumulates risk silently. The incident that reveals the accumulation is not gradual. It is sudden.

The average organization with 500 to 1,000 employees is running between 100 and 200 SaaS applications. A fraction of those are managed by IT. The rest were procured by individual departments, teams, and employees using corporate credit cards, expense reports, and in some cases personal cards that get reimbursed. The finance team knows about the ones with purchase orders. The IT team knows about the ones that went through the security review queue. Nobody knows about all of them.