Who "Owns" AI Inside Your Company?

I own AI at my company. I'm the CTO. When someone asks "who's in charge of AI at Q1Media?" — the answer is me. My name is on it.

And I can tell you from experience: most companies don't have that answer. I've asked this question to a dozen CTOs in Austin over the last month. Nobody has a clean response. And the fact that nobody has a clean answer is the actual problem.

The Participation Trophy of Enterprise AI

Here's 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 says:

• Only 3% of Microsoft 365's 450 million users have adopted Copilot — 15 million paid seats after two years
• When employees have access to both Copilot and ChatGPT, 76% choose ChatGPT. Only 18% pick Copilot.
• Copilot's accuracy NPS dropped from -3.5 to -24.1 in three months — 44% of users who stopped cite "distrust of answers"
• Microsoft's own Terms of Use say Copilot is for "entertainment purposes only". This is the tool 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. The path of least resistance is the path of least impact.

The Org Chart Problem

So who's supposed to fix this? 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.

• 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
• 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 3% adoption.

What I Actually Did

I'll tell you what I chose: a blend of #1 and #2. I set the mandate and I picked the tools. But the mandate wasn't "use AI." The mandate was: stop doing the work AI can do.

I told my 10 developers to stop writing code. I didn't fire anyone. I promoted them — to architects, product owners, micro-CTOs. The agents write the code now. The humans think, review, and decide. That's a fundamentally different posture than "hey, Copilot can help you draft an email."

The difference? I didn't hand them a participation trophy and walk away. I put my own name on the outcome. If AI adoption fails at Q1Media, that's my failure. Not IT's. Not some CAIO I hired to own it for me.

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 — but someone still has to own the outcome.

What I'd Recommend

I. CEO sets the expectation. "AI is how we work now. Not optional." No specific tool mandated — just the direction.

II. CTO owns infrastructure and tooling. Evaluate real tools, not whatever's bundled with your Office license. Build guardrails, security review, 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.

The companies that win this aren't the ones with the most AI seats. They're the ones where someone's name is on the line.

What I'm Watching

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

What I'm Building

• Essentialist.io — This is what happens when you give AI real work instead of email autocomplete. Essentialist runs entire outbound pipelines autonomously — campaigns, replies, knowledge base, CRM advancement. No dashboard. No babysitting. Just outcomes.
• Salesnado.com — One AI agent replaces your entire SDR function — 15 capabilities, all via email. No login, no dashboard, just reply.

What My Team Is Building

Remember those 10 developers I promoted to micro-CTOs? Here's what they shipped in the last two months using Claude Code:

• The BDR App — Sits between our main Console and multiple CRM enrichment APIs and databases. It's the bridge between our ad tech operating system and every data source our business development team needs. No more alt-tabbing between six tools.
• The Q1 Brain — An organizational second brain that goes way beyond anything SharePoint or Google Drive could imagine. Institutional knowledge that's actually searchable, connected, and useful — not buried in a folder hierarchy nobody maintains.
• The Events App — Helps marketing and account executives calculate the precise ROI of trade shows and market events. Not a guess. Not a vibes-based recap. Actual numbers tied to pipeline.

Three real applications. Two months. Built by a team that used to spend their days writing CRUD endpoints. That's what happens when you stop handing out participation trophies and start giving people real tools.

The Bottom Line

Every company has AI. You can buy it for $30/seat/month and nobody will use it.

The question isn't "do we have AI?" The question is: who owns the outcome?

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

When someone's 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. That's when you stop having an AI strategy and start having a business strategy that happens to be powered by AI.

And that's the only kind that matters.