Atlassian Corp Q1 FY2027 earnings call

• Strong Financial Execution: The company delivered a free cash flow of $463 million (26% margin), up 304% year-over-year. Remaining Performance Obligations (RPO) surged 44% to $4.7 billion, indicating robust future demand.
• Enterprise & AI Strategy: Customers are expanding commitments on the Atlassian platform. Over 3,000 customers have upgraded to the Teamwork Collection (a 7x YoY increase), and the Service Collection has surpassed 70,000 customers with >30% ARR growth. More than 87% of enterprise cloud customers are now using Rovo.
• Contextual Advantage: The 'Teamwork Graph' connects over 250 billion objects. Customers with richer graphs are twice as likely to become deep Rovo adopters, who grow ARR more than twice as fast as light users.
• Agentic Collaboration: Introduction of Agentic Multiplayer Protocol (AMP) facilitates human-agent collaboration. Over 10 million human-agent collaborations occur monthly, doubling in six months.
• Forward Deployed Engineers (FDEs): The FDE program is scaling successfully, helping large customers integrate AI workflows and build ontology into the teamwork graph, accelerating product delivery loops.

Total revenue grew 24% year-over-year to $1.8 billion. Cloud revenue grew 31% to $1.3 billion, representing approximately 72% of total revenue. Subscription ARR grew 23% to $6.8 billion. Data Center results were strong with high retention rates among large, complex customers, though specific absolute dollar figures for Data Center were not broken out separately from the total revenue figure in the opening remarks.

• Prudent Approach: Management emphasized taking a thoughtful and prudent approach to guidance, balancing strong momentum against macro uncertainty and fiscal policy dynamics.
• Q2 Deceleration: Cloud revenue guidance for Q2 reflects approximately four points of deceleration compared to prior estimates, due to tougher comparisons and timing effects.
• Full Year Outlook: While Q1 was strong, the full-year guide was raised by less than the beat. This is primarily attributed to timing mechanics related to ASC 606 revenue recognition pull-forwards on the Data Center side, rather than a fundamental shift in confidence.
• Long-term Growth: No meaningful usage-based pricing (UBP) revenue is expected in FY27; monetization remains focused on seat expansion and collection upgrades.

• Macro & Geopolitical Uncertainty: Management cited evolving macro environments, fiscal policy, and geopolitical landscapes as factors necessitating a cautious guidance approach.
• Data Center Migration Pace: While migration is on pace, some large, complex customers (particularly in public sector) require extended timelines for compliance certifications (e.g., FedRAMP High, IL-5), potentially keeping them on legacy platforms longer than initially anticipated until March 2029.
• AI Monetization Timing: Usage-based pricing features are being introduced but are not expected to drive near-term revenue; the focus remains on predictable subscription models.

Q: Ryan McWilliams asked why Data Center results were strong despite customer prioritization of cloud migration, and how hybrid deployments impact this.

A: James Chuong explained that strong retention is driven by the cloud roadmap and early commitments to government certifications (IL-5, FedRAMP). Hybrid deployments allow large customers to migrate over multi-year periods. These deals split revenue between DC and Cloud without double-charging, resulting in slightly higher DC revenue and lower Cloud revenue this quarter, signaling deepening customer commitment to cloud as the final destination.

Q: Fatima Boolani questioned if AI-driven agent coding diminishes the need for Jira/Confluence coordination.

A: Mike Cannon-Brookes disagreed, arguing coordination needs are stronger because AI increases work volume. Humans must still guide intent and handle exceptions. Jira/Confluence provide essential context via the Teamwork Graph. Additionally, non-engineering teams (HR, Finance) are writing code, creating new cross-functional coordination challenges that Atlassian solves.

Q: Matt Hedberg asked about the Forward Deployed Engineer (FDE) motion.

A: Mike clarified FDEs are qualified AI/ML engineers, not customer success staff. They help customers implement AI workflows and build ontology, aiming to leave trained internal teams. This unique model accelerates core software engineering at customer sites and speeds up the request-to-delivery loop, distinct from traditional professional services.

Q: Adam Wood asked about Atlassian's right to win agent orchestration/identity and if AMP will be monetized directly.

A: Mike differentiated Atlassian’s approach (AMP) as a human-centric interface layer bringing agents into existing workflows, unlike centralized control towers. AMP is not directly monetized but drives value by enabling seamless human-agent collaboration across platforms. Governance features like non-human identities support this within the platform.

Q: Greg Moskowitz asked about the 4-point cloud deceleration in Q2 guidance and declining ARR growth forecast.

A: James Chuong attributed the deceleration to lapping the DX acquisition, tougher comps in H2, and a natural evolution toward more predictable annual/multi-year deals as the enterprise sales motion scales. He noted strong NRR and seat growth from competitive displacements remain intact.