That three-way confusion is not a temporary growing pain. It is the central fact about AI in the enterprise right now. And understanding why it exists is the key to figuring out where this actually settles.
Why a CxO in the first place?
C-suite roles do not appear by accident. Looking across how the CFO, CIO, CMO and CHRO all came into being, a pattern emerges. A function earns a permanent seat at the top table when three conditions are met: the work becomes too complex for a generalist to absorb, the cost of failure becomes high enough to demand a single accountable owner, and the activity develops a clean enough boundary to be managed as a distinct domain with its own metrics.
The most instructive case is the CMO. Marketing had real complexity and real risk. A brand crisis is genuinely costly. But it never developed a clean boundary. Marketing bleeds permanently into sales, product, and customer success. No one can agree where it starts and stops. The result: CMO tenure is the shortest in the C-suite and the title keeps getting renamed and reorganised. Two out of three conditions is not enough.
Now run AI through the same test. Complexity: obvious pass. Risk: increasingly clear pass, as regulators attach accountability to executive leadership and the cost of AI failures becomes material. Coherence: this is where the wheels come off.
AI is not one bounded thing. It is simultaneously infrastructure, data strategy, process redesign, workforce transformation, customer experience, and strategic advantage. Every function has a legitimate claim on some part of it. That is why three executives in the same company can each be convinced AI belongs to them, and none of them is entirely wrong. It is also why, just like marketing, a dedicated AI role struggles to develop the clean mandate that durable C-suite positions require.
Why Each Contender Falls Short
The CTO has the most intuitive claim. AI is a technology, the CTO owns technology, case closed. Except the CTO's domain has always been defined by a specific boundary: infrastructure, systems, uptime, security. Things that keep the business running. AI does not respect that boundary. It rewrites how finance makes decisions, how HR evaluates talent, how operations manages supply chains, how sales forecasts revenue. A technology that reorganises every function in the business is not an infrastructure problem. The CTO is the right person to build the engine. Deciding where the car goes is a different job.
The CHRO has a claim that is real but time-limited. AI is unquestionably the most significant workforce disruption in a generation. Reskilling, role redesign, managing the human side of automation: these are genuine CHRO responsibilities and no one should understate them. But they describe a transition, not a permanent ownership model. Once the workforce has been reshaped, the CHRO's specific claim on AI dissolves. You would not ask the CHRO to permanently own the internet because it transformed how people worked in the 1990s. Owning the disruption is not the same as owning the asset.
The CAIO looks like the obvious answer until you ask a simple structural question: what does this role actually own? Every durable C-suite position owns either an asset class or a risk class. The CFO owns capital. The CTO owns systems. The CHRO owns the workforce. The CISO owns security risk. The CAIO owns a method. AI is a type of technology, not an asset class and not a risk category. You would not create a permanent Chief Cloud Officer or a Chief Analytics Officer. CAIO is the same category of thinking, made more compelling only because the technology is more dramatic. The job descriptions confirm the structural weakness: they read as liaison briefs. Partner with, coordinate with, support. That is not the language of ownership.
Who Wins and How It Settles
When something starts behaving like capital, it migrates to whoever owns capital allocation. The data, fine-tuning, and institutional knowledge a company layers on top of a base model is proprietary, it compounds over time, and a competitor cannot simply buy the same thing off the shelf. That is not infrastructure and it is not a workforce programme. It is an asset, and assets raise questions that are already the CFO's territory:
• What are we investing, and what are we getting back?
• Is this building durable value, or a recurring cost dressed up as capability?
• What is our exposure if we become dependent on one vendor or one model?
CFOs know this. CFO involvement in AI strategy has grown faster than any other function over the past two years. They did not wait to be invited. They followed the capital, as they always do.
Having said this, the most likely outcome in the short run is AI governance staying distributed across CTO, CDO, and CHRO, coordinated through standing committees, with the CFO holding real decision-making authority over investment, returns, and risk. The CAIO title will survive where regulators or boards want a named individual accountable for AI risk, for the same reason the CISO survived: when the risk is sharp enough, accountability needs a name on the door. But as strategic owner of AI as a firm-wide asset, that is not what the CAIO job description describes, and there is no structural reason to expect it will.
But once the dust settles, the answer, is probably not the one with "AI" in their job title. My bet is that it’ll be the CFO.
