CEOInterviews.AI
Start App
Aaron Levie
Co-Founder, Chief Executive Officer & Director, BOX INC

Why Enterprise AI Adoption Is Slower Than You Think — Aaron Levie (Box) + Harrison Chase

📅 Jun 29, 2026 LangChain 31 MIN 2513 VIEWS 40 SEGMENTS · 2 SPEAKERS
Aaron Levie, CEO of Box, sits down with Harrison Chase, co-founder and CEO of LangChain, to dig into why AI agents are thriving in software development but still struggling to break through in the rest of the enterprise. Aaron breaks down the structural reasons the knowledge work gap exists, how Box is building its agent harness, and why being headless might actually drive more usage than it kills. Chapters: 0:00 Why Aaron tweets so much (and never uses AI to do it) 1:58 Box's core mission: bridging tech breakthroughs to the enterprise 3:28 Coding agents vs. knowledge work agents — why the ga...

What Aaron Levie said

Written from the verified transcript and checked against it. Every figure links to the moment it was said.

Aaron Levie discussed the slower-than-expected adoption of enterprise AI, attributing it to the need for a bridge between model progress and practical use cases. He argued that AI coding agents succeed because code is verifiable and users are technical, but knowledge work lacks these properties, leading to a multi-year diffusion period. At Box, he described how Box Agent leverages a decade-old architecture with canonical file storage and governance, evolving search for agent consumption and converting content to markdown. He emphasized a headless strategy, indifferent to whether customers use Box's interface or external agents via MCP, citing Salesforce's API exposure as symbolic. Levie predicted cost will become a major story, forcing model mixtures, and noted that agents will always excel at code, making code harnesses a foundation for other tasks.

Key takeaways

  1. Box Agent is designed to be an expert at enterprise content, plugging into broader agents via MCP like Harvey or Claude.
  2. Levie is indifferent to whether customers use Box's interface or headless APIs, predicting usage may be mostly headless.
  3. Cost will become a big story in the next 3 years, forcing enterprises to mix models and use dedicated harnesses for high-value workflows.
  4. Agents will always be better at code than other tasks, so code harnesses should be adapted for non-coding work.

Numbers and commitments

FigureWhat it refers toTypeAt
100x increase in search results consumed by agents metric 12:54
3 years timeframe for cost to become a major factor in AI timeline 24:25
$10 million additional AI spending that enterprises with EPS targets cannot suddenly incur commitment 28:39

Chapters

  1. 0:00Tweeting and AI use
  2. 2:10Enterprise AI adoption challenges
  3. 10:58Box Agent and content expertise
  4. 15:21Headless strategy and customer choice
  5. 20:14Coding agents as a foundation
  6. 24:25Model selection and cost pressures
  7. 28:09Token budgets and enterprise constraints
  8. 30:38Closing thoughts on AI's future

Questions asked in this interview

11
  1. 0:23You're a prolific tweeter. How do you do it?
  2. 1:42Do you use AI for your tweets at all?
  3. 2:10What advice would you have for enterprises who are thinking about this?
  4. 5:22Yeah, on that, what is the answer to that question? What is working?
  5. 10:58How are you thinking about bridging the gap?
  6. 12:48Have you seen that it's changed because of agents?
  7. 15:11As you think about company strategy, do you have a strong opinion on how much you want people to consume AI in the Box AI interface versus via MCP?
  8. 20:14How much do you look at coding agent harnesses for inspiration, and how similar do you think they'll end up being?
  9. 24:14Do you use multiple models in one agent run?
  10. 28:09Are you seeing that at Box?
  11. 30:25One last quick question: can you give us a sneak preview of your next tweet? What's top of mind?
Interviewer 0:06 ↗
Hello. Thank you so much for being here.
Aaron Levie 0:08 ↗
Thank you. I think my last time I was in this building, it was like a rave. Has anybody been to an EDM show here before? Raise your hand. Okay, we have a couple. Yeah, we probably were the same one.
We were talking about that before. I think a lot of folks on our team have been here mostly for that.
Interviewer 0:23 ↗
I was like, this is a very familiar venue. So, okay. I was doing some research on you before, looking at your tweets. You're a prolific tweeter. How do you do it?
Aaron Levie 0:34 ↗
It's funny. Prolific tweeter is sort of a backhanded compliment.
Interviewer 0:39 ↗
No, it's a full on compliment.
Aaron Levie 0:40 ↗
Okay. It's like, do you want to be a prolific tweeter? I don't know. I basically just tweet what we're running into at Box and what we're seeing when we're building agents and working in AI, what I'm hearing from customers and the market, and whatever is in the zeitgeist that resonates. So it's a very boring framework: a couple times a day, whatever I think is happening in the world.
Interviewer 1:10 ↗
A couple times a day, but it's a bunch of paragraphs and it's all spot on, very in tune with what's going on in the ecosystem. I'm in awe.
Aaron Levie 1:18 ↗
Thank you. I think most people know how to write, so you can all try this at home. Just try and type a couple paragraphs and see what happens. It's funny because I got a C++ probably in English in high school, but everybody thinks I write a lot. I was like, you could either write an email or write a tweet, so might as well write a tweet.
Interviewer 1:42 ↗
Do you use AI for your tweets at all? Okay. All right. Well, I think you're definitely one of the most knowledgeable.
Aaron Levie 1:47 ↗
Some of my tweets make it very obvious because I'll look at it later and be like, 'Oh my god, there's up to nine mistakes in this tweet between grammar and spelling.' So it's definitely proof of human work.
Interviewer 2:01 ↗
Yeah, you almost have to add that in on purpose so people know it's not AI.
Aaron Levie 2:04 ↗
Yep. In this case it happens fully organically.
Interviewer 2:10 ↗
I think you're one of the smartest people in terms of what it takes for enterprises to actually adopt AI. I imagine this is because you work with a number of them daily. What advice would you have for enterprises who are thinking about this?
Aaron Levie 2:26 ↗
Yeah. I'm super lucky because since the founding of the company, we get to be in the tech industry in Silicon Valley, seeing the breakthroughs in AI. But to translate that to a regular knowledge worker or enterprise, there has to be a bridge: simple interfaces, usable by end users, packaging infrastructure for use cases. AI is the same: incredible model progress, but most enterprises need a bridge to access it in a way relevant to their use cases. I spend a lot of time with large enterprises and see them adopt AI. The big question is whether we can get the same gains in knowledge work as we see in AI coding. We all use agents for coding, but the rest of knowledge work in marketing, sales, finance, etc. is the challenge. The main question on every enterprise's mind is when and how to deploy full agentic workflows across knowledge work.
Interviewer 5:22 ↗
Yeah, on that, what is the answer to that question? What is working?
Aaron Levie 5:25 ↗
I purposely left it rhetorical because we're figuring it out. The tricky thing is that AI coding agents have every great property: models hyper-trained on code, work is verifiable, users are hyper-technical. But in knowledge work, the work is not as verifiable, users are not as technical, and they don't have access to all the data. Agents inherit those same limitations. So the gap is how to bridge that. We're seeing highly domain-specific agent startups emerge, and enterprises themselves can build internal agents. We're in for many years of diffusion, and the doomers are wrong about takeoff because of the slow rate of diffusion into organizations.
Interviewer 10:58 ↗
How are you guys at Box thinking of tackling that with Box Agent? It seems horizontal, but you're building on a solid data layer. How are you thinking about bridging the gap?
Aaron Levie 11:12 ↗
We're in a quasi-interesting territory because we're horizontal. Our domain understanding is enterprise content at a horizontal level: file systems, how agents work with content, creating a pipeline to make data ready for agents in a secure, well-governed way. We have a document conversion pipeline, security and access controls. Box Agent's job is to be an expert at working with enterprise content, and it needs context of the workflow. It can plug into broader agents via MCP, like Harvey or Claude for legal, taking on domain-specific understanding.

18 more exchanges in this transcript

Sign in free to read the rest of this interview. No card required.

Sign in to read the full transcript

Cite this transcript

APA, MLA, BibTeX
APA

Levie, A. (2026, June 29). Why Enterprise AI Adoption Is Slower Than You Think — Aaron Levie (Box) + Harrison Chase [Interview transcript]. LangChain. CEOInterviews.AI. https://ceointerviews.ai/interview/1051844/

MLA

Aaron Levie. "Why Enterprise AI Adoption Is Slower Than You Think — Aaron Levie (Box) + Harrison Chase." LangChain, 29 Jun. 2026. Transcript, CEOInterviews.AI, https://ceointerviews.ai/interview/1051844/.

BibTeX
@misc{levie2026_1051844,
  author       = {Aaron Levie},
  title        = {Why Enterprise AI Adoption Is Slower Than You Think — Aaron Levie (Box) + Harrison Chase},
  howpublished = {Interview transcript, LangChain. CEOInterviews.AI},
  year         = {2026},
  month        = {jun},
  url          = {https://ceointerviews.ai/interview/1051844/},
  note         = {Speaker-attributed transcript with timestamps}
}