The Stock Market Is Underestimating the Massive Growth Potential of This Artificial Intelligence (AI) Giant That Could Easily Become a $1 Trillion Company

Oracle reported Q4 revenue of $19.2 billion, up 21% year over year, and EPS of $2.11, ahead of analyst expectations, but the stock fell more than 8% on concerns about heavy AI data center capex. The company’s remaining performance obligation surged to $638 billion from $138 billion a year earlier, with management saying 46% of backlog, or about $293 billion, should convert to revenue over the next three years. The article argues this backlog and buildout could drive revenue to $90 billion in fiscal 2027 and support a path toward a $1 trillion market cap.

Analysis

The market is still pricing Oracle as a cyclical software name, but the economics are increasingly those of a capacity-constrained infrastructure landlord with multi-year contracted demand. The key second-order effect is that capex is no longer just a drag on free cash flow; it is the gating item for revenue recognition, which means the equity should re-rate as the supply bottleneck relaxes over the next 4-12 quarters. That dynamic also creates operating leverage: once a data center cohort reaches utilization, incremental revenue should fall through at a much higher margin than the build phase suggests.

The clearest winner is not just ORCL, but the broader AI supply chain that benefits from Oracle absorbing demand that otherwise would have been stranded with hyperscalers. NVDA benefits from the implied acceleration in accelerator deployment, while GS may benefit indirectly through financing activity and capital-markets fees tied to large-scale infrastructure funding. The loser set is subtler: if Oracle succeeds in securing long-duration AI contracts at scale, it pressures smaller colo and GPU-hosting competitors by locking up enterprise demand and potentially tightening access to power, land, and networking equipment.

The consensus miss is the mismatch between near-term margin optics and mid-cycle earnings power. Investors are anchoring on diluted margins and financing needs, but the real question is whether backlog converts on schedule; if it does, earnings estimates for the outer years are likely still too low because they assume a smoother ramp than these contracts can produce. The tail risk is execution: delays in grid interconnects, cooling, or power procurement would push conversion further out and force the market to focus on leverage and dilution instead of backlog monetization.

From a trading standpoint, this is more of a 6-18 month story than a 1-2 week bounce. The setup favors buying weakness after post-earnings de-risking, especially if management continues to pre-announce capacity additions and backlog conversion milestones; the stock likely needs evidence, not promises, to re-rate. The asymmetric trade is that downside from here is mostly multiple compression on capex anxiety, while upside is a credibility-driven re-rating once revenue growth visibly inflects.

Key Decisions for Investors

• Long ORCL on further post-earnings weakness; target a 6-12 month horizon with a thesis that backlog conversion and revenue inflection will overwhelm capex concerns. Risk/reward improves if the stock trades closer to 20x forward earnings, where downside is better absorbed by contracted visibility.
• Buy ORCL Jan-2027 calls or call spreads to express the 12-24 month backlog-conversion story while limiting drawdown from financing and execution risk. Prefer strikes that monetize a move into the low-$300s, where multiple expansion and earnings growth can compound.
• Pair trade: long ORCL / short a basket of weaker AI infrastructure enablers with less contracted visibility or weaker balance sheets. The relative-value edge is that Oracle has identifiable demand, while many peers are still story stocks without comparable backlog.
• Add NVDA on Oracle-related weakness in the AI complex as a second-order beneficiary of accelerated deployment cycles. Use it as a cleaner expression of AI capex continuation if you want less balance-sheet risk than ORCL.
• Avoid chasing the move in the next 1-2 weeks; wait for evidence of data-center ramp milestones or another quarter of backlog conversion before sizing aggressively. Execution slippage is the main catalyst that could reverse the thesis.