Atlassian (TEAM) Q2 2026 Earnings Call Transcript

Image source: The Motley Fool.

DATE

Thursday, February 5, 2026 at 5 p.m. ET

CALL PARTICIPANTS

• Chief Executive Officer & Co-Founder — Michael Cannon-Brookes
• Chief Financial Officer — Joe Binz
• Head of Investor Relations — Martin Lam

Need a quote from a Motley Fool analyst? Email pr@fool.com

TAKEAWAYS

• Cloud Revenue -- Reached $1 billion for the first time, representing 26% year-over-year growth.
• Annual Run Rate Revenue -- Surpassed $6 billion.
• Remaining Performance Obligations (RPO) -- Rose by 44% year over year to $3.8 billion and accelerated for three consecutive quarters.
• Net Revenue Retention (NRR) -- Exceeded 120%, with sequential improvement for the third quarter in a row.
• Million-Dollar Deals -- Record number of deals greater than $1 million in annual contract value, nearly doubling year over year.
• AI Feature Adoption -- Robo surpassed 5 million monthly active users, with Teamwork Collection passing 1 million seats sold in less than nine months.
• AI Impact on Customer Expansion -- Companies using AI code generation create 5% more Jira tasks, see 5% higher Jira monthly active users, and expand seats for Jira 5% faster than non-AI users within the software segment.
• Seat Expansion Rates -- Double-digit seat expansion in Teamwork Collection compared to standalone applications.
• Service Management Metrics -- Jira Service Management passed 65,000 customers and claims enterprise growth over 60% year over year; more than two-thirds of service collection customers now use it for non-IT use cases.
• Cloud Migration Contribution -- Migrations contributed a mid- to high-single-digit percentage to cloud revenue growth and are projected to maintain this contribution for the full fiscal year.
• Midterm Guidance -- Management reiterated a 20%+ compounded annual revenue growth target through fiscal 2027 and 25%+ non-GAAP operating margin for fiscal 2027.
• Pricing Model Comments -- Seat-based pricing remains the preferred framework, complemented by select consumption-based models for features like Forge, extra AI credits, and Bitbucket pipelines.
• Enterprise Penetration -- Atlassian Corporation serves more than 350,000 customers, including over 80% of the Fortune 500 and 60% of the Forbes AI 50.
• Cross-Sell Momentum -- Teamwork Collection package, which bundles multiple products and additional AI credits, delivers higher seat expansion and adoption rates, outpacing standalone application conversion.
• Buyback and Guidance Update Impact -- Management noted raised guidance and a significant buyback acceleration, though immediate impact on the share price was addressed as not correlating with operational performance.
• Non-Technical Seat Expansion -- Significant seat growth reported in HR, finance, and other business teams beyond traditional technology user base.

SUMMARY

Atlassian Corporation (NASDAQ:TEAM) reported a record-setting $1 billion cloud revenue quarter and achieved annual run rate revenue above $6 billion, citing accelerating demand for AI-powered solutions and multi-year enterprise commitments. The company disclosed that AI adoption is materially increasing usage and seat expansion within core products, and that over 1 million seats were sold for its Teamwork Collection in less than nine months. Management reaffirmed its midterm revenue growth and margin targets, while reiterating proactive pricing discipline and a leading position in enterprise workflow transformation.

• CFO Joe Binz emphasized broad-based seat expansion momentum across both technical and non-technical users, with enterprise and SMB segments both contributing to stable growth rates.
• CEO Michael Cannon-Brookes cited customer priorities now centering on AI integration, compliance, and unified systems of work, driving a shift to long-term cloud platform deals.
• Jira Service Management, now used by more than 65,000 customers and half the Fortune 500, is experiencing its fastest scaleup and strong adoption for non-IT workflows.
• Guidance for mid- to high-single-digit cloud migration contributions suggests continued transition from data center deployments, with incentives for cloud upgrades maintained.
• The company reported that Teamwork Collection has double-digit higher seat expansion rates than standalone products, strongly correlating with its AI platform and bundled pricing.
• Management addressed pricing strategy by highlighting hybrid models and customer preference for predictability, with selective use of consumption-based pricing for advanced workloads.
• The company stated that agent-based and AI-enhanced workflows are now operating at scale in both Jira and Service Management, contributing to increased customer stickiness and multi-year commitments.
• Atlassian Corporation remains confident in achieving at least 20% compounded annual revenue growth and expanding margins through fiscal 2027, with ongoing risk adjustments in short-term forecasts.

INDUSTRY GLOSSARY

• RPO (Remaining Performance Obligations): Contracted revenue obliged to be recognized in future periods, representing visibility into booked business not yet delivered.
• NRR (Net Revenue Retention): A measure of recurring revenue growth from existing customers, accounting for expansions, contractions, and churn.
• Teamwork Collection: Atlassian Corporation’s cloud-based suite bundling multiple collaboration apps and advanced AI credits on a seat-based subscription model.
• Jira Service Management (JSM): The company’s service desk and workflow automation platform spanning IT, HR, finance, and operations.
• Agentic Workflows: Automated processes executed by software agents or AI within business applications, often replacing or augmenting human input for routine tasks.
• MAU (Monthly Active Users): The count of distinct users actively engaging with a product or feature within a calendar month.

Full Conference Call Transcript

Martin Lam: Thank you for joining us today. On the call with me today, we have Atlassian Corporation's CEO and co-founder, Michael Cannon-Brookes, and Chief Financial Officer, Joe Binz. Earlier today, we published a shareholder letter and press release with our financial results and commentary for 2026. The shareholder letter is available on the Investor Relations section of our website, where you will also find our other earnings-related materials, including the earnings press release and supplemental investor data sheet. As always, our shareholder letter contains management's insight and commentary for the quarter. During the call today, we will have brief opening remarks and then focus our time on Q&A. This call will include forward-looking statements.

Forward-looking statements involve known and unknown risks, uncertainties, and assumptions. If any such risks or uncertainties materialize or if any of the assumptions prove incorrect, our results could differ materially from the results expressed or implied by the forward-looking statements we make. You should not rely upon forward-looking statements as predictions of future events. Forward-looking statements represent our management's beliefs and assumptions only as of the date such statements are made, and we undertake no obligation to update or revise such statements should they change or cease to be current.

Further information on these and other factors that could affect our business performance and financial results is included in filings we make with the Securities and Exchange Commission from time to time, including the section titled "Risk Factors" in our most recent filed annual and quarterly reports. During today's call, we will also discuss non-GAAP financial measures. These non-GAAP financial measures are in addition to and are not a substitute for or superior to measures of financial performance prepared in accordance with GAAP. A reconciliation between GAAP and non-GAAP financial measures is available in our shareholder letter, earnings release, and investor data sheet on the Investor Relations section of our website.

We would like to allow as many of you to participate in Q&A as possible, so out of respect for others on the call, please take one question at a time. With that, I will turn the call over to Michael Cannon-Brookes for opening remarks. Thank you all for joining us today. As you have already read in our shareholder letter, we closed out Q2 with very strong enterprise sales execution,

Michael Cannon-Brookes: and incredible momentum across our business. We surpassed $6 billion in annual run rate revenue, delivered our first-ever $1 billion cloud revenue quarter, up 26% year over year, and grew our RPO 44% year over year to $3.8 billion. We have strong momentum across our enterprise, AI, and system of work transformations, and you can see this in our numbers. Customers are choosing us for their future, in bigger ways and bigger numbers than ever before. Enterprises like Cisco, Expedia, Reddit, and Synchrony Financial rely on Atlassian Corporation to power their most critical business processes and workflows. Robo surged past 5 million monthly active users of our AI capabilities.

We are seeing firsthand every day how AI is transforming the way that work gets done, and we are directly benefiting as a business. When we look at the thousands of customers in our software team using AI code generation tools, we found that they create 5% more tasks in Jira, have 5% higher monthly active users, and expanded Jira seats 5% faster than those who do not use these AI coding tools. As I have said before, AI is the best thing to happen to Atlassian Corporation, and the results we are seeing today are no accident.

As a long-term focused company, we are now benefiting from years of thoughtful investment across product, R&D, and GTM, which have positioned us to capture this moment. These investments are creating what we believe is a truly differentiated customer experience. First, the data and domain expertise living inside our Teamwork graph, which is now well more than 100 billion objects and connections across first and third-party tools, enables Robo to deliver real business value that is context-aware and actionable for customers across their search, chat, and agentic experiences.

Second, our decade-long investments in enterprise-grade security, data governance, permissioning capabilities, and compliance enable every organization to securely move work forward at scale while deploying these fantastic new AI capabilities with the trust that they need. We provide a system of work built on deep integration into customer workflows, with that compliance, security, and support that enterprises trust built in. Lastly, our unique distribution engine enables us to seamlessly deliver incredible experiences to over 350,000 customers, including more than 80% of the Fortune 500 and 60% of the Forbes AI 50. Customers are realizing the value of our unified system of work and want to continue to partner more closely with us than ever before.

And all of this is driving our results. We closed a record number of deals greater than $1 million ACV in Q2, nearly doubling year over year again, as enterprises are choosing to standardize on the Atlassian Corporation system of work. In less than three quarters, more than a thousand customers have upgraded to our main AI monetization driver, the Teamwork Collection, purchasing more than 1 million seats to get the best AI platform and many more AI credits for their agents. As I look across our business, two things are clear. We have never been more of a strategic partner to the biggest businesses in the world, empowering their AI and future work transformations.

And our momentum is continuing to grow. This gives us confidence in our road ahead and our long-term opportunity. We are truly transforming how work gets done and solving the toughest human-AI collaboration challenges for our customers, and we are doing it every day. We are pushing ahead with strong conviction, and I could not be more bullish about the massive opportunities in front of us as we advance our mission to unleash the potential of every team. With that, I will pass over to the operator for Q&A.

Operator: We will now begin the question and answer session. If you have a question, please press star, followed by the one on your phone. If you would like to withdraw from the queue, please press star followed by the two. First question comes from Rob Oliver from Baird. Please go ahead.

Rob Oliver: Great. Thank you. Good afternoon. Thanks, Mike. Appreciate the clarity and conviction in the letter. Obviously, a ton of fear in the market right now on software, so I thought I would address it by asking you about some of the conversations you are having with your buyers right now. Clearly, the numbers show whether it be cloud NRR, you know, million-dollar deals, Robo adoption that existing customers are expanding with you. And in the letter, you called out some of those reasons, just Cisco around data,

Michael Cannon-Brookes: Expedia around, you know, customer familiarity. But, you know, can you talk about how those conversations have changed, if at all? Recently with your customers, and what is driving this motion towards Atlassian Corporation right now, and if AI is all changing those conversations, thanks.

Michael Cannon-Brookes: Thanks, Rob. Appreciate the kind words in there. The well, customer conversations have changed a lot over the last year. There is no doubt about that, Rob. And I would say all of those changes have been incredibly positive for us. The customer conversations we are having are at a higher level than we have ever been having them before. And those customers are looking for strategic partners to help them through AI. They continue to appreciate our delivery of that AI value to them, inside their processes and workflows. They will call this out directly. We get called out directly that AI capabilities are the reasons people move into the Teamwork Collection.

They are the reasons that people are upgrading to the cloud. They are the reasons they see R&D investments. They use our chat capabilities, our agents, in millions of workflows now per month. They are able to deploy them, get them up and running, and get value from them quicker. We have so many customer quotes and examples where they see this. Right? We have long put software in our customers' hands for them to use and deliver on. That, in return, makes those customer conversations about longer-term commitments. Right? As you pointed out, you see that in our numbers. Right?

Our RPO at 44% growing for accelerating for the third quarter in a row, is a really fantastic vote of confidence, I believe, from those customers. Right? Those are tens of thousands of seats signing multiyear deals, that are voting on not the platform for 2026 for them in but the platform in 2027, 2028, and 2029. And those customers are seeing what we are doing, seeing our progress, and voting with their feet. There is a lot, obviously, of noise out there in the market. Right? As I said in my shareholder, there is no doubt about that. But when I talk to customers, they believe that we are helping them through a lot of that noise.

Delivering for their software teams, their business teams, and their business process, and they are able to get efficiencies and improvements today. And I would say they want all the same things they have wanted in the past. Sometimes, these types of times when there is a lot of noise, Right? We can forget the fundamentals. Right? Enterprise customers want a platform they can trust. They need it to be compliant and secure and all the things they have always needed. They want great ROI. They want efficiency in their business. AI enables us to do that better than we ever had before in our domain, helping their teams to collaborate and be better.

I think we are seeing it in all of our numbers across the board. So, again, that is where you hear us feeling incredibly bullish, right, about what we are doing each quarter and seeing that real acceleration.

Operator: Your next question comes from Keith Weiss from Morgan Stanley. Please go ahead.

Sanjit Singh: Yeah. This is Sanjit Singh for Keith Weiss. Congrats on the $1 billion quarter cloud and the progress with Teamwork Collections, really nice to see. I wanted to follow-up on Rob's question. In terms of kind of the reality on the ground in terms of what the market is, you know, sort of asking and calling for versus customers want, and this is specifically around pricing. And like, I would love to hear your take on where does pricing go to and evolve over the next, one to three years? Market seems concerned on seat-based model, seat-based pricing. Customers probably like seat-based pricing.

And so what do you think this all shakes out in terms of where we are headed in terms of the pricing monetization story for Atlassian Corporation?

Michael Cannon-Brookes: Sure. Thanks, Sanjit. Look. A totally valid and important question. Let me start with the numbers that you can see it, and then I will talk to our philosophy. You can see in everything from the RPO to NRR number, again, 120% ticking up for the third quarter and are 120% plus, north of 120% and ticking up for the third quarter in a row. The pricing we currently have is delivering. Right, for the customers. They are opting for more of what we are doing. And price is not a huge part of any of these that we are having with our customers. It always is. They want to get good value.

They want to understand, but we are a very good value option. We always have been, and we continue to be so. The conversations around consumption-based pricing and pricing models changing, again, our philosophy has always been to deliver the best value we can in the overall ROI sense to our customers. It is our job, I believe, as an application vendor, not an infrastructure vendor, but an application vendor a platform vendor, to manage the costs of everything that we have in the envelope of what the customers pay. We have done that in storage. Done that in network costs. We are now doing it in AI costs.

And the customer's preferred method of payment is still an understandable predictable pricing pattern which tends to be a seat-based model in our category of software in terms of delivering collaboration tools for teams of people how many people are collaborating is a best proxy at the moment for value, and I believe continues to be so. You could worry about our AI costs. Again, you can see in our gross margin improvements, for a probably the third or fourth quarter, do not quote me on that, continue to improve our gross margin that we are able to deliver those 5 million Robo seats and continue to improve gross. That is a huge achievement on behalf of our engineering teams.

But it shows that we can manage those AI costs inside for the vast majority of customers. Now, we do have consumption-based offerings, as you can see. Everything from Forge to extra AI credits, if you go over the limits, to Bitbucket pipelines. Like, there are consumption-based offerings. So we are very clearly in a hybrid model of that, but we do try to make our pricing philosophy what is best for those customers. Right? They want to buy their applications. Not on a consumption basis. But on a familiar predictable basis. Goes into the total cost of ownership that they look at for that equation. So we feel really good about where we are seeing it.

And lastly, you would see the you know, the million seats we have passed in Teamwork Collection in under nine months is a huge achievement on behalf of a lot of teams at Atlassian Corporation. That has a predictable pricing pattern that is there. That has gone from zero to a million seats in under nine months. On this pricing pattern. And those are customers who are upgrading. Why? Because of the pricing philosophy, but also because of what the Teamwork Collection gives them as an AI platform. It gives them significantly more AI credits. Right?

So when they look at that upgrade, AI's list is one of the reasons, but it is baked into the pricing plan that we have on 1 million seats, we would argue it is working really well. Still early in that business.

Operator: Your next question comes from Gregg Moskowitz from Mizuho. Please go ahead, Gregg.

Gregg Moskowitz: Thank you for taking the question. Well, we are in a software twilight zone of sorts. So when a company whose stock is down almost 40% and five weeks on no company-specific news just reports a strong quarter, raises guidance and makes a significant commitment to accelerate the buyback. And yet the shares are right now indicated down a lower or an 10%. So I really do sympathize with how frustrated you all must be. Now as to my question, it is for you, Mike. And what are your thoughts on the medium to longer-term prospects of Anthropic's CoWork as a competitive alternative to Jira? Also, I think it is important to get your perspective on CoWork's new plug-ins.

And so you know, if we were to compare this to the most common Jira use cases, what could something like a CoWork plug-in automate for Jira, but also know, where would it fall short?

Michael Cannon-Brookes: Thanks, Gregg again. Appreciate the sound the kind words you seem as frustrated as we are. So that is great. Look. Firstly, I would say Anthropic is a great partner of ours. Use a lot of their models. We use a lot of their coding tools and working tools. We have just both become partners of Atlassian Williams Racing. It is wonderful. We are both helping that team to get to the front of the grid. With a combination of all of our software and tools. And I think that is a great example. Right? There are going to be new tools that arrive with AI and those new tools are going to deliver new capabilities.

We are seeing that every week. Every month. And that is great for our customers. Those tools continue to require data. They continue to require places to exchange. One of the greatest users of our MCP server as an example, is a way to get to Atlassian Corporation's offering and the Teamwork Graph and the context we have in those other tools is through things like, you know, CoWork's use of Atlassian Corporation's MCP server. That is really good for us. Right? Because it enables you to see how you can utilize and contribute back to the Teamwork graph from lots of different tools using lots of different contexts.

There is no doubt some of these tools are going to exist in different places, with some overlaps. There is significant value, I think, between our offerings and those offerings. So we do not see that as being perhaps the challenge that others do out there. There is a great partnership opportunity there, and we continue to explore that. We continue to use their offerings really strongly internally. There are always going to be a lot of differentiations out there. Our Teamwork graph is very differentiated. The context we have across our applications and other applications is very useful for any of those agentic type tools.

At the same time, you are still going to need human beings in the process in lots of different places. Approval workflows, business processes, they can be accelerated in lots of spots. That is exactly what we see customers doing with Robo agents and with all of the other agents that can now operate inside of Jira. Those agents are accelerating business processes in lots of different ways. They are not eliminating the human impact. Right? The human-AI collaboration is incredibly important, and I think it continues to be so. Lastly, I would just say that is not new for us. Our philosophy of integration goes to listening to customers.

The history of enterprise technology is about integrating with various different offerings. Right? Work with lots of different products. To make sure that our data and our workflows are integrated with what the customers are using. We will continue to do that. That is a very strong part of our philosophy, and I believe what customers really resonate with that we are integrated with deeply enmeshed in their processes and workflows, and we will continue to help those workflows get more efficient.

Operator: Your next question comes from Karl Keirstead from UBS. Please go ahead.

Karl Keirstead: Maybe I will direct this one to Joe. I noticed in the shareholder letter, you talked about next year, just, warning The Street that the DC segment, obviously, on the back of a tough comp would be down meaningfully.

I guess the spirit of my question is if we go back to the medium-term guide that you offered a year and a half or so ago, I think we would get to sort of an implied total revenue growth, if my math is right, of 19, 20% next year, If DC is meaningfully down, I guess I just wanted to test your confidence that the cloud revenue can be up enough such that you still feel comfortable with hitting that previous guide. Through fiscal 2027. Thank you.

Joe Binz: Yeah. Thanks, Karl. We do continue to have confidence in the long-term cloud guide. If you think about the short-term guidance, we have taken the same approach in Q3. FY 2026 that we followed last year. The growth drivers for the cloud business going forward continue to be very consistent. What we shared at the last Investor Day. We expect to tap into large market opportunities to drive healthy revenue growth. Through our strategies around enterprise AI and system of work. All of that drives a great number of users, a higher ARPU, and more opportunity for cross-sell and upsell to higher value additions.

And with AI, we believe we have a unique and differentiated position at this critical pivot point in the market with our Teamwork graph around high-value mission-critical workloads combined with our cloud platform. And there is a lot of long-term opportunity in that space as well. So overall, those are the big drivers. And we continue to expect to drive healthy revenue growth over the next two years in cloud.

Operator: Your next question comes from Aleksandr Zukin from Wolfe Research. Please go ahead.

Aleksandr Zukin: I guess in the spirit of the first two questions, Mike, it feels like you guys are continuing to see really solid growth and really solid progress on all the initiatives you have laid out. I guess my question would be, given the fact that you are probably already both benefiting from within Teamwork's collection a number of AI consumptive drivers. You are seeing Robo, and you are starting presumably to see your customers use agentic interactions even from other systems to enhance the value that both Jira and Confluence provide to Teams.

At what point do you would you expect to see monetization increase, improve, and that greater value proposition to result in acceleration, in stability, of the cloud numbers, specifically? And when do you think that will actually happen?

Michael Cannon-Brookes: Hi, Alex. I can definitely talk to that. Look. I want to reiterate, firstly, what Joe just said in the last answer, we have our long-term guide. We firmly believe in reiterating our confidence in that guide. And, hopefully, you can see in things like our RPO numbers and our NRR numbers, so our retention and our remaining performance obligations. That there is a confidence in that long-term future that comes across. And both of those RPO and NRR numbers are across both cloud and DC. Combinatorial. So that is important. I think you are seeing it today. So we run into this tricky bond. You are seeing that acceleration today.

Our RPO number has ticked up for the third quarter in a row and is growing significantly faster than our cloud revenue growth. And the cloud revenue growth also accelerated this quarter. So I believe you are actually seeing that today. And it will flow through. These customers are signing multi-year, you know, three-year large-scale deals. So in terms of at what point do we expect to see monetization? We are already seeing it and will continue to see it. Right? It is one of the number one reasons to move to the cloud and to upgrade to our cloud platform.

AI is one of the number one reasons to choose the Teamwork Collection as a higher offering, and that is a great economic equation for our customers and for us. You are seeing more than 5 million AI now, as you pointed out, and millions of agentic workflows now running every single month. All of that is leading to our customers continuing to expand their commitment to the Atlassian Corporation platform. AI is a huge part of that platform. Like, we should not mistake that. It is one of our three big transformations. We are heavily invested in delivering that AI to our customers. That monetization is coming through in the Teamwork Collection numbers we are seeing.

In those long-term customer treatments. They understand what we are building today. They see the road map of what we are building tomorrow. Customers have faith in our delivery. Again, the things we announce at our conferences we ship. We ship those very, very quickly now, increasingly quickly after those conferences. That does is build this long-term customer trust.

Operator: Your next question comes from Ryan McWilliams from Wells Fargo. Please go ahead.

Ryan McWilliams: Hey. Thanks. Second question. For Mike, as new models get released, we are hearing examples of developers switching between different models and different coding agents. As they see better model improvements. How do you view your position outside of the large AI labs working to Atlassian Corporation's advantage as customers can use Jira across their organization for the long term and then while still enabling their developers to use their favorite coding tool.

Michael Cannon-Brookes: Cool. Thanks, Ryan. Look. There is a lot of answers to that question. Firstly, we are big fans of model delivery. Every time new models come out, we take those capabilities. We have long set our strength is in adapting and delivering those models to our customers through the value. Again, our customers do not use models. They use applications. Right? We do not sell chips. We sell apps. And those apps have to deliver value, and those models let us deliver better value.

We have a very good AI team world-class in adopting new models, working out where they are stronger, where they are cheaper, where they are faster, where they deliver better quality results, and getting those into our products really quickly. That is our job to do. The customers may not even notice that. They probably do not. They may notice the check got a little better today than yesterday. We continue to do that. We have continued to improve check quality, agentic answer quality, etcetera. And we are able to use all the models again. We use models from multiple foundation labs within the customer's preferences.

And choices our ability to do that, if we can pick the best model for the best purpose across multiple labs, that is a good thing. And that is a good thing for our customers, like, fundamentally, right, in terms of their ability. We take the same position when it comes to agents. Again, we are shipping a whole set of capabilities for Jira directly. That includes Jira Service Manager, Jira Product Discovery, and Jira itself. To assign work to agents inside of any existing workflow or business process. Now you can assign work to a Robo agent out of the box. You can build your own agents.

But you are also able to assign work to agents from all of the other big agentic platforms. And I think that is a real strength of ours, because you can model your business process in Jira, You can model your workflow in Jira, and you can involve other agents from your agent platform of choice or as most enterprises will probably end up with, multiple agent platforms, and we have an out-of-the-box offering that works for you for simple quick cases. This is a real strength for our customers because it means that they have one workflow, and they can take the best of the best that makes sense.

Maybe that one set of agents in finance and a different set in sales. Fine. We are able to help them across the board again to our view of helping integrate with the tools they have. Now lastly, you mentioned some of the software capabilities of those agents. Just wanted to stress as we have said for twenty years, we solve human problems. We do not solve technology problems. We have never solved technology problems. And when we solve human problems, Jira is about the human reference to work. It is a piece of work that is going through a workflow, a set of changes, We use our own Robo dev tool. Sure.

We use old school coding where you just type the characters in, and we use many of the new AI code generation tools. In our engineering team, which is very large and very world-class. We use all of these things. We still use a lot of Jira. Again, the statistics we are showing is that the more people use those tools, they create more issues. They have more workflows. They actually have more MAU in Jira. 55% more MAU, at least. And they expand their seats at a faster rate. Because those are the most cutting-edge companies. Those are growing the fastest. Right?

And I think that shows that the world of collaboration and human challenge of teams getting together to decide what to do is still really important even among all of those technologies. So I think we have a unique position to take all those models into our customer as they need the value from them.

Operator: Your next question comes from Jason Celino from KeyBanc Capital Markets. Please go ahead.

Jason Celino: Great. Thank you. Maybe switching topics a little bit more of a simpleton kind of question, but curious to hear how the migration activity is going, you know, DC to cloud, if you are able to quantify how much that benefit was for the quarter.

Joe Binz: Thank you. Yeah. Thanks for the question. We saw very healthy cloud migrations in Q2. It contributed a mid- to high single-digit impact to cloud revenue growth rates. So given this, we continue to expect migrations to drive a mid- to high single-digit contribution to cloud revenue growth for the full year. So happy with the progress, and it continues to go very well.

Operator: Your next question comes from Ittai Kidron from Oppenheimer. Please go ahead.

Ittai Kidron: Thanks, and thanks Joe, for resetting their own 2027 data center. I wanted to dig into the seat expansion. It clearly was an upside driver. It came exceeded your expectations in the order. But, Joe, I was wondering if you could break down the seat expansion, if there is a way, that internally you look at this in context of new customer additions, expansion with existing customers, whether it is developers or other corporate functions. I mean, every day, we are hearing about companies laying off more and more and more people, yet you are getting more and more seats. I would love to get any insights as to the flavors. Where is it that you are gaining seats?

Where are you still seeing kind of good momentum over there in your confidence level about your ability to sustain the seat growth?

Joe Binz: Yeah. Thanks for the question, Ittai. In terms of where we see the expansion, I would say it is broad-based. It is across both tech and non-tech users. We are making a lot of progress on what we call non-tech or business users, particularly with the Teamwork Collection product. Those seat expansion rates both across the enterprise and SMB remain stable. That has been the case for, you know, four to six quarters now, so we feel really good about the continued progress on that. And that is the way I would describe from a prepaid seat expansion perspective. Sort of the color in terms of what we are seeing on that front.

Michael Cannon-Brookes: Hi. Sorry. If I can just chime in at a sort of a non-financial high level. Look. We are very clear that the system of work is about a continued growth of Atlassian Corporation into the knowledge worker population. Right? When we talk about unleashing the potential of every team, our mission for over two decades, I would stress the every team part. We have got the software collection, which does very, very well. The DX and a lot of other things encompass in a Bitbucket pipelines. Like, there is a lot of great areas of that software collection. We have also got the service collection.

So we are seeing great growth in service collection across HR teams, finance teams, other areas outside of its traditional market in IT and operations teams. But that is certainly an area of growth for us. So there is HR and finance teams seeing a lot in the service collections, for example, and you have seen us ship a lot of features. Also launched customer service this quarter. As an application within that, to go after a new set of teams. We have not been able to get to as well, you would say. In the core Teamwork Collection, look, as we said in our letter, we were seeing double-digit seat expansion.

More than double-digit seat expansion compared to people who buy the standalone applications. And that is baked into the Teamwork Collection packaging, but it is also because of the AI offering and how it works. Right, in terms of getting you get you equate your Loom confluence and Jira seats along with your additions which often gains expansion. But given the nature of our applications, and our continued growth in business teams across an enterprise, sales, marketing, HR, finance, etcetera, what that licensing structure allows those teams to do is to collaborate more.

And collaboration is a very sticky and kind of viral activity that is where you are seeing that expansion coming through in our MAU and in our AI MAU. And also ultimately ending up in our you know, NRR and RPO numbers in terms of long-term commitments from customers. That is and where they are seeing expansion across business teams of all fronts.

Operator: Your next question comes from Koji Ikeda from Bank of America. Please go ahead.

Koji Ikeda: Yes. Hey, guys. Thanks so much for taking the question. I wanted to follow-up on the point about customers that are using AI cogen tools are increasing Jira uses by 5%. You know, 5% on the tasks, on the MAU, and expanding faster. And so what I am trying to get at is understanding how the squares with the productivity gains that we are hearing from the cogen tools. Like, 30% more developer efficiency, driven by cogen. Does that equate to 5% more Jira usage? Maybe I have that completely wrong, but what I am trying to understand is how one helps catalyze use of the other.

And how we can maybe use that plus 5% increase of that Atlassian Corporation usage when Gen I AI is being used as a good read for other parts of the Atlassian Corporation growth opportunity. Thank you.

Michael Cannon-Brookes: Koji, great question. Into some specifics here. Firstly, that is obviously within sort of the software team and software collection. So the first thing I would say is, to if I spoke to him previously, that is a subset of our user base, right, in terms of software teams. And those are generally broad technology teams as well. Right? So not just developers, but you know, security folk and network analysts and operations teams and product managers and designers. There is a lot of different roles involved in a software team well beyond just the coding itself. But it is a subset of our total audience. And, again, service collection had an amazing quarter. In a totally non-software sense.

I think what we are saying there is it is 5% higher or at least 5% higher than non-AI code generation based companies. It does not mean it is a 5% expansion rate. It means they are expanding 5% higher than the rate of expansion of the other groups. So that is where you see that it is not necessarily a 5% total expand rate. You can see in that NRR and other stats, it is higher than that. Right? Secondly, there is a lot of reasons for that, I believe. Firstly, these are the cutting-edge companies. These are the companies that are pushing the boundaries the most.

They tend to be growth-oriented companies, so they tend to be companies that are growing, which is great. But guess who those largest companies are going to be? The future is those ones that are pushing the boundaries and driving forward in a generalized economic sense. So that is really good. Those are the leading companies for us. Secondly, yes, they are getting more efficiency. If you look at the actual delivery efficiency, loading speed is, again, 20 to 30% of the developer's job. And so you may be getting 10, 15, 20% improvement in the overall productivity of your organization if you have thousand people in R&D, something like that.

But that innovation moving quicker does not mean you are finishing your road map. You are coming up with more things to do. So you are adding more tasks, you are also creating a lot more technology, a lot more software and services which makes your architecture more complicated, it gives you more things to manage with something like Compass in terms of the different software code bases and models and pipelines and all the different data structures that you have to deliver your technology products and services as an organization as a customer of ours. And lastly, you create more complexity. Right? The security and compliance of a bank.

The governance functions that have to happen, the structuring and the downtime, the operating of that software. All of these things create Jira issues at large volumes. Right? So if you create more software, you are going to have more management, more overhead, more collaboration, some version of that is what we believe is happening underneath. Right? You have more collaboration to do because you end up with more technology, and that is a good thing. More software in the world is a good thing for Atlassian Corporation. If we have said that for a couple of years now, that is a belief that we are on AI is unlocking sort of human creativity at the highest level. Right?

It is allowing them to create more. That means those humans have to interact and collaborate more, and those created objects need to be managed, operated, maintained, and that is generalized, a good thing for Atlassian Corporation across software and non-software teams.

Operator: Your next question comes from Keith Bachman from BMO. Please go ahead.

Keith Bachman: Hi. Thank you very much. Mike, I wanted to direct this to you if I could. And I wanted to get your perspective and update on JSM specifically. And I will break that into a few parts. If any kind of metrics you could give us on growth, and what the trajectory is. There is a lot of consternation about workflow, broadly speaking, mentioned your stock going on. It is not the only one. ServiceNow goes down almost every day given concerns around the underlying fundamentals of JSM. The second part is, just anything on the competitive dynamics. And then the third is really I wanted to focus on seats for a second within the context of JSM.

And is there any update you can give us on like for like? What I mean by that is you have a JSM workload a customer has, is there seat degradation within the confines of a given workload understand you are still grabbing customers, so seats are probably going. But, really, on a like for like basis, just want to understand some context on seats. Many thanks.

Michael Cannon-Brookes: Sure. Thanks, Keith. Great question. Love questions about the service collections. Doing fantastically. Look. We gave some stats in our shareholder letter. Right? We passed 65,000 customers, which is a big milestone. 50% of the Fortune 500 as a business in and of itself, and the enterprise side of that world growing over 60% year on year. So hopefully, from those sort of high-level statistics, service collection is doing very, very well. It is definitely our fastest-growing product at significant scale. And that is a really important milestone for that business. As I said earlier, yes, that growth is happening on a like for like customer base. I like your sort same store sale analogy.

I get what you are asking there. You are certainly seeing efficiencies coming in some of those customers. At the same time, as a challenger brand, we are seeing great growth in HR. We shipped twelve months ago, a whole series of HR service management, blueprints, and other areas. We are going really well in that sort of part of helping operate a business. Same in finance, same in other areas of operations, often, like, management, these types of things. Service collection is doing very, very well in and we feel very confident that we have a lot more growth to go get there.

Secondly, on the asset management side, you have seen us take assets out of the service collection and put them into the core platform. That continues to be a big growth driver for us as we have a far more modern CMDB like system as a graph compared to a lot of the legacy competitors. And as we connect the assets graph that you have of physical objects often to the Teamwork graph, but we are seeing our agents and our AI capabilities get significantly more powerful, and we are seeing great growth there.

As such, you know, in the last six months, more than 40% of the agentic workflows that have been built are actually in service collection customers and service workflows. It is a very natural area to deploy agents AI agents into your service workflows to help improve the human agentic experience or the human agent experience of delivering value to the customer, or customer just getting the value directly themselves. So that is going very, very well. More than two-thirds of our service question customers are using it for non-IT use cases at the moment, which is a great sign that is happening. Two other things, maybe one, you see we are a leader in our enterprise service management wave.

The analyst community continues to recognize us as a leader and a visionary, but also a significant challenger and growth brand. And we continue to see a lot of migration from legacy service management platforms onto service collection for much higher ROI much better cost equation with a much more modern stack and user experience, and that is really great for us. Lastly, and it should not be last. It is definitely not the most minor. We only GA'd our customer service management app inside the last quarter. So that is delivering great efficiency results for us in running parts of our customer service, as we have said.

And very early in that journey, but really excited about how that can continue to grow the service collection as it continues to power a large part of the license growth.

Operator: Your next question comes from Raimo Lenschow from Barclays. Please go ahead. Perfect. Thank you. Thanks for squeezing me in.

Raimo Lenschow: I have a question on the DC price increases and the gap we have to Jira cloud now. Like, how do you think about that in terms of as an incentive to move? Do you think there is further action in the this can help you there to kind of accelerate that journey? And then I had one quick follow-up.

Joe Binz: Yeah. Thanks, Raimo. You know, from a pricing perspective, on the cloud, you know, we invest quite a bit in R&D. And we are consistently delivering a lot of innovation and value to our customers. And that fundamentally allows us the opportunity to increase prices over time, commensurate with that value delivery. We may do that through pricing packaging of premium SKUs or through list prices. In either case, our prices today remain significantly below many of our software peers and competitors across our portfolio. And because of that and the pace of innovation and value delivery, on mission-critical workflows, we still feel we have plenty of headroom for further pricing.

In terms of data center, we will ensure that any price changes on data center going forward fit into the deliberate and planful approach we are taking in providing the right incentives at the right time to help customers upgrade to the cloud. Overall, however, we believe we remain competitively priced just relative to the value we deliver and competitive alternatives in that space as well. So that is how we think about the pricing perspectives, in terms of the interplay between cloud and data center.

Raimo Lenschow: Yes. Okay. Perfect. Thank you. And then I have one question. I might have missed it, but did you talk to the 20% revenue growth CAGR? Or did you could you clarify that? Because I had a couple of questions from the from the other audience if you kind of reiterated it or not.

Joe Binz: Yeah. Sure, Raimo. There is no change to our midterm outlook calling for 20% plus compounded annual revenue growth through FY 2027. I would say the same thing for our 25% plus non-GAAP operating margin commitment in FY 2027. We remain confident in our ability to deliver healthy and accelerating cloud revenue growth. As we expand operating margin over time. And I would also highlight that with respect to our short-term guidance for FY 2026, we do continue to take a conservative and risk-adjusted approach. So that is the way to think about that.

Raimo Lenschow: Thank you.

Operator: That is all the questions we have time for today. I will now turn the call over to Mike for closing remarks.

Michael Cannon-Brookes: Thank you, everyone, for joining our call today. Thanks to all of the Atlassian Corporation teams for delivering a truly fantastic quarter. And as always, we appreciate all your thoughtful questions and continued support. From the investor and shareholder community. Have a kick-ass weekend, everybody.

This article is a transcript of this conference call produced for The Motley Fool. While we strive for our Foolish Best, there may be errors, omissions, or inaccuracies in this transcript. Parts of this article were created using Large Language Models (LLMs) based on The Motley Fool's insights and investing approach. It has been reviewed by our AI quality control systems. Since LLMs cannot (currently) own stocks, it has no positions in any of the stocks mentioned. As with all our articles, The Motley Fool does not assume any responsibility for your use of this content, and we strongly encourage you to do your own research, including listening to the call yourself and reading the company's SEC filings. Please see our Terms and Conditions for additional details, including our Obligatory Capitalized Disclaimers of Liability.

The Motley Fool has positions in and recommends Atlassian. The Motley Fool has a disclosure policy.