GTM Playbook for Energy and Utilities — The Complete Operator Guide in 2027

The revenue problem being solved

Most energy-tech vendors do not have a product problem. They have a timing problem dressed up as a pipeline problem, and it destroys revenue predictability in a way that no amount of outbound volume repairs.

The mechanism is specific to this sector. An investor-owned utility (IOU) cannot simply decide to buy your software. Its spending is recovered from ratepayers, and that recovery is authorized by a state public utility commission through a rate case — a formal proceeding that sets what the utility may charge and which capital and operating expenditures it may recover. Rate cases run on multi-year cycles, commonly three to five years depending on the state and the utility. Between filings, the authorized revenue requirement is essentially fixed. A vendor who arrives eight months into a thirty-six-month cycle is not being rejected; there is simply no approved dollar to spend, and no champion inside the utility can conjure one.

The revenue damage compounds in three ways. First, forecast integrity collapses: deals that "feel" late-stage sit at 80% for four quarters because the technical evaluation genuinely finished, but the funding gate is calendar-bound rather than persuasion-bound. Second, sales capacity is misallocated — reps spend cycles on accounts that are structurally unbuyable this year while accounts entering a filing window go uncovered. Third, cash planning breaks, because the same $1.5M contract may land in Q2 or eleven months later, and nothing in a standard CRM stage model surfaces the difference.

The second half of the problem is that the three buyer types in this sector do not behave alike, and vendors routinely run one motion across all three. IOU enterprise deals are large, slow, and regulatory-gated — commonly six figures to low seven figures in annual contract value, with cycles frequently spanning a year or more. IPP and renewable-developer deals are smaller, faster, and driven by asset-level return on investment: an operations lead who can show a megawatt-hour uplift or an operations-and-maintenance cost reduction can often approve inside a quarter or two. Industrial and commercial energy buyers sit somewhere between, driven by emissions-disclosure obligations, power purchase agreement negotiations, and on-site energy CapEx rather than by rate recovery at all.

Running a single motion across those three creates predictable failure. The IOU-calibrated motion is too slow and too consultative for a developer who wants a pilot on one wind farm next month. The developer-calibrated motion arrives at an IOU without a regulatory story, without cyber attestation, and without a rate-case-aware close plan — and loses to an incumbent original equipment manufacturer that has been in the account for two decades.

The operator's job in 2027 is to convert this from ambient chaos into a scheduled system: know each target's rate-case position, segment the motion by buyer type, and instrument the pipeline so that the funding gate is visible as a field, not discovered as a surprise in month nine.

Root-cause map

Before adding headcount or spend, trace the failure back to its actual origin. Most stalled energy-tech pipelines trace to four roots — funding timing, compliance disqualification, pricing-unit mismatch, and buyer-type blur — and each has a different remedy. Adding sales development representatives fixes none of them.

Read the map as a diagnostic sequence rather than a menu. Start at funding timing, because it invalidates everything downstream: a perfectly compliant, perfectly priced proposal into a locked budget year still produces zero. For each named account, record the last rate case decision date, the typical cycle length in that jurisdiction, and the next expected filing. Those facts are public — commission dockets are published — and a single analyst can build the map for thirty accounts in a few weeks.

Move to the compliance gate second. If the application touches bulk electric system operations, North American Electric Reliability Corporation Critical Infrastructure Protection (NERC CIP) obligations flow to the utility, and the utility pushes evidence requirements onto you. Vendors without a coherent security package get filtered before technical evaluation, which is why the loss looks inexplicable from the outside: you never entered the comparison. Operational technology security review routinely adds months to procurement, so the package must exist before the request for proposal, not after.

Third, check the pricing unit. Utilities model cost per customer meter, per megawatt, per substation, or per feeder because that is how their own economics and their regulatory filings are constructed. A per-user price forces the buyer to translate your quote into their unit before they can evaluate it — and the translation itself signals that you do not speak the language.

Fourth, check buyer-type blur. If your close plan, proof points, and reference customers are identical across an IOU, an IPP, and a manufacturer, at least two of the three are being underserved.

Benchmarks and ranges

Use ranges, not point estimates. Energy-tech benchmarks vary enormously by buyer type, and a blended average across all three ICPs is a number that describes no real deal.

Cycle length. IOU enterprise deals commonly run twelve to twenty-four months from first qualified conversation to signature, with the variance driven almost entirely by where the account sits in its rate-case cycle rather than by sales execution. IPP and renewable-developer deals typically compress to six to twelve months, because an asset-level operations budget is authorized annually rather than through a commission. Industrial and commercial energy buyers land in a similar six-to-twelve-month band, gated by capital approval and internal sustainability reporting cycles.

Contract value. Treat IOU deals as the large end — commonly several hundred thousand dollars to low seven figures annually for enterprise platform scope, with major distributed energy resource management or advanced distribution management system programs running far higher once implementation services are included. IPP and developer contracts commonly sit in the low hundreds of thousands to high six figures depending on portfolio megawatts under management. Industrial buyers commonly sit lowest, in the mid-five to low-six figure band per site or per program.

Services-to-license ratio. Plan for roughly one-to-one at the low end and up to three-to-one in year one for complex grid-operations deployments. This is not a failure of product design; utilities require integration with legacy supervisory control systems, geographic information systems, meter data management, and customer information systems, and that integration is real work. Model it in the plan or it eats gross margin silently.

Pilot conversion. The single largest lever on conversion is whether the pilot carried a pre-agreed, quantified operational hypothesis. Pilots defined as "let's see what the data shows" convert at a small fraction of the rate of pilots defined as "reduce truck rolls on these fourteen feeders by a stated percentage over nine months, measured this way, reviewed by this named operations director." Write the measurement method into the pilot agreement, including the baseline period and who owns the data.

Retention and expansion. Net revenue retention above roughly 110–120% is achievable for platforms that expand along three axes: additional service territories, additional functional domains, and additional commission-approved programs. Below about 105%, the expansion motion is broken — usually because the initial deployment was scoped to a single territory with no contractual path to the next one. Fix that in the master agreement, not in the renewal conversation.

Payback. Customer acquisition cost payback stretches long in this sector, particularly for IOU-heavy books, precisely because the cycles are long and the pre-sales engineering load is heavy. Two to three years is a realistic planning assumption for an IOU-weighted business; a developer-weighted book can approach the twelve-to-eighteen-month band more common in general B2B software. This is the core reason to keep a faster-cycling segment in the mix even when IOU logos are the strategic prize — the IPP and industrial revenue funds the IOU wait.

Win rate. On genuinely qualified pipeline — meaning the account is inside a funding window, the compliance gate is cleared, and the buyer type is correctly identified — a competitive win rate in the low-to-mid twenties percent is a reasonable target against entrenched incumbents. If your reported win rate is dramatically higher, the qualification bar is likely filtering out real competitive deals; if it is far lower, you are probably entering evaluations you were never eligible to win.

Trade-offs and alternatives

Every structural choice in this Playbook trades something away. Make the trades explicitly.

IOU-first versus developer-first. Leading with investor-owned utilities buys credibility, large contract values, and multi-year stickiness — utilities rarely rip out an operational system. It costs you eighteen to twenty-four months of burn before meaningful revenue, requires a regulatory function earlier than the revenue supports, and concentrates risk in a handful of accounts. Leading with IPPs and developers buys speed, reference volume, and cash, but the logos carry less weight in an IOU procurement and the contracts are smaller and more churn-prone as portfolios change hands. The common resolution: sell developers for cash and product hardening, sell one or two IOUs in parallel for the strategic reference, and be honest in board materials about which one is funding the company.

Direct versus channel. Grid and generation original equipment manufacturers and the large utility engineering firms have decades of account presence, existing master agreements, and procurement-approved status. Selling through them shortens procurement dramatically and can bypass a vendor-onboarding process that takes a year on its own. The cost is real: resale margin, a partner-controlled customer relationship, roadmap influence flowing to the partner, and slow motion when the partner's field organization has no incentive to prioritize you. The practical trade is to co-sell rather than resell early — keep the paper direct where possible, use the partner for access and credibility, and only concede margin when the partner genuinely originates.

Shared savings versus fixed subscription. Shared-savings pricing — taking a percentage of demonstrated energy or operations savings — lowers the buying barrier, aligns incentives, and can produce outsized revenue on high-performing accounts. It also creates measurement disputes, unpredictable revenue recognition, baseline arguments that consume customer-success time, and a revenue line that is hard to explain to investors. A fixed subscription with a smaller performance kicker usually beats pure shared savings for a company that needs a forecastable revenue base. Reserve pure shared savings for accounts that will not otherwise transact.

Deep single-domain versus broad platform. Going deep on one functional domain — outage management, asset performance, demand-side programs — makes you the obvious best answer in a narrow evaluation and shortens the technical sale. It caps account expansion and leaves you exposed when a platform vendor bundles your function into a larger agreement. Going broad early spreads engineering thin and invites comparison against entrenched suites on every axis. The workable sequence is depth first to win the beachhead, then adjacent domain expansion inside existing accounts, where you already hold the integration and the security clearance.

Build a regulatory function versus outsource it. An in-house head of regulatory and government affairs gives you continuous docket awareness, direct commission relationships, and the ability to time filings. It is an expensive senior hire that produces no attributable bookings for several quarters. Outsourced counsel or a consulting firm costs less and starts faster, but the knowledge does not compound inside the company and the relationships belong to someone else. Most operators outsource until the account map makes the calendar work unmanageable, then hire — typically once the business is supporting a meaningful multi-territory book.

One geography versus multi-state. Each US state is effectively a separate regulatory market with its own commission, its own docket rhythm, and its own policy mandates. Expanding to a new state means new relationships and a new calendar, not just a new territory quota. Saturating one region — including its municipal utilities and cooperatives, which buy faster and with far less regulatory overhead than IOUs — is usually cheaper than spreading two reps across a dozen states.

Rollout plan

Sequence the build so that each stage produces the input the next stage needs. The Complete rollout below assumes an early-stage vendor with a working product and a small number of design partners.

Quarter one — map before you sell. Build the account and calendar map for roughly thirty named targets across the three ICPs. For each, capture buyer type, last commission decision, expected next filing window, incumbent systems, and known policy mandates in that jurisdiction. This artifact is the highest-leverage document an energy-tech Operator produces, and it is built from public dockets and industry press, not from paid data.

Quarter two — remove the disqualifiers. Assemble the operational technology security package: architecture diagrams, data-flow documentation, access-control model, incident response process, and evidence of how your system supports the customer's own compliance obligations. In parallel, reprice into sector-native units and draft a master agreement designed for multi-year term, annual escalators, and clean expansion into additional territories without renegotiating from zero.

Quarter three — pilot with a number. Run two pilots, no more. Each gets a written hypothesis, a defined baseline period, a named data owner on the customer side, and an executive sponsor who has agreed in advance what result triggers expansion. Scope tightly — one substation cluster, one feeder group, one portfolio of assets. A sprawling pilot produces ambiguous data and a stalled renewal.

Quarter four — convert and publish. Take the pilot into territory-level rollout and publish the measured outcome in a form the customer's own regulatory team can reference. A quantified result that a utility can cite in its own filing is worth more than any case study you write for your website, because it makes your line item defensible in the next proceeding.

Year two — expand along the three axes. Adjacent functional domain inside existing accounts first, because you already hold integration and security clearance. Adjacent utility type second — municipal utilities and rural cooperatives buy with far less regulatory overhead and make excellent volume. Adjacent geography third, and only with a fresh calendar map for the new jurisdiction.

Steady state — govern with three meetings. A weekly rollout standup covering active deployments, at-risk implementations, and any filing that moves a deal. A monthly funding-window review that walks the calendar map across the top accounts and reprioritizes coverage. A quarterly regulatory horizon scan covering pending federal orders, state dockets, and policy mandates that create or remove demand. Three meetings, owned by named people, is enough governance for a business under fifty million in revenue.

Hiring sequence. The pattern that works: a founding team that pairs software leadership with genuine operating experience inside a utility, an ISO/RTO, a developer, or an energy consultancy — domain credibility is the price of the first meeting. Then a utility-native account executive who has carried a quota into these accounts before. Then a solutions engineer with power-systems background, because the technical evaluation is genuinely engineering-deep. Then a second account executive covering the faster IPP and industrial segments. Then sales leadership plus the regulatory function once the calendar work exceeds what a founder can carry.

Related questions

How do you find a utility's rate-case position?

State commission dockets are public. Search the commission's filing system for the utility's most recent general rate case, note the decision date and the test-year period, and check the state's typical cycle length. Industry trade press covers major filings in real time.

Do municipal utilities and cooperatives follow the same cycle?

No. Municipal utilities and rural electric cooperatives set their own rates through city councils or member boards rather than state commissions, which usually means shorter approval paths and faster procurement — smaller deals, but a useful volume segment while IOU cycles mature.

Should a seed-stage vendor chase investor-owned utilities at all?

Start one or two IOU relationships early for the reference and the learning, but fund the company on developers and industrial buyers. IOU cycles will outlast a typical seed runway, and a business that depends on one closing in month fourteen is fragile.

What makes a pilot convert to a rollout?

A written, quantified hypothesis agreed before the pilot starts, a defined baseline, a named data owner, and an executive sponsor who pre-committed to what result triggers expansion. Exploratory pilots without those four elements rarely convert.

How much should services revenue be?

Expect roughly one to three times license value in year one for grid-operations deployments. Model it deliberately — either staff it and price it as a margin-positive line, or partner it out to an engineering firm and keep the software margin clean.

FAQ

Why is per-user pricing a problem when selling to Utilities?

Utilities model their own economics per customer meter, per megawatt, per substation, or per feeder, and those units flow into their regulatory filings. A per-user quote forces the buyer to translate before evaluating, and the translation itself signals unfamiliarity with the sector. Price in the unit the buyer already uses in its cost recovery.

How early does compliance work need to start?

Before the first request for proposal, not after. Operational technology security review is a gating step that routinely adds months to procurement, and vendors without a documented posture are frequently filtered out before technical evaluation begins. Treat the security package as a go-to-market asset with an owner and a maintenance schedule.

Is events spend really worth thirty percent of the mix?

In this sector, generally yes at early stage. Utility and energy buying communities are small, relationship-dense, and concentrated at a handful of annual conferences where an entire target account's leadership is reachable in three days. The cost is high and the attribution is slow, so measure by meetings with named target accounts rather than by badge scans.

What is the fastest path to a first reference customer?

An independent power producer or renewable developer with a single, well-instrumented asset portfolio. The buyer is closer to the operating budget, the return-on-investment case is measurable within a quarter or two, and there is no commission gating the spend. Convert that into a publishable measured result, then take it into utility conversations.

How do you forecast a pipeline where funding is calendar-gated?

Add an explicit funding-window field to every opportunity, separate from stage. An opportunity can be technically won and financially blocked at the same time, and a stage model that cannot express that will forecast the same deal into four consecutive quarters. Forecast only opportunities whose window is open in the period.

When does an Operator hire a dedicated regulatory leader?

When the calendar and docket work across the account base exceeds what a founder or head of sales can carry — typically once the business supports a multi-territory book across several jurisdictions. Before that, outsourced counsel plus disciplined docket monitoring is usually the better use of cash.

Sources

• https://www.ferc.gov/
• https://www.naruc.org/
• https://www.nerc.com/pa/Stand/Pages/CIPStandards.aspx
• https://www.eia.gov/
• https://www.iea.org/reports/world-energy-outlook-2024
• https://www.utilitydive.com/
• https://www.woodmac.com/
• https://www.eei.org/
• https://sepapower.org/
• https://www.nrel.gov/

Related on PULSE

• [How do you build a renewable energy trading and ETRM software go-to-market motion in 2027?](/knowledge/gp0058)
• [GTM Playbook for IoT Hardware in 2027 — The Complete Operator Guide](/knowledge/gp0025)
• [GTM Playbook for Aviation and Aerospace in 2027 — The Complete Operator Guide](/knowledge/gp0024)
• [GTM Playbook for Automotive and Auto Tech in 2027 — The Complete Operator Guide](/knowledge/gp0023)
• [GTM Playbook for Pharma and Life Sciences in 2027 — The Complete Operator Guide](/knowledge/gp0022)
• [GTM Playbook for AgTech in 2027 — The Complete Operator Guide](/knowledge/gp0021)