Atlassian (TEAM) Q1 2027 Earnings Call Transcript

Atlassian reported Q1 FY2027 revenue of $1.772 billion, up 24% year over year, with Cloud revenue up 31% to $1.302 billion and free cash flow up 304% to $463 million. GAAP operating margin was 11%, versus negative 7% in Q1 FY2026; remaining performance obligations rose 44% to $4.746 billion. Management forecast Q2 revenue of $1.825–$1.835 billion and FY2027 revenue growth of about 13.8%, while citing macro uncertainty and tougher second-half comparisons. Usage-based pricing enforcement begins in early December 2026, but management does not expect meaningful revenue from it in FY2027.

Analysis

The key distinction is between demand quality and near-term growth optics. Multiyear commitments and enterprise expansion support revenue visibility, but they do not eliminate the risk that Cloud growth decelerates as migration revenue is recognized across hybrid deployments and the comparison base toughens. The market may treat the guide as a demand signal when part of the variance is timing and mix; the next two quarters should distinguish those explanations. Watch current RPO and subscription ARR against reported Cloud growth, not headline AI usage alone.

AI is currently a retention, seat-expansion and package-mix thesis—not a standalone usage-revenue thesis. That can still compound value, but adoption counts are not evidence of willingness to pay. The critical proof points are paid collection upgrades, net retention, seat growth, and gross margin after inference costs. Usage-based pricing beginning in December is a potential customer-friction catalyst, not a FY27 earnings lever on management’s framing. FDEs may shorten enterprise deployments, but their uncharged, engineering-heavy model could also absorb capacity before measurable monetization.

Competitive read-through is favorable for Atlassian’s Service Collection if workflow consolidation persists, but ServiceNow’s similar customer-implementation push underscores that AI-enabled displacement is contested, not exclusive. Data Center retention and delayed public-sector cloud readiness also temper any assumption of a smooth migration ramp. Over 6–18 months, success depends on converting context and agent collaboration into broader paid workflows without degrading margins. Contrarian risk: investors may be over-crediting engagement metrics while underweighting the guide’s deceleration and the time required to monetize AI.

Key Decisions for Investors

• Avoid chasing the initial post-call move. Reassess TEAM after the first full trading session and use the next quarter’s Cloud growth, current RPO, subscription ARR, and net retention to determine whether the slowdown is mainly hybrid revenue timing or weaker demand. A further guide reduction or deterioration in those indicators falsifies the constructive read.
• Conditional long TEAM on stabilization after the guidance-driven repricing, sized as a growth exposure rather than an immediate AI-monetization trade. Upside case: enterprise expansion and paid collection mix offset tougher comparisons; downside: Cloud growth decelerates faster than ARR/RPO imply and the multiple compresses. No price target without current valuation and market-price data.
• Track December usage-pricing enforcement and subsequent quarters for package upgrades, paid AI usage, gross-margin trend, and any evidence of customer pushback. If adoption rises but paid mix and seat expansion do not, reduce the AI premium thesis; if monetization improves while margins hold, revisit adding exposure.
• Treat ServiceNow as a competitor watch, not a short recommendation: compare disclosed displacement wins, growth, and valuation before initiating a relative-value position. A sustained TEAM share gain in service workflows would support the competitive thesis; evidence that implementation capacity or product breadth limits conversions would weaken it.