The land sold in July for $263.7 million, and the deed did not carry the name of the company that intends to use it. In September, local officials in Washington state disclosed that the buyer was a developer. On Nov. 2, Amazon Web Services confirmed the purpose: a data center campus of up to 21 buildings on nearly 1,000 acres outside West Richland.
The property is the Lewis and Clark Ranch. The buyer identified in the September disclosure was Trammell Crow, a Dallas-based developer of industrial and data-center projects. Amazon is the end user, which means the buildings will be leased rather than owned, at least at the start.
None of that sequence is unusual. A developer buys land, secures entitlements and a power allocation, builds the shells, and leases them to a hyperscaler that would rather not appear in a county deed record a year before its corporate announcement is ready. The order of events here, sale then disclosure then confirmation, is how these projects normally arrive in a rural county.
What the confirmation establishes is scale. Twenty-one buildings on 1,000 acres is not a warehouse with servers in it. It is a campus the size of a small industrial park, with substations, water lines, backup generators, and a construction schedule measured in years rather than quarters. For Benton County, it is a property-tax base and a permitting file. For the grid, it is a customer that will eventually ask for hundreds of megawatts.
That last number is the one that decides whether the project is welcome. The Pacific Northwest has some of the cheapest and cleanest electricity in the country, most of it hydroelectric, and that is exactly why data-center developers have been circling it. The same supply is already committed to homes, farms, aluminum smelters and the region’s own technology employers, and utilities across the West have been revising load forecasts upward as AI demand arrives.
Counties elsewhere have responded by pausing or rejecting data center applications over power and water. The tension is not usually about the buildings. It is about who pays for the substation, how much of the utility’s new capacity is reserved for one customer, and whether residential rates rise to support it.
Water is the second front. Some designs evaporate water for cooling, and a campus of this size can consume millions of gallons a day in summer. Others use closed-loop systems that trade higher electricity use for lower water draw. Which design AWS picks at West Richland has not been disclosed, and it will determine much of the local argument.
Washington has also been reconsidering how it taxes the industry. The state has offered sales-tax relief to qualifying data centers, a policy that lawmakers have revisited as the sector’s power demand has grown. A project of this size gives both sides of that debate a concrete case.
The economics of the county are more favorable than the politics. Data centers generate property tax and construction work without asking for much in services. They do not send children to school or call the fire department often. But the permanent jobs are few relative to the acreage: a campus of 21 buildings might employ a few hundred people in operations, security and maintenance, against thousands of construction workers during the build.
For Amazon, the site is one more entry in a capital plan that has become the largest in corporate history. AWS has been buying land, signing power contracts and ordering equipment at a pace set by its customers’ appetite for AI compute, and it has been willing to pay ahead of demand to hold position. The $263.7 million land bill is small against the cost of the buildings and the servers that will go inside them.
For the neighbors, the timeline is the part that matters. Land purchases close quietly, utility agreements are negotiated under confidentiality, and the first visible sign of a project is often a fence. By the time a company confirms what it is building, the permits are largely in hand and the argument over siting has moved to the rate case.
Trammell Crow’s role is worth noting for what it says about how the industry now builds. Ten years ago a cloud company bought its own land and hired contractors. Today the largest buyers use developers to carry the entitlement risk, the construction schedule and the local relationships, then lease the finished shell. The developer’s name appears on the application; the tenant’s name appears later, once the outcome is secure.
That arrangement is efficient, and it makes local oversight harder. A county planning department reviews a warehouse project from a company it has not heard of, on land whose eventual occupant is a matter of speculation until the lease is signed. Residents who want to know what will be built next to them often learn it from a press release rather than a hearing.
Amazon’s confirmation answers the question of who, and leaves the questions of how much power, how much water, and how many years of construction. Those will be settled in filings that arrive one at a time. The ranch land that sold in July without a name attached is now, officially, the site of a 21-building campus, and the county’s next few years of utility planning will be written around it.
