Ask any utility leader what's keeping them up at night, and it's rarely something abstract like "technology" or "systems." More likely, it's something specific, like a crew schedule that falls apart the morning after a storm, or a compliance filing that takes three systems and a shared drive to assemble. It's something real and urgent.
And the list of those issues is long, whether it's regulatory compliance or an aging workforce, or how data centers are driving load growth that's rewriting long-term resourcing plans. At the same time, there's an expectation to consistently do more with less. So, when a utility goes looking for a new system to fix one of those challenges, the instinct might be to pick whatever clears the budget fastest.
That's an understandable reaction, but it usually overlooks the fact that so many systems that can solve today's problem aren't equipped to still be solving it in two years. So, the real question isn't what something costs, it's how well (and how quickly) it can close the gap between the problem you have today and the one you'll have next. It's about value, not cost.
Meeting you where you're going
The reality is that fitting a utility's real operations into something built for a generic customer isn't easy. A vendor can stand up software in a week, sure. But the harder question is about how well a system that's built somewhere else can flex to match your actual territory, your workforce, your compliance footprint — especially once all three keep shifting under you?
I'll tell you a pattern we see constantly. A large share of the utilities that come looking for something new have already been burned once. They configured a system, it fit for a year or two, and then it didn't. Now they're not just looking for a tool. They're looking for one that won't put them back in the same spot in 18 months.
That's the test that actually matters. Not "does it do what we need today?" But "will it still be doing that when today looks different?"
Speed and flexibility only go so far if a utility can't trust what sits underneath them. Grid systems live at the intersection of critical infrastructure and increasingly sophisticated threats, and OT-IT convergence has only raised the stakes. Layer AI into grid operations, and the questions get sharper. Who has access to this data? What is it being used to train?
You can't hand frontline teams more control over a system unless you trust the security holding that system together. A straight answer on data handling, backed by a real track record, isn't a differentiator anymore, it's the minimum requirement.
Consolidation doesn't equal rigidity
Every utility I talk to is looking at consolidation right now. They want fewer vendors and less sprawl. They want to run fewer systems and get them to do more. People assume that ceiling is about budget size, but it's not — it's about how flexible and extensible the system can be.
A utility with a flexible system can still adapt as conditions shift, because the constraint is capital, not the tool. A utility with a bigger budget and a rigid system hits the same wall anyway, because no amount of spending buys back the time lost reconfiguring something that was never built to bend.
Smaller munis and co-ops usually feel this first. They don't have the staff to build workarounds, so the system itself has to flex. Larger investor-owned utilities have more room to absorb the friction, but they pay for it in slower response, right when conditions are moving faster than a multi-year upgrade can keep up with.
I've seen this play out at a utility serving close to 1 million customers in the Pacific Northwest. Their vegetation management group was running crew operations on a system sized for 20 crews, but the business outgrew it. By the time they went looking for something better, they were coordinating hundreds of contractors through a tool that couldn't flex without a rebuild every time.