Who "Owns" AI Inside Your Company?

Do you know who owns AI inside your company? Who makes the decisions today?

Seriously. I've asked this question to a dozen CTOs in Austin over the last month. Nobody has a clean answer. And the fact that nobody has a clean answer is the actual problem.

The Participation Trophy of Enterprise AI

Let me tell you what's happening at most enterprises right now:

1. IT rolls out Microsoft Copilot because it's already in the Microsoft stack
2. Leadership sends an email — "We now have AI! Ask Copilot to help you write emails!"
3. Everyone nods and goes back to what they were doing
4. The CTO checks a box — "AI: ✅ Implemented"
5. Nothing changes

Copilot is the participation trophy of enterprise AI. You get it for showing up. And then it writes your emails — which is so 2023 it makes my teeth hurt.

Here's what the data actually says about Copilot adoption:

• Only 3% of Microsoft 365's 450 million users have adopted Copilot — 15 million paid seats after two years on the market
• When employees have access to both Copilot and ChatGPT, 76% choose ChatGPT. Only 18% choose Copilot.
• Copilot's accuracy NPS dropped from -3.5 to -24.1 in three months — and 44% of users who stopped cite "distrust of answers"
• Microsoft's own Terms of Use say Copilot is for "entertainment purposes only" and shouldn't be relied on for important decisions. This is the tool they've baked into Word, Excel, Outlook, and Teams.

Meanwhile, Anthropic shipped Claude Code, an agentic coding tool that rewrites entire codebases. Cursor lets developers orchestrate fleets of AI agents across parallel context windows. These tools are transforming how people work. Copilot is autocomplete with a marketing budget.

But enterprises pick Copilot because it's already there. Already licensed. Already approved by IT. And that's the real problem — the path of least resistance is the path of least impact.

The Org Chart Problem

So who's supposed to fix this? Who actually owns AI adoption?

I've seen six models. Every one of them has problems.

1. CEO-Driven Mandate (Shopify, Meta) The CEO says "everyone uses AI or else." Shopify's Tobi Lütke told every team: prove AI can't do the job before asking for headcount. Meta ties performance reviews to AI usage and runs leaderboards on token consumption.

• Pros: Fast, unambiguous, hard to ignore
• Cons: Can feel forced. Employees resent mandates they don't understand.

2. CTO/Engineering-Led The CTO picks the tools, runs the pilots, trains the team.

• Pros: Technical depth, right tool selection
• Cons: Siloes AI as a "tech problem." Marketing, sales, ops get left behind.

3. Chief AI Officer (CAIO) A dedicated exec who wakes up thinking about AI. 40% of Fortune 500 companies now have one. Median comp: $353K.

• Pros: Singular focus, cross-functional mandate
• Cons: Can become a political bottleneck. Another layer of bureaucracy.

4. Product-Led (Each Team Owns It) Every product team picks their own AI tools and builds their own workflows.

• Pros: Fast iteration, teams solve their own problems
• Cons: Fragmented. No standards. Shadow AI everywhere.

5. Bottom-Up / Grassroots Let enthusiasts lead. Zapier hit 97% AI adoption through hackathons and show-and-tells.

• Pros: Organic, high buy-in from practitioners
• Cons: Slow. Inconsistent. Depends on having the right people.

6. IT Department Checkbox (Most Enterprises) IT picks Copilot. Rolls it out. Sends an email. Done.

• Pros: Easy
• Cons: Useless. This is how you get a 3% adoption rate.

The Dashboard Analogy

This reminds me of dashboards. Most marketers don't hate dashboards — they just don't trust them. The numbers show what, not why. Every tool tells a different story. They're built to impress in a meeting, not to help you make a decision at 9pm when something's broken.

Copilot is the same thing. It's built to look good in a board presentation. "We've deployed AI to 50,000 seats." Great. But a corporate trainer who spent 100+ hours with Copilot said it made her workload heavier, not lighter. That's a dashboard that nobody trusts.

What I'd Actually Do

Here's my recommended model:

I. CEO sets the mandate and expectation

• "AI is how we work now. Not optional."
• No specific tool mandated — just the expectation

II. CTO owns infrastructure and tooling

• Evaluate real tools, not whatever's bundled with your Office license
• Build the guardrails, the security review process, the approval workflow

III. Start with one team. Prove ROI in 30 days. Then expand.

• Don't boil the ocean
• Pick your most frustrated team — the one drowning in manual work
• Give them real tools (not Copilot), measure what changes, then roll it wider

Line-of-business leaders are now the largest decision-maker group for AI tools at 46%, surpassing both CIOs and CTOs. The people closest to the problems are choosing the solutions. That's the right instinct.

What I'm Watching

• The $500 Billion Mistake: Why No One Is Using Copilot — Brutal takedown of Copilot's adoption numbers. The data is damning.
• CIO vs. CTO vs. CDO: Who Should Own Intelligence Now? by Riviera Partners — Best breakdown of the C-suite ownership question I've found.
• Anthropic's 2026 Agentic Coding Trends Report — What real AI adoption looks like when you move past autocomplete.

What I'm Building

• Essentialist.io — This is what happens when you give AI real work instead of email autocomplete. Essentialist runs the entire outbound sales pipeline autonomously — sends campaigns, classifies replies, searches a knowledge base, drafts responses in your brand voice, and advances your CRM pipeline. No dashboard. No human babysitting. Just outcomes.
• Salesnado.com — Built on top of Essentialist. One AI agent replaces your entire SDR function — 15 capabilities, all via email. No login, no dashboard, just reply. That's the bar enterprises should be measuring against, not "it wrote me an email subject line."

The Bottom Line

The question isn't "do we have AI?" Every company has AI. You can buy it for $30/seat/month and nobody will use it.

The question is: who owns the outcome?

Not the rollout. Not the license. Not the training deck. The outcome.

When someone owns the outcome — when their name is on the line for whether AI actually changes how the company works — that's when the participation trophy turns into a competitive weapon.

At that point, you don't have an AI strategy. You have a business strategy that happens to be powered by AI. And that's the only kind that matters.