Everybody Wants AI, Nobody Wants the Data Center

Everyone loves the magic of AI until the machinery behind it wants 200 acres, a new substation, and a steady stream of power and water. We’re digging into the thing we all rely on but rarely understand: the modern data center, the hidden backbone of cloud computing, streaming, medical records, and the AI tools showing up in every workplace.

We start with the upside, because it’s real. Data center development can bring construction jobs, tax revenue, infrastructure investment, and a surge of work for electricians, engineers, HVAC teams, security providers, and local businesses. Then we flip the perspective to the people living nearby and the questions that instantly change the mood: Will my utility bill rise? Will it hum all night? Can the roads handle the traffic? How many permanent jobs are there, really? And why does it feel like the public heard about it after someone called it a done deal?

From there, we build a claim scenario that turns abstract risk into a real-world mess: an electrical failure during final testing, a fire, damaged specialized equipment, long replacement lead times, contract finger-pointing, angry customers, and a viral narrative that travels faster than facts. We walk through the insurance and risk management pieces that decide what happens next builder’s risk, delay in completion, professional liability, business interruption, cyber insurance coordination, pollution liability, and crisis response. The big takeaway: insurance can fund parts of the recovery, but it can’t purchase trust retroactively. If you care about responsible AI infrastructure, share this, subscribe, and leave a review with the toughest question you think every data center project should answer.

Transcript

Why Data Centers Spark Debate

SPEAKER_00 0:26

Let me start with a confession. I love technology. I love innovation. I love watching a city land a major project and suddenly everybody's talking about jobs, investment, and what comes next. I also love a healthy amount of skepticism. Because somewhere between that glossy announcement and that giant ceremonial check, somebody should probably ask, where's this power coming from? How much water does this thing use? Who's paying for the infrastructure? What happens if the neighbors hate it? And naturally, what insurance policy is supposed to clean up the mess if any of that goes wrong? Welcome back to Risky Business. I'm Jessica Villarreal, and today we're talking about data centers, or as I like to call them, the building everybody needs, nobody fully understands, and absolutely everybody has an opinion about. The title of today's episode is Everybody Wants AI, nobody wants the data center. Now, before anybody starts sending me angry email, relax. I'm not saying nobody wants them. Plenty of communities do. Data centers can mean construction, tax revenue, infrastructure investment, and very serious economic opportunity. But the second one is proposed near somebody's house, ranch, school, or water supply, the conversation changes quickly. People love AI when it's making a vacation itinerary. They feel a little differently when the infrastructure behind it wants 200 acres and a new substation. And honestly, both reactions make sense. The part that everybody likes? Well, let's begin with the

The Real Economic Upside

SPEAKER_00 1:59

fun part, right? Data centers are a huge part of the AI economy. Every time we ask a computer to write an email, generate an image, run a business system, store medical records, or stream another season of a show we should have stopped watching three episodes ago, that data has to go somewhere. The cloud is not actually a cloud. It's a building, a very expensive building, filled with servers, cooling systems, backup generators, electrical equipment, and enough technology to make me stand at a safe distance and nod like I understand all of it. These projects can create major opportunities for contractors, engineers, electricians, HVAC firms, security providers, technology vendors, and local businesses. Hotels fill up, restaurants get busier, construction crews arrive, professional service firms get involved, cities gain attention, developers gain momentum, and insurance people start opening spreadsheets because nothing says opportunity like a multi-billion dollar project with several hundred ways to go sideways. That is not negativity. That is what I call job security. The part people don't like? Let's talk about that. Let's put ourselves in the shoes of somebody who lives nearby. You bought land because you wanted quiet. Maybe open space, maybe dark skies, maybe cows who mind their own business. Then one day you hear a data center maybe coming. Suddenly you're reading about power demand, water usage, transmission lines, backup generators,

Neighbors Ask The Hard Questions

SPEAKER_00 3:29

and tax incentives. You're wondering whether your utility bill is going to go up, you're wondering whether the facility will hum all night, and you're wondering whether the roads can handle construction traffic. You're wondering how many permanent jobs will actually exist after the project is complete. And you're wondering why the first time you heard about any of this was after somebody had already used the phrase, done deal. This is where business leaders can get themselves into trouble because concerned residents are not automatically anti-business. They may simply be asking questions nobody bothered to answer. And there is a difference between resistance and distrust. Resistance says, I don't want this. Distrust says, I do not believe you've told me the whole story. One is a development issue, and the other is a reputation issue. And reputation can quickly become very expensive. There's mistakes that even smart people can make. And that's a fascinating part. The people developing the project may genuinely believe they're bringing something valuable to the community. The people opposing it may genuinely believe that they are protecting the community. Both groups can be sincere. Both groups can also communicate terribly. The developers start speaking in tax-based projections and megawatts. The residents start speaking in fear, frustration, and Facebook comments. And now everybody's using the same words, but have completely different conversations. One side says, this is progress. The other says, this is our home. This is not an insurance problem yet, but give it time. Because poor communication

When Mistrust Turns Into Claims

SPEAKER_00 5:03

has a remarkable ability to become a lawsuit. We're creating a monster. Now, this is my favorite part. Let's build the claim. Imagine a massive data center is almost ready to open. The investment is enormous. The opening date has been announced. The executives are booked. The press release is drafted. Somebody's ordered one of those giant pairs of ceremonial scissors. During final testing, a critical piece of electrical equipment fails. There is a fire. The suppression system activates. Nobody is seriously injured, thank goodness. But several pieces of specialized equipment are damaged. The opening is delayed, and the replacement equipment has a lead time so long that people begin speaking about it in fiscal quarters. The contractor blames the subcontractor. The subcontractor blames the manufacturer. The manufacturer blames the installation. The owner blames everyone. The customers waiting to move into the facility start sending notices. Somebody nearby posts a shaky video online with a caption AI facility explodes near neighborhood. It was not an explosion, it was an electrical event. But electrical event does not get shared 400,000 times during lunch. Now the CEO has physical damage, delayed revenue, contract disputes, angry customers, and a reputation problem. That is not a claim. That's a group project. What pays? Well,

Insurance Coverage That Actually Matters

SPEAKER_00 6:29

let's walk through it. And I promise not to make this feel like a continuing education class, but there is builder's risk because the project is still under construction. Builder's risk is probably the first policy everyone reaches for. It may cover certain physical damage to the building, materials, and equipment. But the real question is not whether they have builder's risk. The real question is whether they have the right builder's risk. Was testing included? Was the equipment covered? Had any part of the project already been accepted? Was the failure caused by defective work? Was the bad component excluded while the damage it caused remained covered? Insurance loves a nuance. It's one of our most charming qualities. A policy may say, we're not paying to replace that faulty part, but it may cover the fire damage caused by the faulty part. Or it may not. This is why reading the policy after the smoke clears is not considered a best practice. Now there's a delay in completion. We have lost revenue. The facility was supposed to open. Customers were supposed to move in. The project was supposed to begin generating income. Delaying completion coverage may help when a covered physical loss delays the project. The important phrase here is covered physical loss. If the project is delayed because of a fire, maybe. If the project is delayed because somebody forgot a permit, probably not. Insurance does not cover every bad decision. If it did, there would be no underwriting department left. Professional liability. Now we ask why the equipment failed. Was it designed incorrectly? Was the wrong equipment specified? Did an engineer miscalculate the load? Did somebody sign off on something they should not have approved? That may bring professional liability into the conversation. And this is where contracts become very important because companies love signing agreements that say, we accept responsibility for everything that's ever happened and everything that may happen in the future. Then they call their insurance advisor and ask whether the policies match. Sometimes it does. Sometimes the carrier reads the contract and says, This is an impressive amount of confidence. Then there's business interruption. The physical damage may be expensive. The downtime may be worse. What happens when the facility cannot operate? What happens when customers lose access to systems? What happens when contracts require service credits or penalties? Business interruption coverage may help, but only if the loss fits the policy. Was there physical damage? Where did it occur? How long was the waiting period? Was the outage caused by the facility, the utility, or something off-site? Whose income was actually lost? The owner? The operator? The customer? This is where everybody quietly moves their chair back and says, I thought someone else was covering that. That sentence has launched many claims meetings. Then there's cyber. Now let's make it even more interesting. Even if the electrical failure was not accidental, what if someone compromised the control system? Now we may have cyber, property, and business interruption issues colliding all at the same time. Cyber coverage may help with forensic investigation, business interruption, data restoration, ransomware response, privacy claims, and customer lawsuits. But policies do not always coordinate gracefully. The cyber policy may point towards the property policy. The property policy may contain a cyber exclusion. And the insured is standing in the middle like a child whose parents both said, go ask the other one. This is why coverage coordination matters. The policies should definitely meet each other before the claim, preferably over coffee. Then there's pollution. Now imagine that the incident damages a fuel system connected to the backup generators. Diesel reaches the soil, possibly underground. Now we have cleanup cost, environmental testing, potential regulatory action, and very unhappy. We'll definitely say, but we have general liability. And everyone in insurance will take one deep breath together. General liability policies often contain pollution exclusions. Pollution coverage may need to be purchased separately. Never assume the word liability means every type of liability. Insurance would be far too easy if that were the case. There's a reputation and crisis response that needs to happen. Now we have the public conversation. People online are sharing bad information. Residents are angry. The media is calling. Certain policies may help with crisis management or public relations expenses after a covered event. That can be useful. But let me be clear. Insurance can pay for communication support. It cannot make people trust you. Trust is not a policy limit. And it cannot be purchased retroactively. That part has to be built before you have the crisis. What should a smart CEO hear in all of this? Not that data centers are bad, not that the communities are difficult, not that innovation is too

Trust Planning And The Responsible Path

SPEAKER_00 11:44

risky. The lesson is that growth gets complicated. The second it touches real people, real infrastructure, and real contracts, a smart CEO should be asking, what could delay this project? What equipment cannot be quickly replaced? Who's responsible if the design fails? What happens if the grid is strained? What happens if neighbors complain about noise? What happens if the project uses more water than expected? What happens if a cyber event interrupts operations? What happens if the story online is worse than the actual incident? And are we communicating early enough that the community hears from us before it hears from somebody with a ring light and a conspiracy theory? That last one is free consulting. You're welcome. So what would I want in my community? I would want information. I'd want transparency. I'd want to understand the impact, the benefit, and the plan. I would want the developer to answer hard questions without acting offended that anybody even asked. I would also want residents to recognize that the technology we all use requires physical infrastructure somewhere. We cannot demand faster AI, more cloud storage, and constant digital access, then become morally opposed to the building that powers it. We can, however, demand that it be built responsibly. That's not anti-growth. That's adult supervision. Here's where I land. Data centers are not automatically heroes. They are not automatically villains. They're infrastructure. And infrastructure is only as smart as the planning behind it. The best projects will not be the ones with the loudest announcements. They'll be the ones that understood the contracts, the community, the utilities, the environmental impact, the operational exposures, and the insurance program before something went wrong. Because once that fire starts, the system goes down, or the internet decides what happened before the facts are available, everybody suddenly becomes very interested in risk management. I'm Jessica Villarreal, and this has been Risky Business, the podcast where I take the complicated, the controversial, and the expensive and explain it in a way that hopefully makes you laugh before you call your lawyer or your insurance advisor, preferably me. See you next time.