How to build new logo pipeline for geospatial analytics sold to electric utilities

The vegetation program manager decides. They are often a forester by training, have run this program for fifteen or twenty years, and have been shown aerial and satellite analytics every year for the last eight. They are not sceptical because they are conservative. They are sceptical because an early product once handed them four thousand findings, three thousand of which were wrong, and their crews spent a season driving to trees that did not need touching.

Above them sits a vice president of asset management or operations who owns reliability performance, and increasingly a wildfire mitigation officer whose role did not exist a decade ago and who holds the newest money in the building.

Two other functions are not buyers and can decide the outcome. Regulatory affairs cares about one thing, which is whether the cost can be recovered and whether the program matches what was filed. Procurement cares about whether you are a qualified supplier, and will stop a signed intention dead for six months over insurance and security paperwork.

And then the line clearance contractor, who is either your distribution channel or your quiet opposition, depending entirely on how they are paid.

Utilities are not slow because they are unimaginative. They are slow because the money is regulated, the commitments are public, and being wrong is expensive in a way that being late is not. Every belief below follows from that, and so does every counter.

What they believe today.

• We already have the data. There is a LiDAR flight from a few years ago, imagery somewhere in the GIS, and a contractor who walks the line. Data is not the gap.
• The cycle is the program. We trim every circuit on a fixed rotation because that is what was approved, and deviating from it is not ours to decide.
• Remote detection does not work well enough. We tested it, the false positives were unusable, and our crews lost confidence in the list.
• This is an operating expense in a year when every operating expense is under pressure, and it competes with tree crews we already cannot fully fund.
• Vegetation is the contractor's responsibility. That is what we pay them for.

What has to be true before they can buy.

• The product is not detection, it is a work order a crew will accept. Findings are worthless and are sometimes worse than worthless, because a crew that drives to three wrong trees stops believing the fourth. The measure is crew hours redirected to miles that needed the work, and it should be the first number in your email rather than an accuracy figure.
• The cycle is a commitment in a filing, and filings are amended with evidence. That reframes your product entirely. You are not asking a program manager to abandon an approved practice on your say so, you are giving them the documentation a deviation requires. Condition based work is a regulatory argument before it is an operational one.
• Having imagery is not having a layer. A flight from three years ago is a snapshot. What changes the program is the same measurement repeated annually so that growth rates, not absolute heights, drive the schedule. Change over time is the asset, and it is the thing they genuinely do not have.
• Cost recovery is part of your pitch, not their problem to solve after the fact. Whether this sits in operating expense, rides inside a capital hardening program, or belongs in a mitigation plan filing decides whether it is affordable, and a vendor who raises it first looks like someone who has sold into this industry before.
• Contractor incentives are a legitimate subject for the first conversation. If the contractor bills time and materials, precision reduces their revenue, and pretending otherwise wastes a year. If the contractor is moving to unit or performance based work, they need your evidence more than the utility does.

The whole reframe compresses into one sentence worth saying out loud in a first meeting: you are not selling a better way to find trees, you are selling the evidence that lets them spend the same budget on the miles that matter and defend that choice in a filing.

• Wildfire mitigation plans and their annual updates. Filed publicly in the states that require them, and they state inspection commitments, circuit miles, spend and often the technology already in use. This is your prospect's strategy, written by your prospect, available to you before their own crews have read it.
• General rate case filings and supporting testimony. These lay out the vegetation management budget, the trim cycle, the miles and the reliability targets, in numbers, under oath. A rate case is also a calendar: the year before a filing is when new programs get built into the request.
• Annual reliability reporting with outage cause codes. When the share of outages attributed to vegetation moves the wrong way, that is a public number a vice president has to explain, and it is the single most useful sentence you can quote back to them.
• Commission orders, disallowances and enforcement actions. A regulator refusing to let a utility recover spend, or ordering improvement, creates a mandate with a deadline attached and a name on it.
• Major storm events and the after action reports that follow. Restoration reviews name the causes and the gaps, and the six months afterwards is when unfamiliar approaches get funded.
• Federal and state grid resilience awards. Public, named, with amounts and scopes, and frequently including inspection and situational awareness work that has to be spent within a window.
• Line clearance contract solicitations and awards, plus job posts for vegetation program managers, GIS analysts and wildfire mitigation staff. A contract going out to bid is the moment the whole program is under review.

Mitigation plans and rate case filings are the two to build on. Everything a normal outbound program guesses at, this industry publishes: the budget, the cycle, the miles, the target and the failure.

• How many circuit miles, and how much of it is in elevated risk terrain? Miles are the pricing unit and the risk profile decides whether this is a compliance purchase or a nice to have.
• Is there a filed obligation? A mitigation plan commitment or a reliability penalty mechanism turns your product from an improvement into a way of meeting something already promised.
• Which budget: vegetation, asset management, or the mitigation office? The mitigation office usually has the newest money and the fewest incumbent relationships, which is why it is the best door in a large utility.
• How is the line clearance contractor paid? Time and materials means an internal counterweight you need to know about in week one rather than month eight.
• Is there an enterprise geographic information system, and who owns integration into the work management system? A finding that cannot become a work order in their own system does not get used, whatever it costs.

Quote their own filing back to them. Not aggressively, and not as a gotcha, but as evidence that you arrived having read what they published rather than what their homepage says.

Then lead with crew productivity rather than detection, because the program manager has heard every accuracy claim in the industry and has stopped hearing them.

Each one demonstrates that you read the docket, states a distinction the program manager recognises, and offers thinking rather than a demonstration. In an industry where everyone opens with satellites and artificial intelligence, being the person who read the filing is the differentiator.

• We use AI and satellite imagery to find vegetation encroachment. Every competitor in the market opened with that sentence, several of them to this same person, in this same quarter.
• An accuracy percentage with no false positive rate and no definition of ground truth. The program manager's entire scar tissue is about false positives, so a precision claim without them reads as either naive or evasive.
• Any suggestion that the trim cycle is irrational. It was approved by a regulator, it is defended in testimony, and telling its owner it is obsolete puts you on the wrong side of a document they helped write.
• A note to the chief executive. Utilities are hierarchical, the note will be forwarded down with a name attached, and the program manager now knows you went over their head before you met them.
• A named competitor's failed pilot. This industry is small, everyone has worked together, and the people involved will hear about it within a fortnight.

We tried this and it did not work. The defining objection of the niche, and it is usually true. Do not defend the category. Ask which year, what resolution and what the false positive rate was, then propose a blind test on circuits they have already worked, scored against their own completion records, with the result theirs whether or not they buy. The program manager has never been offered a test they could lose safely, and the offer itself is persuasive before any data moves.

The commission approved our cycle. Agree, then reposition. You are not asking them to break the commitment, you are supplying the evidence base a modification requires, and the regulator is far more receptive to a documented risk based program than to an assertion. This is the single move that turns your product from an operational tool into a regulatory one, and it changes who in the building is willing to champion it.

There is no budget this year. Almost always true, and the answer is a calendar question rather than a discount. Which docket, which filing, and when does the next one get drafted. Programs enter this industry through filings, so being in the room the year before the request is written is the whole game, and a vendor who understands that is immediately easier to talk to.

Our contractor handles vegetation. Ask how the contractor is paid, and listen to the answer rather than countering it. On time and materials, you have found the structural reason the program has not changed in a decade, and it is not the program manager's fault. On unit based work, the contractor is your best possible partner and the conversation should include them by name.

• Blind test or paid pilot on a defined set of circuit miles: commonly $25K to $100K, scored against the utility's own historical work records rather than against your own assessment.
• Annual subscription priced per circuit mile, with distribution and transmission priced separately because the risk and the resolution requirements are different. Total annual value commonly lands between $150K and $1M depending on territory size.
• Multi year agreement aligned to the rate case period, which the utility often prefers because a commitment inside the recovery window is easier to justify than an annual renewal.
• Integration work into the geographic information system and the work management system, priced separately and never skipped. A finding that does not become a work order is not used.
• Signer: a vice president of asset management, operations or wildfire mitigation. Decider: the vegetation program manager. Blockers: procurement and regulatory affairs. Cycle: nine to twenty four months, and the budget calendar matters more than the sales calendar.

One structural note. A reference from a comparably sized utility is worth more here than in any other niche in this set, because these buyers attend the same three conferences and phone each other before they commit. Your second deal in a region is materially easier than your first, which is an argument for concentrating geographically rather than chasing the biggest logo.

• Monthly, work the commission dockets in your target states for mitigation plan updates, rate case filings, reliability reports and orders. This is the research spine and it cannot be outsourced to a keyword alert alone, because the useful detail is in the testimony rather than the headline.
• Annually, map the filing calendar for every utility on your list and work backwards. The productive window is the year before a rate case, not the month after it.
• As they happen, treat major storms and enforcement actions as interrupts. The six months after a restoration review is when things change.
• Quarterly, pull job posts for vegetation, geographic information systems and wildfire mitigation roles, and watch for leadership changes at the vice president level.
• Eight to twelve accounts a week is a full program, because each first email needs a filing read properly. This is a universe of a few hundred utilities and several hundred cooperatives, so precision is everything and there is no second attempt at a first impression.
• Three touches, then wait for the next filing. There is always a next filing, and it gives you a reason to write that is about them rather than about your follow up.

Every other buyer in this collection makes you guess at their budget and their commitments. This one publishes both, under oath, on a schedule. The only question is whether you read it.

Everything above is about who and what. This is about how, and it is where most outbound in this niche quietly dies. Seven rules. None of them are optional.

None of this is specific to your niche. All of it is specific to whether anyone ever reads the angle you spent an hour getting right.

That is what we do. ExpertLayer runs this exact loop for firms with proprietary technology: the docket monitoring across your target states, the mitigation plans and rate cases read for the numbers that matter, the reliability reports, the storm reviews, the filing calendar mapped per utility, the angle written per account in the language of that filing, the sending across warmed mailboxes, and the reply reading. You take the technical conversations and the blind tests.

The first step is free and it is the same research described above. Send us your website and we will come back with 10 companies that hit these triggers right now, with the filing, the commitment or the order, the contact, and the opening line for each.