Category: Private Equity

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

    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.

  • 97% of PE-Backed Finance Teams Now Use AI — So What?

    97% of PE-Backed Finance Teams Now Use AI — So What?

    You’ve seen the headline by now. 97% of finance leaders in VC and PE-backed companies are using AI, with three-quarters reporting ROI within twelve months. Impressive, right?

    No. Not really.

    Because the question was never “are you using AI?” — it was always “what are you actually doing with it?”

    The 97% Number Is Meaningless Without Context

    Let’s be honest about what “AI adoption” means in most finance departments right now. Someone installed Copilot. An analyst is using ChatGPT to summarise board packs. The FP&A team found a plugin that formats their Excel models faster.

    That’s not transformation. That’s convenience.

    It’s the equivalent of calling yourself “digital” because you moved your filing cabinet to SharePoint in 2015. The tool changed. The thinking didn’t.

    The 97% figure tells us that AI has become table stakes — like having a laptop or knowing how to use a pivot table. It tells us nothing about whether these teams are fundamentally rethinking how finance operates.

    Copilots vs. Architecture: The Real Divide

    Here’s where the split is happening, and it’s widening fast.

    On one side, you’ve got finance teams using AI as a copilot. It sits alongside existing workflows, making them marginally faster. Summarise this report. Draft this email. Clean this data set. The human is still the bottleneck — AI just lubricates the process.

    On the other side — and this is a much smaller group — you’ve got teams building AI into the architecture of the finance function itself. Autonomous agents that monitor cash positions in real-time. Systems that don’t just flag variance but investigate it, pull the supporting data, and draft the narrative before a human ever looks at it. Governance frameworks that are designed specifically for agentic AI, not retrofitted from your SOX compliance playbook.

    The difference isn’t speed. It’s operating model.

    A copilot-enhanced finance team is still batch-oriented. They still run month-end. They still produce reports on a cadence designed around human processing time. An AI-native finance team operates continuously. The concept of “closing the books” starts to dissolve when your systems are reconciling in real-time.

    What AI-Native Finance Actually Looks Like

    I’m not theorising here. I run an AI assistant — Saul — that operates 24/7. It monitors my email, manages my calendar, tracks my investment portfolio, executes trades, scans news, and handles routine correspondence. It doesn’t wait for me to ask. It acts, escalates when needed, and learns from the outcomes.

    That’s what AI-native looks like at the individual level. Now scale that to a finance function.

    Imagine a portfolio company where the finance team’s AI agents are handling bank reconciliations autonomously, flagging only genuine exceptions. Where cash flow forecasting updates continuously based on real-time revenue data, not last month’s actuals plugged into a spreadsheet. Where the CFO’s morning briefing isn’t a deck someone spent three hours building — it’s a synthesised intelligence report generated overnight from live data sources.

    This isn’t science fiction. The technology exists today. The gap is in the willingness to let go of the old operating model.

    PE Firms Are Asking the Wrong Question

    When a PE firm conducts due diligence on a portfolio company’s finance function, the question “do you use AI?” is already obsolete. Everyone uses AI. The answer is always yes.

    The right questions are harder: What’s your AI architecture? Which workflows are fully autonomous vs. human-in-the-loop? What’s your governance model for agentic systems? How does your finance function operate differently today than it did eighteen months ago — structurally, not just faster?

    KKR has already flagged this concern — that AI capability gaps could create a meaningful split in exit outcomes. Portfolio companies that have genuinely integrated AI into their operations will command premium multiples. Those that bolted on a chatbot and called it transformation will not.

    This is the real game-changer in PE-backed finance: not whether AI exists in the business, but whether it’s load-bearing.

    The CFO Role Is Splitting in Two

    The 2026 CFO agenda looks fundamentally different depending on which side of this divide you’re on.

    One version of the CFO sees AI as a tool in the toolkit. Useful. Saves time. Makes the team more efficient. They’ll adopt it incrementally, bolt it onto existing processes, and measure success by how many hours it saves per month.

    The other version sees AI as infrastructure — as fundamental to the finance function as the ERP system or the chart of accounts. This CFO is redesigning processes around AI capabilities, not adapting AI to fit legacy processes. They’re thinking about data architecture, agent orchestration, and continuous assurance — not just “can we automate the board pack?”

    PE operating partners need to know which type of CFO they’ve got. Because the incremental adopter will deliver incremental value. The infrastructure thinker will deliver step-change capability. And in a compressed hold period, that difference matters enormously.

    The Competitive Moat Isn’t Adoption — It’s Depth

    When 97% of your peers have adopted the same technology, the technology itself is no longer a differentiator. The moat moves downstream — to depth of integration, quality of data architecture, sophistication of governance, and willingness to let AI operate autonomously within defined boundaries.

    Most finance teams are wading in the shallows. They’ve got AI, sure. But it’s supervised, constrained, and fundamentally optional — remove it tomorrow, and the function still operates the same way, just slower.

    The teams that will win are the ones where AI removal would be structural. Where the operating model has been redesigned so thoroughly that the AI isn’t an enhancement — it’s a dependency. Not because of recklessness, but because the architecture is sound, the governance is robust, and the results speak for themselves.

    97% adoption is the starting line, not the finish. The race that matters hasn’t even begun for most.