The short answer
A neocloud team should commit to a site only when the credible energization date lands inside the window of its GPU delivery schedule. If power arrives early, the team pays for an empty building. If power arrives late, the team holds purchased hardware that cannot earn. The work is to find the date that is actually credible, then line it up with delivery.
Three dates, defined
Energization date: when the utility delivers power to the site, usually first megawatts.
Ready-for-service date: when the building is commissioned and can run customer workloads. This comes after energization, because commissioning takes time.
GPU delivery date: when the hardware is scheduled to arrive and be installed.
The common mistake is comparing the GPU delivery date to the energization date. The right comparison is delivery against the ready-for-service date.
The mismatch cases
| Case | What happens | What to do |
|---|---|---|
| Power early, GPUs late | Rent and holding costs run on an empty hall | Negotiate a phased start or a rent step tied to delivery |
| Power late, GPUs on time | Hardware sits idle and revenue slips | Hold a fallback site, or negotiate delay remedies before signing |
| Phased power, GPUs in one batch | Only part of the order can be installed | Match the order batches to the megawatt ramp |
| Date quoted, no evidence | The date is a hope, not a plan | Do not commit until the date is backed by documents |
How to rate a date's credibility
A quoted date is only as good as what sits behind it. From weakest to strongest:
A verbal estimate from a seller or broker.
A utility letter that says capacity may be available.
A utility letter or agreement tied to this site and this load.
A completed utility study with a named substation and scope.
Long-lead equipment ordered, with delivery dates, plus a checked access route.
Also confirm that entitlements and the site's water and fiber items are not holding up the date.
Five decision rules
Use the credible date. Take the quoted date and move it by the evidence rating above.
Compare against ready-for-service, not energization. Add commissioning time.
Ask for phasing. If hardware arrives in batches, the power ramp should match.
Build the fallback before you need it. Keep a second validated site warm until the first date is backed by a study or an order.
Put delay remedies in writing. Terms for late delivery belong in the agreement before signing. Have counsel review them.
What the client gets
Build sources powered sites and validates each one, including the evidence behind its energization date. The neocloud team gets a shortlist ranked by credible date, not quoted date, and Build bundles the services that close the gaps, such as utility coordination, entitlement work, and engineering review, so the site is ready when the hardware arrives.