Atlassian Corp
SWB:48D
US |
Johnson & Johnson
NYSE:JNJ
|
Pharmaceuticals
|
|
US |
Berkshire Hathaway Inc
NYSE:BRK.A
|
Financial Services
|
|
US |
Bank of America Corp
NYSE:BAC
|
Banking
|
|
US |
Mastercard Inc
NYSE:MA
|
Technology
|
|
US |
UnitedHealth Group Inc
NYSE:UNH
|
Health Care
|
|
US |
Exxon Mobil Corp
NYSE:XOM
|
Energy
|
|
US |
Pfizer Inc
NYSE:PFE
|
Pharmaceuticals
|
|
US |
Palantir Technologies Inc
NYSE:PLTR
|
Technology
|
|
US |
Nike Inc
NYSE:NKE
|
Textiles, Apparel & Luxury Goods
|
|
US |
Visa Inc
NYSE:V
|
Technology
|
|
CN |
Alibaba Group Holding Ltd
NYSE:BABA
|
Retail
|
|
US |
3M Co
NYSE:MMM
|
Industrial Conglomerates
|
|
US |
JPMorgan Chase & Co
NYSE:JPM
|
Banking
|
|
US |
Coca-Cola Co
NYSE:KO
|
Beverages
|
|
US |
Walmart Inc
NYSE:WMT
|
Retail
|
|
US |
Verizon Communications Inc
NYSE:VZ
|
Telecommunication
|
Utilize notes to systematically review your investment decisions. By reflecting on past outcomes, you can discern effective strategies and identify those that underperformed. This continuous feedback loop enables you to adapt and refine your approach, optimizing for future success.
Each note serves as a learning point, offering insights into your decision-making processes. Over time, you'll accumulate a personalized database of knowledge, enhancing your ability to make informed decisions quickly and effectively.
With a comprehensive record of your investment history at your fingertips, you can compare current opportunities against past experiences. This not only bolsters your confidence but also ensures that each decision is grounded in a well-documented rationale.
Do you really want to delete this note?
This action cannot be undone.
52 Week Range |
122.02
272.95
|
Price Target |
|
We'll email you a reminder when the closing price reaches EUR.
Choose the stock you wish to monitor with a price alert.
Johnson & Johnson
NYSE:JNJ
|
US | |
Berkshire Hathaway Inc
NYSE:BRK.A
|
US | |
Bank of America Corp
NYSE:BAC
|
US | |
Mastercard Inc
NYSE:MA
|
US | |
UnitedHealth Group Inc
NYSE:UNH
|
US | |
Exxon Mobil Corp
NYSE:XOM
|
US | |
Pfizer Inc
NYSE:PFE
|
US | |
Palantir Technologies Inc
NYSE:PLTR
|
US | |
Nike Inc
NYSE:NKE
|
US | |
Visa Inc
NYSE:V
|
US | |
Alibaba Group Holding Ltd
NYSE:BABA
|
CN | |
3M Co
NYSE:MMM
|
US | |
JPMorgan Chase & Co
NYSE:JPM
|
US | |
Coca-Cola Co
NYSE:KO
|
US | |
Walmart Inc
NYSE:WMT
|
US | |
Verizon Communications Inc
NYSE:VZ
|
US |
This alert will be permanently deleted.
Good afternoon, ladies and gentlemen. Thank you for joining Atlassian's earnings conference call for the second quarter of fiscal 2019. As a reminder, this conference call is being recorded and will be available for replay from the Investor Relations section of Atlassian's website following this call. I will now hand the call over to Ian Lee, Atlassian's Head of Investor Relations.
Good afternoon, and welcome to Atlassian's Second Quarter Fiscal 2019 Earnings Conference Call. On the call today, we have Atlassian's Co-Founders and CEOs, Scott Farquhar and Mike Cannon-Brookes; our Chief Financial Officer, James Beer; and our President, Jay Simons.
Earlier today, we issued a press release and a shareholder letter with our financial results and commentary for our second quarter fiscal 2019. These items were also posted on the Investor Relations section of Atlassian's website at investors.atlassian.com. On our IR website is also an accompanying presentation and data sheet available. We'll make some brief opening remarks and then spend the rest of the call on Q&A.
Statements made on this include forward-looking statements. Forward-looking statements involve known and unknown risks, uncertainties and other factors that may cause our actual results, performance or achievements to be materially different from any future results, performance or achievements expressed or implied by the forward-looking results. 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. Further information on these and other factors that could affect the company's 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 Form 20-F and quarterly report on Form 6-K.
In addition, during today's call, we will discuss non-IFRS financial measures. These non-IFRS financial measures are in addition to and not a substitute for or superior to measures of financial performance prepared in accordance with IFRS. There are a number of limitations related to the use of these non-IFRS financial measures versus their nearest IFRS equivalents, and they may be different from non-IFRS and non-GAAP measures used by other companies. A reconciliation between IFRS and non-IFRS financial measures is available on our earnings release, our shareholder letter and in our updated investor data sheet on our IR website.
I will now turn the call over to Mike for his brief opening remarks before we move to Q&A.
Good day, everyone. Thanks for joining us today. Q2 was a beauty, a great way to cap off 2018 as we surpassed $1 billion in calendar year revenue for the first time. In Q2, we had $299 million in revenue, up 39% year-over-year. For the quarter, we also generated more than $122 million worth of free cash flow. In October, we closed the acquisition of OpsGenie, a leader in incident alerting and on-call schedule management. We're tremendously excited to have them join the Atlassian family as we double down on IT teams this year.
IT organizations big and small are becoming more service driven and agile oriented and as technology becomes the key ingredient for growth and survival of nearly any business. We're excited about the role we play in helping IT drive that transformation, and OpsGenie plays a key role in strengthening the service and response muscle for IT teams across the Fortune 500,000.
During Q2, we also acquired Butler for Trello, one of Trello's most popular integrations. Butler gives Trello users the ability to work smarter and faster by bringing the power of workplace automation to their Trello boards. Individual users can shrink multiple steps into one, will have things like user assignments or status change based on triggers or rules that they set up themselves. It's a superpower that we're excited to bring to the millions of daily Trello users.
I'm also excited to share that JIRA Software recently surpassed 65,000 customers. This is more customers than the entire company had when we went public just three years ago. Including OpsGenie, we ended Q2 with a total customer count of more than 138,000. We provided more detail on these announcements along with many other updates in our earnings release and shareholder letter that was issued earlier today.
And with that, I'll pass the call to the operator for Q&A.
[Operator Instructions]. The first question comes from Bhavan Suri with William Blair.
I guess I just want to touch on a couple quick things, and I had just 1 question but with two small parts. When you think about the quarter specifically, I love to understand sort of the impact pricing changes had in terms of pull forward and sort of what the impact of that might have been, just some quantitative and also qualitative commentary on sort of how that played out to the customer behavior you've seen in the past year given the pricing increase, what they thought, share and et cetera, and then the pull forward.
Thanks, Bhavan, for that question. The first thing that I really like to emphasize is that our key top line metric that we focus on to measure our business continues to be revenue. And that's because we are not like most traditional enterprise software companies in that the significant majority of our business is made up of either monthly or annual subscriptions or annual maintenance contracts. And we expect this to be increasingly the case as our customers continue to choose our Cloud and Data Center offerings. To further emphasize this point, again, unlike many other software companies, multiyear deals are only a tiny fraction of our business while pull-forward activity, by our customers, ahead of a Server price increase, drives really just a timing difference rather than a change in the scale of our relationship with that customer.
So as a result, we very much believe that revenue is a best reflection of the underlying customer demand for our business when you consider our performance over time. But more specifically to address your question around pull-forward activity, as we indicated on the call last quarter, we did see a significant volume of Q2 transactions coming in ahead of the Server price increases taking effect. And this activity came in the form of both early annual renewals and multiyear renewals. So this pull-forward activity, in essence, replaced what would otherwise have occurred in the second half of our current fiscal year or the following 2 fiscal years as well. In terms of the part of your question around the customer behavior and so forth, again, as expected and I must say I'm pleased by the overall reaction to the price increases that we've had from our customer base, and I think that's illustrative of the way we roll out price increases. We give lead time. And of course, accompanied with those price increases are very significant improvements in the product. We're investing heavily in our product every month, and this comes through in some sort of value we create for our customers.
The next question comes from Nikolay Beliov with Bank of America.
I just had a pretty basic question for the team. You've highlighted 65,000 JIRA Software customers. Can you please remind us roughly the split between JIRA Core and JIRA Software? And right now, where do you think is the penetration of the potential market for JIRA Software? Are we in the second inning? The fourth inning? Just wanted to get the opinion of the team.
Thanks for the question. It's Scott here. We don't break out JIRA Core and JIRA Software. But I think JIRA Core is a relatively recent offering for us, and it's still growing. So it would be safe to say that the majority of our revenue in the JIRA broadly, JIRA family comes from JIRA Software and JIRA Service Desk, and that's still the majority is JIRA Software. From -- I think your -- what was your second question, was around are we in the third, second or third or fourth inning? I think that's an American term. I think you have to translate that to like a cricket term, are we in the third day of the test I guess. And for us, like the way I think about it is the software market is growing incredibly fast, so every company is becoming a software company. So the market itself is growing very fast. We are growing or continue to grow our customer base within that market incredibly well. And then we're also growing our share of wallet within our customer base as we do more things for them such as OpsGenie, which we talked about; the JIRA Service Desk. And we also, as we start going adjacent into more likely teams, we're seeing that as a sort of a new market opportunity for us as well. So I feel very good about the -- both the TAM and the relatively small penetration we have within that TAM today.
And just to add 1 point on to what Scott was saying there, the U.S. Bureau of Labor Statistics recently came out with some data estimating that the number of software developers in the world is going to be growing 24% annually through 2026, so a very interesting illustration of the future potential.
Got it. And James, quick question for you. Long-term deferred revenue increased sequentially quite a bit. We haven't seen that in a while. What drove that? And what do you think the forward trends will be in the long-term DR over the next couple of quarters?
Yes. Well, as you say, long-term deferred revenue sequentially was up around $14 million, and that certainly is a larger bump than we would usually see from 1 quarter to the next. And that was very much driven by this pull-forward activity that I was referring to earlier, in particular, obviously, the multiyear part of that pull-forward activity because the long-term deferred revenue represents activity that will be earned into revenue beyond 12 months from now.
The next question comes from Heather Bellini with Goldman Sachs.
This is actually Ted Lin on for Heather. I was wondering if you could just give us an update maybe on your overall philosophy on pricing. Historically at the teams, like you've gotten a lot of people in at a very low price to help improve willingness to pay. And so for a lot of your customer base, it's pretty high value-to-cost product. So how do you capture more of the value that you're customers are getting longer term?
Yes. This is Jay. So I think you captured the philosophy in your question that we believe in providing incredible product in the most affordable price. That's been consistent through the company's history. We also believe on creating opportunities to land inside of customers where we remove prices as part of the friction. And so in OpsGenie, you'll notice that in October, shortly after close, we lowered pricing, introduced a free plan. We are transparent with our pricing. So across the spectrum of what customers can buy and how they grow with us, we basically share those price points so they don't have to ask. And that's effectively the philosophy. Where we work to participate in greater share of wallet is in adding more capability and more premium features that support enterprises as they scale with us. And so we've done that in the context of the data center product family, which we've talked about as growing nicely and continues to grow in the cloud. We've done that in the context of access, which is effectively a premium capability that supports a stronger identity and security management for customers.
And I guess, on the core, given the strong outperformance and the strong pull forward that you saw, how should we think about kind of that impacting the shape of the seasonality of deferred revenue and billings kind of for the rest of the fiscal year?
Well, I would just sort of reconfirm that, that pull-forward activity would have come from both the second half, both quarters of the second half of this fiscal year as well as the 2 subsequent fiscal years, fiscal '20 and '21. And you're right. By looking at that sequential part of both short-term and long-term deferred revenue, you can get something for a steer as to the balance of where that pull-forward activity came from.
The next question comes from Ittai Kidron with Oppenheimer.
Couple of questions for me. First of all, since you know how many people pulled in revenue, can you roughly tell us what was billing growth without this pull-in effect? And then the second question, more in the competitive front. Now that GitHub is part of Microsoft, you haven't talked much in your prepared remarks about Bitbucket. But can you tell us if anything is changing competitively? How's momentum in that business? Is anything changing out there in the marketplace?
Yes, just briefly to the first point. I'd just sort of reemphasize our focus on revenue as the top line metric that we factor to really understand the underlying relationship with our customers at the time. Scott, are you going to take the second one?
Yes, I think you have -- acquisition from Microsoft, we haven't seen any material change this quarter in the competitive market. We believe what we have said previously, which is that Microsoft's primary goal in acquiring GitHub was to get more of their developers into Azure, and that's what we continue to see to be the Microsoft focus. So there's no real change in the last quarter on that front even with the changes in how they price GitHub.
The next question comes from Keith Weiss with Morgan Stanley.
I was hoping to sneak in two questions, 1 on OpsGenie and kind of the competitive environment that you see out there, where kind of like the combined offering that you guys are bringing to market is going to sort of be able to gain some competitive advantage. And then on -- maybe one for James on the operating margin side of the equation. Also like a really impressive quarter for operating margin. You saw some real nice year-on-year improvement. The guidance doesn't have that. The guidance is a much -- kind of more muted year-on-year comparing terms of operating margins. Can you talk to us a little bit about sort of where those areas of investment are and sort of why, on a year-on-year basis, it would will be so much lower kind of improvement on operating margin in Q3 versus Q2?
Scott here. I'll take the question about the OpsGenie in the competitive market. We feel incredibly bullish and excited about the market for incident management. If you -- so those of you who are sort of new to the story, as developers move their workloads to the cloud, as companies become more -- -- or the software company, developers are increasingly being on call. They're responsible for making sure that their code, it stays up to your production and performance. And when it's not, they need -- the company's being weighted with alerting their developers and coordinating responses. Now the responses could be around down time. They could be around security incidents, all these things that are involved when you're running a code at scale in the cloud. And OpsGenie offers a response and plays in that space, and we've been really very bullish about that. We have OpsGenie that does the incident alerting part. We have JIRA, which handles a lot of the tasks before and after, and we know JIRA is the way that our work gets done in organizations. And so putting those 2 things together is very powerful. And we also have StatusPage, which is the leading provider of -- StatusPage is on the web that need to get with your customers if you're having downtime. And so when customers have problems, they want to know that something's up with the provider, and we use StatusPage for that. So that combination of those three products is, in my opinion, unmatched out there in the market, and we're really bullish about bringing those together.
Excellent.
And Keith, on the margin side of things, let me handle that. In Q2, obviously, we did see a strong operating margin really driven by some nice performance on the revenue line. And then on the spending side of things, both in the cost of goods sold, we saw some nice benefits there as we continue to work on the efficiency and effectiveness of our hosting expenditures. On the operating expense side, I'd point to some timing issues around the arrival of additional headcount and also some lesser-than-expected spending around certain professional services. So all of that combined to drive the Q2 result. And as you note, we are expecting margins to be lower in the back half of the year. So as you think about the Q3 story, there are a few different things driving that. First of all, Q3 is when we issue additional salary increases to our team, and so that begins to kick in. And also, Q3 represents -- so the calendar year, obviously, and therefore the payroll tax reset associated with our employee expenditures.
And in addition to that, as we talked about on the last call, we've really been putting effort and investment into our hiring engine if you will, and we're pleased with the progress that we're making in that regard. And so while we increased our employee count substantially in Q2, I would expect -- obviously, about half of that was driven by OpsGenie. I would expect the organic level of headcount to continue to increase in Q3 as we particularly invest in our R&D-centric model. And within the R&D area, we see a lot of different opportunities, obviously, right across our business, but I would particularly point to our Cloud products as a whole, to our work on our Cloud platform, which you can think of really as us developing common componentry that we'll utilize across the different cloud services. Of course, this will allow us to build cloud services more efficiently and more quickly as well as helping us adjust our ability, improve our ability to deal with larger deployment sizes while continuing to enhance our security and privacy, compliance requirements, that sort of thing. We've talked a lot about the IT market opportunities, so we'll particularly investing there. I'd call out OpsGenie as one clear example in that arena. And then I'd also point to the data center offerings for our on-premises customers. We've been very pleased with the growth rate in recent quarters there, and I would expect that to continue into the future.
The next question come from Richard Davis with DG Financial.
CG, but that's okay. So I think it was like 85% of your new customers came on as cloud subscribers. Is there any difference in lifetime customer value for cloud customers versus on-premise? I'm sure there's a different shape in the profitability, but I've just always wondered about that.
Richard, this is Jay. Not materially. I think as we've mentioned before, Cloud is a little more expensive than Server. We also have the ability to operate Cloud a little differently than we can in Server because we have kind of visibility into how the product's being used and we have kind of different avenues that we can leverage for cross-sell and expansion and kind of connecting to the customer kind of in product to open up different paths and avenues for cross-selling and other products. But from a lifetime value, I think they're pretty comparable, and that's seeing some strengths, I think, that the products provide themselves and the value they provide to customers.
Richard, this is Mike. Just chipping one thing. When Jay says the customer lifetime value is comparable, he means on a customer potential basis. So we tend to calculate, for example, if someone is a 50-person company, going wall to wall in that company, we can sell 50 seats. If someone is a 50,000-person company, we can potentially sell 50,000 seats. So for the size of the company, our potential return or lifetime value is equivalent. Generally, the larger the company, the less likely they ought to choose cloud today. But obviously, that's changing on a sort of on a timescale basis if that makes sense.
The next question comes from John DiFucci with Jefferies.
This is Zach Lountzis for John. Could you talk a little bit about the Slack partnership, how it's going, the transitions from Stride and HipChat? And then any changes there competitively with Microsoft or anyone else?
Mate, I can talk to that. It's Mike. Sure. Look, it's going -- I'd say the partnership's going very, very well. We have a great relationship there. We continue to work together and build out features and functions that help joint customers across our product portfolios to have the best experience that they can. We continue to move through the transition and migration period for HipChat and Stride customers. Again, there's about 1 month and a bit left at that, so we continue to work with big and small customers to help them migrate and to get into that future world. I don't know if we have anything else to call out on the go-to-market side there, but it's been going pretty well so far.
And then, James, if I could, the -- you guys raised that convert a few quarters ago. You're at like $800 million or something in net cash today. I was wondering how you guys think about the positioning there going forward? Any additional raises that you might be looking to make and what the ideal balance is really?
Yes, I think the converts as well as our ongoing free cash flow generation provides us with substantial financial flexibility. So we're very pleased by that given the scale of the market opportunity that we have in front of us. So we're obviously very pleased with, in particular, the continued progression of our cash flow results.
The next question comes from Michael Turits with Raymond James.
On the upside on the billings, how much of it was in addition to pull forward? May have been -- is there any particular shift to more data center and multiyear contracts either at data center or on maintenance?
Yes. Mike, I wouldn't point to anything in particular other than what I've really commented on already. So remember that the price increases really applied to our Server business. We did not increase prices on the Data Center business. So it was really much more that part of the overall platform that we offer that was driving the pull forward.
Got it. And then also a strong quarter on the other line, which includes marketplace. Anything that suggests any particular inflection there?
Yes. We were very pleased with the marketplace performance as we have been now for a number of quarters. One additional accounting element sort of in terms of a technical issue is that pull-forward activity related to our customers buying marketplace apps. Our portion of those purchases drop straight into revenue in the quarter that they occurred since we've already satisfied any conditions that we need to be able to execute on at that point.
The next question comes from Rishi Jaluria with D.A. Davidson.
Two quick ones. First, just the stat you gave around cloud customers, that's definitely really impressive. It's nearly 75% of total customers. Can just give us a sense for how this number has directionally trended over time? And where do you think it'll end up over time, especially given that 85% of net new customers were cloud customers? And I got a follow-up.
Look, I can answer that. I mean, directionally, it's clear in the numbers. As I said, it's more than 85% of new customers come into the cloud. I would say we expect that to continue to trend upwards as companies increasingly -- fundamentally, if you zoom out, the cloud can provide a better offering than I think most companies can run themselves, right? It can be more secure. It can be faster. It takes away the operational management hurdles. You don't have to upgrade it. So there's inherent obvious advantages in the cloud. Our belief is it's going to be a decade-long transition. And the majority, the vast majority of software will be run in the cloud. So we're seeing 85% plus of new customers coming in choosing that. It's logical that our overall customer base would trend to that and then continue to trend upwards as that's the case. At the same time, we don't force migrate customers. It should be very clear. We are pro-customer choice, and there's a significant number of companies for whom that's not their choice. That is a distinct advantage of Atlassian over a pure cloud vendor, is that we can provide a better, more holistic offering as companies go through that transition internally over the next decade.
That's helpful. And then one follow-up for James on the gross margin guidance. I guess just how should we be thinking about why implied Q4 gross margins should be dropping from where they are? And then with the AWS migration being done, what should the longer impact on gross margins be?
Yes. So in the back half of this fiscal year, we'll continue to be investing in some of the data center infrastructure in Asia Pacific in particular, so that will drive some additional COGS for us. Over the longer term, obviously, as Mike was just pointing out, we would expect cloud to continue to steadily grow as an overall proportion of the business. And we know cloud comes with lower gross margins than the -- behind the firewall platform offerings that we have because, obviously, we're doing the hosting work, whereas behind the firewall, our customer is paying for that activity.
The next question comes from Keith Bachman with BMO Capital Markets.
I had two quickies and a longer-term question. But was there any inorganic help or was the inorganic help in any way material in the quarter you just reported? In addition, Europe looked like it had some strength there. Was there anything you wanted to call out in Europe as being unusual? Or what was the driver of strength? And then I'll wait to ask my follow-up.
Yes. So in terms of inorganic activity, we closed the OpsGenie transaction at the start of the quarter. And when we announced that transaction, we indicated that it would drive around 1 point of revenue growth for us during fiscal '19. So that would be the only factor we would have got a full quarter effect of OpsGenie on the revenue side there. In Europe, what I would point to there is that our channel is a very important component of our distribution generally. And indeed, around half of our channel partners are in Europe, so it's a particularly important part of our European distribution business. And those channel partners in Europe in particular worked effectively with our customers around some of the pull-forward activity that we spoke of earlier. And some of that activity, I mentioned the marketplace activity in an earlier answer, does drop immediately in the quarter to revenue. So that would have also benefited that EMEA growth rate that you see.
Okay, fair enough. And then the question I wanted to ask, again, directional and philosophical, is when you're thinking about your revenue growth profile, there's a few things that impact it. One is prices. The other is mix. But I'm just also trying to understand how we should be thinking about subscriber growth as being a driver of future revenue growth. And is there any kind of metrics that we should be thinking about? Is it the key driver of your growth going forward? Or just any kind of categorization of how that impacts the top line.
I can talk about that, I guess, philosophically. Look, we've been very clear that we have a lot of different growth sectors in our quite unique business. And that's a constant challenge, intellectual challenge for us to manage between the different levers. But I've think we've done, if you look at our history, a pretty good job so far. When we talk about that, obviously, you get the headline customer number, which was past 138,000, which is a great number. But that only means that, that is a singular domain, and I think it was a singular company that's becoming like a customer. They then have a lot of different ways to grow. As you've seen us over time build out the portfolio, as we add more products, there are more things that, that particular customer can buy. Secondly, obviously, the customers themselves can grow inside the product that they're already in.
So if they land in JIRA Software, they land in Trello, they're on Confluence, they can just literally add more of their company to that. So if they've got 10,000 employees, they might start with a 50-person team somewhere. And our job is to continue to deliver value to them over time so that they will grow into 100-person customer for us, then 1,000-person and hopefully to a 10,000-person customer. And that's just within our stable. The other thing obviously is things like the marketplace, which has been called out a couple of times in the call, which is an ability for that customer to grow outside of things that Atlassian builds. And we provide the platform for that to connect those vendors and the great ecosystem we have with those customers in a transactional way. And then last year, you've seen us, I would say, judiciously exercise our acquisition model over time as another way for the business to grow. So the headline customer number, 138,000, is a very good one, but we have a lot of ways to grow those customers within that number.
The next question comes from Jonathan Kees with Summit.
It was indeed a ripper of a quarter, and that's impressive given the gloom in June. And you see in the headlines. You read in the headlines in the news. I guess my question is more what concerns you in terms of the macro issues. Or are you not seeing much? I would think you at least encounter stuff like the government shutdown. You do have exposure to government, the federal business. There is indications of IT slowdown, and that would impact software. You obviously don't manufacture in -- stuff in China, so that doesn't impact you. But in general, what are the macro issues that you're seeing and that concerns you?
Yes. Jonathan, I'll take that one. We aren't seeing anything specific in terms of macro weakness. As you point out, our exposure to China is really immaterial. And while we certainly wouldn't say that we're immune to a recession, we also believe that, as was quoted back around the IPO times, that our business is very much built for stormy weather. So the company has been able to very nicely weather the last 2 recessions. And I think our low-cost, high-value model is a big driver of that. And another thing to consider, of course, is that the way we distribute our product, it's really chosen by the end users rather than sold top down and pushed onto those users. And so feel good about the business model's ability to withstand a dip economically.
Okay. All right. That's helpful. If I can ask one other question, you've mentioned that, James, that obviously, margins could be going down in the second half, specifically operating margins. Sales and marketing ticked up substantially on a sequential basis there and actually over the last several quarters. Is this going to be the new norm? I know in the past, you've talked about initiatives to try to promote Trello, focus on that first, launch across the world and then focus on monetization later. Are we talking about who are going to be seeing increased levels of sales and marketing going forward even beyond second half?
Well, on the call last quarter, we spoke about the fact that we were going to enter into a specific marketing campaign around OpsGenie in combination with, as Jay was discussing earlier, the price reductions that we rolled out into the marketplace. And you may have seen some of that activity around the country. So that was a big focus of Q2. And I would say that we do have some plans for the balance of this year to continue to push on that IT market opportunity. The other thing that I would point to is Jira Software cloud was relaunched just back in October, and Jay and his team have been putting considerable marketing effort behind that as well. So I wouldn't necessarily draw a long-term trend around the current level of activity in sales, marketing arena, but we're very pleased with the investments that we've been making there and expect to make for the balance of this fiscal year.
The next question comes from Derrick Wood with Cowen and Company.
Great. And I guess, on that comment, the relaunch of the Jira Software Cloud and the increase in the user scale capabilities with JIRA and Confluence, I'm curious, are you seeing increased interest from your on-premise base looking to migrate to the cloud? Or you generally see kind of the cloud versus the data center base swimming in two different lanes?
Yes. Derek, I'll take that. Migration between server -- from server to cloud has been kind of ongoing with -- as different segments to the market, to the point that Mike made earlier, moved to cloud for all of the advantages that Mike described. We also kind of opened the aperture on cloud to support larger companies where we moved kind of, as you noted, the user limit increase from 2,000 to 5,000 for JIRA Software. And Confluence, Confluence as we do that, it will open up the opportunity for larger customers to move. The data center business continues to grow for companies that, for reasons that they're choosing, want to remain on server but run our products at scale to support thousands to tens of thousands of users. And so I think the way we think about server and cloud still is celebrating the choice of a customer to run the product where it best fits them but provide incredible value in both server and cloud to support where they want to go and where they want to move to.
And then can you give us some color on what the reaction has been from your installed base on the OpsGenie acquisition? And I guess, given the price reduction, are you already starting to see transaction volume move significantly higher? Or is there some time needed to digest the offering?
Derrick, well, we've been -- it's Scott here. We've been very pleased with the response to all the things we've done. We've acquired OpsGenie. We've rebranded and we changed pricing. We put advertising dollars behind it. We've improved the integration to the rest of our products. So we've been happy with all the results that have come from all those things. We do have examples of many people in the base who have moved from competitive products to OpsGenie purely on the basis of our acquisition and knowing that the increased integrations will come over time. So we're already seeing some of that earlier on. And so overall, we're very happy with how that's working out.
The next question comes from Jack Andrews with Needham & Company.
It's Khanh Ngo filling in for Jack today. It seems that a majority of the IT first responders are still relying on legacy tools like Excel to manage their loading system. So what gets IT users to shift behavior to next-gen tools like OpsGenie? And how far away are we from seeing like a critical mass of users rely on software to automate their loading processes?
I'll take that again. It's Scott here. Look, we've experienced this over a long time. The majority of people 10 years ago were using spreadsheets to manage their software development process too. And as people had to move at a faster pace, those people have to be more collaborative, we see the shift to tools dedicated to this purpose. And we'll see that. We are seeing that today with, I think, first responders. There's a large number out there. And as you have to be more -- if you have to be quicker in response as you have to run more cloud services and increasingly, you become more of a software company, bringing software to your customers, those things need to change. And so I would say there's two areas of this.
One area is still moving from spreadsheets. Obviously, that's a huge opportunity for certain people that just aren't first responders today. Many corporate IT, they don't make change very often. They'll release once a quarter or once a year. Internally, it's a very convoluted release process been on in public cloud. And then as a result, when things don't change, they break away frequently. But we all know that these days the pace of change in the environment is increasing. People are using cloud products. And so whether you're internal IT teams or you're producing software for your customers, that pace of change means that you're releasing more often, you're going to have more downtime. And all those things drive the need for products like OpsGenie to help responders. So our views is like there's a lot of different areas that are going to be growth opportunities here not -- even for people that aren't using spreadsheets today.
Okay, that makes sense. And as the features and integrations between Jira Ops and OpsGenie kind of converge, how does messaging around IT change? Do you guys go to the -- try to solve more of a platform solution, kind of emphasizing the synergies that having multiple products bring to the IT user?
Yes, that's a really great question. We've now been known for 15 years now of being amazing for software teams and providing all the products that software teams need to get their jobs done from Confluence that handles requirements and documentation all the way through. And over time, we've seen IT teams start adopting those products as well, particularly in the software business but also the JIRA Service Desk across their help desk environment. They'll use Confluence, IT run sheets and run books. So we've had a deep presence in IT for a long time, but what we're seeing now is as we provide more of a solution, we're becoming more of a trusted vendor at a high level of the organization, COOs and down. So we now also are seen as a trusted vendor to provide most, if not, all of what they need in their IT teams. So that's the sort of market shift that we're seeing at the moment.
[Operator Instructions]. The next question comes from Patrick Walravens with JMP Securities.
Can I step back and ask how you guys think about when you should build it yourself and when you should buy it? And maybe you can use OpsGenie as an example.
I'll take that one. Scott here. We have a strong bias to building things. We've got a long history of building -- bringing products to market. We brought Bitbucket server to market. We brought Confluence, JIRA, JIRA Service Desk, Jira Ops. There's a lot of products we bring to market. So that's our strong preference. We also have -- beyond that, if we -- the time-to-market aspect is really the reason we would opt to bring something in, where we want to move faster or there's an existing product out there. We also have a very strong marketplace. And where there's an existing solution in the marketplace, where we believe it's something core to our customers, we'd lean towards acquiring something from the marketplace rather than trying to compete with them. So we sort have a preference there to make things rather than competing with our marketplace. And then down towards that, yes, there's a time-to-market area, we will move to acquire something. On the acquisition side, we've got a very strong track record of success there in terms of products and making sure that they're successful inside the organization. And that comes from our strong bias on acquiring companies that have a strong cultural fit with Atlassian, a strong business model fit in terms of bringing high-volume, well-priced products and also having a fit with our customer base. And OpsGenie fits -- OpsGenie specifically, that fits very strong in all three of those, great cultural fit, perfect business model alignment and fits right into the customer base and the next thing they need to buy.
And do you guys have -- are there still major gaps sort of functionally for IT ops? Or do you have most of what you need now?
I'd say that's an interesting question. I'd say we provide a huge amount of what IT do today. So if I think internally the areas we're focused on, one is that we're changing that perception. So people do turn to us and will choose stable products and see what we already have to serve them. But we are also building and investing. We have a huge R&D investment to tackle the areas we don't have at the moment, and some of those are very small adjacencies on top of the platforms we already got. And you see with JIRA, we -- JIRA, we got this incredible platform in JIRA that handles all the workflow. And often is the case of just targeting specific workflows, I'd say, on top of the platform that we've already built.
Okay, this concludes our question-and-answer session. I would like to turn the conference back over to the management team for any closing remarks.
Thanks, everyone, for joining our call today. We appreciate the time and look forward to keeping you updated on our progress. Thanks a lot.
The conference has now concluded. Thank you for attending today's presentation. You may now disconnect.