Selling Into Utilities: Rate Cases, Capital Cycles and Why Your Q4 Push Doesn't Register

Your quarter is not a real thing to them

The first time I watched a rep lose a utility deal to the calendar, I thought he had been lied to. He had a champion in network operations who loved the product, a technical evaluation that went clean, and a verbal "we want this." He pushed for signature in December because December was when he needed it. The champion went quiet, came back in February, and said the words every rep selling into this sector eventually hears: "It didn't make the plan."

Not "we chose a competitor." Not "we lost budget." It didn't make the plan. There is a document, it gets built at a particular time of year, it gets approved by people your champion has never met, and if your line item is not in it, nothing you do in Q4 matters. You can offer a discount that would get you fired at any other account and the answer is the same, because the constraint was never price.

This is the thing that makes utilities feel impossible for the first year and then feel like the easiest sector you have ever sold into. The buying rhythm is slow, but it is legible. It is written down. It is, in most jurisdictions, literally public. Once you learn to read it, you stop guessing about timing, which is more than you can say for almost any other market.

The money comes from a filing, not a budget line

Here is the piece most reps never bother to understand, and it explains nearly everything else.

A regulated utility does not set its own revenue. It goes to a regulator and makes a case for what it needs to spend and what it should be allowed to charge customers to recover that spend. Capital investment — poles, wires, transformers, substations, and increasingly the systems that manage them — typically goes into the rate base and earns a regulated return over its useful life. Operating expense usually does not work that way. It gets recovered, but it does not earn.

Sit with that for a second, because it inverts every instinct you brought from selling SaaS. In most of your accounts, opex is the easy money and capex is the painful ask. In a regulated utility, capital spend is the thing the business is structurally built to want, and a recurring operating cost is the thing that has to justify itself against a tighter test. I have watched deals get easier the moment the buyer figured out how to classify them as part of a capital programme rather than a software subscription, and I have watched deals stall for a year because nobody on the vendor side even knew that distinction existed.

You do not need to be an expert in utility finance. You need to know enough to ask your champion how they intend to fund it, and to not look confused by the answer. If they say "we'd want this to sit inside the asset replacement programme," that is very good news and you should immediately ask which programme, what its approval status is, and who owns it. If they say "I'd take it out of my opex," you need to find out how big that pot is and whether it has already been committed, because in a lot of these organisations it has been committed since before the fiscal year started.

What a rate case does to your deal

A rate case is the proceeding where the utility argues for what it can spend and charge. Around one, two things happen that affect you directly.

Before and during a filing, the organisation is in justification mode. Everything is being built into a case that has to survive scrutiny from a regulator and, often, from consumer advocates who are paid to argue that the utility is spending too much. This is a fantastic time to be useful and a terrible time to push for a signature. If your product helps them show that a proposed programme is targeted, evidence-based and defensible, you are contributing to the case. Give them material. Let them use your analysis in their justification. You are buying a place in a document that will fund purchases for years.

After an outcome, the picture changes. If the utility got most of what it asked for, there is approved capital with programme owners under real pressure to deploy it against the schedule they committed to. That is your window. If they got cut, budgets tighten, discretionary work dies first, and anything that reads as "nice to have" is gone. Same product, same champion, completely different year.

So the single best piece of account research you can do is find out where each of your target utilities sits in that cycle. In many markets these filings and decisions are public record. It is not glamorous work. It is also the closest thing to a cheat code I have found in this sector, because it tells you which accounts to work now and which to nurture, and almost nobody selling to utilities does it.

Who you are actually selling to

Forget the org chart you would build for a normal enterprise account. The centre of gravity in a distribution utility is not the CIO and it is usually not the CFO.

Head of asset management is the person who owns the question of what gets replaced, when, and why. They are the ones who have to defend a spend plan against both the engineers who want to replace everything and the finance people who want to replace nothing. They think in asset classes, condition data, failure modes and remaining useful life. They are usually the closest thing you will find to an economic buyer for anything involving asset risk, and they are the person I would open the account with. I have written a separate breakdown of what the first thirty seconds with a head of asset management actually needs to sound like, because the opener that works on a VP of Sales will get you hung up on here.

Network operations owns the live system. Outages, switching, restoration, crews. They are the most operationally busy people in the building and the most allergic to anything that adds a screen to look at. They will tell you the truth about whether your product would actually get used, and their scepticism is worth more than a friendly executive's enthusiasm. If ops says "nobody would look at that during a storm," believe them and change the product story.

Reliability engineering owns the metrics the regulator watches. They live in outage frequency and duration statistics, worst-performing feeders, root cause analysis. If your product moves any of those, they are your best technical champion, because their job is measured on exactly the thing you are claiming to improve.

Then there are the people who can only say no. Procurement, who will run a process you did not design. Regulatory affairs, who will care whether your claims can be defended in a filing. And OT security, who will ask what your system touches and will kill you cheerfully if the answer involves anything near the operational network. None of these will buy your product. All of them can end the deal. Find them early, ask what would make them uncomfortable, and deal with it while you still have time.

One more thing about people. Tenure in this sector is long. The engineer you talk to may have been at that utility for twenty years and may still be there in ten. That cuts both ways. Burn someone with a pushy close and you have not lost a quarter, you have lost an account for a decade. Be useful to someone early in a cycle and they will bring you into the next programme without being asked.

Reliability and safety beat efficiency in every internal memo

If you take one thing from this post, take this one.

When your champion writes the memo that asks for money, that memo has to survive a room. The room contains engineers, finance, regulatory affairs and probably a lawyer. Every argument in it will be tested. And there is a hierarchy of arguments that reliably wins in that room, and it is not the hierarchy you were trained on.

Safety wins. Always, first, unconditionally. A case built on preventing an asset failure that could hurt somebody — a member of the public, a lineworker — does not get argued down in the same way other cases do. Nobody in that room wants to be the person on record saying the safety case was not worth funding.

Reliability wins next, because it is regulated. Outage performance is measured, reported, and in many regimes tied to penalties or incentives. A programme that demonstrably improves reliability metrics has a natural home in a filing and a natural defender in the room.

Compliance wins after that, for the obvious reason.

Efficiency comes last. Not never — cost savings help — but it is the weakest argument in the memo, and it is the one every vendor leads with. "We'll reduce your truck rolls" is a fine supporting line and a terrible headline. I have sat in on discovery calls where the rep spent twenty minutes building an efficiency case to a reliability engineer who was politely waiting for them to say something about feeder performance.

So write your value proposition in their language. Not "we make your inspection process more efficient" but "we help you find the assets most likely to fail before they fail, and evidence that decision." Same product. One version can go in a memo. This is most of what I try to teach in the discovery playbook for network and asset buyers — the questions are designed to get the buyer describing their own case in their own words, so you can hand it back to them in the shape a memo needs.

Timing outreach to a capital planning window

Here is how I would sequence a year, given the rhythm above.

There is a period when the capital plan for the coming period is being built — when programme owners are assembling what they want to do and what it will cost. That is when your line item can still get written in. Reaching a head of asset management during that window with a credible, quantified, defensible case is worth more than ten touches at any other time of year. Ask your champions directly when that window is. They know. It is not a secret and they are not being coy about it, they just assume you already know because everyone inside the industry does.

There is a period after approval when programme owners are under pressure to actually deploy against commitments. This is when procurement moves faster than you expect and when "we've had budget for this since the spring" turns into an unexpectedly quick close.

And there is storm season, whenever it falls in your geography. During it, do not chase. Nobody in network operations is going to take your call while crews are out. After it, though, there is a genuine opening, because every major weather event produces an internal review and a list of things that went badly. If your product speaks to anything on that list, you have a warm reason to be in the room and a champion with fresh evidence.

What you should stop doing is running your utility accounts on your own forecast rhythm. The end-of-quarter discount push does not register. It signals that you do not understand how they buy, which costs you credibility with people who are quietly grading you on exactly that.

The two questions that tell you inside five minutes

Most of the utility "pipeline" I have reviewed is not pipeline. It is a collection of interested engineers doing research. Interested engineers are lovely and they will take your calls forever. Here are the two questions that separate them from funded work, and I would ask both on the first substantive conversation.

One: "Which approved programme would this sit inside, and who owns that programme?"

Note what it does. It does not ask if there is budget, which invites a hopeful answer. It presumes a programme and asks them to name it. A funded initiative has a name — an asset replacement programme, a resilience programme, something with an internal acronym — and a named owner. You will get that name in one sentence. A research project produces hedging: "we'd need to identify a home for it," "that would probably come out of the innovation budget," "I'd have to check." All of those mean the same thing, and the thing they mean is not no, it is not yet.

Two: "What happens to your reliability numbers if you do nothing for another two years?"

This one tests whether there is pressure. A funded initiative exists because something is getting worse and somebody has to answer for it. If they can describe the trend — ageing asset population, a feeder that keeps failing, a commitment made to the regulator — you have a real driver and a case that will write itself. If the answer is a shrug, or "honestly, probably nothing," then you have found somebody's interesting side project. Keep the relationship, because those people become programme owners. Just do not forecast it.

If both answers come back strong, your job shifts from qualification to helping your champion build the internal case, which means being unusually generous with evidence and unusually disciplined about your number when procurement finally arrives. Holding price after the technical win is its own skill in this sector, and I have laid out how I would run that negotiation separately, because discounting into a regulated buyer for calendar reasons they do not share is the most common self-inflicted wound I see.

Where I would start

Pick your top ten utility accounts. For each one, find out where they sit in the regulatory cycle and when their capital planning window falls. Then sort your outreach by that, not by your close date. You will find that half of your list should be nurtured and a quarter of it should be called this month, and that is a far better use of a year than treating all ten the same.

Then practise the opener, because the head of asset management call is short and unforgiving and you get one shot per quarter with a person who has been at that utility longer than you have been in sales. That is the specific thing I built DrillCall for — running the same thirty-second opening and the same two qualifying questions against a buyer who pushes back the way a real one does, until the language stops sounding like a vendor and starts sounding like someone who has read a rate case. If I were breaking into this sector today, that is the hour I would spend before I picked up the phone.