ctaio.dev Ask AI Subscribe free

The Emerging C-Suite / CADTO

Chief AI, Data & Technology Officer (CADTO)

The converged role that merges CTO, CAIO, and CDO

The Chief AI, Data, and Technology Officer is the newest seat in the emerging C-suite — and the broadest. It folds three previously separate mandates into one because AI made them impossible to own apart.

Direct answer

A Chief AI, Data, and Technology Officer (CADTO) is a single executive who owns AI strategy, the enterprise data foundation, and technology operations — the combined mandate of a CTO, a Chief AI Officer, and a Chief Data Officer. The role exists because generative AI made those three jobs inseparable: you cannot govern AI without owning the data it learns from and the platform it runs on. The unifying asset is one governed view of the customer.

The role, defined

The CADTO is what happens when three of the emerging C-suite roles stop being separable. The CTO owns the platform, the Chief AI Officer owns the intelligence, and the Chief Data Officer owns the data that intelligence learns from. For most of the last decade those were three distinct jobs with negotiated borders. Generative AI erased the borders: a single model-deployment decision is at once a platform call, a governance call, and a data call, so no one of the three executives can make it alone.

The mechanism that creates the role is the same one that created every converged title before it. When a single decision spans three mandates and no one person is accountable for it, the decision stalls — and eventually the org chart is redrawn to put one name on it. The CADTO is that name. It usually extends one step further into the digital products and platforms built on the stack, because that is where the AI, the data, and the technology either compound into something customers value or expose the seams between three teams.

What a CADTO owns

AI innovation & strategy

The enterprise AI roadmap and which use cases get built; moving generative AI from pilots into production; owning the responsible-AI posture so "we use AI" is governed, not a press release.

The data foundation

A governed, unified view of the customer — the single record AI personalization and analytics depend on. The load-bearing wall; everything else leans on it.

Technology & operations

Infrastructure, cloud, enterprise applications (CRM, ERP, HRIS), security, and the systems that simply have to work — often in real time, in front of customers.

Digital products

The apps, sites, commerce, and experiences customers touch — each one a place the AI, data, and platform either compound or expose the gaps between teams.

Where the CADTO sits

Reports toCEO, COO, or CFO (AI-governance portion sometimes split out to an independent line in regulated firms)
OwnsAI strategy & governance, the enterprise data foundation, technology operations, and the digital products built on top
The unifying assetOne governed view of the customer — every model, experience, and analytics decision draws from it
Does not always ownAI risk governance in regulated industries, which often reports independently of the build function
Closest peersCAIO, CDO, Chief Digital Officer, CISO

When to converge into one CADTO

Convergence makes sense

  • The business runs on customer data at scale — multiple brands or channels describing the same underlying customer
  • AI is a value lever across the portfolio, not a single feature, and every use case wants the same data and governance
  • Three executives keep negotiating the same model, vendor, and deployment decisions instead of making them
  • Speed of execution matters more than functional depth in any one of the three areas

Keep the roles separate

  • One competent CTO already absorbs AI and data without strain — the title would just be longer
  • You are in a regulated industry where AI governance must report independently of the build function
  • Any one of AI, data, or platform is deep enough to be a full-time executive job on its own
  • The title would be a signal, not a mandate — no budget, no authority to say no across all three areas

Frequently Asked Questions

What is a Chief AI, Data, and Technology Officer (CADTO)?
A Chief AI, Data, and Technology Officer (CADTO) is a single executive who owns AI strategy, the enterprise data foundation, and technology operations — the combined mandate of a CTO, a Chief AI Officer (CAIO), and a Chief Data Officer (CDO). The role exists because generative AI made those three functions inseparable: governing AI requires owning both the data it learns from and the platform it runs on. In most versions it also covers the digital products built on that stack.
How is a CADTO different from a CTO?
A CTO owns the engineering platform and how systems are built and operated. A CADTO owns that plus the AI strategy and governance and the enterprise data foundation. The practical difference is the customer data layer: a CADTO is accountable for the single governed view of the customer that AI, analytics, and personalization all draw from, while a traditional CTO treats data as something the systems happen to store. A CTO given an explicit, enforced AI-and-data mandate is effectively running as a CADTO.
Why is the AI, data, and technology role converging into one seat?
Because AI collapsed the boundaries between the three mandates. A single decision — which model a customer-facing product should use — is simultaneously a platform decision, a governance decision, and a data decision. Split across three peer executives, it gets negotiated rather than made. Merging the seats removes the border dispute and the deployment-decision turf war that stalls AI programs in organizations that keep the roles separate.
Who does a CADTO report to?
Most commonly the CEO, COO, or CFO, and the reporting line signals the mandate. Reporting to the CEO or COO usually means a transformation-and-growth mandate with board visibility; reporting to the CFO often means the role is framed around cost, ROI accountability, and operational control of the technology P&L. In regulated industries the AI-governance portion is sometimes pulled out and given an independent line so the function that builds models is not the sole voice governing their risk.
When should a company NOT merge these roles into one CADTO?
Two cases. First, when the company is small enough that one competent CTO already covers AI and data without strain — a converged title there is relabeling, not org design. Second, in heavily regulated industries (financial services, healthcare, defence) where AI governance must report independently of the team that builds the models. There, regulators expect structural separation, which pulls the AI mandate back out of the combined seat. Convergence is an efficiency argument; governance independence is a safety argument, and safety wins.
Is the CADTO a permanent role or a transitional title?
Unknown. It may be the stable name for AI-era technology leadership, or a transitional title that lasts only until owning AI, data, and platform together is simply assumed to be the CTO job and the name collapses back. The Chief Digital Officer followed that arc — it peaked, then dissolved as "digital" became everyone's responsibility. The CADTO may consolidate the same way once AI stops being treated as a separate thing to govern.
·
Thomas Prommer
Thomas Prommer Technology Executive — CTO/CIO/CTAIO

These salary reports are built on firsthand hiring experience across 20+ years of engineering leadership (adidas, $9B platform, 500+ engineers) and a proprietary network of 200+ executive recruiters and headhunters who share placement data with us directly. As a top-1% expert on institutional investor networks, I've conducted 200+ technical due diligence consultations for PE/VC firms including Blackstone, Bain Capital, and Berenberg — work that requires current, accurate compensation benchmarks across every seniority level. Our team cross-references recruiter data with BLS statistics, job board salary disclosures, and executive compensation surveys to produce ranges you can actually negotiate with.

Designing your AI, data & technology leadership?

The newsletter covers how these roles actually divide responsibility — when to merge AI, data, and platform into one seat, and when to keep them apart.