Asset Classes

Powered Shell Data Centers: What Developers Need to Know

This post explains what powered shell data centers are, why the model is gaining traction and what developers need to diligence before pursuing one. It covers the boundary between base building and tenant fit-out, power, cooling pathways, leasing structure, capital risk and AI-assisted delivery workflows.

by Build Team May 9, 2026 5 min read

Powered Shell Data Centers: What Developers Need to Know

A powered shell sits between raw land and turnkey data center capacity, which makes scope control the whole game.

A powered shell data center is a completed or near-completed building with secured power, base infrastructure and connectivity pathways, but without the full tenant-specific IT fit-out. The developer delivers the envelope and site infrastructure. The tenant, hyperscaler or operator finishes the interior.

The model matters because data center demand is moving faster than traditional delivery. JLL's 2026 Global Data Center Outlook projects 97 GW of new capacity between 2025 and 2030 and up to $3 trillion of infrastructure investment by 2030. Developers want that demand without taking every technical decision onto their own balance sheet.

Powered shell is the middle ground between dirt and commissioned capacity.

What is included in a powered shell?

The definition varies by deal, but a powered shell usually includes 5 components:

  1. The building envelope

  2. Secured utility capacity or a defined path to capacity

  3. Structural readiness for data center loads

  4. Space and pathways for mechanical and electrical systems

  5. Fiber access or clear connectivity routes

DatacenterHawk defines a powered shell as a secure facility with the physical structure, power to the site and connectivity options, while excluding major IT infrastructure such as UPS systems, generators and cooling systems. Miller Thomson's April 2026 analysis describes it as an envelope with critical base infrastructure, utility upgrades, cooling pathways and structural readiness for high-density IT loads.

The excluded scope is just as important. Server racks, cabling, security systems, GPUs, CPUs, tenant-specific power distribution and final cooling configuration often sit with the tenant or operator. If that boundary is vague, the project becomes a dispute.

Why is the model gaining traction?

Powered shell works because different parties want different forms of control.

Developers want to advance a site beyond raw land without funding a full turnkey facility before tenant requirements are certain. Tenants want speed, secured power and design control. Operators may lease the shell, complete the fit-out and sell downstream capacity.

Hyperscale tenants with strict technical standards

Large cloud and AI tenants often have their own standards for redundancy, cooling, security, equipment layout and operations. A fully built facility can force them to retrofit someone else's choices. A powered shell gives them control while shortening delivery.

Developers with strong land and power access

Some developers can assemble land, secure entitlements and advance utility work, but do not want to become full data center operators. Powered shell lets them monetize early-stage work without taking on the operating model.

Markets where power is the scarce asset

When grid connection waits exceed 4 years in primary markets, the value is not only the building. It is the secured power path. A powered shell with credible capacity and entitlement status can be more valuable than a more finished building with uncertain energization.

What developers need to diligence

A developer should define what is delivered at handoff, what remains with the tenant and what conditions trigger additional landlord obligations. The main diligence areas are:

  • Power. Capacity, delivery date, substation status, interconnection milestones, backup strategy and utility agreements.

  • Structure. Slab capacity, clear heights, loading, roof design, expansion zones and equipment yards.

  • Cooling pathways. Space for chillers, cooling towers, CRAH or CRAC systems, liquid-cooling readiness and water strategy.

  • Fiber. Carrier options, route diversity, rights of way and meet-me-room strategy.

  • Security. Perimeter, access control, blast or setback considerations and separation from adjacent uses.

  • Entitlements. Permitted use, generator approvals, air permits, noise limits, water discharge and local political risk.

  • Handoff terms. Commissioning responsibility, latent defects, warranties, insurance, acceptance testing and change control.

A normal commercial lease is not enough. Miller Thomson notes that powered shell projects are defined by the boundary between base building infrastructure and tenant fit-out, and that the boundary must be reflected clearly in project documentation.

Powered shell is not always lower risk

The model reduces some risks and introduces others.

It reduces tenant-spec risk because the tenant controls final interior choices. It can reduce capital exposure because the developer may stop before funding full IT-ready capacity. It can also widen the tenant universe if several operators can complete the fit-out.

But it increases interface risk. If the shell misses the tenant's cooling load, redundancy standard or equipment density, the tenant may face redesign work. If the power date slips, the shell is just an expensive building.

The core risk is pretending it is industrial shell delivery with bigger power.

Where AI helps in powered shell delivery

AI is useful because powered shell projects depend on coordination across land, power, legal, engineering, tenant requirements and financing.

A well-designed workflow can:

  1. Track utility milestones and compare them with lease obligations

  2. Extract scope boundaries from term sheets, leases and design documents

  3. Flag conflicts between tenant standards and base-building assumptions

  4. Maintain a responsibility matrix across landlord, tenant, operator, utility and contractors

  5. Build a live risk register for power, cooling, entitlement and handoff issues

  6. Generate diligence summaries for lenders or investment committees

AI should not decide the technical standard. It should make contradictions harder to miss.

The buyer question is where control should sit

A powered shell is a bet on control. The tenant gets control of fit-out. The developer gets control of land, power and base infrastructure. The operator, if involved, gets a faster route to capacity.

Before choosing the model, developers should ask 4 questions:

  • Is the power path credible enough to create value before full fit-out?

  • Is tenant demand specific enough to justify advancing the shell?

  • Is the scope boundary clear enough to finance and lease?

  • Does the team have the technical discipline to manage handoff risk?

If the answer is yes, powered shell can work for AI-era capacity. If the answer is no, it can become the most expensive halfway point in the data center stack.