Teahose.
SIGN IN
NEW HERE — WHAT TEAHOSE DOES
We read the entire AI & tech firehose — so you don't have to.
PODPodcastsAll-In, No Priors, Acquired…
NEWNewslettersStratechery, Newcomer…
PAPPapersPhysical AI research
PHProduct Huntdaily launches
VCInvestor ScoutSequoia, a16z, Benchmark…
CLAUDE DISTILLS →
7 reads, 30 sec each — free, 6 AM ET.
+ a live graph of the companies, people & themes underneath.
HOME/THE A16Z SHOW/AI Inside the Enterprise
POD
// EPISODE
THE A16Z SHOW

AI Inside the Enterprise

DATE April 24, 2026SOURCE THE A16Z SHOWPARTICIPANTS A16Z ANNOUNCER, AARON LEVIE, ERIK TORENBERG, MARTIN CASADO, STEVEN SINOFSKY
// KEY TAKEAWAYS3 ITEMS
  1. 01The Valley-to-Enterprise Gap Is a Workflow and Technology Divide, Not a Communication Problem
  2. 02AI Should Be Treated as a User, Not as Software
  3. 03The Integration Wall Is the Defining Obstacle, and AI Doesn't Solve It

1. Key Themes

The Valley-to-Enterprise Gap Is a Workflow and Technology Divide, Not a Communication Problem

The gap between Silicon Valley's AI adoption and enterprise deployment isn't ideological — it's structural. Engineers benefit from verifiable work (code), high technical aptitude, and the ability to self-debug, which creates artificial optimism about how fast AI can diffuse into less-structured environments.

"The gap is caused by the styles of work that exist in Silicon Valley and in engineering roles versus sort of the rest of the world... The technical aptitude of an engineer is just like insanely high... and then, obviously, you have all the benefits of just the models are really good at code and the work is verifiable." — Aaron Levie 00:04:13

"It's not even that we're like talking past each other like in one of those kind of classic like government versus industry. It's just literally like there is just a pure workflow and technology set divide." — Aaron Levie 00:04:40


AI Should Be Treated as a User, Not as Software — And This Reframes Everything

The most important architectural and organizational shift underway is treating AI agents like human employees rather than software integrations. This means drafting on the existing access control, onboarding, permissions, and workflow infrastructure built for people.

"Instead of viewing AI as software, like just view it as a user... take your product, make it a CLI tool, and then have the AI be an agent that actually uses this... This is a very, very significant architectural and mental shift." — Martin Casado 00:10:43

"If you have the mindset that an agent is more like a human and you hire the agent, you give it its own email address, it can access documents like humans can, it can log in, it can request the things that it needs — then it will be drafting on all of the process that we've put in place for humans." — Martin Casado 00:22:05

"I am all for agent onboarding. Like the agent comes and it goes to orientation. And then the CEO gives it the culture discussion... I actually honestly think, given the technical nature of these agents, we're going to have to go through the processes that we've refined around humans." — Martin Casado 00:23:40


The Integration Wall Is the Defining Obstacle, and AI Doesn't Solve It

Every large enterprise is sitting on a mass of fragmented systems that haven't been integrated and can't be magically fixed by AI or agents. Agents hitting walls in enterprise will mirror the experience of calling customer service and getting bounced between departments.

"The thing that's not different about AI and that agents don't fix, that nothing fix, is that any enterprise of 1,000 people or more or that's older than 10 years is just a mass of stuff that's sitting there waiting to be integrated. And you can't just say it's going to integrate. AI actually doesn't help to integrate anything." — Erik Torenberg 00:13:03

"Agents basically don't have any — there's no real exception yet for the agent having the same problem because you basically — as you pass through a different human, it's a different set of access controls that that human has." — Aaron Levie 00:15:54

"What's going to happen is you're going to have a lot of agents that don't have access to the right data. They're kind of working through systems that are not the real sources of truth for the information. They're getting the wrong number. They're getting the wrong document." — Aaron Levie 00:17:09


2. Contrarian Perspectives

AI Is Making Code Worse, Not Better, and We Haven't Solved That

While AI dramatically increases coding velocity, there is a real and underappreciated risk that it is introducing more entropy and technical debt than it is resolving. The net productivity gain may be illusory in some cases.

"When you code with AI, your code kind of gets worse over time pretty materially. And so it's almost like you're introducing as many problems as you are solutions. And I don't think we've actually figured out how to manage that." — Martin Casado 00:43:05

"If you're using AI, yes, you're productive. But are you creating more problems than you've actually solved for solutions?" — Martin Casado 00:43:33

Aaron Levie corroborated this from his own company experience: AI built 80-90% of a feature, but a full security review still rate-limited the release — suggesting the bottleneck has simply moved, not disappeared. 00:46:45


The "SaaS-pocalypse" Is Even Dumber Than It Sounds — Agents Are Just More Seats

The narrative that AI kills SaaS is backwards. Agents require their own identity, access rights, and seat — meaning SaaS companies face an explosion of addressable users, not a collapse.

"It is another seat. There is no way around it. And like if you're a SaaS company, you're crazy to try to say, oh, just use the credentials of another human. Like that's just — that would be like bad security practice from the get-go." — Erik Torenberg 00:29:42

"As soon as I saw that announcement [Salesforce going headless], I had like five to ten personal use cases where I would need the headless version of Salesforce... if you imagine being able to run compute in the form of agents across all of your data systems, the use cases become pretty wild." — Aaron Levie 00:26:38


Top-Down AI Mandates Are the Primary Source of Reported Enterprise AI Failures

The widely-cited stat that "95% of enterprise AI efforts fail" is misleading. The actual failure is centralized, top-down AI mandates — not AI adoption itself. Individuals throughout large companies are using AI successfully; organizations just don't know how to account for it.

"The board goes to the CEO, what does the board say? We need more AI. And what does the CEO say? Oh, okay, I'll get like a consultant to do more AI. And then they have some centralized project that nobody knows how it works. They haven't aligned their operations and those things will fail." — Martin Casado 00:06:08

"I am sure everybody is using ChatGPT very effectively. What they really should be saying is... organizations don't know how to adjust these kind of age-old processes that have been worked on for a decade around data and governance and operations and compliance." — Martin Casado 00:06:36


More AI-Written Code Means More Engineering Jobs, Not Fewer

Counterintuitively, the more software that gets written (especially AI-assisted), the more engineers will be needed — because complexity grows and demands more management, maintenance, and security oversight.

"The funniest concept that the more code we write, the less we would need engineers would be the opposite because now your systems are even more complex than before, which means that you're going to be running into even more challenges of when you need to do a system upgrade or when there's downtime." — Aaron Levie 00:52:40

"AI writing code will get rid of infrastructure... which is this kind of very strange prediction given the fact that there's more software than ever before been written. And sitting on the board of a bunch of infrastructure companies, some that have been flat for a while, they're all doing fantastic because there's so much software." — Martin Casado 00:53:42


3. Companies Identified

Box

Cloud content management company focused on enterprise. CEO Aaron Levie is deeply engaged with enterprise customers, building AI agents and integrating agentic workflows into the platform. Box launched a search agent that fans out multiple queries simultaneously and re-ranks results — a clear example of AI-native product design.

"We launched a box agent that gives a bunch more capabilities built into it... it searches across your whole box environment, but it doesn't have the same limitations of a human-based search where you type in one query, you get back a set of results... it fans out, does multiple queries, it can look through hundreds of results instantly and do its own re-ranking." — Aaron Levie 00:38:33


Salesforce

Enterprise CRM giant. Flagged as a bellwether for enterprise software's move to headless/agentic architecture. Their announcement of going "full headless" signals the shift to agents as primary users of enterprise software.

"The big news last week was Salesforce... they went full headless. And they basically said, we want to be used everywhere across all of our different agents. And I see that as a little bit of a bellwether because I think as Salesforce goes, so does a lot of enterprise software." — Aaron Levie 00:25:39


Accenture / Deloitte (Major System Integrators)

Traditional consulting/implementation firms. Flagged as essential — not ironic — partners in deploying enterprise AI. Their role in change management, systems integration, and implementation is actually more important in the AI era than before.

"There were some kind of snarky comments online around it that I was fascinated by... to me, it was like the most obvious announcement of all time, which is a large enterprise is going to have to go through the change management, the systems implementation, the integration of technology for these agents to be able to go and work." — Aaron Levie 00:17:58


4. People Identified

Aaron Levie

CEO of Box. Described as the most in-the-trenches enterprise CEO actively talking to customers every day and bridging Silicon Valley thinking with enterprise reality.

"You are the most in-the-trenches CEO who is really talking to customers every single day in the enterprise... My job these days is just bring reality to the valley and then bring the valley to reality as much as possible." — Aaron Levie 00:03:24 / 00:03:39


Martin Casado

General Partner at a16z. Former founder and enterprise infrastructure expert. Provides the clearest articulation of treating AI as a user vs. software, and identifies the entropy/code quality problem as a major unresolved challenge.

"These models don't integrate well with software, actually. I think it turns out, and what we're learning as an industry, is if you view them more like humans and you draft on the mechanisms we put in place for humans, they're much easier to integrate." — Martin Casado 00:22:33


Steven Sinofsky

Board Partner at a16z, former President of Windows Division at Microsoft. Provides historical grounding on how technology transitions (cloud, internet, office software) have played out inside large organizations, particularly around productivity claims and adoption curves.

Referenced repeatedly for his pattern recognition on prior tech transitions, including the evolution from hybrid cloud architectures to final-form cloud — used as an analogy for the current AI architectural uncertainty. 00:11:39


5. Operating Insights

Agent Onboarding as a Real Operational Practice

Enterprises deploying agents should create formal onboarding processes — not just technical provisioning. Give agents their own identity, email, documented context about the organization, and structured introductions to each department's workflows and data. This is not a metaphor; it's the actual mechanism for making agents useful without causing chaos.

"I am all for agent onboarding. Like the agent comes and it goes to orientation... every department does their pitch. Yes. Like this is what we do... given how much entropy they have and how unruly they are, we're going to have to go through the processes that we've refined around humans." — Martin Casado 00:23:40


Don't Race to Automate — First Use AI to Acquire Information, Then to Act

For enterprises and operators deploying AI internally, the highest-success, lowest-risk path is staging: start with read-only, information-retrieval agents before deploying action-taking agents. This mirrors how the internet first delivered value through access before enabling transactions.

"The fork is — is this an agent that is seeking information and presenting it to some human? Or is this an agent that's supposed to go act and do something? Like is it acquiring or is it doing? Because if it turns out that's what happened with the internet — the internet got very, very valuable when the first step was just providing access to things to people." — Erik Torenberg 00:19:51


Measure AI Output Quality, Not Token Count

Companies that measure AI productivity by token usage are creating perverse incentives — employees run agents on meaningless tasks just to hit metrics. Operators should build evaluation frameworks around output quality, error rates, and reduction in rework — not activity volume.

"Many companies are incentivizing people to use AI by counting tokens... I spoke to someone yesterday who worked for one of these large companies that famously does this. And he's like, me and my coworkers have agents do useless tasks just so that we can — no joke." — Martin Casado 00:14:28


6. Overlooked Insights

The Speed of AI Model Change Is Itself a Deployment Blocker — And This Is Underappreciated

The pace of AI progress, normally celebrated, is actively slowing enterprise adoption. Enterprise architecture teams have been burned by committing to platforms and paradigms that became obsolete (e.g., early AI investments from 3-4 years ago). The industry treats this as an impatience problem, but it is actually a rational risk management response. This creates a structural window for startups or platforms that can offer architecture-agnostic or modular approaches.

"As an enterprise architecture team in the real world, you're like, man, like what horse do I want to get behind? And which architecture path do I want to get behind? Because I've been burned by doing the wrong thing in AI maybe three or four years ago... I'll go have conversations with CIOs and their AI teams. And I'll say, hey, what are you using for your core agent orchestration? And they'll say, yeah, we're in the middle of a debate between these two or three paradigms. And you hear that across almost every single customer." — Aaron Levie 00:08:59 / 00:09:51


System Integrators Are the Sleeper Investment Opportunity of the AI Era

Buried in a brief aside is what may be the most important near-term business opportunity: the next generation of system integration firms. The work of connecting AI agents to legacy enterprise systems — change management, permissions architecture, workflow redesign — will take decades and represents a massive professional services and tooling opportunity that Silicon Valley is currently mocking rather than targeting.

"There's going to be businesses that are doing that for decades. Like it's going to be an incredible opportunity for this kind of next generation set of firms as well as existing ones that lean into that." — Aaron Levie 00:18:22

The irony noted in the podcast — that people mocked OpenAI partnering with Accenture and Deloitte — signals that this opportunity is genuinely underappreciated by the tech community, which is precisely when the best investments are made.