Public Company Underwriting Case Study

Applied Underwriting Case Study: Oracle Corporation

AI Infrastructure, Capital Intensity, Financing, and Residual Common Equity

The Underwriting Question

Can Oracle convert extraordinary AI infrastructure demand into durable cash returns sufficient to justify the scale of its capital investment, financing requirements, and long duration commitments before residual value reaches common equity?

Executive Underwriting Conclusion

Demand is visible in Oracle’s public disclosures. The harder underwriting issue is the economics of fulfilling it. Data center construction, servers and accelerators, power infrastructure, lease commitments, cash interest, taxes, preferred distributions, and dilution all sit between contracted demand and the value ultimately available to common shareholders.

Oracle enters this buildout with real advantages: substantial operating cash generation, liquidity, capital markets access, and a deeply embedded software and database franchise. Those strengths give management room to fund the expansion without treating every quarter as a financing event.

The scale of the build still matters. Capital is being committed well ahead of revenue recognition. Funded debt is rising, equity linked capital has been issued, and long duration infrastructure obligations are accumulating. Returns depend on capacity coming online, customers deploying as expected, and utilization reaching levels that justify the investment.

Oracle should be underwritten through the cash economics of the buildout. RPO and OCI growth establish demand and operating momentum. They do not establish the return on the capital required to serve that demand. The analysis has to follow those contracts through infrastructure spending, financing, cash conversion, and the claims ahead of common equity.

The case does not require a predetermined view on the common shares. It requires discipline about where value is created, how it is financed, and what remains after the obligations created during the buildout are recognized.

The Central Underwriting Question

Does Oracle’s extraordinary contracted AI and cloud demand generate sufficient cash returns to justify the scale of its data center investment, financing requirements, lease commitments, and execution risk, and how much residual value remains for common shareholders after those claims are recognized?

Why Oracle Is a Capital Structure and AI Infrastructure Case

Oracle is often discussed as a technology growth company, which is understandable given OCI growth, AI demand, and the size of its contracted backlog. That framing is incomplete once growth requires a rapidly expanding physical infrastructure base.

The current strategy combines contracted demand with substantial capital expenditures, debt issuance, equity financing, long duration data center commitments, power requirements, equipment procurement, customer concentration, and execution risk. Those factors now belong in the core equity underwriting, not in a separate financing discussion.

Oracle does not earn the economics of its backlog when a contract is signed. Capacity has to be built, financed, powered, deployed, utilized, maintained, and paid for before the value can be judged at the common equity level.

Applied Analytical Sequence

Operating Performance → EBITDA Quality → Cash Flow Conversion → Capital Structure → Leverage and Liquidity → Downside Resilience → Residual Common Equity

Operating Performance

Oracle entered the current infrastructure cycle with a large recurring software and database business that generates substantial operating cash flow. That legacy cash engine matters because it provides internal funding capacity while OCI expands.

At the same time, OCI is changing the economic profile of the company. Infrastructure revenue is growing substantially faster than the mature software businesses, but the associated growth requires far more physical capital than Oracle’s traditional software model.

Consolidated revenue growth can obscure the changing capital profile of the business. The installed software franchise remains a major source of cash, while OCI requires a much larger physical asset base. The combined company should be judged on whether infrastructure growth improves residual cash generation after the associated investment is funded.

Cloud Infrastructure Growth

Oracle Cloud Infrastructure has become the principal growth engine in the company’s current investment cycle. Rapid OCI growth supports the strategic rationale for expanding capacity, but growth alone does not establish the return earned on the capital required to produce it.

Incremental OCI revenue should be measured against the incremental asset base, financing cost, depreciation, lease obligations, power expense, and operating costs required to support it.

The investment case becomes stronger as newly deployed capacity reaches attractive utilization, produces durable cash margins, and earns returns above the full cost of the capital used to build it. Rapid growth without those economics is not enough.

Remaining Performance Obligations and Contract Quality

Oracle’s remaining performance obligations provide unusually strong visibility into future contracted business. RPO is still a backlog measure, not collected cash and not an unconditional measure of future economic value.

RPO represents contracted performance obligations that are expected to be recognized over time according to the terms of the underlying agreements. Revenue recognition depends on Oracle performing its obligations and on the timing and structure of customer deployment.

Some large AI infrastructure arrangements have included customer prepayments or customer supplied equipment. Those structures can materially reduce Oracle’s own funding requirement and improve contract economics. They should be distinguished from contracts for which Oracle must fund a larger portion of the required infrastructure itself.

Headline backlog is only the starting point. Contract economics depend on funding structure, deployment schedule, customer concentration, performance requirements, duration, pricing, renewal terms, and the amount of Oracle capital required before revenue can be earned.

EBITDA Quality

EBITDA and operating income can provide useful measures of operating performance, but neither should be treated as cash available to common shareholders. Oracle’s infrastructure expansion increases the importance of examining the capital intensity behind reported earnings.

For Oracle, earnings quality should be evaluated through utilization, depreciation, equipment useful lives, financing costs, contract economics, and the amount of recurring capital required to maintain technological competitiveness.

A dollar of earnings from the mature software franchise does not carry the same capital burden as a dollar produced by AI infrastructure. Incremental infrastructure earnings should be judged against the cash invested to produce them, rather than folded into consolidated growth and assumed to carry the same economic quality.

Cash Flow Conversion

Cash conversion connects Oracle’s contracted growth to the balance sheet. Strong revenue growth and substantial operating cash flow can coexist with a need for external capital when infrastructure spending runs ahead of internally generated cash.

Oracle’s underlying enterprise remains highly cash generative. At the same time, negative free cash flow during the buildout shows that internal cash generation is not funding the full pace of expansion. That gap is being financed, and the terms of that financing matter to the common shareholder.

The issue is whether the infrastructure program produces enough incremental cash to cover the capital consumed, financing claims created, and dilution accepted during the buildout. Until that cash arrives, reported growth and financing capacity should not be mistaken for completed value creation.

Cash Conversion Bridge

Cloud and Software Revenue − Operating Costs − Cash Interest − Cash Taxes ± Working Capital − Data Center Construction − Servers, Accelerators, and Networking − Power Infrastructure − Lease Cash Requirements − Preferred Distributions − Other Mandatory Uses = Residual Cash Available

Capital Expenditure Program

Oracle’s capital expenditure program has expanded rapidly as the company builds capacity for large AI and cloud contracts. At this scale, capital allocation and infrastructure returns become central to the underwriting.

Capital expenditures should be separated conceptually between capacity that is already contracted, capacity supported by customer prepayments or customer supplied equipment, speculative or anticipatory capacity, maintenance requirements, and infrastructure that may require additional investment before reaching economic utilization.

High capital spending can create substantial value when the assets earn attractive risk adjusted returns. The key variables are the amount invested, the timing of deployment, utilization, contract economics, and the financing cost carried before the assets reach maturity.

Data Center Construction and Capacity Deployment

Contracted demand becomes economically useful only as capacity comes online and customers deploy. Construction schedules, equipment delivery, power availability, networking, cooling, permitting, labor, and third party data center execution can all move the timing of revenue and cash returns.

Oracle has itself identified construction timing, customer funding, and operational issues as variables that can affect future capital requirements. Outside reporting has also described changes to individual project plans. Those reports should be treated separately from company reported financial facts, but they reinforce the importance of deployment timing in the underwriting.

A delayed data center does not necessarily destroy contract value. It can, however, defer revenue recognition while financing costs and other commitments continue to accrue. The economic impact depends on the contract terms, the duration of the delay, the ability to redirect capacity, and which party bears the incremental cost.

Capital Structure and Debt Financing

Oracle has used substantial debt financing to support the infrastructure expansion. The company retains investment grade market access and meaningful liquidity, but the increase in funded debt creates higher interest expense and a larger senior claim ahead of common equity.

Debt can be an efficient source of capital when the assets financed with it generate returns comfortably above the borrowing cost. It becomes more restrictive when revenue conversion is delayed, utilization disappoints, refinancing terms worsen, or infrastructure requires additional capital before producing expected returns.

Gross debt alone is not enough. Debt should be evaluated against recurring operating cash flow, interest coverage, maturity concentration, liquidity, infrastructure commitments, and the expected cash return on the assets being financed.

Equity Financing and Dilution

Oracle’s financing strategy also includes equity and equity linked capital. Mandatory convertible preferred securities create a senior distribution claim before conversion and ultimately increase the common share count. An at the market common equity program creates additional potential dilution.

Equity financing reduces the amount of incremental debt required and can protect the company’s investment grade profile. The cost is borne through dilution of the residual claim.

Debt and equity solve different financing problems. Debt preserves the share count but adds fixed claims. Equity protects leverage at the cost of dilution. Oracle’s infrastructure returns ultimately have to clear the combined economic cost of both.

Construction, Lease, Purchase, and Equipment Commitments

Funded debt does not capture the full economic burden of Oracle’s infrastructure strategy. Long duration data center leases, power arrangements, equipment purchases, construction commitments, and other contractual obligations can require substantial future cash even before all associated assets appear as conventional funded debt on the balance sheet.

A narrow funded debt measure can understate the burden on future cash when large contractual commitments sit outside that figure. For Oracle, those commitments are part of the capital structure analysis because they reduce flexibility whether or not they are labeled debt.

The capital stack should therefore be viewed broadly: funded debt, preferred capital, commenced lease liabilities, significant noncommenced lease commitments, power obligations, purchase commitments, and other material claims on future cash.

Liquidity and Refinancing Capacity

Oracle’s liquidity should be evaluated through cash on hand, revolving capacity, operating cash generation, maturity management, covenant compliance, access to debt markets, and access to equity capital.

Oracle’s current profile is not a near term solvency case. The company has substantial operating cash flow and demonstrated access to capital. The issue for common equity is the price of that access if external financing remains necessary for longer than expected.

Refinancing can extend maturities and protect liquidity, but it does not by itself improve the economics of an infrastructure investment. Durable improvement requires the assets financed with that capital to produce cash returns that exceed interest, lease expense, depreciation, maintenance investment, and the cost of dilution.

Customer Concentration and Counterparty Risk

Oracle’s traditional software franchise serves a broad customer base, but incremental AI infrastructure growth is increasingly influenced by a smaller number of very large counterparties.

Public disclosure does not support assigning precise concentration percentages or unsupported credit conclusions to individual customers. What can be underwritten is the sensitivity created by large contracts, including customer funding, deployment schedules, renegotiation risk, and changes in infrastructure requirements.

Concentration matters most when Oracle commits capital before the related revenue is recognized. Contractual protection and customer funding can reduce that exposure. Capital committed at Oracle’s risk increases it.

Technology, Utilization, Power, and Execution Risk

Technology Obsolescence

AI accelerators, servers, networking equipment, and related infrastructure can lose economic relevance faster than traditional long lived infrastructure. Useful life assumptions and refresh requirements therefore matter to cash returns.

Utilization

Capacity creates value only when it is deployed at sufficient utilization and pricing. Underutilized infrastructure can carry depreciation, power, lease, and financing costs without producing the expected revenue.

Power Availability

Large AI campuses require substantial and reliable electricity. Transmission, substations, generation availability, utility coordination, and long duration power arrangements can influence both deployment timing and project economics.

Construction Execution

Labor, materials, permitting, site development, cooling, networking, and third party provider execution can affect the timing and cost of capacity.

Vendor Concentration

Dependence on a limited number of advanced accelerator, networking, and infrastructure suppliers can affect equipment availability, pricing, and deployment schedules.

Return on Invested Capital

The ultimate test is whether the incremental cash generated by new capacity exceeds the full economic cost of construction, equipment, financing, leases, power, maintenance, and technological refresh.

Downside Cases

Base Case

OCI growth remains strong, RPO converts broadly within contractual expectations, customer prepayments and customer supplied equipment continue to reduce portions of Oracle’s funding requirement, deployment remains broadly on schedule, utilization rises as capacity opens, and capital markets remain available on investment grade terms. Under this case, negative free cash flow represents a temporary investment phase and the infrastructure build ultimately produces attractive incremental cash returns.

Moderate Downside Case

Some data center openings move later, revenue recognition is pushed outward, utilization ramps more slowly, capital expenditures remain elevated, financing costs remain higher, and additional equity issuance is required. Oracle remains financially functional, but common shareholders experience greater dilution and a longer period before the infrastructure program produces meaningful residual cash.

Severe Downside Case

Material deployment delays, lower utilization, contract renegotiation or deferral, higher construction and power costs, faster technology turnover, and weaker operating cash conversion occur while long duration commitments remain in place. Additional debt or equity is required and capital return flexibility declines. The principal risk is not necessarily enterprise failure, but compression of residual common equity as senior and competing claims consume a larger portion of the economics.

Core Credit Oriented Underwriting Principle

Contract Visibility, Infrastructure Economics, and Residual Cash Returns

RPO provides visibility into future business, but it does not fund the infrastructure required to serve it. Capacity has to be built, financed, powered, deployed, and utilized before the backlog becomes durable cash. The contract should be followed through the capital structure before value is assigned to common equity.

Capital Structure Assessment

Oracle’s infrastructure expansion is supported by a strong incumbent business, substantial operating cash flow, investment grade market access, and unusually large contracted demand. Those characteristics distinguish the company from a speculative infrastructure build without established customers or internal cash generation.

Execution now has to show up in cash. Capacity being financed today must produce recurring returns after interest, depreciation, leases, power, equipment refresh, taxes, preferred distributions, and other required uses.

RPO growth supports visibility. Revenue growth supports scale. Neither settles the capital question. Refinancing can extend the runway without improving project economics, while equity issuance can protect leverage by diluting the residual claim.

The clearest evidence of successful execution would be sustained growth in operating cash flow and free cash flow as deployed capacity matures, alongside improving utilization and less dependence on external financing.

Residual Common Equity Analysis

Credit oriented underwriting starts with the enterprise, recognizes the claims against it, and reaches common equity last.

For Oracle, the residual claim should be evaluated after recognizing funded debt, preferred capital, lease liabilities, material noncommenced infrastructure commitments, purchase and power obligations, other contractual claims, and the dilution associated with equity financing.

The company’s large RPO balance may support substantial future enterprise value, but that value belongs to common shareholders only after Oracle has funded and performed the obligations required to earn the associated revenue.

Oracle can grow rapidly and still produce a disappointing common equity outcome if the capital required to support that growth absorbs too much of the economics. Residual value depends on the cash return after the full cost of the buildout is recognized.

Investment Committee Monitoring Framework

Framework Application

The framework moves from the operating business toward common equity. Applied to Oracle, that sequence keeps the size of the AI backlog and the pace of OCI growth from obscuring the financing, infrastructure, and cash conversion requirements behind them.

Investment Committee Conclusion

Oracle is a useful test of credit oriented public equity underwriting because the growth story and the financing story are now inseparable. Cloud revenue and AI demand matter, but the common equity outcome depends on whether contracted demand produces enough cash to cover the infrastructure and financing claims required to deliver it.

Oracle’s installed franchise, capital markets access, and contracted demand provide substantial support for the investment program. The scale of capital expenditures, debt issuance, equity financing, lease commitments, power requirements, and execution risk also means that the common shares cannot be valued apart from the capital structure.

The investment committee should follow contracted demand through deployment, revenue recognition, operating cash flow, infrastructure spending, financing cost, and dilution. The backlog establishes an opportunity. The residual claim depends on what Oracle earns after paying to fulfill it.

Primary Reference Sources for Final Verification

• Oracle Corporation Annual Report and Form 10-K for fiscal 2026
• Oracle Corporation Quarterly Reports on Form 10-Q
• Oracle fiscal 2026 earnings releases and investor materials
• Oracle official debt and equity financing announcements
• Oracle debt and mandatory convertible preferred offering documents
• Oracle official data center, power, and infrastructure announcements
• SEC EDGAR filings
• Credible third party reporting used only where necessary to discuss reported project timing or financing developments, clearly distinguished from company reported facts

Case Study Disclosure

This case study is based solely on publicly available information and is provided to demonstrate the analytical process used within the Zepeda Capital Holdings Credit Oriented Public Markets Framework. It is intended for educational and informational purposes only. Nothing contained herein constitutes investment advice, an offer or solicitation to purchase or sell securities, or a recommendation regarding any security. The analysis reflects information available as of the periods identified and may change as additional information becomes available. Readers should conduct their own independent due diligence before making investment decisions.

Related Applied Underwriting Case Studies

Additional applications of the Zepeda Capital Credit Oriented Public Markets Framework across distinct industries, capital structures, and operating environments.