AI is moving faster than most boards can govern it. This is a working point of view — and a working library — for finance leaders, audit committees, and directors who need a defensible answer before the question arrives.
The capital side of AI — and the side software-trained CFOs underweight.
The operating side — where finance owns visibility, controls, and the board narrative.
Two decades of software-led growth taught CFOs to optimise the bits: subscriptions, cohorts, gross margin, payback. AI quietly drags the balance sheet back toward the atoms — capital commitments, supply, energy, and physical risk.
That doesn't change what the CFO is responsible for. It changes what the CFO needs to be fluent in: capital allocation under uncertainty, control design around non-deterministic systems, and a board narrative that holds up to an audit committee.
The next decade of finance leadership belongs to CFOs who can hold capital discipline and AI fluency in the same hand — and translate both into something a board can sign.
Every AI tool touching the close, the forecast, or the reporting pack needs an owner, a control, and a paper trail.
Directors need a written policy, a stated risk appetite, and a reporting cadence — not vendor demos.
Compute is a capital commitment. Build / buy / lease, scenario planning, and unit economics belong on the CFO desk.
Adoption without controls is the most expensive path. The fastest finance teams build both at the same time.
Twelve questions, three pillars, one honest score. Directional, not a certification — answers stay in your browser.
This is a directional self-assessment to start a conversation, not a certification or an audit. Your answers stay in your browser.
A working toolkit, built out one piece at a time. Tags show what's live and what's on the way — nothing here pretends to be finished before it is.
Why the AI era is pulling the finance seat back toward atoms — and what software-trained CFOs need to relearn.
The control points to put around any AI touching your month-end, forecast, or reporting workflow.
A starting-point policy and risk-appetite statement, written to survive a committee review.
How to frame compute and infrastructure as a capital commitment — build, buy, or lease — instead of a cloud bill.
A single-page board reporting pack that gives directors a defensible line of sight on AI risk and spend.
A structure for cataloguing every AI model and tool in finance, with owners, controls, and review dates.
Fractional CFO engagements, board and audit-committee advisory, and AI-governance reviews for finance teams that need a defensible answer before the question comes from the board.