What's Changing in the Telemetry You Own

Every CTO at a mid-sized European energy and environment firm has had the same Monday. Your forecast-error dashboard shows balancing-interval error at one point eight percent, point-four wider than last week. Your duty controls engineer has left a note. Two wind assets in the north cluster had a ramp-rate event Sunday the model did not predict. Your phone buzzes. It is your biggest TSO customer. One sentence: "Our board is looking at an AI-native pilot for forecast-error reduction, happy to talk before we shortlist." Your senior data scientist mentioned a recruiter call from a developer over coffee Thursday. Your CEO has a CAIO shortlist from the board on his desk. Your CFO forwarded the Shopify R&D trajectory this morning: "Worth discussing before Q2 planning."

You have run this function for ten years. The pattern used to be simple. Hire strong engineers. Ship forecast, asset-intelligence, or diligence code at the release cadence. Hold the integration bar against the customer's SCADA environment. Meet the board on platform uptime and feature velocity. The business was understandable.

Something changed. What used to take fifty engineers on a forecasting or asset-intelligence product now runs on five. Compression arrived faster than the discipline to absorb it. Ninety-five percent of corporate AI deployments produce no measurable P&L impact, and the gap between what the tools can do and what your firm's system absorbs is where your seat now lives or loses. An AI-native at ten percent of your unit economics is beginning to pitch into asset-ops optimisation, forecast-error reduction, and diligence automation. Your senior controls engineer carries integration reasoning that has never been written down, and a developer client is offering forty percent more to hire him.

You are not running one R&D function. You are running two, and only one is on your scorecard. One funds what you already ship. The other funds what has to exist by 2028: the asset-telemetry rights you have not renegotiated, the regulatory-precedent corpus you have not encoded, the integration depth into the top ten customer SCADA environments that outlasts three model swaps. On one hurdle rate the first wins every quarter. On one scorecard the second does not exist.

This briefing covers what is happening in your sector, what it means for the R&D function you run, and the three questions your team should answer before the next board cycle.

Energy and environment is the one sector in Europe where the knowledge problem runs in reverse. Every other industry is trying to capture expertise before it retires. You are trying to encode expertise faster than you create it. Every offshore-wind assessment, every hydrogen pathway, every BESS permit, every grid-connection response, every forecast-model calibration against a Nordic winter operating profile generates asset and regulatory precedent worth more next year than today. The firm where that knowledge compounds institutionally has a structural advantage competitors cannot hire away. The firm where it lives in three senior heads loses the advantage the month two of them take a developer offer at forty percent premium.

The AI-natives in your category are starting to arrive. They are pitching into asset-ops optimisation, forecast-error reduction, trading-signal generation, diligence automation, and regulatory-submission drafting. Sierra, Harvey, Decagon, and the sector-specific entrants shipped to first reference customers in the past twelve months at roughly ten percent of your per-project or per-seat unit economics. Your TSO, DSO, and IPP customers' procurement teams run comparison quotes where your price sits next to the AI-native's per-outcome number. They are not asking which is the better product. They are asking which pricing model their CFO can defend.

Your feature shipped on the current foundation model is on an eighteen-month obsolescence curve. Your integration depth into the top ten customer SCADA environments is the asset the AI-native cannot replicate without your customer base.

Between 2015 and 2020 the sector watched a major industrial-software platform launch with enormous capital and a promise to unify asset intelligence across every vertical. It retreated. It tried to build a horizontal platform without owning vertical asset-data rights and without winning the integration fight into specific customer operating environments. The narrower competitors with tighter integration took the market. That memory is fresh. The CTOs who remember it and act on it are already shipping the data-rights audit and the integration-depth graph this quarter. The ones running Copilot across the engineering team and calling it an AI strategy are the ones the board will replace in 2028.

Your build engine. Copilot adoption is at seventy percent across your engineering team. Cycle time has not moved. Velocity is up on the dashboard. Your controls engineers are pushing ten-thousand-line PRs barely reviewed, and the integration code that touches your customer SCADA environments is where the foundation rots fastest. Twelve months in, your team cannot execute a category rewrite when one arrives. The review discipline that worked on a four-person controls team in 2022 is training the wrong practice on agent-generated volume now.

Your platform and data. Spotify's best developers have not written code since December because Spotify spent four years on platform foundation. You cannot replicate four years in eighteen months while also defending against an AI-native at ten percent of your unit economics. You can buy build-side discipline from the tool layer. Redirect compounding capital into the layer the tool vendors cannot sell: asset-telemetry rights renegotiated across your next twenty-four months of customer contract renewals, a model-agnostic agent-memory store for asset behaviour and regulatory precedent, an integration-depth graph published for your top ten customer SCADA and DCS environments. Model layer commoditises. This layer compounds.

Your product thesis. Your board asked for the firm's three-sentence thesis last quarter. Your answer was the one from three years ago. Your rate card assumes AI-augmented features will price like legacy features. They do not. The AI-natives in asset-ops optimisation, forecasting, and diligence are quoting per-outcome. You quote per-project or per-seat. That is a capital-allocation question about where the moat gets built, not a pricing one. Your CFO and commercial leader need a joint document with you before the AI-native forces the conversation on their terms.

Your R&D bench. Your senior controls engineers, senior data scientists, and senior regulatory specialists carry the reasoning behind every integration, every forecast-model calibration, every permit strategy your product runs on. Two of them have recruiter calls from developers at forty percent salary premium this quarter. You stopped hiring juniors in 2024. No routine work, no training ground, no senior bench in 2030. The firm that cuts for this year's number has a cheaper function in Q4 and an empty bench in five years.

Your board-level authority. Thirty percent of European AI-strategy ownership sits with the CIO, twenty-three percent CDAO, twenty-one percent CAIO, one percent COO. You are not on the list. Not because you abandoned the mandate. You have not yet claimed it. Your CEO has a CAIO shortlist. Every month without a visible claim, the thesis drifts further from the seat that can defend it. Your Q1 boundary agreement with the CEO lands before the CAIO shortlist, not after.

Your sector is repricing from below because AI-natives are shipping outcomes-priced products at ten percent of your unit economics. Your function is compressing because five engineers now produce what fifty did, and the review bar that worked for fifty cannot hold the volume five produce with agents. Same force, two altitudes. But there is a third thing happening that most mid-market energy and environment CTOs have not named yet.

The integration depth you have been writing off as technical debt is the moat you have already built. Twenty years of field-conditioned integration into customer SCADA, DCS, and CIM environments. Every permit response you filed. Every ramp-rate event your model learned from. Every grid-code nuance your regulatory specialist walked the TSO through. A two-person AI-native cannot replicate that layer because they do not have the customer base that generates the signal. You do. The window closes in roughly eighteen months, which is the time between now and when the first AI-native entrants have enough of their own customer footprint to start building the same layer.

In 2006, a handset manufacturer shipped the best-engineered product in the world. The queue for their next flagship was eighteen months out. Their CTO's scorecard was battery life, keyboard quality, enterprise email reliability, carrier relationships. Every metric was green. Apple shipped a platform. By 2011 that handset manufacturer's market share in its own category had fallen from forty-three percent to ten. The 2006 scorecard never turned red. It just stopped being the one the market was scoring. The job had not changed. The unit of judgment had.

You have twelve to eighteen months. The CTOs who claim the authorship of this decision in Q1 author the decade. The ones who wait until the CAIO hire arrives inherit a seat that has narrowed to platform uptime and feature velocity, and a scorecard that stopped mattering the quarter their biggest TSO customer opened a pilot with someone else.

Every CTO has had the AI conversation. Most are making the same four decisions. A smaller group is making different ones.

Three questions every energy and environment CTO is tracking. The second is the crux. The first and third are how you earn the right to answer it.

Four concrete moves any energy and environment CTO can start this quarter. Each addresses one sub-function. Pulled together, they become one architecture the firm builds on.

The energy and environment CTO has four places to go. None can do what we do.

The big tech-transformation practices ship a standardised AI-governance framework scaled across a sector book. Their cost structure requires reusability. Your seat is idiosyncratic. A reusable framework on an idiosyncratic seat produces governance theatre you cannot defend to the board.

The hyperscaler and industrial-cloud professional services arms price the engagement as enablement for cloud or platform consumption. Their business model requires lock-in. Every build-or-buy decision routes through their pricing and their APIs for three years.

The AI-platform vendors and asset-intelligence upstarts have a quote on your desk. Their product is a feature-velocity intervention measured on seats or asset-connection count. Telling you to spend freed capacity on the data-rights and integration-depth moat instead is structurally impossible for them to say.

An in-house or fractional CAIO splits the seat. Strategy CAIO is revenue-measured; Platform CAIO is uptime-measured. One person cannot hold both in an asset-operations environment. Two-thirds of newly-appointed CAIOs spend year one compiling inventories instead of setting direction.

The four options you have already looked at. None can run the capital-allocation conversation the seat requires. GRAIL is the fifth.

We start with your R&D leadership team because the change cannot outrun the team's personal understanding of what is possible. Three workshops. Each delivers standalone value. Each earns the right to the next.

The questions where your R&D leadership cannot agree on an answer are the ones worth an hour on the agenda.