The CFO Who Can’t Measure AI Is About to Become the CFO Who Can’t Raise

When a $60 billion AI coding platform starts a CFO council, the signal is not subtle.

Cursor — the AI coding company SpaceX has agreed to buy — just launched a working group of finance leaders to answer one question: how do you keep AI spend tied to value? That is not a product marketing stunt. It is the market admitting that “return on intelligence” has left the innovation lab and landed on the CFO’s desk.

And if you are a PE-facing CFO who still treats AI as an IT experiment with a cute pilot budget, you are already late.

The board is no longer asking “are we using AI?”

They are asking the harder question: what is the return?

Cursor’s own framing is blunt. AI spend is shifting from experimental pilots into a major recurring operating expense. McKinsey’s numbers make the gap obvious: most organisations have deployed AI somewhere, but only a minority can trace it to enterprise-level EBIT impact. That is the CFO’s problem in one sentence — high adoption, weak attribution.

BCG’s token-cost work is even more direct: token costs are attracting CEO and board-level attention, and CFOs need answers when those questions start. This is no longer “can the model write a draft email?” It is “why did our model bill triple, and what operating leverage did we buy with it?”

Boards do not fund vibes forever. They fund measurable capacity.

Why PE will force this earlier than corporate

In private equity, the conversation compresses.

LPs want cleaner, faster, more machine-readable portfolio data. Operating partners want cycle-time compression, not another slide deck about “AI enablement.” And portfolio company CFOs are being asked, often mid-hold period, to show that AI is either:

• cutting cost-to-serve,
• shortening close / reporting cycles,
• improving cash conversion, or
• raising the quality of decisions under pressure.

If your answer is “we’re experimenting,” you sound ornamental. In a PE board pack, ornamental dies quietly.

The firms that win will treat AI less like a side project and more like a capital allocation problem: what is the unit cost of intelligence, where does it create EBITDA, and what do we stop funding if it doesn’t?

Return on intelligence is a finance discipline, not a tech slogan

Cursor’s council is aiming at the right missing layer: shared benchmarks for AI productivity, frameworks for measuring returns, and practical approaches to model allocation and cost management. That is classic CFO work dressed in new language.

The practical version looks like this:

• Define the unit of work. Not “AI usage.” Actual output: closed tickets, reviewed contracts, reconciled exceptions, forecast cycles, board packs produced, cash applications cleared.
• Measure cost per accepted unit. Tokens are inputs. Accepted work is the output. If you only track spend, you are budgeting a furnace, not a factory.
• Separate leverage from theatre. A tiny cohort of power users often creates most of the value. That concentration is a management problem, not a model problem.
• Route work deliberately. Cheap models for routine extraction. Stronger models for high-stakes judgement. Unrouted “everyone uses the top model” is how token bills become board items.
• Put AI in the operating rhythm. If it only lives in a pilot Slack channel, it will never show up in free cash flow.

This is not anti-AI. It is anti-unmeasured AI.

The CFO who can’t measure AI will struggle to raise

In PE, capital is allocated on credibility. Credibility is the ability to explain what changed the numbers.

So when a sponsor asks “what did AI do for this business?”, the weak answer is activity:

• we rolled out copilots,
• we ran workshops,
• we have 40 use cases in the backlog.

The strong answer is economic:

• close cycle down from X to Y days,
• cost per invoice exception down Z%,
• forecast reforecast latency cut by half,
• gross margin lift from better pricing/support triage,
• token cost per accepted unit of work under control and declining.

One of those lists gets you the next round of investment. The other gets you a polite nod and a smaller mandate.

That is the real risk. Not that AI fails. That AI succeeds somewhere in the organisation while finance still cannot price, govern, or defend it. In that world, the CIO owns the tools and the CFO owns the blame when the bill arrives.

What good looks like in a portfolio company

If I were walking into a PE-backed finance function this quarter, I would not start with a model beauty contest. I would start with four controls:

1. AI P&L visibility. Token/API cost by team, workflow, and vendor. No more “software misc.”
2. Value hypotheses per workflow. Before scale-up: baseline metric, expected delta, owner, kill criteria.
3. Routing rules. Which work gets which model, and who can override.
4. Board language. One page: spend, output, unit economics, risks, next capital ask.

That is enough to turn “we use AI” into “we run intelligence as an operating system with a cost of capital.”

And yes — some initiatives will fail. Good. Failed experiments with clear kill criteria are cheaper than indefinite pilots with no owner.

The quiet transfer of power

For a decade, finance absorbed digital transformation after the fact: clean up the data, explain the variance, retrofit the controls. AI is different because the spend line is rising fast enough, and uneven enough, that boards will not wait for a post-implementation review.

Cursor building a CFO council is confirmation, not novelty. The frontier companies already know the bottleneck is no longer model capability. It is economic discipline.

So the question for CFOs — especially those in PE-backed businesses — is no longer whether AI belongs in the stack. It is whether you can sit in a board meeting and defend the return on intelligence without hand-waving.

If you can’t, someone else will. And they will own the budget that used to be yours.

Mark Hendy is a PE-facing CFO who works through Tanous. He writes about finance leadership where AI, capital allocation, and operating reality collide.