Tokenizing a Data Center Before It Generates Revenue

A data center under construction has no tenants paying rent, no metered IT load, and no operating history. It also holds some of the scarcest contracted positions in digital infrastructure. Interconnection queues nationally hold more than two terawatts of requested generation and storage capacity, and utilities are now processing large-load requests from data center developers on multi-year timelines. Vacancy in primary markets sits near record lows and most capacity under construction is spoken for before it is energized. So yes — a pre-revenue data center can be brought to digital capital markets. What decides it is what sits inside the entity.

Site control, interconnection, offtake — the three that matter

A pre-revenue asset is real enough to structure when a reviewer can trace its core claims to executed instruments held by the issuing entity. For a data center in construction, that means three things.

Site control. Recorded fee title or a long-term ground lease in the entity's name, with zoning and entitlements in place for the intended use and megawatt density. A purchase and sale agreement in due diligence is a position, not control.

Interconnection. This is the one that separates a project from a proposal. What exists in writing: a completed load study, an executed electric service agreement or large-load interconnection agreement with the utility, a defined substation scope, and a written allocation of who pays for network upgrades. A documented queue position with a study complete and an energization window is underwriteable. "We're in the queue" is not.

Offtake. Executed colocation agreements or a build-to-suit lease with committed critical IT load in megawatts, a stated term, escalators, and a ready-for-service date the tenant is contracting against. Committed capacity is what converts a construction site into a forward revenue position.

Behind those three sit the EPC contract — ideally on a GMP basis rather than cost-plus — and purchase orders for long-lead equipment: transformers, medium-voltage switchgear, generators, chillers. Which of these the entity holds, and which stay with the parent, is the whole question of what a token holder actually owns. The structural mechanics behind that boundary are covered there rather than repeated here.

The megawatts are the asset the competition cannot order

Sponsors consistently overweight the physical build and underweight the grid position. Racks, containment, chillers and gensets are procurable. Any funded developer can order the same equipment from the same vendors on roughly the same lead times, and long-lead items are financeable through ordinary equipment finance channels. The steel and the switchgear are not what make the project underwriteable.

The power is. An executed interconnection position in a constrained market — Northern Virginia, Central Ohio, Phoenix, Dallas — is not procurable on any timeline a competitor controls. It is the product of a queue entry made years earlier, a completed system impact study, and a utility commitment that new entrants cannot buy their way past. Transformer lead times have run multiple years in recent procurement cycles; substation energization dates, not construction schedules, set most ready-for-service dates in this asset class.

That has a direct structuring consequence. The interconnection agreement, the colocation contracts and the site control must be assigned to, or written in the name of, the entity being offered. A project entity that owns the shell while the parent retains the utility agreement and the tenant relationships has separated the underwriteable thing from the thing being offered. A careful reviewer catches that in an afternoon.

What does not qualify

A development plan is not an asset. Neither is a pitch deck, a land parcel under option, a site "identified" for 200 MW, or a memorandum of understanding with an unnamed hyperscaler. The most common near-miss is the letter of intent with nothing signed behind it — a term sheet for colocation capacity, non-binding, with no committed load and no ready-for-service date. It signals interest. It does not survive underwriting.

The test is mechanical: for every claim in the deck, is there an executed instrument, and is the entity being offered a party to it? Capacity described as "reserved," power described as "secured," and tenants described as "in advanced discussions" all fail that test in the same way. So does a signed agreement held by an affiliate that was never assigned.

None of this is a judgment about the project's merit. A well-sited development with a good sponsor and no executed interconnection agreement may be an excellent thing to build — it is simply not yet a thing to structure and offer. The honest sequencing answer is that documentation, not construction progress, is the gate. A powered shell three months from delivery with unassigned contracts is further from issuable than a graded pad with an executed service agreement and two signed colocation deals.

Construction-phase reporting: what a holder should see

Pre-revenue does not mean pre-reporting. It means reporting on progress rather than performance, and the standard should be higher during construction than after stabilization, because there is no operating data to fall back on.

What a holder should expect, monthly rather than annually: draw schedule against budget with contingency remaining and change orders itemized; an independent engineer's or owner's representative report; a lead-time register for long-lead equipment showing ordered, expedited and slipped items; and milestone status tied to externally verifiable events. In this asset class those events are specific — substation energization, powered shell delivery, commissioning progression from factory acceptance testing through integrated systems testing at design load, certificate of occupancy, tenant fit-out, and ready-for-service acceptance under the colocation agreement.

The discipline is that each is verifiable by someone other than the sponsor. A commissioning certificate and a utility energization notice are documents. A construction percentage is an assertion. Equally important is disclosure of what has not happened: a milestone that slipped, a study that came back with an upgrade cost, a tenant that has not yet accepted. The reporting surface a holder sees — dashboard, milestone history, document access — is described at how it works, and it is worth agreeing what will populate it before the structure is issued rather than after.

During construction, order of priority is stated as order, not amounts: construction lender, equipment finance, any mezzanine layer, then holders. Nothing distributes while the asset is being built, because there is nothing to distribute, and a build-stage structure implying otherwise has told holders something false before the first document is signed. A tokenized interest with a counsel-defined transfer path does not create a public market and should never be described as if it does — though it does move the position from permanently illiquid to potentially transferable.

What to bring to the first conversation

Short list: the recorded site control document. The interconnection file — application date, study status, executed agreement, upgrade cost allocation, energization window. Executed colocation or lease agreements with committed megawatts and ready-for-service dates, and a clear statement of which entity is the counterparty today. The EPC contract and the long-lead procurement register. The construction debt and equipment finance stack, because it defines the priority order everything else sits behind. Broader context on how this asset class is structured sits in tokenization for energy and digital infrastructure.

Timing is the one thing nobody should promise. Energization dates move on utility scheduling, transformer deliveries and permit conditions. We will not quote you a close date, and you should distrust anyone who does. Milestones exist precisely so the structure does not have to pretend to know the calendar. And the securities question sits where it always does: it is a security, offered under an exemption determined by counsel, through offering documents counsel prepares. Commertize neither selects the exemption nor drafts those documents.

The honest summary: a pre-revenue data center is not disqualified by the absence of revenue. It is disqualified by the absence of documented position. Put the site, the megawatts and the offtake inside the entity, report the build against milestones a third party can verify, and the pre-revenue phase becomes a structuring problem rather than a disqualifier.

Have an asset you're thinking about? Register at commertize.com to see the platform — onboarding, KYC, holder dashboard and reporting. Or contact the team and tell us what the asset is; if it isn't a fit, that is a useful answer to get in one conversation rather than three.

Educational only — not legal, tax or investment advice, and not an offer of any security. Any securities offering is made by a sponsor, through documents prepared by the sponsor's counsel, under an exemption that counsel determines.

Have an asset you're evaluating for tokenization? Send the offering memo to deals@commertize.com or start at commertize.com/tokenize, and we will return a written tokenizability and capital-structure memo within 48 hours — free, no obligation.

Confidential review. No cost, no commitment, no calls unless it is a fit.