Why Vertical Software Companies Build Around Utility Procurement Cycles

The sales cycle that doesn't fit the sales deck

Most SaaS sales training assumes a discovery call, a pilot, a champion, a budget owner, and a close within two or three quarters. Sell into a utility and that model breaks almost immediately. A regional electric cooperative or investor-owned utility can take twelve to eighteen months longer than a typical enterprise buyer to sign, and that gap isn't a sign of a weak product or a slow sales team. It's structural.

Utilities operate on multi-year capital and operating budget cycles that are often locked before a fiscal year even starts. A software purchase that wasn't planned for in last year's budget submission may need to wait for the next cycle to open, regardless of how well a pilot performed. Layered on top of that are regulatory approval steps: integrated resource plans, competitive solicitations, and commission sign-off before a contract can be executed. Energy Innovation's breakdown of the utility procurement chain walks through this sequence in detail, and it's worth reading for anyone who assumes a utility buys software the way a mid-sized retailer does. The California Public Utilities Commission's own description of its solicitation process shows the same pattern from the regulator's side: competitive bidding rounds followed by formal commission approval, with no shortcut for a vendor that's already won over the engineering team on the buyer's side.

Then there's incumbent lock-in. Utilities run critical infrastructure on systems that were often installed decades ago and validated through years of operational history. Replacing or even integrating with those systems carries real risk, and utility buyers are institutionally risk-averse in a way that's rational given what happens when a grid system fails. Salesforce Ventures has written about how this risk aversion and siloed buying culture shape the sales motion for vendors selling into utility markets, and the throughline is that low tolerance for unproven vendors slows everything down, even when the product itself is strong.

How teams fund the wait

A vertical software company that only builds product and waits for contracts to close will run out of runway before its first utility deal signs. So engineering-led teams selling into energy markets tend to fund development through consulting work or paid pilot contracts, treating those engagements as bridge revenue rather than the business model itself.

This looks different from a typical SaaS pilot. A 90-day free trial doesn't cover a year of engineering salaries. A paid, scoped pilot with a utility, often structured as a professional services engagement, can. The team gets real revenue, real usage data, and a foothold with a buyer who might otherwise never have taken a meeting. The risk is the one covered in the piece on the consulting retainer that quietly replaces the product roadmap: consulting revenue is easy to renew and hard to walk away from, and a team can end up optimizing its roadmap for the next statement of work instead of the product it's actually trying to build. In utility software specifically, that risk is sharper because the sales cycle gives consulting work more time to become the default source of income rather than a bridge to it.

The better version of this pattern treats every pilot as an explicit, time-boxed step toward a subscription or licensing contract, with the terms of that transition written into the pilot agreement itself. A vague pilot that ends with "we'll see how it goes" tends to drift. A pilot with a defined evaluation period, a named path to procurement, and a mutually understood price for the contracted version tends to convert.

What changes in hiring and roadmap

A startup selling into a fast enterprise sales cycle can hire ahead of revenue with some confidence, because the gap between a signed pilot and a signed contract is measured in months. A team selling into utilities can't make that same bet with the same timeline. Hiring the second or third engineer often waits until a pilot has actually converted, not when it looks promising, because "promising" can sit in a regulatory queue for a year without moving.

Roadmap prioritization shifts too. Features that shorten the regulatory or procurement path, like audit logging, role-based access aligned to how utilities structure internal approvals, or integrations with the incumbent SCADA or asset management systems already in place, often outrank features that would win over a typical SaaS buyer faster. A feature that makes the security review easier can matter more to close rate than a feature that makes the product more pleasant to use day to day.

This is also where pricing strategy tends to converge with what's already happening in other vertical categories. Utilities are a finite, well-defined market, and once a contract is signed, switching costs are high for the same reasons incumbent lock-in made the sale slow in the first place. That combination pushes vertical software companies toward the retention-first pricing logic described in why vertical SaaS founders price for retention instead of growth: a smaller number of durable, hard-to-replace contracts rather than a large volume of easily churned ones.

The metric that actually matters

Pipeline volume is a misleading signal in this market. A utility software company can have a healthy-looking list of pilots and letters of interest and still be eighteen months from its first real contract revenue. The metric worth tracking closely is pilot-to-contract conversion time: how long it actually takes, engagement by engagement, for a paid pilot to turn into a signed multi-year agreement, and what specifically caused the ones that stalled to stall.

That data matters more than deal count because it tells an engineering leader whether the bottleneck is regulatory, budgetary, or something the product team can actually influence. A utility that's waiting on its next integrated resource plan cycle isn't a lost deal, but it also isn't a deal that will close this quarter no matter how good the pilot went, and a company that treats performance-based ratemaking rules and procurement calendars, the kind NARUC documents in its work on how ratemaking treatment shapes utility IT investment decisions, as background noise will keep mistaking early enthusiasm for near-term revenue.

Slower, but harder to dislodge

Once a utility software contract closes, it tends to stay closed. The same regulatory and operational friction that made the sale slow also makes it expensive for a utility to switch vendors later, and multi-year terms are common because the buyer doesn't want to repeat the approval process again in eighteen months either. A vertical software company that survives the funding gap through consulting or pilot work, without letting that work quietly become the whole business, ends up with a customer base that looks small on a slide but is unusually resistant to churn. The question worth asking isn't why the deal is taking so long. It's whether the team can still afford to wait for it once it closes.