What four decades of IT spending actually bought

Latest Thinking from TalentCloud team
What four decades of IT spending actually bought
Written by
TalentCloud Research Team
Published on
July 29, 2026

The argument in three lines

  • Four decades of compounding IT investment; labour-productivity growth is essentially where it was in 1995.
  • The money converted into margin far more reliably than into output per hour — and margin is the scoreboard boards are actually using.
  • What separated the 1990s winners from the losers was not budget. It was whether the business restructured around the technology or layered it on top.

Four eras, four forcing functions

Worldwide IT spending will reach $6.31 trillion in 2026 — up 13.5% on last year, with data centre systems alone growing nearly 56%. Before deciding what that means, it is worth looking at the shape of the last four decades rather than the level.

Line chart of worldwide IT spending from 1990 to 2032, rising from roughly $0.8 trillion to $6.31 trillion in 2026, with a five-year plateau after 2000 and three projection scenarios reaching $8.1 to $12.6 trillion by 2032.
Worldwide IT spend, 1990–2032, US$ trillions. Markers are observations — the line between them is interpolation, not data. The pre-2005 leg is estimated, because definitions of “IT spending” changed materially. Source: Gartner worldwide IT spending forecasts, April 2026. Click the chart to open it full size.

Three things stand out. Spending roughly doubled in the late 1990s. Then it went flat for five years — not down, just flat, while the capacity already built was absorbed. Then it ground upward through the cloud decade at a pace nobody wrote headlines about. And since 2023 it has bent almost vertically.

Each bend had a forcing function, and they are not interchangeable:

  • Y2K, 1995–99 — $300–600 billion. A deadline that could not move: the one advantage no programme since has enjoyed.
  • Dot-com, 1998–2001 — 80 million miles of fiber for close to a trillion dollars. 85% was still dark by the mid-2000s.
  • Cloud, 2010–20 — $74 billion of public cloud in 2010, about 3% of enterprise IT. It started from almost nothing.
  • AI, 2024–26 — $725 billion of hyperscaler capex guided for 2026, up about 77% year on year.

Four eras, four forcing functions, one obvious question: what did any of it pay back?

The divergence nobody puts on a slide

Put three series on one axis — labour productivity, equity returns, corporate net margin — and the shape of the answer is hard to unsee.

Line chart comparing US labour productivity growth, S&P 500 annualised returns and S&P 500 net profit margins across the 1990s, 2000s, 2010s, 2020s and a projected 2027 to 2032 era, with productivity flat near 2 percent and net margin rising from 6 to 15 percent.
What each era paid back, percent. US labour-productivity growth, S&P 500 annualised return and S&P 500 net profit margin, by era. The final leg is dashed on every series: it is a scenario, not a forecast. Sources: BLS and IMF productivity series; FactSet S&P 500 net margins. Click the chart to open it full size.

US labour-productivity growth ran at about 2% a year in the 1990s and spiked near 3.3% in the 2000–05 window, then fell back to roughly 1.5% for the entire cloud decade. It has not recovered.

Now look at margin. The S&P 500’s blended net profit margin hit 13.4% in Q1 2026 — the highest since FactSet began tracking the measure in 2009 — after sitting in the mid single digits through the 1990s.

IT spending has been converted into margin — pricing power, cost displacement, concentration — far more reliably than into output per hour. Whatever your board says it is measuring, that is the scoreboard it is actually using.

The finding that complicates all of this

The standard narrative says 1990s IT investment produced the late-90s productivity boom. McKinsey Global Institute spent a year testing that and published the results in October 2001. What they found was that virtually all of the 1995–2000 acceleration came from just six sectors — retail, wholesale, securities, semiconductors, computer manufacturing and mobile telecom. Within those sectors, IT was not found to have a dramatic independent impact; it contributed to roughly the same degree as other factors of production. The primary drivers were competition and industry-specific innovation.

MGI’s 2017 follow-up sharpened it: the gains materialised only where complementary business-process change happened, usually because competitive pressure forced it. Two cases from the same decade, on the same technology, make the point better than any model.

  • Restructured around it — Walmart, Intel. Walmart rebuilt distribution and store operations around its systems. Intel overhauled production to move faster to higher-value products. Sector productivity rose.
  • Layered it on top — retail banking. Grew IT spend through 1995–99 while sector labour productivity fell. It built online banking, made customers happier, and moved nobody to higher-value products.

Same technology. Same era. Same spend trajectory. Opposite outcomes. Convenience without restructuring produced no productivity gain at all.

What this means for the AI cycle

Three inferences follow — each held loosely enough to be argued out of.

1. The payoff arrives one era late, and in the buyer’s hands rather than the builder’s

The productivity surge didn’t coincide with 1990s spending. It arrived after it, while budgets were frozen and the vendors were going bankrupt. Meanwhile 85% of that decade’s fiber was still dark by the mid-2000s, and eventually got used at pennies on the dollar by Netflix and Google. Overbuild is not the same thing as waste; it is a transfer from the people who financed it to the people who arrive after the write-down.

The AI version has one important difference, and it cuts against the optimists. Fiber in the ground depreciates over twenty-plus years, and its salvage value survived the bust. A GPU fleet depreciates over three to five — the salvage value of an AI overbuild is far thinner.

2. The binding constraint is competitive pressure, not budget

If the 1990s payoff came from six sectors that restructured under pressure, the question for a board is not “how much are we spending on AI.” It is which of our businesses is under enough competitive pressure to actually restructure around it. Budget is the easy variable, and the one least correlated with outcome.

The current evidence is consistent with that. McKinsey’s 2025 State of AI survey found near-universal adoption and almost no enterprise-level financial effect: 88% use AI in at least one business function, 39% report any enterprise-level EBIT impact (most below 5%), 7% describe AI as fully scaled, and roughly 6% qualify as high performers.

What separates the top group is not model quality or budget. It is workflow redesign. MIT’s NANDA study reached the same place by a different route, finding the overwhelming majority of GenAI pilots delivering no measurable P&L impact, with the gap traced to enterprise integration rather than to the technology. This is the ERP story and the lift-and-shift cloud story, repeated with new nouns.

3. Most large enterprises won’t own the assets they benefit from — and shouldn’t want to

Total IT-related investment has reached about 5% of US GDP, exceeding the dot-com peak. But unlike 2000, which was driven almost entirely by firms using IT, this boom is driven by the firms producing it. For a large non-tech enterprise, your own AI budget is a rounding error next to the supply-side build: you are a price-taker on compute. That argues for a specific posture — be a late, cheap, aggressive buyer of compute rather than an early builder. It is close to the opposite of what most 2025–26 AI strategies assumed.

Three paths to 2032

Rather than a single forecast, three scenarios, weighted by judgement rather than by any model. Each has a historical rhyme — which is the honest way to describe how the weighting was reached.

Three panels comparing IT spend scenarios to 2032: A. Acceleration at about 12 percent CAGR reaching $12.6 trillion, weighted 20 percent; B. Disciplined build at about 6.5 percent CAGR reaching $9.2 trillion, the base case weighted 50 percent; C. Digestion at about 4.3 percent CAGR reaching $8.1 trillion, weighted 30 percent.
Three paths to 2032. Each panel shows one scenario against the other two in grey, 2026 to 2032. Weightings are judgements, not model probabilities. Click the chart to open it full size.

What to do about it

Five things worth putting in front of a board this quarter.

  • Manufacture the deadline. Y2K’s structural advantage was a date that could not move, which forced scope discipline. AI has no such date, so governance has to supply one — per workflow.
  • Fund the back office first. Budget concentrates in customer-facing pilots where returns are hardest to attribute. Measured ROI is consistently highest in unglamorous internal automation.
  • Buy the workflow, build the moat. Vendor-partnered deployments succeed materially more often than internal builds. Build only where the workflow is the differentiation. See our series on deploying AI at commercial scale.
  • Underwrite on a three-year asset life. Model refresh cycles are shorter than any prior IT asset class. Treat inference cost curves as your single largest sensitivity.
  • Instrument for margin, not adoption. Seat counts and usage dashboards are the 2026 equivalent of counting installed servers. Cost-to-serve, cycle time and gross margin per unit are what the last three cycles were graded on.

What would change our mind

Four observable markers, each with a direction attached before the fact:

  • Q4 2027 hyperscaler guidance. Flat or declining 2028 capex after four years of 50%+ growth would move C to the base case.
  • Enterprise ROI evidence by mid-2027. BCG’s 2026 survey found roughly 26% of firms generating meaningful financial value. Above about 50% makes A live.
  • Inference cost per token. A sustained order-of-magnitude fall pushes spend down while adoption rises — C’s spend line with A’s productivity line.
  • Depreciation-schedule disclosures. Any hyperscaler extending useful asset life beyond six years is defending reported earnings against the amortisation wave.

The uncomfortable version

Global IT spend in the 1990s was roughly $2 trillion a year, and it coincided with productivity growth around 2.4%. The base case for 2027–32 is $8–9 trillion a year against productivity growth near 2.0%. If that holds, AI’s aggregate economic return per dollar will be materially worse than the internet’s.

That is not an argument against spending. It is an argument about dispersion. Aggregate productivity figures average the leaders together with the non-adopters and the failed implementations. The 1990s produced Walmart and retail banking, out of the same technology in the same decade. Which one you resemble was determined by whether you restructured, not by what you spent.

Every one of these cycles came down to the same constraint: not the technology, and not the budget, but whether the organisation had the people and the process design to restructure around it. That is the part that doesn’t arrive with the invoice.

The spend is the easy part. It always was.

Sources and method

Gartner worldwide IT spending forecasts (April 2026: $6.31T for 2026, +13.5%; $7.6T by 2029). McKinsey Global Institute, US Productivity Growth 1995–2000 (October 2001) and its 2017 follow-up. McKinsey State of AI 2025. MIT NANDA. BCG AI-adoption survey, 2026. BLS and IMF productivity series. FactSet S&P 500 net margins (Q1 2026 blended: 13.4%, highest in the series since 2009). Hyperscaler capex guidance as reported through Q1 2026 — Amazon about $200B, Alphabet $175–190B, Meta $115–145B, Microsoft $120B and above, together roughly $725B and about 77% above 2025.

Pre-2005 spend is estimated, because definitions of “IT spending” changed materially over that period. Projections are scenarios, not forecasts. The equity-return series is illustrative and is not investment advice.