Topics Pioneers Insight Method Author
Back to Pioneers
Mike Cannon-Brookes
Entrepreneurs 3 Curated Dialogues

Mike Cannon-Brookes

Atlassian·CEO

Rendering the long image…

Frontier Insights

Frontier Thesis
AI valuation outpaces reality, and the “SaaS apocalypse” narrative oversimplifies software economics. True defensibility belongs not to thin wrappers with negligible switching costs, but to systems possessing enterprise distribution, institutional workflow integration, and deep, permissioned team collaboration graphs.

Strategic Decisions
Atlassian is pivoting from raw seat counts to value- and outcome-based monetization, anchoring AI capabilities like Rovo to their proprietary graph of over 100 billion nodes. They prioritize durable ROI and enterprise context over short-term revenue extraction.

Risks & Warnings
Faster code generation simply pushes friction into auditing, mental modeling, and governance. Furthermore, enterprise adoption hinges on solving token economics; opaque credit schemes and fragile user trust remain critical monetization bottlenecks.

Key Views & Dialogues

20VC: Atlassian CEO on Why Agents Won’t Replace Interfaces | Why Enterprises Won’t Trust Chinese Models | Why The Jury Is Still Out On The Benefits of Specialised Models with Mike Cannon-Brookes

20VC

Atlassian is betting that agents will expand interface value, especially for collaborative work requiring taste, context and human interaction. The Teamwork Graph turns each customer’s people, decisions, documents, code and workflows into queryable context for agents. Atlassian currently uses no Chinese models in production while routing Nemotron, Mistral and other models by quality, cost and speed; specialized models must sustain “exponential gains” as general models improve.

View summary (7)
  • A central product bet for Mike Cannon-Brookes is that agents will expand, not erase, the value of interface design. Functional “just get it done” work can disappear into agents, but collaborative work still needs taste, context and human interaction; horizontal agents, vertical agents and first-party interfaces can coexist. His blunt rule: “Headless is brainless,” and he is “a big bear on the magic button thesis of AI.”
  • Atlassian’s strategic asset is the Teamwork Graph: a fresh, company-specific index of people, decisions, documents, code and workflows that agents can query. Its job is to infer and organize context before an agent asks, much as Google indexes the web before a search. Cannon-Brookes stresses, “It’s the customer’s context. It’s not our context,” making customer-specific organizational context—not generic acquired data—the valuable layer.
  • Enterprise resistance is aimed at “Chinese models,” not open models generally, and Atlassian currently uses no Chinese models in production. It does use Nemotron, Mistral and other open models, routing each job toward the best price-performance outcome. Cannon-Brookes says US models increasingly use Chinese models to train themselves, making national labels less technically clean, but concedes customer concern is real today.
  • The jury remains out on whether most specialized models can sustain an advantage over rapidly improving general models. Proprietary datasets and highly specialized applications such as robotics or world models might justify specialization, but many supposed proprietary models are merely billion-dollar foundations tailored for roughly $1 million. The falsifier is clear: they must maintain “exponential gains” in price-per-watt performance as the generic frontier advances.
  • AI cost management is becoming a core enterprise-software capability, not a back-office exercise. Atlassian operates an internal AI gateway team for model routing, blending and harness selection across the quality-cost-speed triangle. Cannon-Brookes initially prioritizes magical adoption—“If five people are using a feature, I don’t care how much it costs”—then optimizes aggressively if usage reaches five million.
  • Cannon-Brookes has revised downward his estimate of future inference prices, although lower unit costs will drive much more usage. Capital, talent, chips, data-center design and distillation should push price-performance down “at a precipitous rate,” but he rejects infinite demand: technology production already exceeds customers’ ability to absorb business change. A supercomputer-equipped phone still does not burn its CPU 100% of the time.
  • As technology becomes abundant, competitive scarcity shifts from privileged knowledge to creative application. Borrowing Culture Amp founder Didier’s phrase, Cannon-Brookes says business is moving “from a world of information asymmetry to imagination asymmetry.” The personal counterweight is deliberate slowness: agents multiply activity and demands on attention, so leaders must preserve deep thinking and learn to “slow down to go fast.”

Read the deep dive →

Listen to full conversation →

Atlassian’s Most Controversial Growth Decision | Mike Cannon-Brookes

Gradient Dissent

Atlassian’s market extends beyond developers, with Jira and Rovo connecting technical and business workflows through a permission-aware teamwork graph exceeding 100 billion objects and connections. Cannon-Brookes expects agents to remove workflow steps rather than eliminate workflows, while faster code generation still requires human review, accountability, and evidence of realized productivity. Atlassian’s “grow longer, not grow faster” doctrine prioritizes durable demand and future investment alongside roughly 21% revenue growth, 26% cloud growth, and 40% RPO growth.

View summary (7)
  • Atlassian’s addressable market extends far beyond developer tooling: more than half its users have no technical job function. Cannon-Brookes’s category definition is deliberate: “We solve people problems. We don’t solve technical problems.” Jira evolved from a 2002 bug tracker into an issue tracker, road-mapping system, and broad workflow engine connecting technical teams with finance, HR, sales, marketing, and other business teams.
  • Cannon-Brookes expects AI to compress business processes, not make workflow software disappear. Agents will remove individual boxes and branches from a flowchart, but their files, links, comments, and outputs still re-enter processes for review, approval, or further automation. His counter-consensus call: AI is “an accelerant, not a replacement.”
  • The strategic asset beneath Rovo is a permission-aware “teamwork graph” containing more than 100 billion objects and connections, growing north of 50% quarter on quarter. Built since 2019 from links spanning Atlassian products and external SaaS applications, it powers enterprise search, context, ranking, and agent actions. More than 3.5 million people were already using Atlassian AI features monthly: “We don’t want to market AI; we want to ship it.”
  • AI is clearly increasing task-to-code speed, but Atlassian refuses to equate faster code generation with customer value or even realized productivity. Coding consumes roughly one-third of a developer’s week, while generated code shifts effort into rebuilding mental models and reviewing output. With token-heavy tools potentially costing thousands of dollars per developer and tens of millions annually across Atlassian, DX combines quantitative delivery metrics with qualitative surveys to find actual ROI.
  • Atlassian’s application-layer strategy is to supply context and select models rather than bet the product on one model vendor. Its production AI gateway runs north of 75 models, and Rovo Dev may use two or three on a typical task, including Claude Code or Gemini. A notable internal use case was not greenfield creation but an API change across more than 500 repositories—“mowing the lawn” at scale so engineers can return to “landscape architecture.”
  • Cannon-Brookes rejects both mass developer displacement and the idea that only senior engineers will remain employable. He expects Atlassian to employ more developers in five years, with a continuing economic case for pairing one senior with four or five less-experienced engineers whose output AI can amplify. Accountability remains human: whoever commits or approves code owns it, regardless of whether Rovo Dev, Cursor, Claude Code, or GitHub Copilot produced it.
  • The operating doctrine is “grow longer, not grow faster,” even as Atlassian reported roughly 21% revenue growth, 26% cloud growth, and 40% RPO growth. Cannon-Brookes wants durable growth north of 20%–30% five years out, not a quarter optimized by spending every available dollar on immediate revenue. His investor-relevant test is whether the company is seeding future demand or merely harvesting yesterday’s work until “the fields are barren.”

Read the deep dive →

Listen to full conversation →

Atlassian CEO, Mike Cannon-Brookes on Why Everything is Overvalued & Are We in an AI Bubble

20VC

Atlassian CEO Mike Cannon-Brookes says most AI assets are vastly overvalued, with circular revenue obscuring whether scale produces durable economics and enterprise deployment still lagging magical demos. He sees low initial switching costs, limited pricing power for coding tools, and design becoming scarcer as software creation gets cheaper; per-seat pricing will likely coexist with nuanced usage models. The investable test is whether startups secure distribution before incumbents acquire innovation, while workflow changes, data quality, security, and model obsolescence delay value realization.

View summary (7)
  • “Most of the things are vastly overvalued” — but some are undervalued and will be worth far more, and “the far more is probably overweight”: the dot-com pattern where Amazon emerged from the rubble. The circular-revenue adage — an AI company gives $100M to a model company, which gives $150M to a cloud, which gives $200M to Nvidia, “and you’re all like losing 50 million bucks on the way through” — is why “we aren’t in an era where we have a durable business model,” and anyone claiming to know where value settles “is probably not telling you the truth.”
  • Of at least ten CEOs Harry has asked, Cannon-Brookes is the only one who wouldn’t pay 10x for AI coding tools: “the competitive vector between them is not going to let you do that” — charge 10x and engineers switch — and coding is only 10-30% of a developer’s week anyway. Search, debugging and ops fill much of the rest, and more services — hypothetically, 100 becoming 1,000 — means more gremlins: a “Gordian loop of AI solving the problems AI created with AI.”
  • The moat logic investors should keep: “You cannot build a business fast that has high switching costs.” LLMs were “dropped on the whole world at the same time” — unlike PCs or mobile, which took years to permeate — so switching costs for almost everything built right now start small, and they will have to build up from value delivered, data, workflows and familiarity. The race remains: “can the startup acquire distribution before the incumbent acquires innovation?”
  • Per-seat pricing isn’t dying. Value-based pricing fails twice — buyer and seller must agree on measuring the outcome, and the shared-savings math works “for one loop, one lap of the world” (once the $100 support ticket costs $90, you can’t keep charging for the discount). Customers dislike consumption models, which tend to flip into another form of payment, as with unlimited storage. He expects a blended model: “the answer is probably a nuance and subtlety like always.”
  • More engineers in five years, not fewer — Mike spoke right before Matt from AWS, and the two “violently agreed.” Atlassian is hiring more grads than last year, some 10x engineers may become 100x with the new tools, and the roadmap is unlimited: “find me a software company that gets to the end of its roadmap.” As creation gets cheap, design becomes the scarce, hard-to-copy differentiator.
  • On what may take longer than expected: the “delta between magical demos and actual value delivered is quite high” — enterprise AI deployment may take much longer than hoped, requiring workflow changes, data cleanliness, security, education and more. And the future interface isn’t necessarily a chatbot (“otherwise we’d all just use the terminal”) — it’s stable UI plus prompt layers, with a better click-to-value ratio.
  • 23 years in, the operating creed: “the founder’s job is to fight the entropy of ambition” (Tobes’s line, which Mike wrote down), and Atlassian’s defense through technology transitions is creativity — “we’re not going to be able to defend our way through it. We’re going to have to create it.”

Read the deep dive →

Listen to full conversation →