If your AI roadmap depends on capacity from a third-party data center developer, the delivery date in the contract is a risk to price in, not a promise. Crusoe, a Denver-based developer valued at $30.9 billion, has sold an unfinished Wyoming campus to Google, a company it had hoped to sign as the tenant. The episode is a useful stress test for anyone buying compute, leasing space or planning around someone else’s construction schedule.

What happened

According to TechCrunch, Crusoe confirmed on Friday that it sold an unfinished data center project in southeastern Wyoming to Google. Crusoe announced the project last year with Tallgrass, an infrastructure company backed by Blackstone, and planned to scale it eventually to 10 gigawatts of power capacity. Crusoe had tried to land Google as a customer for the site and failed.

TechCrunch reports that Google is taking over development after reportedly raising concerns about cost and construction timeline under Crusoe’s management. The price Google paid was not disclosed, but Google announced plans to invest $17 billion in the campus. DatacenterDynamics, covering the Cheyenne announcement, says the site is set to run on fuel cells and gas generation, coupled with carbon capture.

The relationship continues elsewhere, since Crusoe is developing another data center for Google near Amarillo, Texas. Bloomberg first reported the Wyoming sale in June, and Crusoe went on to raise a $3.9 billion round in September.

Why it matters

TechCrunch says the deal shows how hard it is for independent developers to deliver massive projects on time and within budget, given the challenges of securing equipment and power. Local opposition can add further friction. This one sale suggests, but does not prove, that a hyperscaler with doubts about a developer’s schedule may take the project over instead of waiting. If that happens more often, risk and control would shift toward the biggest buyers, who can fund a build themselves.

The setback did not stop Crusoe from raising money or serving large clients. Its customers, per TechCrunch, include Oracle and OpenAI at its Abilene campus, Microsoft at a neighbouring 900-megawatt site with a first building expected in mid-2027, and Meta. Bloomberg reported that Jane Street signed a $13 billion, five-year cloud deal with Crusoe. The sources do not say how investors or customers judge the Wyoming loss, so treat any read on their confidence as speculation.

The power plan is another signal. On-site gas generation and fuel cells suggest that grid access, not land or chips alone, shapes where and how fast capacity arrives.

What it means for you

If you lease capacity or sign multi-year cloud commitments with a developer, ask where power and equipment are secured today, not where they are planned. Request the construction milestones, and find out what happens to your contract if the site changes hands or the schedule slips. Clauses on assignment and delay remedies matter more when a project can be sold mid-build.

Budget for slippage. If a launch depends on new capacity arriving in a given quarter, keep a fallback with a hyperscaler or a second provider, and avoid committing all workloads to one unfinished campus. Crusoe makes money from leasing space for customers’ own GPUs, renting its own GPUs and selling inference capacity. Know which one you are buying, because exposure to construction delays differs for each.

Founders raising money for infrastructure plays should expect tougher questions on delivery. Teams comparing model and inference costs can track vendor pricing on AI Tool Radar, and funding in the sector is logged on Funding Pulse.

What to watch

  • Whether Crusoe’s Amarillo project for Google stays on schedule, as a test of the remaining relationship.
  • The first Microsoft building at Abilene, expected in mid-2027.
  • How Google delivers the Cheyenne campus, including its gas and fuel cell power plan and local reaction.
  • Whether other hyperscalers take over stalled developer projects, which would show whether this deal is a pattern or a one-off.

Sources