Slide 01

Your CFO Is Not Qualified to Evaluate AI Tools. Neither Is Procurement.

CxO + Board

Core claim

AI changes the work itself. Running that decision through a procurement process designed for printers is not a strategy — it is a delay with extra steps.

Your CFO is good at their job. This is not an attack on finance. The problem is not that finance and procurement are involved. The problem is that in many companies they are effectively making AI decisions. And they are not qualified to do that. Not because they are not smart. Because they have not done the work of understanding what AI actually changes inside a business.

The distinction AI changes what people are capable of, how many people you need, which functions can be automated, and which processes can be eliminated. That is not a purchasing decision. That is an operating decision.

Slide 02

You Are Running Your AI Strategy Through the Same Process as a Printer Request

Market signal

What a printer does IT ticket

Someone files a ticket. IT plugs it in. Everyone moves on. A printer does not change how your analysts think or what your engineering organization is capable of delivering next quarter.

What AI actually does Restructures

AI determines whether your engineering organization ships in two weeks or two months. It changes what your customer service team can handle. It changes which roles you need and at what ratio.

How most orgs decide Same process

Cost, vendor risk, contract terms, budget line item. Evaluated by finance. Approved or rejected. A transformative operating decision made through a framework built for office equipment.

A printer does not restructure what your customer service team is capable of. A printer does not determine whether your engineering organization ships in two weeks or two months. AI does all of those things.

The printer analogy exposes the governance gap

Slide 03

Benjamin Franklin Would Not Evaluate Boeing vs. Airbus. Your CFO Cannot Evaluate AI.

Domain knowledge gap

The analogy

Franklin was brilliant. You would not ask him to choose between Boeing and Airbus for your commercial fleet. His intelligence is not the issue. His domain knowledge is.

Your CFO understands capital, risk, contracts, cash flow, and budget cycles. Real skills. But evaluating what an AI coding assistant does to engineering velocity — or which large language model handles regulatory text well enough to trust in a compliance workflow — is a different kind of knowledge. And your CFO does not have it. Neither does your procurement team.

Not a criticism Your CFO does not have this knowledge because the field barely existed two years ago. That is not a failure. It is a condition. Pretending otherwise is the failure.

What domain knowledge actually requires

Knowing whether an agent framework will integrate with your existing systems — or just demo well. Understanding which models handle your codebase patterns versus which ones fail on your specific edge cases.

Recognizing that two tools with almost identical feature lists on a vendor comparison spreadsheet can produce wildly different results for your team, your architecture, your workflows. The only way to know is to have done the work.

Resolution Bring in people who understand aviation and let Franklin manage the economics. Finance controls the money. Engineering controls the evaluation. In that sequence.

Slide 04

Change the Sequence. Not the Authority.

The fix

Current sequence (broken)

Finance and procurement evaluate the tool first — cost, vendor size, contract terms, risk profile.
The field narrows before the people who understand the work ever see it.
Engineering gets invited to comment on a decision that has already been mostly made.
An operating decision gets made through a commercial evaluation framework.

Correct sequence

Engineering evaluates first. They know what the work requires, what the codebase demands, what integration will actually cost.
They narrow the field to two or three options with operating rationale.
Finance evaluates the commercial terms on the short list. Negotiates. Controls the budget.
An operating decision gets made with operating knowledge. A commercial decision gets made with commercial knowledge.

Slide 05

AI Changes the Work Itself. That Is Why This Decision Is Different From Every Tool Before It.

Operating implications

People

What people can do changes

Not just faster. Different. A developer with the right AI tooling can carry the cognitive load of three without it. That changes headcount planning, compensation strategy, and what a senior engineer's time is worth per dollar of salary.

Functions

Which functions can be automated changes

Not which tasks within a function. Which entire functions. Customer service triage. Compliance review. First-pass code review. Documentation. The list is growing every quarter. Your headcount planning model should be recalibrated annually, not every five years.

Roles

Which roles become more valuable changes

The $20-per-seat tool that makes junior developers 40% faster does not have the same value as the $60-per-seat tool that makes your senior architects 2x more leveraged. The right answer depends on your specific engineering bottleneck — which is an operating question.

Slide 06

Who Is Actually Making Your AI Decisions Right Now?

Decision close

The leadership audit

In your last AI tool decision, who evaluated first — the people who understand the work, or the people who manage the budget?

If the answer is finance or procurement, you do not have an AI strategy. You have a procurement process that occasionally approves AI tools. The distinction matters because the wrong evaluator, in the wrong sequence, produces consistently wrong outcomes — tools that demo well but never change what your people can actually do.

This is not about giving engineering unlimited budget. It is about giving engineering the authority to narrow the field before finance evaluates what is on it.