Who Foots the Bill for Infrastructure Upgrades?

When a data center developer comes to town promising jobs, tax revenue, and economic momentum, local officials tend to roll out the welcome mat. What often gets buried in the excitement — until it's too late — is a deceptively simple question: who actually pays to make the grid, roads, and water systems capable of handling what's coming?

The answer shapes everything. It determines whether a project is a net win for a community or a slow-moving subsidy extracted from ratepayers and taxpayers who never voted for any of it.

The Infrastructure Tab Is Bigger Than Most People Realize

Data centers don't slot quietly into existing infrastructure. A hyperscale facility can draw 100–500 MW of power — enough to serve tens of thousands of homes — and it needs that power reliably, redundantly, and at scale. That means new substations, transmission line upgrades, expanded water capacity for cooling systems, and, in many cases, road improvements to handle construction traffic.

The infrastructure bill for a single large data center campus can run into the hundreds of millions of dollars before a single server rack is installed.

The question of who pays for those upgrades isn't just an accounting exercise; it's a political and ethical one. Ratepayers across a utility's service territory can end up subsidizing infrastructure built specifically to serve a private commercial tenant — often without knowing it. Grid upgrades that get "socialized" across the customer base mean your electricity bill edges up to support a facility owned by one of the most profitable companies on earth.

This is the context that makes the cost-responsibility question so charged. And it's why the model a developer agrees to — or refuses to agree to — at the outset of a project matters enormously.

Developer Pays vs. Community Pays: The Fork in the Road

There are essentially two models in play across the industry, with a spectrum of hybrid arrangements in between.

In the developer-pays model, the data center operator agrees to cover all infrastructure upgrade costs directly tied to their interconnection and operational needs. This includes utility-side improvements, substation construction, and any grid hardening required to deliver reliable power at the scale they need. Some developers also pick up road and utility extension costs as part of negotiated development agreements with local governments.

The alternative — where infrastructure costs get spread across the community — happens in a few ways. Utilities may classify upgrades as "system improvements" rather than project-specific costs, which triggers cost socialization across ratepayers. Local governments may issue bonds or allocate capital funds for infrastructure that primarily benefits the incoming development. Tax incentives may offset costs on paper while shifting the burden forward in time.

Neither model is inherently villainous. Infrastructure that a data center pays to upgrade often benefits other users too — a new substation serves the surrounding area, and a road improvement helps local traffic patterns. The issue is proportionality and transparency. When a developer captures the economic benefit but externalizes the infrastructure cost, the math stops working for everyone else.

Festus, Missouri: What Community Opposition Actually Looks Like

The situation unfolding in Festus is a useful case study because it's not unique — it's a preview of what's happening in dozens of mid-size communities across the country as data center developers move beyond saturated coastal markets into secondary locations with cheaper land and available power.

Residents pushed back hard against a proposed large-scale data center development in their community. The opposition wasn't irrational NIMBYism; it reflected a legitimate calculation: the visible disruption — construction traffic, noise, and industrial character imposed on a residential area — arrives immediately, while promised benefits like tax revenue and jobs materialize slowly and often fall short of projections.

What makes the Festus situation instructive is the infrastructure dimension. When developers absorb infrastructure upgrade costs, it changes the negotiating dynamic. Communities have more leverage when they're not being asked to put skin in the game. Conversely, when a project requires public infrastructure investment to proceed, local officials face pressure to approve it just to justify the money already spent.

The developer-pays-all model, when it's real and not buried in accounting sleight-of-hand, is actually the cleaner deal for communities — but it needs to be enforceable, not aspirational.

Development agreements need teeth: clawback provisions if promised jobs don't materialize, bonds or letters of credit guaranteeing infrastructure commitments, and independent verification of cost allocations rather than developer self-reporting. Without these mechanisms, "the developer pays" can mean very little in practice.

The Festus opposition signals something broader: communities are getting more sophisticated about what they're being asked to accept, and they're scrutinizing the fine print in ways they didn't a decade ago. Developers who treat community engagement as a checkbox exercise rather than a genuine negotiation are learning this the hard way.

The Grid Is the Chokepoint — And Investors Should Pay Attention

From a pure infrastructure-investment perspective, the funding question has long-term implications that don't get enough attention in underwriting models.

Data center demand is real and growing. AI workloads, cloud migration, and the general digitization of everything are driving power demand in ways that most utility forecasts from five years ago wildly underestimated. PJM, the grid operator covering 13 states and DC, has a queue of generation interconnection requests that has ballooned to over 250 GW — much of it attributable to data center demand clusters in markets like Northern Virginia.

This creates a fundamental tension. The grid needs significant capital investment to accommodate this demand. That investment has to come from somewhere. If developers fully internalize infrastructure costs, it raises their project economics — which affects the returns being underwritten by private equity and infrastructure funds.

Some developers are working around this by pursuing behind-the-meter generation — on-site power from solar, batteries, or even small modular reactors — specifically to avoid grid upgrade costs and interconnection queue delays. This isn't altruism; it's economics. A 200 MW data center that can interconnect in 18 months with behind-the-meter generation is worth more than one stuck in a 4-year queue waiting for a utility substation upgrade.

The emerging model that makes the most sense for long-term infrastructure investors is one where developers treat power infrastructure as a capital asset rather than a utility service — owning or co-owning the generation and transmission assets that feed their facilities. This aligns incentives, accelerates development timelines, and removes communities from the position of involuntary infrastructure co-investors.

What Responsible Development Actually Requires

For developers, the calculus is changing. Markets like Ashburn and Phoenix that once absorbed enormous data center growth are running into genuine constraints — power capacity, water availability, and community tolerance. The next wave of development is moving into markets that are less experienced with these projects and, consequently, more anxious about them.

Transparency about infrastructure cost allocation isn't just good citizenship — it's risk management. Projects that get stopped by community opposition or regulatory challenges cost more than projects that were designed with community buy-in from the start. The math is straightforward.

For investors evaluating data center development opportunities, infrastructure cost treatment deserves the same scrutiny as offtake agreements and construction timelines. A project that looks financially attractive because infrastructure costs are being deferred, externalized, or buried in utility rate base adjustments carries political and regulatory risk that won't show up in a pro forma.

For communities, the lesson from Festus and dozens of places like it is to engage early and specifically. Not "we oppose this project" as a first move, but "here are the specific infrastructure commitments we require, here's how they'll be verified, and here's what happens if they're not met." That's a position with leverage. Blanket opposition without specific demands is easier for developers and officials to route around.

The infrastructure upgrade question was always at the center of data center development economics. It just took communities getting burned a few times — and developers getting projects killed by organized opposition — for everyone to start taking it seriously.

Explore more about infrastructure opportunities in the InfraSale Marketplace.

INTERNAL LINK SUGGESTIONS:

• [INTERNAL LINK: data center economics]
• [INTERNAL LINK: community engagement strategies]
• [INTERNAL LINK: infrastructure investment trends]