Buyer guide

Chief AI officer or head of AI: which role, and when

A chief AI officer is the executive accountable for AI across an organisation: which uses are worth funding, what risk is acceptable, how the spending is tracked and how the workforce adapts. A head of AI usually sits a level below and runs delivery: the team, the platforms, the vendors and the systems in production. You need one named executive owner before your first AI system touches customers, money or personal data, and that owner can be an existing technology, data or information chief. A separate chief AI officer earns the seat when AI decisions routinely cross functions and nobody has the authority to settle them. Until then, a head of AI, an interim leader or a retained team can carry the delivery.

Chief AI officer. The senior executive accountable for how an organisation uses AI across every function, including its strategy, risk, spending and workforce, as distinct from the head of AI who leads delivery.

Checked . The government memo, framework and guidance this page cites were read on each publisher's own site on this date. They change: the US memo applies to federal agencies, and the UK guidance is written for government bodies. Where this page summarises either, it is not legal advice.

What a chief AI officer and a head of AI each own

The titles get used loosely, so start with what each person answers for. A chief AI officer answers to the chief executive or the board for AI across the whole organisation. A head of AI answers for making it work: the team that builds, the platforms it runs on and the systems in production. One sets direction and carries the risk, and the other ships. In a smaller organisation one person does both, which is fine as long as the mandate says so.

The clearest written description of the executive job I know comes from the US government. In April 2025 the Office of Management and Budget (OMB) told every federal agency to retain or designate a Chief AI Officer, positioned highly enough to engage regularly with the agency's deputy secretary. The memo's list of duties reads like a decent job description for any large organisation: promote AI adoption through a governance and oversight process, act as senior adviser on AI to the head of the agency, keep an inventory of AI use cases, put processes in place for high-impact uses, advise on making the workforce AI-ready, advise on AI investments and support efforts to track AI spending.

Look at what is missing from that list. Nothing in it builds anything. Building is the head of AI's job, and confusing the two is how an organisation ends up with a strategist expected to ship, or an engineering leader expected to run the board's conversation about risk.

A chief AI officer, a head of AI and an existing executive given the AI mandate, compared
DimensionChief AI officerHead of AIExisting executive with the AI mandate
The question they answerWhere should AI change this organisation, and what risk will we accept to get there?How do we build, buy and run the AI systems we have agreed on?The chief AI officer's question, answered by an executive who already carries another brief.
Usually reports toThe chief executive or the boardA chief AI, technology or data officerStays where they are, with AI added to the remit
OwnsAI strategy, the register of AI uses, risk acceptance for high-impact uses, AI investment and the workforce planThe AI team, platforms and vendors, evaluation, the production systems and what they cost to runBoth, until the load says otherwise
Judged onWhether AI spending pays back across the organisation, and whether its use stays inside the agreed riskSystems shipped, adoption, quality against agreed thresholds and cost per taskThe same measures, reported to the same board
What goes wrong without oneAI decisions are made function by function, and nobody can stop a use or move budget between teamsA strategy exists and nothing ships, or every team builds its own platformNothing, until AI loses the fight for time against the rest of the brief
Fits whenAI decisions routinely cross functions and need settling at leadership levelThere is agreed work to build and run, and a team or supplier to leadAI use is early, or concentrated in one function

The third column is the one people skip. The OMB memo itself lets an agency designate an existing chief information, data or technology officer as its Chief AI Officer, provided that person has significant expertise in AI. If a government that requires the role will accept an existing executive in it, a private company does not need a new title to take AI seriously.

What government guidance asks for

Public bodies are in a different position, because some of this is written down for them. In the US, OMB memo M-25-21 (3 April 2025) requires every federal agency to have a Chief AI Officer. At the largest agencies, those covered by the Chief Financial Officers Act, the post must sit at Senior Executive Service level or an equivalent senior grade, and elsewhere at or above grade 14 of the General Schedule. Those largest agencies must also convene an AI governance board chaired at deputy secretary level or equivalent, with the Chief AI Officer as vice-chair.

UK guidance takes a different route. The government's Digital and Data Profession Capability Framework defines a chief data officer, a chief technology officer and a chief digital and information officer, and has no chief AI officer role. The AI Playbook for the UK Government does not call for one either. It asks for an AI governance board, or AI expertise on an existing board, to set principles and review and authorise uses of AI, and for a senior responsible owner who is accountable for the use of AI in each project. For a UK public body, the practical answer is usually to give the AI mandate to an existing chief, then make the board and the project owners real.

Private companies have no rule either way. The US National Institute of Standards and Technology (NIST) AI Risk Management Framework, a voluntary framework, states the principle plainly: executive leadership takes responsibility for decisions about risks associated with AI system development and deployment. Whoever holds the title, that responsibility has to sit with someone senior enough to carry it.

When you need a chief AI officer, and when you do not

I would not create a chief AI officer title to show the board that AI is being taken seriously. A title without decision rights, a budget and the authority to stop things is a spokesperson. The role earns its seat when several of these are true.

AI decisions keep crossing functions
Marketing, finance and operations each want a different tool, a different vendor and a different policy, and the disagreements end up in the chief executive's diary.
AI changes what you sell or how you are regulated
When AI is part of the product, the pricing or a regulated decision, its risk belongs at the same table as financial and legal risk.
Spending is significant and scattered
Seats, model usage and supplier fees sit in several budgets, and nobody can say what the total is or what it returns.
High-impact uses need someone to accept the risk
Uses that affect customers' money, health, rights or jobs need a named person senior enough to approve them, and to stop them.
The existing executives have no time
The chief technology or data officer owns AI decisions in principle, but the rest of the brief means they never get to them.

A head of AI is the right first hire when the strategy is broadly agreed and the gap is delivery: use cases picked, budget approved and nothing in production. That person needs a team or a supplier to lead, and an executive sponsor who already sits at the leadership table.

You need neither yet when AI use is a handful of off-the-shelf assistants run through their vendors' admin controls, or one function running one pilot. Name an executive owner, keep a register of the tools in use and put a short policy in place. Our guide to measuring AI ROI shows how to tell whether that early spending is paying back, which is the evidence a bigger role will later be justified on.

Interim and fractional options

A permanent senior hire takes time to find and to land, and the decisions do not wait for it. There are four ways to cover the gap, and they cover different halves of the job, so be clear which half you are buying.

Give an existing executive the mandate
The quickest route, and the one the US federal memo allows. It works when that person has real AI expertise and the time is protected in writing, rather than squeezed out of the rest of the brief.
An interim or fractional executive
An experienced AI leader for a few days a week or a fixed term, who sets the strategy, the register and the governance while you hire. The limit is accountability. Someone in two days a week can recommend a risk decision, but an executive you employ still has to own it, so write down which decisions the interim leader may take and which they only recommend.
A retained team for the delivery half
When the missing piece is someone to own the architecture, the vendor and model decisions and the build, a retained implementation team can hold that while your leadership holds the strategy and the risk. It does the head of AI's delivery work. It does not take the executive seat.
A fixed-scope strategy piece
When the open question is where AI should pay back and what it will take, a short fixed-scope engagement can produce the roadmap and investment case a new executive would otherwise spend their first quarter writing.

Whichever you choose, plan the exit on the first day. Interim cover with no end date becomes the operating model by default, and the permanent hire then inherits decisions nobody wrote down.

How to hire: write the mandate before the advert

The job advert is the last thing to write. Settle the mandate first, because candidates will ask about it and the good ones will walk away from a vague answer. For either role, decide who they report to, which decisions they may take alone, which budget they control, what they can stop and how the first year will be judged.

Then test for judgement. These are the questions I would ask any candidate for either role, and I would pay more attention to how specific the answers are than to the vocabulary in them. The brief below puts the mandate and the questions on one page you can send before the first interview.

Chief AI officer or head of AI role brief
Role brief: [chief AI officer / head of AI], [organisation]

1. Why now. [What has changed that makes this role necessary.]

2. Reports to. [Chief executive / board / chief technology, data or information officer.]

3. Decisions this role takes alone. [For example: approving a new AI use below a set risk tier, choosing a vendor under a spend limit.]

4. Decisions this role recommends. [For example: accepting the risk of a high-impact use, moving budget between functions.]

5. Budget. [What the role controls, and what it must ask for.]

6. What the role can stop. [Uses, pilots or purchases it may pause or end.]

7. Team and suppliers. [Who the role leads now, and who it may hire or contract.]

8. First-year measures. [Two or three numbers the role will be judged on, with today's baseline.]

Questions for candidates:
a) Tell us about an AI use you stopped or advised against. What did you recommend instead?
b) How would you build the first register of AI uses here, and what would you do about unapproved tools you find?
c) Which risk decisions would you take yourself, and which would you bring to the board?
d) How would you know by month six whether our AI spending is paying back?
e) Walk us through a vendor or platform decision you made, the options you weighed and what you would change now.
f) What would you hand over if you left after a year?

This page quotes no salaries. I could not find a primary source that publishes private-sector pay for these roles, and pay tracks the scope of the mandate more than the title. Benchmark against your own leadership team for comparable scope, or ask a search firm for current data.

Where 1AYM fits

Two of our offers map onto this decision. If nobody owns the technical side of the AI programme, our Fractional AI Implementation Team does the head of AI's delivery work while you settle the permanent structure. We own the target architecture and the vendor and model decisions, build the platform and the first production workflows alongside your engineers, and keep a dated decision log. It is retained, typically two to three days a week under one statement of work, and it is designed to end with your own team running what we built. For a large international marketing agency, we hold the lead architect role on its AI platform while the agency's own leadership sets the direction, which is the split this page argues for.

If the executive question comes first (where AI should pay back, and what it will take), the AI Opportunity & Feasibility Sprint answers it in a fixed scope, typically two to four weeks, and ends in a roadmap and an investment case that a new chief AI officer or head of AI can pick up. If you already have a scoped job, whether a small fixed-scope statement of work or a larger build, we can resource it on contract from the collective of associates who work with 1AYM, held to the same standard. If you would like to talk through who should own AI in your organisation, book the call below.

For engineers: what the AI mandate should leave in the stack

If you lead engineering, whoever holds the AI mandate should leave evidence in the systems, not only in board papers. These are the artefacts to expect within the first two quarters. Several map directly to duties in the OMB memo or the NIST framework.

A register of AI uses, as data
Every AI tool, model endpoint and agent in a versioned register with an owner, a purpose, the data it touches and a risk tier. A release check fails when a service calls a model endpoint that has no entry. It is the private-sector version of the use case inventory the OMB memo asks each Chief AI Officer to maintain.
Risk tiers with a gate
A written rule for what makes a use high-impact, and a gate in the deployment path that holds those uses until a named approver signs off. The memo asks for a process to determine and document high-impact uses, and for an independent review before the risk is accepted.
One route to the models
Model calls go through a gateway or a shared client that applies identity, logging, rate limits and data rules in one place, so a policy change is a configuration change rather than a hunt through every team's code.
Evaluation in CI
Each production AI system has a versioned test set and pass thresholds in its repository, and a change to a prompt, model or tool definition that drops a score below threshold fails the build. That is how the memo's requirement to measure and monitor performance becomes something an engineer can check.
Cost telemetry
Spend per workflow and per task, from model usage, seats and supplier invoices, on one dashboard. Tracking AI spending is on the memo's list of duties, and it is not possible without tagging at the call site.
Switch-off and incident route
Each AI capability sits behind a flag that turns it off without a deploy, with an incident route that names who decides. The NIST framework asks for roles, responsibilities and lines of communication for managing AI risk to be documented, and an incident is when they get tested.
Portability
Prompts, evaluation sets and tool definitions held in your repositories behind a thin model interface, so a vendor decision one AI leader makes can be reversed by the next.

Sources

  1. [1]Office of Management and Budget, M-25-21: Accelerating Federal Use of AI through Innovation, Governance, and Public Trust (3 April 2025), read 29 September 2026
  2. [2]NIST, Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1 (January 2023), read 29 September 2026
  3. [3]UK government, Artificial Intelligence Playbook for the UK Government (10 February 2025), read 29 September 2026
  4. [4]Government Digital and Data Profession Capability Framework, Chief data officer (last updated 29 August 2025), read 29 September 2026
  5. [5]Government Digital and Data Profession Capability Framework, Chief technology officer (last updated 29 August 2025), read 29 September 2026
  6. [6]Government Digital and Data Profession Capability Framework, Chief digital and information officer (last updated 29 August 2025), read 29 September 2026

Frequently asked questions

What is the difference between a chief AI officer and a head of AI?

A chief AI officer is an executive who answers to the chief executive or the board for AI across the organisation: strategy, risk acceptance, investment and the workforce. A head of AI leads delivery: the team, the platforms, the vendors and the production systems. In a smaller organisation one person can hold both, as long as the mandate says which decisions they take.

Does a company need a chief AI officer?

Not always. It needs one named executive who owns AI, and that can be your chief technology or chief data officer. A separate chief AI officer is worth hiring when AI decisions routinely cross functions, the spending is significant and scattered, or high-impact uses need someone senior to accept the risk.

Can our CTO or chief data officer be the chief AI officer?

Yes, if they have real AI expertise and the time to do the job. The US government's rules for federal agencies allow an existing chief information, data or technology officer to be designated Chief AI Officer, on condition that the person has significant expertise in AI.

What is a fractional chief AI officer?

An experienced AI leader engaged part-time or for a fixed term, usually to set strategy and governance while a permanent hire is found. The risk decisions still need an owner inside the organisation, so write down which decisions the fractional leader may take and which they only recommend.

Who should a head of AI report to?

To whoever owns AI at executive level: a chief AI officer where there is one, otherwise the existing chief who holds the mandate. Reporting into one business function works only if that function's priorities are the only ones AI serves.

How much does a chief AI officer cost?

This guide quotes no salary, because no primary source it could cite publishes private-sector pay for the role, and pay tracks the scope of the mandate more than the title. The cost drivers are the reporting line, the budget and team the role controls, and whether you hire permanently, bring in an interim leader or cover the delivery side with a retained team.

Do UK public bodies have to appoint a chief AI officer?

The UK guidance read for this page does not ask for one. The AI Playbook for the UK Government asks for an AI governance board, or AI expertise on an existing board, and a senior responsible owner accountable for the use of AI in each project. US federal agencies are different: OMB memo M-25-21 requires each one to have a Chief AI Officer. This is not legal advice.

Further

We build these systems for a living. See the engagement files for what that looks like in practice, or write to us if yours is the next one.

Last reviewed · 1AYM