Why AI Efficiency Is Now a Board Governance Issue

Jim Delaney
Sep 28, 2026
•
7
min read

Every Prompt Has an Energy Bill

Last week I argued that most PE portfolios aren't getting AI operating leverage because they treat AI as a tool when they need to treat it as an operating system. That gap already has a price in the valuation multiple.

This week, Forbes gave it a second price: the energy bill.

In Why AI Efficiency Is Now A Board Governance Issue (Forbes, Sep 21, 2026), board director Heather Wishart-Smith cites the International Energy Agency: electricity used by AI data centers rose roughly 50% in 2025 alone. Lawrence Berkeley National Laboratory projects U.S. data centers could consume 6.7% to 12% of all U.S. electricity by 2028, up from about 4.4% a few years earlier.

Her conclusion is the right one. AI efficiency has moved off the IT budget and onto the board agenda. A board that can't explain, layer by layer, where its AI footprint comes from isn't governing it.

I'd go a step further. The biggest AI efficiency problem isn't compute. It's context. And the fix is the same Operating Foundation I wrote about last week.

‍

Three Layers, One Common Root Cause

The Forbes piece splits AI efficiency into three layers. Each has its own expert and its own headline number.

  • Platform. France Hoang, CEO of BoodleBox, explains that each prompt normally carries every earlier message and attachment with it, resent every time. BoodleBox sends only what's relevant to the current request and cuts token use by up to 96%.
  • Infrastructure. Sam Tabar, CEO of WhiteFiber, says AI clusters routinely run below 40% utilization, sometimes below 30%. The power, cooling, and capital behind those clusters is going to idle hardware.
  • Data. Michael Gale, CMO at EDB, points to indexing, retrieval, and context management as the layer where companies can actually intervene. In one telecom pilot, tightening how much context went into each inference call cut token use by about 57% and data center emissions by up to 87%, without a meaningful drop in response quality.

Look at where those gains came from. Two of the three had nothing to do with better chips or a better model. They came from sending less context, and better context, into every AI call.

That's a governance problem wearing an engineering costume. You can't send only the relevant context if nobody has defined what's relevant, verified that it's current, or decided who owns it.

‍

Workslop Is What an Ungoverned Foundation Produces

Hoang's sharpest line in the article isn't about tokens. It's this: "What's better than reducing tokens? It's not using tokens at all."

He's talking about AI workslop: polished-looking output that turns out to be vague, irrelevant, or wrong, because nobody defined the problem before prompting.

Last week I described a CRO asking her AI tools why deals were slowing down and getting confident, plausible, and completely wrong answers. The tool wasn't broken. It was ungrounded. It had no verified record of her ICP, her qualification criteria, or her pipeline, so it filled the gap with something that sounded like an answer.

That's workslop. And workslop costs you twice:

  1. You pay for the tokens that produced the wrong answer.
  2. You pay again when someone acts on it, whether that's a forecast the board relies on, outreach sent to the wrong accounts, or a rep chasing a deal that was never qualified.

Then the team re-prompts, attaches more documents, and drags more history into the next call. The token bill grows and the answer still isn't grounded.

The guardrail I described last week is the most efficient thing in the stack: an AI skill checks its dependencies before it runs. If the qualification criteria, positioning, or pipeline data it needs hasn't been verified as current, the skill doesn't fire. You get no output, just a flag saying what needs to be verified first.

That's Hoang's point turned into a mechanism. The cheapest token is the one a governed system refuses to spend.

‍

Mapping the AI Operating Leverage Trinity to the Efficiency Stack

The three components from last week, Foundation, Layer, and Analytics, line up closely with what Forbes says boards now need to govern.

Operating Foundation (Context Vault)

  • Leverage: Single source of truth for Identity, Direction, Evidence, Active Work, and Decisions & Authority.
  • Efficiency: Each AI call pulls only the verified, relevant context it needs. No full history, no attachment sprawl. This is the data layer Gale says companies can control.

Operating Layer (AI Skills)

  • Leverage: Scores leads, routes deals, drafts outreach, forecasts risk.
  • Efficiency: Each skill is scoped to a defined job and gated on verified context. The problem is defined before any token is spent, and the task gets the right-sized tool: a golf cart, not a Lamborghini.

Managed Analytics (Health & Drift Detection)

  • Leverage: Monthly audits catch Foundation drift before it breaks workflows.
  • Efficiency: Gives the board a layer-by-layer account of where AI spend goes and whether it's producing outcomes. That's the reporting Wishart-Smith says is becoming a board competency.

The architecture that stops AI from hallucinating is the same one that stops it from wasting tokens. They're not separate initiatives. They're one discipline.

‍

The Portfolio Multiplier: Paying the Same Energy Bill Over and Over

This is where it matters most for private equity.

Last week I described a fund where every portfolio company builds and rebuilds the same operating foundation (qualification criteria, lifecycle definitions, playbook logic) on its own. I called that a missed synergy. It's also a duplicated energy bill.

Every portfolio company without a governed Foundation is:

  • Attaching the same undefined, unverified context to thousands of prompts a day
  • Re-prompting to fix output that was never grounded
  • Running general-purpose models on tasks a smaller, scoped skill could handle
  • Doing all of this with no audit that would show the waste

Gale's warning applies here: an unoptimized query doesn't run once, it runs millions of times a day as agent activity grows. Multiply that by every company in the fund.

A portfolio-wide Context Vault flips the math. The fund defines and verifies the Foundation once, and every company inherits it. Skills run on context that's already scoped and current. The efficiency gains compound across the portfolio the same way the operating gains do.

‍

Five Questions Every Board Should Be Asking

When I ran portfolio companies for OMERS Private Equity, the discipline that kept strategy honest wasn't a policy document. It was a cadence: Hoshin Kanri, with clear objectives, owners, measures, and regular reviews where assumptions got challenged. AI efficiency needs the same treatment.

Forbes suggests boards ask vendors, "What am I actually getting per watt, not per dollar?" Good question. Here are five more for the operating side:

  1. Where does our AI get its context, and who verifies that it's current? If the answer is "whatever the user pastes in," that's where the waste starts.
  2. How many of our AI workflows are gated on verified context? Every ungated workflow can produce workslop at scale.
  3. What does a completed outcome cost us? Not a prompt: a qualified lead, a routed deal, an accurate forecast. Outcome per token is the operating version of intelligence per watt.
  4. Are we matching the tool to the job? Or are we taking the Lamborghini to the grocery store?
  5. When did we last audit for drift, and what did we find? If nobody can answer, drift is already happening. You just can't see it yet.

A board that gets clear answers is governing AI. A board that gets blank looks is funding experiments.

‍

Same Architecture, Two Returns

Last week's post ended with a binary choice: build a portfolio-wide AI operating system, or keep funding independent AI pilots.

This week adds a second reason the choice matters. The same Foundation that turns AI Users into AI Operators, and that McKinsey ties to a roughly 130% higher median revenue multiple, also cuts the tokens, power, and rework behind every AI interaction.

Efficiency and operating leverage aren't competing priorities. They come from the same three components working together:

  1. The Foundation decides what's true and relevant, so AI sends only what it needs.
  2. The Layer does defined work and refuses to fire on unverified context, so no tokens go to workslop.
  3. The Analytics shows the board where the spend goes and whether it's working.

Scrutiny is coming, from regulators, LPs, and buyers at exit. The funds that can explain their AI footprint layer by layer will have an answer. The rest will have an energy bill and a slide deck.

Ask your board which one they have.

Let's Connect → See how a portfolio-wide Context Vault makes AI both more effective and less wasteful.

Jim Delaney
Sep 28, 2026
•
7
min read