The Agent Era: Building Software Beyond Chat with Box CEO Aaron Levie

What It Covers

Box CEO Aaron Levie joins a16z partners Steve Sinofsky and Martin Casado to examine how enterprise software must evolve when AI agents outnumber employees by 100 to 1,000x, covering agent security risks, SaaS economics, compute budgeting, and why AI diffusion will move slower than Silicon Valley expects.

Key Questions Answered

• •Agent-to-human ratio reframes software architecture: When agents outnumber employees by 100–1,000x, software must be built primarily for agent consumption, not human interfaces. This means prioritizing CLI access, durable APIs, and MCP protocols over UI polish. Box already allocates equal engineering time to agent interfaces as to human-facing product design.
• •AI diffusion timeline is systematically underestimated: Enterprise AI adoption at companies like JPMorgan will lag startup deployment by years due to legacy system complexity, security vulnerabilities, and integration risks. SAP-scale ERP systems encode domain knowledge across UI, middleware, and data layers simultaneously — no agent can "vibe code" its way through that architecture anytime soon.
• •Agents select backends on durability and cost, not interface quality: Contrary to the popular "build for agents" marketing framing, agents already demonstrate preference for backends based on cost parameters, reliability, and data durability — not documentation quality or API aesthetics. Software companies should focus on building genuinely better systems rather than agent-targeted marketing layers.
• •Agent identity and liability create unsolved enterprise security problems: Treating agents as independent users breaks down because operators retain full liability for agent actions, agents have no privacy rights, and prompt injection attacks can extract any information present in a context window. Enterprises should currently restrict agents to read-only consumption layers until containment standards emerge.
• •Engineering compute budgets will become the defining CFO challenge: As every engineer runs parallel agent experiments, token spend becomes a direct line item competing with headcount costs. Companies spending 14–30% of revenue on R&D must now decide how much of that budget converts to token consumption — a question with no established benchmarks and significant EPS implications.