Power-first project structure can survive a named neocloud developer change
Cheyenne shows a power-first AI project can survive a neocloud developer change
Analysis by Frank Locascio and TheBRRR Research
What happened
Crusoe was no longer the developer for a proposed 1.8 GW Cheyenne project, but Black Hills said the project was not paused, remained targeted for early-2028 service and had received $201M of refundable customer contributions to reserve generation equipment.
Why it earned coverage
Contradictory headlines about a Crusoe pause were resolved by the utility's project-level receipt.
Investment transmission
Utility tariff, direct customer relationship and funded long-lead equipment can preserve project continuity even when an intermediary developer exits.
Affected exposures
Next observable receipt
Definitive large-power contracts, customer identification, regulator approvals, generation-equipment milestones and early-2028 service schedule.
What would invalidate it
Customer withdraws, refundable contributions are returned, definitive agreements fail or service date slips materially.