Oracle's New AI Models Won't Save Apps-Unless They Turn Into Real Workflow Revenue

Oracle's real test is whether AI can become billable workflow software

The key question is not whether Oracle can ship another model. It is whether those models can do real work inside the applications businesses already pay for.

From feature to worker

Management says customers have moved past the experiment stage with AI and want complete agentic solutions to help run their businesses. That is the shift that matters: features get demos, but workflows get budgets.

Oracle's pitch is that Fusion Applications can do work, not just display data. The company describes agents spanning finance, HR, supply chain, and customer experience that can plan, reason, and execute processes across those systems. If that holds up in practice, AI moves from add-on functionality to a core part of how the software earns its keep.

Demand also looks real. Oracle finished FY2026 with total cloud revenue of $34.0 billion, while both cloud infrastructure and cloud applications continued growing. But investors still need proof that agentic capabilities convert into recurring application revenue rather than short-lived excitement or isolated pilots.

Why embedding agents in apps could matter more than the model itself

The potential moat is not merely model capability. It is how easily the model fits into software customers already use, buy, and operate.

Distribution and stickiness are built into existing workflows

Oracle already has a large installed base, and agentic AI is being placed directly into the workflows those customers use every day. Fusion Applications can do work across finance, HR, supply chain, service, and sales, which makes the suite harder to displace the more real tasks it handles.

Redwood is the distribution path. Oracle says the Redwood experience is a requirement for accessing embedded AI capabilities in Sales and Service, and that in-product accelerators can automate up to 80% of the migration effort. That does not guarantee adoption, but it does reduce friction compared with asking customers to adopt a separate AI layer from scratch.

On the backend, Oracle's argument is that controlling apps, data, infrastructure, and AI tooling together can simplify deployment and performance. OCI Supercluster networking sub-10 microsecond latency at massive scale gives a concrete example of that infrastructure edge. The practical upside is cleaner integration and lower friction when AI lives inside the same stack as the application and the data it acts on.

The stack advantage only matters if usage follows

That advantage is only meaningful if customers actually use the agents inside daily workflows. Oracle also says its embedded AI can be turned on in many cases no complex integrations, no custom models, no separate platforms to manage. If deployment is simpler and the tools prove useful, existing customers are the clearest launchpad.

The investor debate: infrastructure growth versus application monetization

The bull case is straightforward: Oracle has strong demand, and that demand could shift from pure compute spend toward higher-value application spend as customers mature in their AI adoption.

Why the bull case still looks credible

Oracle ended FY2026 with total cloud revenue of $34.0 billion. It also reported FY 2026 Cloud Infra (IaaS) Revenue $18.1 billion, up 77% USD and FY 2026 Cloud Apps (SaaS) Revenue $15.9 billion, up 11% USD. Bulls read that as two sides of the same build-out: infrastructure demand is leading, but the applications business is still growing.

Management's comment that customers have moved past the experiment stage with AI strengthens that view. If customers are shifting from testing to implementation, Oracle's infrastructure lead could support future software pull-through.

Where the bear case gets traction

The counterargument is that the financials still lean heavily on infrastructure. In the fourth quarter, Oracle still missed on cloud revenue, and cloud applications revenue came in below expectations. At the same time, the company said it will raise roughly $40 billion to fund data-center expansion.

That leaves Oracle with a harder test: can it turn current demand into cleaner app revenue before capex and execution concerns start to dominate the story? A large backlog helps, but it does not settle the question of mix.

What would actually validate the thesis

The market does not need another demo. It needs evidence that AI is becoming part of the core revenue story.

The signals that matter most

• Redwood migration progress. Redwood is a requirement for accessing embedded AI capabilities in Sales and Service, and Oracle says accelerators can automate up to 80% of the migration effort. Adoption here matters because it controls access to embedded AI in those products.
• Real agent usage. Look for signs that built-in tools are being used in daily work, not just shown off in walkthroughs.
• Broader suite expansion. The key question is whether AI moves with customers as they expand core modules across ERP, HCM, SCM, and CX.
• Better app conversion. After the recent miss on cloud revenue, investors need firmer evidence that application revenue is catching up, rather than the quarter being carried mostly by AI-driven infrastructure demand AI infrastructure as a key growth driver.

Catalyst and invalidation

The next earnings reports and customer adoption updates should show cleaner conversion from infrastructure demand to application revenue. If Oracle can demonstrate broader Redwood migration, sustained agent usage, and healthier app growth, the thesis gets stronger. If not, the story risks staying trapped between AI optimism and capex scrutiny.