Independent financial research   /   Evidence before inferenceAbout Jeong-Mo Goo

Business field notes

Property sectors

Data-center REITs: power, capacity and capital intensity

Understand data-center leasing, power constraints, development spending and the difference between demand growth and shareholder returns.

Real estate with technical requirements

Data-center REITs provide facilities that support computing and connectivity infrastructure. Power delivery, cooling, reliability, security and network access matter alongside the building. Business models differ: large dedicated deployments and smaller colocation arrangements can have different customers, contract structures and service requirements. Square footage alone is often an incomplete capacity measure. Read how the issuer describes installed power, available capacity and utilization, and distinguish operating facilities from land or power rights intended for future development.

Translate demand into funded capacity

Demand for computing does not immediately produce rent. A project may require permits, grid connections, equipment and substantial spending before a customer begins paying. Contracted backlog can improve visibility but is not current revenue; commencement dates, customer conditions and development requirements matter. Power availability can be a competitive advantage and also a bottleneck. Examine who pays electricity costs, how costs pass through and whether contractual arrangements leave exposure to price changes, availability constraints or service-level penalties.

Competing views on growth

The favorable view links growing digital workloads to demand for reliable, connected capacity. The opposing view highlights expensive construction, customer concentration, technology changes and the risk of committing capital before demand becomes durable cash flow. Strong revenue growth can coexist with weak free cash flow while facilities are built. A project can be attractive at one cost of capital and less attractive after financing changes. Evaluate expected returns on completed capacity and per-share economics, not just the size of announced investment.

Issuer disclosure checks

Review development budgets, preleasing, projected delivery, power commitments, debt maturities and customer concentration. Ask whether booking figures describe annualized revenue, total contract value or another measure. Compare renewal spreads and churn only when definitions match. Separate maintenance from expansion spending, recognizing that reliable infrastructure still requires replacement. AFFO is nonstandard; inspect treatment of recurring infrastructure capital, stock compensation and other adjustments. Joint ventures and customer-funded projects can reduce funding needs while also changing how much economic ownership the REIT retains.

Work through the numbers

Hypothetical worked example

A hypothetical project costs $200 million and is expected to generate $16 million of stabilized annual NOI. The simple yield on cost is 8%. If final cost rises to $230 million with the same NOI, yield falls to about 6.96%. A one-year delay also postpones cash receipts and may add carrying costs. Neither yield is an equity return: the calculation excludes corporate overhead, financing, tax, future replacements and the cash-flow timing needed for a full valuation.

A common mistake

Do not equate a large computing-demand forecast or booking announcement with cash available for dividends. Check the capacity, timing and capital required to deliver it.

What to check in the disclosures

  • Define capacity and booking metrics.
  • Review power availability and obligations.
  • Compare development cost with stabilized income.
  • Read AFFO and recurring infrastructure spending.

Sources & scope

This guide focuses on US REITs. Examples are hypothetical unless explicitly attributed. Definitions and issuer disclosures can change; use the current source and the issuer's own reconciliation.

Educational material, not a recommendation or personalized investment advice. How these guides are prepared · Report a correction

Continue learning

Connect the next piece.

All guides →