The Bill AI Is Sending You

Let me tell you what actually happened in Indianapolis this week.

On July 15, the Indiana Utility Regulatory Commission stood up and said, in effect, we’re going to open the hood on how much profit your electric company is allowed to make, and we’re going to look hard at these financial mechanisms called trackers that let utilities collect money from you outside the normal rate case process.

Two new investigations. One on return on equity, the profit rate regulators guarantee investor-owned utilities on their capital spending. One on trackers, the surcharge lines on your bill that let a utility like NIPSCO or AES Indiana recover certain costs almost automatically, without going through the full public scrutiny of a rate case.

If you only read that as a consumer protection story, you’re missing the real one. This is a story about who gets to build the physical infrastructure that AI runs on, and at what price, and it’s happening in a state that just landed a 3.8 billion dollar SK Hynix memory fab that will be feeding chips straight into Nvidia’s supply chain. Indiana is not a bystander in the AI buildout. It’s one of the places where the buildout is actually happening. Which is exactly why the state is now the place where the fight over who pays for it is happening too.

Here’s the mechanism, explained the way I’d explain it to you over a beer.

A regulated utility doesn’t make money like a normal business. It doesn’t sell electricity for a markup and pocket the difference. Instead, regulators let it earn a guaranteed rate of return on whatever capital it spends building poles, wires, substations, and plants.

That guaranteed rate is the ROE. AEP’s Indiana Michigan Power was pulling a 12.6 percent return on equity over the twelve months ending in March, the highest of any AEP subsidiary anywhere. Think about that for a second. In a year when Hoosier households are furious about their bills, one utility subsidiary is running a return that would make a private equity partner jealous, and it’s fully sanctioned by the state.

That’s the balancing act at the center of this whole story. Every rate case is a negotiation between two things that are structurally in tension: the utility’s shareholders want the highest guaranteed return the commission will bear, because a higher ROE means every dollar of capital spending is more profitable, which means the utility wants to spend more capital, not less.

Meanwhile the ratepayer wants the lowest bill possible. Those interests do not converge on their own. They only converge if a regulator forces them to. So question one that everybody should be asking, the one IURC is now actually trying to answer, is what specific levers get pulled to make sure the commission is representing the family in Fort Wayne and not just rubber-stamping whatever the utility’s finance team modeled.

Earlier this year the commission already trimmed AES Indiana’s rate case down from what the utility asked for, approving 70 million against a larger request, and Commissioner Bob Deig dissented on the AES order because he didn’t think it went far enough. So this isn’t performative. There’s already a track record of the commission actually cutting utility asks.

Now here’s where it gets interesting for anyone thinking about AI infrastructure specifically, which is the whole reason this story is worth 2,500 words instead of a tweet.

Trackers exist because building for a predictable, slow-growing grid used to be a predictable, slow business. You’d forecast demand, file a rate case every few years, true things up. But data center load doesn’t move at the pace of a traditional rate case.

NIPSCO just signed a supply settlement with Amazon. AES Indiana’s resource plans are explicitly modeling accelerating large-load growth, and its own environmental critics have flagged that the utility’s updated capacity plans lean harder into natural gas specifically because data center demand keeps pushing the load forecast up.

Trackers are the tool utilities reach for when they need to recover costs faster than the traditional rate case cycle allows, and there’s no faster-moving cost driver on an Indiana utility’s balance sheet right now than the capital it’s spending to serve hyperscaler and chip-fab load. So when regulators say they’re investigating trackers, they’re not investigating some obscure accounting footnote. They’re investigating the exact financial plumbing that lets a utility pass the cost of building for AI onto the general ratepayer base faster than anyone can publicly object.

That’s the second core tension people miss: financial trackers exist to stabilize utility revenue against demand swings, but the swing driving Indiana’s grid right now isn’t residential demand fluctuating with the weather. It’s a small number of enormous, well-capitalized customers, chip fabs and data centers, whose load additions dwarf anything a normal household does. A tracker built to smooth out ordinary volatility becomes something very different when it’s actually smoothing out the cost of building gigawatts of new capacity for Amazon and Nvidia’s supply chain. The mechanism hasn’t changed. What it’s being used for has.

Which gets us to the part of this story that should actually keep you up at night if you’re a founder or an investor betting on U.S. compute buildout: the political tolerance for this arrangement is visibly running out.

Governor Mike Braun didn’t just appoint a new IURC chairman, Anthony Swinger. Braun publicly said Hoosiers can’t take it anymore and called for a rehearing of a prior AES rate hike approval. Swinger, who came out of the state’s ratepayer advocate office, is now the one running these investigations, and he’s already recused himself from twenty pending dockets because of his prior work fighting utilities on behalf of consumers.

This is a governor who ran on affordability installing a former ratepayer advocate to go after utility profits, in a state where NIPSCO’s residential bills jumped nearly 27 percent in a single year and CenterPoint’s jumped almost 25. Whether that’s good policy or regulatory overcorrection is a real debate, but don’t mistake it for background noise. It’s the leading edge of a fight that’s going to show up in every state with heavy data center load, because the affordability math and the AI buildout math are now the same math, and politicians have figured that out faster than most tech investors have.

So who actually wins and loses if this goes all the way through?

Utility shareholders lose in the direct sense, a lower authorized ROE mechanically compresses the return on every dollar of capital spent, and it reduces the sector’s attractiveness relative to other capital-intensive plays competing for the same investor dollars.

But here’s the twist that a lot of affordability advocates don’t want to say: a utility with a squeezed ROE and tighter tracker rules doesn’t necessarily build less.

It just gets pickier about what it builds and who it builds it for. The households and small businesses. Which is why Amazon signed a supply settlement with NIPSCO instead of just complaining about it. Which is why AES Indiana’s rate case increasingly gets negotiated with an eye toward large-load customers who can offer contractual certainty in exchange for capacity.

If general ratepayers are going to push back harder on absorbing the cost of the AI buildout, and Indiana regulators are now explicitly signaling they will, then the marginal dollar of new grid capacity increasingly gets financed by the hyperscaler and the fab directly, through negotiated large-load tariffs and dedicated service agreements, not socialized across the residential rate base through a tracker. That’s not a side effect of this story. That is the story, and it’s the same pattern I’ve written about with nuclear pipelines and co-location deals elsewhere: whoever can pay for their own dedicated power gets to build. Whoever can’t gets stuck in the queue behind a rate case.

That reshapes the competitive landscape among AI infrastructure players in a way that has nothing to do with model quality.

If you’re a hyperscaler or a chip company that can walk into a state utility commission with a balance sheet strong enough to sign a direct supply agreement, bypass the socialized cost fight entirely, and effectively buy your way to the front of the interconnection queue, you have a durable advantage over a smaller AI infrastructure player who’s stuck depending on the general grid and therefore stuck depending on the political mood of whichever state government is running the affordability fight that year.

This is the binding constraint again, the one I keep coming back to in this publication: it was never really about chip supply, and it’s increasingly not even just about megawatts. It’s about who can secure a bespoke financial relationship with a regulated utility that insulates them from the affordability politics everyone else has to navigate.

For the innovation question, whether tighter ROE rules choke off grid innovation, I’d push back on the framing most consumer advocates use and most utility lobbyists use in the opposite direction. A lower guaranteed return doesn’t stop a utility from investing in genuinely differentiated infrastructure, flexible interconnection tech, storage, faster permitting workflows.

What it stops is low-differentiation capital spending that only ever made sense because the guaranteed return made spending itself profitable regardless of whether the underlying asset was the smartest way to serve the load. If Indiana tightens ROE and tracker rules, you should expect utilities to get more selective and more creative about how they finance data center-driven buildout, not less active. The lazy capital gets squeezed out first.

And that’s ultimately the second-order price effect everyone should be watching. If regulators successfully compress ROEs and tighten tracker recovery, the headline story is lower bills for residential customers, and that’s probably true in the near term.

But the capital still has to get raised somewhere to build the gigawatts Indiana’s data center and chip-fab pipeline actually needs. If it can’t come from socialized rate base recovery anymore, it comes from direct large-load contracts, and those contracts get priced to reflect the exact risk and financing cost that used to be spread across everyone.

Consumer advocates should be careful what they wish for here. Squeezing the tracker doesn’t make the capital need disappear. It just changes who negotiates the price of that capital and who has the leverage to negotiate well. Right now, that’s Amazon and SK Hynix, not the median Hoosier household, and definitely not the smaller AI infrastructure players who don’t have a balance sheet big enough to cut their own deal.

If you’re building or investing in this space, here’s the takeaway that matters by audience.

If you’re a founder in AI infrastructure, this is your reminder that your unit economics increasingly depend on your ability to negotiate directly with a regulated utility rather than ride the general grid, and that capability is becoming a moat in its own right, separate from your model or your product.

If you’re an investor, watch state affordability politics the way you’d watch a supply chain risk, because a governor with an affordability mandate can move faster than a utility’s five-year capital plan, and that volatility now sits directly upstream of your portfolio’s compute costs.

If you’re an operator inside a utility or a hyperscaler’s infrastructure team, the lesson from Indiana is that the socialized-cost path is closing faster than most people in the industry expect, and the teams that lock in direct large-load agreements now are buying themselves years of certainty that everyone else will be fighting state legislatures for later.

If you’re in government, Indiana just handed you a playbook, not a warning. You can run an affordability investigation and still land the SK Hynix fab. The two aren’t in tension. What’s in tension is who bears the cost of the grid that fab and its neighbors need, and that’s a choice regulators are now making explicitly instead of letting it happen by default through a tracker line item nobody reads.