Selling to Utilities and Regulators: A PM's Stakeholder Survival Map

A utility sale rarely dies because the product fails technically — it dies because a PM tracked one buyer instead of a coalition. Procurement, operations, regulatory affairs, IT/OT security, and the state Public Utility Commission each score a pilot on different criteria, run on different clocks, and can each unilaterally kill a deal everyone else already approved.

Quick answer: Treat the utility as five to seven distinct stakeholders — procurement, operations, regulatory affairs, IT/OT security, finance, and the PUC — mapped by influence, alignment, and who bears the risk if the pilot fails. Track the alignment debt that accumulates between steering-committee meetings, or a technically-won pilot can die on a veto nobody saw coming.

This piece maps that coalition, gives you a repeatable framework for scoring each player, walks through the cautionary shape of a pilot that won on merit and lost on politics, and shows how to keep the map current between meetings instead of just at kickoff. For the wider landscape this fits into, our complete guide to energy and climate product management covers the adjacent terrain — grid economics, decarbonization pressure, and the buyer types that recur across the sector.

The Utility Is Not Your Buyer — It's a Coalition With Four Clocks

Selling into a utility means selling into at least four functions with incompatible timelines: procurement (compliance and cost), operations (reliability and safety), regulatory affairs (rate-case defensibility), and finance (capital budgeting cycles). Treating them as one "buyer" is the single most common reason a technically strong pilot stalls for a year with no clear next step.

Gartner's research on B2B buying groups puts the average number of stakeholders in a complex purchase at somewhere around six to ten people, across ordinary commercial deals. Utilities routinely exceed that, because a regulated entity carries an external stakeholder — the commission — that a normal enterprise buyer never has to satisfy. That extra layer is not a formality; it can override every internal "yes" you've collected.

Four functions worth naming explicitly, because each optimizes for something the others barely notice:

• Procurement wants a defensible, lowest-risk contract it can justify in an audit, not necessarily the best product.
• Operations wants zero surprises on a live grid — reliability and safety outrank almost every other consideration, including cost.
• Regulatory affairs wants a paper trail that survives a rate case, because every dollar spent may need to be justified to the commission later.
• Finance wants the spend to fit inside an annual capital plan that was locked months before your pilot existed.

The clock mismatch is the deeper issue. Operations thinks in outage windows and maintenance seasons; regulatory affairs thinks in multi-year rate-case cycles; your own roadmap thinks in sprints. This is the same structural tension covered in our piece on the hardware-software two-clock problem — except at a utility, it's not just hardware versus software, it's software versus an entire regulated capital-planning apparatus that moves on a different calendar than any of your internal deadlines.

Read the table as a warning, not trivia: a pilot can satisfy every row except one and still die. The row most PMs skip — regulatory affairs — is the one that decides whether any of the others get to matter.

The Stakeholder Survival Map: Influence, Alignment, and Who Bears the Risk

Map every stakeholder on two axes — influence over the decision and alignment with your solution — then overlay a third question: who absorbs the consequences if this fails? That third question catches the quiet stakeholders whose formal influence looks low but whose late veto is absolute.

The two-axis grid is a variant of the Miller Heiman Strategic Selling model (now part of Korn Ferry's sales methodology), which has separated buyers into economic, user, technical, and coach roles for decades. Utility coalitions map onto it cleanly — the economic buyer is finance, the user buyer is operations, the technical buyer is IT/OT security, and your best coach is usually a mid-level operations lead who wants the tool to work and will tell you the truth.

The risk-bearer overlay is the framework's real payoff. A control-room supervisor with no title on the org chart can sink a rollout if they're the one who answers for an incident at 2 a.m. A junior regulatory-affairs analyst can sink a renewal if they're the one who has to explain the spend in the next rate filing. Ask, plainly, in every discovery call: "who else needs to sign off, and who gets blamed if this goes wrong?"

Each stakeholder is effectively hiring your product to get a different job done — the dispatcher wants fewer alarms, the CFO wants a clean rate-base story, the regulatory lead wants an audit trail. Separating what each one needs done from what they say they want is exactly the discipline behind the Jobs to Be Done framework, and it's worth running that lens across every seat on your stakeholder map, not just the end user.

The Pilot That Won on Merit and Died on a Veto

A composite pattern recurs often enough across utility pilots to be worth naming plainly — not one client, but a shape you'll recognize if you've run one of these cycles. The product clears every technical gate, operations loves it, procurement signs the statement of work — and then regulatory affairs, never formally looped in, raises a rate-case risk in month four that kills the renewal.

Here's how it typically unfolds:

1. Discovery goes well. Operations and IT sponsor the pilot; the business case is strong; procurement runs a clean, if slow, RFP.
2. The pilot launches and performs. Metrics look good; the operations champion is thrilled; a renewal conversation is scheduled.
3. Regulatory affairs surfaces late. Someone asks how the spend will be characterized in the next rate case — capital or O&M, cost-recovery eligible or not — and nobody has an answer, because nobody asked regulatory affairs to weigh in during the pilot.
4. The commission relationship becomes the blocker. Regulatory affairs, worried about defending an unbudgeted or ambiguously categorized cost to the state commission, quietly recommends against renewal rather than risk a fight it didn't choose.
5. The deal stalls, then dies, and everyone who championed it internally is as surprised as you are.

Regulatory affairs isn't being obstructive here — it's doing its job. Bodies like NARUC (the National Association of Regulatory Utility Commissioners) exist precisely because state commissions scrutinize how regulated utilities justify spending to ratepayers, and regulatory-affairs teams live inside that scrutiny every day. A cost that looks obviously worthwhile to operations can look like unbudgeted risk to someone who has to defend it in a filing.

The failure wasn't technical and it wasn't really political malice — it was an unaddressed gap in the map. If your product touches anything with reporting or disclosure obligations, regulatory affairs should be in the room by the second discovery call, not the first renewal conversation. This is doubly true if your product intersects carbon accounting or emissions reporting, where the underlying measurement, reporting, and verification obligations are themselves a live regulatory topic that this stakeholder group already owns.

Alignment Debt: The Silent Killer Between Steering Committee Meetings

Alignment debt is the gap between what a steering committee approved on paper and what each member privately still believes weeks later — and it compounds silently, because utility committees meet monthly or quarterly while private doubt accumulates daily. By the time the debt surfaces, it's usually too large to renegotiate in a single meeting.

Steering committees are unusually vulnerable to a documented failure mode: the Abilene Paradox, named by management theorist Jerry Harvey, where a group collectively agrees to a course of action that no individual member actually wants, because everyone assumes everyone else is enthusiastic. Utility committees — hierarchical, risk-averse, and heavily invested in appearing unified to outside stakeholders — are close to an ideal breeding ground for exactly this dynamic.

Watch for these tells between meetings:

• A stakeholder who used to ask detailed questions goes quiet in status updates.
• A champion starts hedging language ("we're still evaluating" instead of "we're moving forward").
• Meeting attendance from one function starts slipping to a delegate.
• Follow-up items assigned to a specific person quietly stop getting done.

Any one of these is a symptom of alignment debt building somewhere you can't see. It shows up especially fast in technically sophisticated stakeholders — operations engineers who distrust a forecasting-heavy product, for instance, often go quiet rather than argue, particularly if the product's outputs feed decisions where the cost of a wrong call is measured in real capacity. Our analysis of how AI demand-forecasting errors cascade into megawatt-scale mistakes is a useful read for understanding exactly why this group double-checks everything before it trusts a model's output.

The fix isn't a bigger meeting. It's a standing habit of one-on-one check-ins with every stakeholder on the map between committee sessions, explicitly asking what's changed since the last one — because the committee setting itself is often what suppresses the honest answer.

Running the Map Through a Real Sales Cycle

Build the survival map in the first two discovery calls, then update it every time a steering-committee meeting happens or a stakeholder goes quiet for more than two weeks. A map built once at kickoff and never revisited is already stale by the time procurement sends the first contract redline.

A working cadence looks like this:

1. List every function touched by the outcome, not just the people already in the room — ask sponsors directly who else needs to be there.
2. Score influence and alignment independently. A friendly conversation is not the same as real alignment; test alignment by asking what could change their mind, not by how warmly they greeted you.
3. Name the risk bearer for every workflow the product touches, even if that person never appears in a meeting.
4. Re-score after every steering-committee meeting, especially when someone was unusually quiet — silence is data.
5. Loop in regulatory affairs and anyone PUC-facing during discovery, not after the pilot has already generated a paper trail you don't control.
6. Revisit the map before every renewal or expansion conversation, since influence and alignment both drift as budgets, reorgs, and rate cases change the incentives underneath people who haven't changed roles.

Treat the buying cycle itself as a journey with an emotional arc, not a linear approval chain — confidence typically peaks right after a successful pilot demo and erodes quietly through the gap before renewal, exactly where alignment debt does its damage. Building that arc out explicitly, the way a customer journey map would for an end user, is one of the more reliable ways to predict where a utility deal is about to wobble before it actually does.

Where Prodinja Fits: Turning the Map Into a Living System

Key Takeaways

• A utility is a coalition, not a buyer — procurement, operations, regulatory affairs, IT/OT security, finance, and the PUC each score your product differently and run on different clocks.
• Map influence, alignment, and risk-bearing separately — the person who bears the risk if a pilot fails often has more effective veto power than their title suggests.
• Regulatory affairs is the most commonly missed stakeholder, and the one most likely to kill a technically successful pilot late, over rate-case or disclosure concerns nobody raised early.
• Alignment debt accumulates silently between steering-committee meetings — watch for hedging language, quiet attendees, and missed follow-ups as early warning signs.
• Groups can unanimously "agree" to something no individual member wants — the Abilene Paradox is a real risk in hierarchical, risk-averse utility committees, not a rhetorical flourish.
• Rebuild the map at every inflection point — after each committee meeting, before every renewal conversation, and whenever a stakeholder goes unusually quiet.
• A static spreadsheet map decays fast; treating stakeholder health as a tracked, living signal — rather than a one-time exercise — is what catches drift before it becomes a lost deal.