跳到正文

AI Capital Is Running Ahead of AI Earnings

AI Capital Is Running Ahead of AI Earnings
AI Capital Is Running Ahead of AI Earnings

Oracle’s Miss and the Growing Gap Between Compute Investment and Cash Flow


The easiest way to misunderstand an AI bubble is to look for the 1999 version: vaporware companies with no product, no revenue, and absurd market caps.


That is not the current setup.


This bubble—where it exists—is capex-shaped, expectation-shaped, and time-to-cashflow-shaped. The public market is not funding “nothing.” It is funding a timeline: the belief that today’s AI spending becomes durable, high-margin, multi-year earnings fast enough to justify today’s valuations and today’s infrastructure buildout.


When that timeline slips, you don’t get a polite correction. You get an expectations crash: revenue doesn’t arrive at the promised slope, margins don’t scale at the promised speed, and the stock reprices even if the company is “growing.”


Oracle just gave a clean, recent example of how this happens in real life.


1) The Oracle Problem: When “AI Demand” Exists but Cashflow Doesn’t


Oracle’s latest outlook missed what the market wanted—not because “AI isn’t real,” but because the business mechanics look increasingly like an infrastructure race with uncertain payback periods.


In Oracle’s December 2025 update, the company issued a sales and profit forecast that came in below Wall Street expectations: it guided adjusted EPS of $1.64–$1.68 vs. ~$1.72 expected, and revenue growth of 16%–18% vs. ~19.4% expected. 


At the same time, Oracle lifted expected fiscal 2026 capex by roughly $15B, tied to AI cloud data center buildout. 

Investors responded by marking the stock down sharply, because the market is now forcing a question it postponed in 2023–2024:


What is the ROIC (return on invested capital) of the AI buildout, and when does it show up in earnings?


Oracle’s numbers make the tension visible:

  • Oracle’s quarterly revenue was ~$16.1B (about +14% YoY) but still described as missing expectations in major coverage. 

  • Capex is projected to surge to ~$50B (Financial Times reporting: “over 40%” increase; also widely framed as a scale-jump into AI data centers). 

  • Reuters’ Breakingviews emphasizes the cashflow mismatch: capex ~$12B vs operating cash flow ~$2.1B in the period discussed, a textbook “cash burn for growth” profile—except the market thought Oracle was migrating into a more stable cloud annuity model. 

  • FT highlights balance-sheet strain concerns, noting Oracle’s debt rising and credit protection costs moving—signals that bondholders are asking for more compensation to fund the buildout. 


This is not a moral failure by Oracle. It’s a structural dynamic:

  1. AI demand pulls forward infrastructure investment (data centers, chips, power, cooling, networking).

  2. That investment front-loads cash outflows.

  3. Revenue arrives later, and margins arrive later still—especially if pricing becomes competitive or customers demand financing-like terms.


A bubble begins not when demand is fake, but when the market prices demand as if payback is guaranteed and fast.


Oracle’s downgrade moment is essentially the market saying:


“Show me the path from AI enthusiasm to durable, margin-rich earnings—while you’re also spending tens of billions.”


And that’s the heart of the new bubble: the gap between narrative velocity and earnings velocity.


2) The Second Signal: “AI Companies” Missing Their Own Growth Story


Oracle is a mega-cap infrastructure and software business. But the bubble risk is easier to see in smaller “pure AI” names because the narrative is often simpler:

  • “Enterprises are adopting AI rapidly.”

  • “We are the software layer for AI.”

  • “Revenue will ramp.”

  • “Operating leverage will appear.”


The problem is that enterprise adoption is real but uneven, procurement cycles are slow, and budgets can shift from “experiments” to “platform consolidation” without producing the hockey-stick revenue line investors are paying for.


Example A: C3.ai — Revenue stalling under the AI label


C3.ai’s own results show how the “AI premium” can detach from operating reality.


In its Fiscal Q2 2026 results (reported Dec 3, 2025), C3.ai reported:

  • Total revenue: $75.1M

  • Subscription revenue: $70.2M (93% of total)

  • GAAP net loss per share: $(0.75) (non-GAAP $(0.25)) 


Revenue at ~$75M is not inherently “bad.” The issue is the mismatch between the AI narrative (implied scale) and the actual business profile (still loss-making, still relatively small revenue base, still sensitive to deal timing and services mix).


Earlier in 2025, market coverage repeatedly framed C3.ai as missing revenue expectations in certain quarters. One Yahoo Finance summary, for example, described a quarter where revenue fell ~19% YoY and “missed Wall Street’s revenue expectations.” 

(Always treat secondary summaries cautiously; the company’s own release above is the cleanest source for the raw numbers.)


Bubble mechanics show up when:

  • The market prices the company as a future platform winner,

  • but the revenue line behaves like a niche enterprise vendor under procurement friction,

  • while profitability remains a distant target.


This is the “AI wrapper” problem: the label compresses skepticism. Investors skip the boring questions (“what’s repeatable?”, “what’s the sales cycle?”, “what’s the churn?”, “what’s CAC payback?”) because the macro story is intoxicating.


Example B: BigBear.ai — Revenue misses and guidance pressure under “AI demand”


BigBear.ai is a smaller name, but it illustrates the same dynamic: AI narrative meets contracting realities.


In Q2 2025, Reuters reporting (via a market feed) noted:

  • Revenue fell ~18% YoY and missed analyst expectations (per LSEG),

  • net loss widened materially (with non-operating items cited),

  • and the company guided full-year 2025 revenue of $125M–$140M. 


The company’s own announcement also states its updated full-year 2025 revenue outlook of $125M–$140M. 


This matters because it’s the opposite of the bubble’s implied story. The bubble story says: “AI spending unlocks growth.”

But in practice, especially for government-adjacent and services-heavy AI implementations, you can get:

  • delayed awards,

  • lumpy projects,

  • budget reprioritizations,

  • and revenue volatility that does not deserve software-like multiples.


Again: demand for AI is real. But the translation layer from interest → signed contracts → recognized revenue → profits is where bubbles die.


3) The Third Signal: “Raised Guidance, Still Not Enough” — Expectations Become the Product


Bubbles often reach the stage where the product isn’t the product. The product is the beat-and-raise ritual.


A classic Reuters line about Palantir captured the vibe in May 2025: shares fell hard even though results and forecasts improved, because they failed to impress investors whose expectations had already moved beyond reality. 


This is how bubbles evolve:

  1. Phase 1: “AI is coming.” (Narrative)

  2. Phase 2: “Look at the growth.” (Revenue acceleration)

  3. Phase 3: “Look at the guidance.” (Forward expectation)

  4. Phase 4: “Look at the rate of change of guidance.” (Second derivative)

  5. Phase 5: “Nothing is enough.” (Fragility)


Once you’re in Phase 4–5, even good news causes sell-offs, because the market is addicted to acceleration itself.


Business Insider described a similar “expectations trap” recently around Broadcom: strong results, but shares dropped because investors wanted even more clarity and magnitude on AI revenue. 

This isn’t about Broadcom per se; it’s about a regime where AI narrative expectations are priced as a certainty.


4) Why This Bubble Is Different: It’s an Infrastructure Bubble Wearing a Software Mask


The dotcom bubble overbuilt fiber. The 2000s overbuilt housing finance. The 2020–2021 era overbuilt duration assets at near-zero rates.


The AI cycle’s main bubble risk is overbuilding compute relative to near-term monetization.


Oracle’s capex shift is a clean example because it’s explicit: enormous spending justified by AI cloud demand, with the market suddenly asking about cashflow discipline and financing structure. 


Here’s the uncomfortable reality:

  • Compute is not just “servers.” It’s power, grid constraints, cooling, land, network, supply chain, financing, and depreciation schedules.

  • If you build too much too early, you don’t just get idle capacity. You get financial gravity: lease obligations, capex commitments, and margin pressure.


FT noted Oracle’s reliance on leasing and large future commitments; the more this becomes true across the sector, the more the AI cycle begins to look like a capital markets story, not just a software story. 


When the cycle turns, software companies can slow hiring.

Infrastructure-heavy companies can’t “unbuild” a data center.


That asymmetry is where bubbles hide.


5) The “Oracle Miss” as a Template for How AI Disillusions Markets


The market reaction to Oracle’s forecast miss matters because it’s a pattern:

  • Growth is real.

  • AI demand is real.

  • But the price of that growth assumes an unreal timeline.


Oracle missed on a forecast and future cloud-contract metric while ramping spending. Reuters described the miss in a “closely watched metric for future cloud contracts” and a below-expectations growth outlook. 


That’s exactly how disillusionment starts:

  1. The market sees “AI demand”

  2. Then it sees “AI spending”

  3. Then it sees “AI profits (later)”

  4. Then it asks: “What if later is much later?”


And the re-rating happens before the earnings collapse, because the re-rating is a duration reset: the market suddenly discounts the future at a harsher rate.


6) What “Bubble” Actually Means in This Context


“Bubble” does not mean “AI is fake.”


It means:

  • The marginal dollar invested assumes a return that requires perfect execution.

  • The story assumes no pricing pressure and no substitution.

  • The buildout assumes the demand curve stays steep enough to absorb capacity.

  • The market assumes the second derivative stays positive.


Oracle’s update makes the financing and execution pressure visible. 


C3.ai’s losses and scale show how small the “AI application layer” revenue can be compared to the multiples applied. 


BigBear.ai’s miss shows how “AI demand” does not automatically become revenue. 


The bubble is the gap between AI as a technology and AI as a priced certainty.


7) A Practical Bubble Checklist for Investors


If you want something operational (not philosophical), here is the bubble checklist that matters now:


A) Capex-to-cashflow mismatch


Oracle’s capex vs operating cashflow gap is the kind of thing that forces a narrative into a spreadsheet. 

If capex is outrunning cash generation, you are no longer investing in software. You are investing in financing + utilization rates.


B) Guidance misses, even small ones, trigger large repricing


Oracle guided EPS and growth below expectations and got punished hard. 

This indicates the market is priced for perfection.


C) “AI company” revenue base remains small and loss-making


C3.ai’s revenue and loss profile makes it clear: this is not yet a scaled platform business. 

If the company is priced as a future monopoly but operates like a vendor, the multiple is fragile.


D) Volatility and lumpiness in contract-driven AI businesses


BigBear.ai’s miss and revised outlook illustrate this. 

If revenue is project-like, it cannot wear subscription-like multiples for long.


E) “Not enough” syndrome after a huge run


Reuters framing around Palantir’s market reaction—strong update, still punished—captures the regime. 

When expectations become the product, the stock becomes a forward disappointment machine.


8) The Most Important Distinction: AI Adoption vs AI Monetization


You can have widespread adoption and still have a bubble—because adoption is not the monetization bottleneck.


In enterprise AI:

  • pilots happen fast,

  • production happens slow,

  • budget approvals are political,

  • and “AI features” often get bundled into existing platforms instead of sold as standalone revenue.


That bundling is lethal to the “pure AI” revenue story. It compresses pricing.


Meanwhile, the infrastructure layer is racing ahead of that monetization timeline.


So the bubble risk is not “AI stops.”

The bubble risk is:


AI continues, but monetization per unit of compute is lower than expected.


That is how you get a capex hangover.


9) What Happens If This Bubble Deflates


Deflation doesn’t require a crash. It can happen via:

  • multiple compression,

  • sideways markets while earnings catch up,

  • and selective busts among the weakest names.


A “small AI deflation” theme is explicitly raised in Reuters Breakingviews around Oracle. 


Mechanically, deflation looks like:

  1. Guidance misses are punished.

  2. Capex plans face skepticism.

  3. Financing costs creep up.

  4. Customers renegotiate terms.

  5. Margins disappoint.

  6. Stocks re-rate lower even as revenue grows.


This is why “AI bubble” talk can be simultaneously true and misleading:

  • It’s true because the market priced a perfect timeline.

  • It’s misleading because the technology will likely keep compounding.


10) The Takeaway


The current AI bubble—where it exists—is not about whether AI works.


It’s about whether the market has confused:


“AI is transformative”

with

“AI transforms earnings at the speed implied by current valuations and capex commitments.”


Oracle just reminded the market that those are different claims. 


C3.ai and BigBear.ai remind the market that “AI company” is not a revenue model—execution is. 


And the expectation regime across AI-linked equities suggests we are closer to the fragile end of the cycle than people want to admit. 


HIVEAI.png