Atlassian CEO on the SaaS Apocalypse, AI Agents & What Comes Next

What It Covers

Atlassian CEO Mike Cannon-Brookes joins a16z's Alex Rampell to analyze the SaaS market selloff, arguing that public markets cannot distinguish between three fundamentally different business models, and explains how AI agents are forcing companies to redesign human-software collaboration workflows rather than simply add AI features.

Key Questions Answered

• •Three SaaS categories: Rampell identifies three distinct SaaS types that markets treat identically: seat-based tools tied to work AI can now replace (Zendesk), seat pricing used as a headcount proxy unrelated to output (Workday), and hybrid models (Adobe). Investors who cannot separate these categories are mispricing both risk and opportunity across the entire sector.
• •Input-constrained vs. output-constrained processes: Cannon-Brookes frames AI's business impact through process type. Input-constrained work (customer service, legal contracts) has a fixed volume ceiling, so AI reduces cost. Output-constrained work (engineering, marketing) has no ceiling, so AI increases throughput. Identifying which category each team operates in determines whether AI shrinks headcount or expands capacity.
• •Consumption-based pricing creates customer resistance: Enterprise buyers actively dislike AI credit and token pricing because they cannot control or benchmark consumption across vendors. Customers prefer per-seat pricing because it is predictable and transferable. Vendors who tie usage spikes to their own feature releases—without customer consent—accelerate churn and erode trust in outcome-based models.
• •Vibe coding extends software, not replaces it: Rather than rebuilding core systems, AI-assisted coding enables companies to build narrow, highly customized extensions on top of existing platforms. A Miami office conference-room app that reads Workday data and applies local HR rules becomes buildable without a dedicated IT team, making underlying systems of record stickier and more valuable, not obsolete.
• •Human-agent trust loops require deliberate design: Agents that act without checkpoints lose user trust; agents that ask constant questions create paralysis. Cannon-Brookes describes Atlassian's approach of allowing users to chat with an in-progress agent mid-task to inspect its actions. Trust accumulates over repeated successful completions, eventually allowing users to skip review steps they previously required.