Growth Pays for Growth - Who carries the cost when the AI Data center growth plan changes

The next phase of AI infrastructure development is becoming a negotiation over who carries the costs of growth. The new load needs power. Existing customers need protection. Communities also need clarity about water use, cooling infrastructure and the consequences of a development plan changing.

States are making that responsibility more explicit. Ohio’s data-center tariff establishes minimum-demand obligations. Virginia’s approved large-load rate class begins in January 2027. Texas’s new interconnection standards took effect October 8, 2026. Pennsylvania’s GRID framework, implemented through executive action, calls for incremental power and project-related cost coverage. These measures differ in scope and legal form, but all sharpen the obligations around expansion. [5–8]

Selected hyperscaler agreements suggest a broader bargain is taking shape. Their value cannot be understood by adding announced megawatts. Five questions connect the energy deal to the system and communities supporting it.

Who pays for the power

Google’s February announcement for Pine Island, Minnesota links its planned data center to an Xcel Energy package of wind, solar and iron-air storage. Google says it will pay all costs associated with its electric service and contribute $50 million to Xcel’s distributed battery program. The mechanism combines service-cost responsibility with investment in supply and flexibility. [1]

Meta’s March agreement with Entergy Louisiana takes another route. Entergy says Meta pays its full cost of service for proposed generation, transmission and storage infrastructure. Seven planned combined-cycle gas plants total more than 5,200 MW. These commitments must still be assessed against infrastructure delivery and the customer’s demand ramp. [2]

Can existing customers save

Entergy projects approximately $2 billion in additional customer savings over 20 years from the Meta arrangement. Its explanation is that customer payments help offset fixed costs other customers would otherwise carry. That is an identified benefit mechanism, but savings remain a forecast. Delivery, demand and regulatory treatment determine the outcome. [2]

Must a new plant be built

Fortum’s September announcement describes a 22-year Google PPA supporting Loviisa’s life extension and an expected additional 10 MW uprate. The agreement reaches up to half the plant’s capacity during 2030–2049. Much of its contribution concerns continued operation of existing nuclear generation. Preserving supply is different from commissioning an equivalent amount of new generation. Exploration of further energy development should also be distinguished from committed projects. [3]

What do local communities receive

At Arkansas’s Steel River solar and storage development, Google committed $5 million to energy-affordability initiatives, including community solar subscriptions, weatherization and school-efficiency projects. That is a defined commitment, not evidence that all local concerns have been resolved. [4]

Customer-cost protection and community programs address different needs. An agreement can allocate electricity-service costs while leaving land use, water or noise unresolved. Each promise needs an accountable administrator, identifiable recipients, a delivery schedule and measures of results.

Who pays for cooling and whose water supports growth

Cooling makes that distinction concrete. Pine Island’s city disclosure describes a sealed chilled-water loop that transfers heat to ambient air, eliminating evaporative cooling and a continuous freshwater draw for cooling. Domestic water use remains. The relevant commitment is non-consumptive cooling, rather than an entirely water-free site. [9]

Meta specifies a closed-loop glycol system at Richland Parish, with dry cooling for most of the year. That wording does not establish year-round water-free operation. The disclosure reviewed does not identify the remaining seasonal cooling arrangement or confirm a reclaimed-water source. Those are unresolved diligence items. [10]

Google’s existing Hamina facility uses seawater-based cooling and supplies recovered heat to local homes and businesses. This is a documented freshwater alternative, but the Loviisa PPA is a power-supply arrangement, not a campus at the nuclear plant. Hamina’s design should not be assumed for every new Finnish facility. [11]

Executives need the contracted water source, annual and peak-day consumption, and the operating response to extreme heat. They also need to know who funds treatment, pipelines and utility upgrades. The supplying generation has its own footprint: Fortum identifies seawater cooling and thermal discharge at Loviisa. A campus’s cooling claim therefore does not establish the water impact of its entire electricity supply. [12]

Who pays if demand does not arrive

Infrastructure has long delivery schedules and substantial fixed costs. Delayed demand can leave assets idle; slower growth can leave capacity underused; an exit can leave unrecovered investment. Minimum-demand charges, financial security and termination obligations can keep specified responsibilities with the new customer.

Ohio provides a concrete example: its new letter of agreement requires reimbursement of 100% of buildout costs for cancellation or a delay exceeding 12 months before target energization. That protection should be evaluated within the governing arrangements, rather than assumed to cover every cost or apply to every featured deal. [5]

The KFAP signal

Our interpretation is that growth-related obligations are becoming a more explicit part of the large-load infrastructure proposition. The execution test spans electricity and water: who funds the system, who carries changes in demand, and how promised benefits reach recipients.

For KFAP, that means connecting the load ramp to energy and cooling delivery, assigning responsibility at the interfaces, and testing commitments against changes in timing or scale. Growth pays for growth only when those obligations can sustain the development plan after the announcement.

Primary sources

Company announcements, regulatory sources and project disclosures. Cooling and water disclosures reviewed 13 October 2026.

[1] Google and Xcel Energy — 24 February 2026

https://blog.google/innovation-and-ai/infrastructure-and-cloud/global-network/data-center-pine-island/

[2] Entergy Louisiana and Meta — 27 March 2026

https://www.entergy.com/news/entergy-louisiana-announces-a-new-agreement-with-meta-that-will-deliver-an-additional-2b-in-customer-savings

[3] Fortum and Google — 9 September 2026

https://www.fortum.com/media/2026/09/inside-information-fortum-and-google-partner-drive-sustainable-growth-finland-sign-nuclear-power-purchase-agreement

[4] Google and Steel River — 14 July 2026

https://blog.google/innovation-and-ai/infrastructure-and-cloud/global-network/steel-river-arkansas/

[5] AEP Ohio — current data-center tariff and agreements

https://www.aepohio.com/company/about/rates/data-center-tariff/