Atlassian (TEAM) Q3 2026 Earnings Transcript

Atlassian reported Q3 revenue of $1.8 billion, up 32% year over year, with cloud revenue surpassing $1.1 billion and RPO rising 37% to $4 billion. Management said Rovo AI usage is growing more than 20% month over month and that customers using Rovo are growing ARR at roughly 2x the rate of non-users, while NRR stayed above 120% and Service Collection ARR topped $1 billion. The main caution is data center lumpiness from upfront license revenue pull-forward, but management reaffirmed cloud migration is on track and expects mid- to high-single-digit cloud growth contribution from migrations.

Analysis

The market is still underestimating the durability of Atlassian’s AI monetization because it is not selling “AI” as a standalone feature; it is using context density to reduce the effective cost per task. That matters because the best second-order effect here is not just higher usage, but a widening moat: as Rovo gets embedded into workflows, switching costs rise while token economics improve versus generic agents. The result is a self-reinforcing loop where usage expands, ARR expands faster, and the product becomes more defensible precisely because it is cheaper to operate at scale.

The bigger earnings-quality issue is the data-center pull-forward. Near term, this makes reported growth and backlog metrics look stronger than underlying underlying demand, but it also sets up an easier comp and potentially cleaner cloud re-acceleration once the accounting noise laps. Investors focusing on the headline RPO print risk missing that the real signal is the implied enterprise willingness to commit longer and broader, while some of the apparent conservatism in seat expansion is simply migration staging rather than demand weakness.

Competitively, the clearest loser is legacy ITSM and adjacent workflow vendors that depend on fragmented tool stacks and weaker context graphs. The more interesting competitive implication is for horizontal AI agents from large platform players: if Atlassian becomes the system of record for work context, third-party agents may still win front-end mindshare while Atlassian captures the monetization layer underneath. That is a better economics outcome for TEAM than most investors appreciate, and it supports continued share gains without requiring a heroic standalone AI product cycle.

The contrarian risk is that the current multiple already prices in a long runway of cloud, AI, and seat expansion, while the data-center normalization masks some volatility over the next 1-2 quarters. If Rovo usage growth decelerates from 20%+ monthly or if migration cohorts start compressing faster than expected, the narrative breaks quickly. Near term, the stock likely trades on whether the company can convert next week’s disclosures into a cleaner ARR bridge; if not, the market may continue to discount the quality of growth despite the strong underlying demand.

Key Decisions for Investors

• Long TEAM on a 3-6 month horizon via stock or call spreads; thesis is that normalized ARR disclosure reduces accounting overhang and re-rates the cloud/AI growth mix. Risk/reward is favorable if the market prices cleaner visibility rather than headline revenue alone.
• Pair trade: long TEAM / short CRM for 1-2 quarters. TEAM is capturing workflow and AI attach inside the operating layer, while CRM faces more skepticism around AI monetization quality and saturation in core enterprise seats.
• Add to TEAM on any post-Investor-Forum pullback if management demonstrates ARR normalization without cloud deceleration. Use weakness below the event as entry, with a target of multiple expansion over the next earnings cycle.
• Avoid initiating or increase short exposure to legacy ITSM/workflow names over the next 6-12 months; the displacement dynamic appears structural, and competitive losses can accelerate once enterprise proof points spread.
• For tactical upside, buy TEAM call spreads into the next product/event catalyst if implied volatility is still compressed. The near-term catalyst profile is asymmetric because the market has not fully priced a clean disclosure bridge plus continued Rovo adoption.