AI datacenter capex will far exceed forecast revenue through 2030
Investors are pouring more into AI data center infrastructure than they can hope to recoup by 2030, according to Gartner. “Enterprise and consumer AI revenue will be insufficient to support profitable returns on all planned AI capital expenditures during this period,” said Gartner Senior Director Analyst Will Sommer.
Investors are pouring more into AI data center infrastructure than they can hope to recoup by 2030, according to Gartner. “Enterprise and consumer AI revenue will be insufficient to support profitable returns on all planned AI capital expenditures during this period,” said Gartner Senior Director Analyst Will Sommer.
AI data center owners would need to generate $8.5 trillion in revenue through 2030 to cover announced capital spending, financing costs and expected investment returns, he said. “However, total enterprise and consumer AI revenue that can be attributed to AI data centers during this period is forecast to reach no more than $3.6 trillion.”
Gartner joins a growing chorus warning that major AI players may be over-committing themselves. Bain and Co. recently made a similar forecast, estimating that annual spending on AI infrastructure could reach $1.5 trillion by 2031 and that the AI services market would need to top $6 trillion annually to pay for it.
This is particularly bad news for neocloud providers, said Gartner. While the hyperscalers are large enough to absorb the financial pressures, the research company suggests that the cost pressure will force more than 80% of neocloud providers to cease independent operations.
The Bain and Gartner surveys don’t cover quite the same ground, but their conclusions are very similar: a lot of AI infrastructure investment is never going to make a return, and companies need to prepare themselves for some degree of financial loss.
In context
- Topic: Estrategia y Gobierno de TI — Decisiones de portafolio, costo total, gobierno y marcos de referencia.
- Source: CIO
- Published: 16/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
There is a wide gap between a company that has technology projects and one that has a technology strategy. The first accumulates initiatives; the second decides what it will not do. Moves like this are usually the moment somebody at the top finally wrote down the list of what gets left out.
I read it looking for coordination cost. Every technology decision splits work across areas that do not report to each other, and that is where the return leaks out. If nobody defined who resolves it when two areas disagree, the project already has its grounding date set.
What usually goes wrong
What usually goes wrong is the part never discussed with the areas that will carry the work. It gets decided at the top, communicated downward, and the resistance shows up not as opposition but as slowness. Nobody says no; everything simply takes twice as long and nobody can explain why.
What to watch
- Who ends up owning the decision, and with what budget of their own rather than borrowed.
- Whether business metrics appear or only delivery metrics — cost per transaction beats percentage complete.
- The real calendar of contracts and renewals: that is where you see whether the move was strategic or was an expiry date.
How I read this entry
I would treat it less as a technology story and more as a market signal. If one player moves this way, in twelve to eighteen months the rest will have to answer something. Better to decide now, calmly, what that answer will be, rather than improvise it when a client asks.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
