Everybody, welcome. Thanks for being here, all of you guys, and especially the three people here that I've known for a long, long time. All right, Dynatrace, without further ado, we've all been waiting for. I've been waiting for this because it's such an interesting time for you guys. Rick McConnell , CEO, Steve Tack, Chief Product Officer, and Noel is down in the front. Thanks, Noel, for being a continued supporter of this conference. All right, I'll go back and forth between you guys, but Rick. I mean, this has been a multi-year journey, and it's not always the straight line that we all want.
When you sit here today, your conviction around this growth that we all think that you guys can doâwhy are you so convinced that I would even start, better days are in front of Dynatrace, and the best days are in front of Dynatrace?
Well, first of all, thanks for having us. We're delighted to be here, and thanks for your support over the course of those years. It's been awesome. The starting point, I think, always with regard to whether you believe in a company has to be whether you believe in the market.
Yeah.
I think without a doubt, to some extent, even irrespective of what happens to Dynatrace, observability is a market that will benefit from tailwinds from AI.
Yeah.
You have more cloud, more AI, that results in more data, more complexity, and more requirements for automation. In an AI world that is driving toward agentic that are developing code, agentic that are monitoring code, agentic that are monitoring overall software workloads, and then automatically repairing or auto-remediating those, this is a very sophisticated task ahead, and it involves the assimilation, monitoring, evaluation, and analytics associated with billions of interconnected data points in real time with context. Market is number one. Number two is really Dynatrace, and we believe that in the case of Dynatrace, we have an architecture that is perfectly tuned in many ways for the complexity that we see.
Yes.
It has extraordinary scale with an integrated data lakehouse called Grail, has logs, traces, metrics, business events, real user data, whatever, all kept together in a single data lakehouse that can be accessed for context, and then that can be analyzed using deterministic AI analytics to get to an actual answer, not based on correlation, but based on causation. Once you have confidence that you know exactly what is happening in your software environment, you can then ask agents to take action. There is no short answer to your question, but I would say if you go through market, check. If you go through Dynatrace's architecture, check. If you go through various metrics like gross retention in the mid-90s, these sorts of elements, you see customers use our product, they love using our product, it has become indispensable in their overall working environmentsâthat is a check.
Yep.
It is on us then to deliver the monetization of the road ahead.
Yeah.
I am excited about our ability and opportunity to achieve that.
Excellent. Steve, I am going to have a question for you in one second.
Sure.
But just on the most recent quarter, it was slight beat, reiteration. I think what I appreciated with talking to you guys is, I think you thought internally it could have been a better quarter.
Yes, it did.
There were certainly some things that did not play out probably as you expected. You had some slipped expansion deals. There is always a timing thing with these big enterprise deals. As you sit back and reflect on the quarter and as you think about the back half of this year, has there been any more visibility on what is going on in these enterprise buying cycles? And sometimes, whether it is an expansion or renewal, it is always hard, I understand that. But is there any more telemetry that you guys have on the buying environment that gives you confidence for the back half of the year?
This is always going to be one of the challenges, I suppose, in large enterprise buying cycles. It is always the case, as you might imagine, that we go into a quarter with an understanding of the pipeline and understanding the close rate to achieve it. Candidly, we have been, over my five years with the company, very, very consistent in delivering against that.
Yeah.
In the last quarter, we saw some lightness in net new ARR, and it was just because more of the deals slipped into the next quarter than we expected, so that is how we called it. But we do not think that there is anything fundamentally wrong or at risk in the business. We see all the fundamentals lined up. In particular, if you look at Q1 and Q2 combinedâ
Yeah, Q1 was great.
We blew up Q1, 41% net new ARR growth. Q2 was flat net new ARR growth, but combined 17% net new ARR growth. If you had told us that at the beginning of the year, we would have said, "Very, very healthy." Last year was 12% net new ARR growth, up to 17% in the first half. So the question is, can we continue on the directional progression up and to the right in terms of net new ARR growth? That is exactly what we are focused on. We think the market is there, the pipeline is there, the capabilities are there in terms of the product and solution, so that is what we are going to continue driving against.
I lied, Steve. One more question to follow up on that. One of the recurring themes that we're hearing is companies are deploying these FDEs to
Yeah
I think really kind of accelerate some of these deals, because they're big and they're impactful, and there's a lot of decision-making. I know you've augmented your sales force, and you have six -month quotas, and you've sort of limited the number. You've done a lot to your sales force to position them to close deals. Do you think about FDEs? Do you think about incremental things that can be done to accelerate the sort of buying patterns that you're seeing out there?
Yes, is the short answer.
Right.
Just thinking about how do we accelerate buying patterns. One of the breadcrumbs that I've laid out, for example, in the call was pricing. Do we want to contemplate pricing or packaging adjustments or delivery? That's one area. There are a number of levers that we can play. For example, we just acquired Arize, just a month and a half or so ago. Huge opportunity to access the developer. So, adding to a developer persona is a persona and an ICP that we haven't seen in the past, because we've been always focused on selling to the CXO of large companies. The ability to expand in terms of segmentation and how we're attacking the market, I think, is another area.
Short answer, without belaboring all the levers, is we see a number of levers, half a dozen or so really core levers in the business, to be driving and motivating an evolution in the business to go drive activity. One of the other elements that we just delivered, or announced a week and a half ago or so, I guess now, was the partnership with CrowdStrike.
Yeah.
This was, you asked me in your last question, Matt, about, well, have you reflected on certain elements that you could have potentially used to change the dimension of last quarter? One of them, as we saw very late in the quarter, one of the legacy logs vendors started to come back with pricing that suggested, "Well, you can take your observability logs over to Dynatrace, but I'm not changing the price of your overall log environment, even though you're going to take half of it away.
This is where CrowdStrike came in. Very excited to have announced this in their Fal.Con conference in Barcelona, a week and a half ago or so. The result of it was that we can now take Bindplane, which is a telemetry routing capability that we bought back in April, and use that to route observability logs to Dynatrace, SIEM logs to CrowdStrike, and you can take out the legacy log vendor altogether.
Yeah.
I use that simply as an example of the kinds of things we're looking at to remove friction and to basically overcome any hurdles of being able to get customers to where they want to be, which is an end-to-end observability environment. It is that end-to-end observability environment that is necessary. It is sacrosanct. It is needed for an ability to really ultimately get to autonomous operations. Because if you don't collect telemetry and those capabilities into a single integrated system, it is darn near impossible to be able to figure out how you would ever have an agent take action against insights, because you couldn't trust the insights. It is sort of a stat cycle of things that you need to be able to deliver, beginning with end-to-end observability, leveraging deterministic AI, driving agentic action driving toward autonomous operations that we're leading toward here.
I was going to get to CrowdStrike in a little bit, but you prompted the question. Steve, from your perspective, we hear a lot of partnerships. They're all the time. Sometimes they don't do anything. Why is this one exciting for you guys? You've mentioned it, Rick, but from a product, from a customer perspective, do you see tangible benefits that will benefit your ARR growth?
Yeah, 100%. I agree with you. It is tough to find partnerships that work, and they really have to deliver value to the customer. Rick sort of hit on it. When we talked to the CrowdStrike team, they were seeing some similar dimensions that we were, where they're talking about security buyer, we are in there with observability, and there's a lot of things where you need those different worlds to play together. Not necessarily to be one single product per se, but an outage, a breach, there are similar things that you have to solve through that. Part of the real goal is to make sure you have the right data, as Rick was saying, that you can take action and drive answers from.
That's where the ability to get the telemetry, and it's a little bit of a plug, Noel was sharing the recent Gartner Magic Quadrant, a few hours old, about observability pipelines, that was recognizing Dynatrace's ability to deliver across that. Having the right data in the right spot, but then really solving that customer problem, whether it's a breach, whether it's an outage, the ability to drive towards those answers and help them, a lot of what you said, be confident that they can move at the speed that agentic takes, and that they can be confident to continue to drive and invest that way.
The only thing I would add to that, Matt, is that, which I didn't mention earlier, a lot of partnerships, to your point, you make an announcement about a partnership, and maybe nine months later or a year later, you've done some integrations, then you come back and ask about it later and wonder if they actually happened. In this case, there is immediate benefit. There is nothing that needs to get delivered jointly by the product teams in the respective companies, us and CrowdStrike, to be able to take advantage of this. Bindplane can do the routing right now, today, to observability logs to Dynatrace, SIEM logs to CrowdStrike, and with no further integration. So, it's ready to go immediately.
Are there any other go-to-market mechanisms in place that can also accelerate that? I don't know, quota retirement or any incentives on either companies?
Yeah, we haven't. I don't want to get ahead of myself. We haven't done any cross-company quota retirement or anything like that. But, suffice to say, we believe that there is a ton of synergy here. We're linked at very senior levels within the two organizations, and we'll continue looking for ways to potentially work together. Our view is, at the highest level, which is maybe a different 30-minute session.
Yeah
We do believe that observability and security are converging.
Yeah, well, they certainly are, for sure.
We've been very, very consummate, very surgical in our application security strategy that Steve Tack has really been driving for us, which is we've only been investing in areas of security or application security in particular where observability data matters.
Because we don't want to compete against CrowdStrike and Palo Alto Networks and the other major security vendors. It doesn't really make sense for us to do that. But in areas like vulnerability analytics, this is an area that benefits immeasurably from having observability data. These are areas where we can add substantial value to customers.
So it sounds like what I'm hearing is that both companies recognize the opportunity. You both saw shortcomings in your individual products and the combined sort of partnership.
Huge synergy.
is going to be mutual benefit.
Yeah, huge synergy. With very little overlap, which sometimes causes channel conflict or other problems.
Okay. I want to talk a little bit about the whenever I've chatted with you or Jim or others, inevitably it comes to, like, this all sounds so amazing and the telemetry and I think everybody agrees that the market dynamics are really, really strong. Your consumption's growing north of 20%.
Yep.
I think you bring up a good point. I think we all get fixated on the quarterly results, but really, I mean, the first half was a really, really strong quarter, or first strong half of the year.
Yep.
I don't want to get out over my skis thinking about acceleration, but what do you see in the business, the metrics that gives you confidence that better growth could be in front of you? There's some leading indicators out there, but as you sit here today, like, where do you see that confidence?
Well, I think there are many, but let's cover a few of the ones that you had mentioned. To begin, consumption growing in the 20s is a good place to start. You see very, very healthy consumption in the platform. The result of that is that over the course of time, we would expect that ARR and consumption would converge. This is a good indicator. Our pricing methodology with our Dynatrace Platform Subscription is a commit-based pricing model, so it takes a while for a commit, frankly, to catch up with consumption growth, but that just makes consumption even a better leading indicator of what we believe is to come. So driving that is core. Second is logs.
Yes.
A huge business. Three quarters ago, we were at $100 million in logs consumption. We are very close now to $250 million, three quarters later, or two and a half quarters later even. So the result of that is you have a business that is growing north of 100% that is absolutely mission critical in everything that is happening in AI and elsewhere, that now is at scale.
Yeah.
As I sometimes say, when logs was $20 million growing at 150%, it is about a $2.25 billion ARR foundation, and it does not have as much impact as growing north of 100% when it is actually a $200 million plus business. So we think that that is a huge catalyst. And then observability is a core driver. In order to deliver all this agentic and autonomous operations, you need end-to-end observability, and we like to think we do that as well or better than anybody else in the market. And finally, maybe I just point out Arize.
Yeah.
Arize is this business that we just acquired, is very top of mind, very topical for basically every customer that we talk about. And what Arize does, for those of you not familiar with it, is it basically is not focused on the resilience aspect of observability. It's focused on the AI reliability, the efficacy of the AI data. And we believe that both are absolutely critical in the environments to come. You got to make sure your software's actually working. You also need to make sure that the results coming out of LLMs are not going through hallucinations and they're not outside bounds of guardrails, they're not experiencing model drift. And you need to make sure that the agents are actually working the way you expect the agents to work. All of this is a huge catalyst for growth.
I'm going to come to Arize in just one second, but I want to tie two things together, the consumption growth and then this idea of maybe tweaking how customers pay for overage.
Yeah.
You guys have been extremely generous, I think.
We do.
And very customer-friendly. But I think the reality is there's probably, you're probably leaving some value on the table. Give us your You haven't announced anything, but just what is the thought on sort of the overage element of your story? It doesn't feel like it's a back half thing this year, but could it be a next fiscal year opportunity?
So, good catch on the breadcrumbs I was trying to lay out at the earnings call, Matt. Yes, it wasn't an announcement, but we do recognize that our overage plan is extraordinarily customer-friendly.
Yes.
Extraordinarily customer-friendly. The result of that is that we are looking at that to evaluate how do we get that back to sort of middle ground. The result of this is that basically what we do today is we don't charge any premium on overages. Yet the problem is investors, all of you, sell side, buy side, everybody's looking at us for performance based on net new ARR.
Yeah.
Well, overages are revenue, but not ever net new ARR. The problem is you've got consumption growth, which is very strong in the 20s. If a customer is expanding their consumption growth, but then they hit overages, then those overages are not driving net new ARR because they are not driving early expansions. They're resulting in revenue, which is overage revenue, but not even at a premium rate.
Yes.
They're not encouraging either higher commits upfront, nor are they encouraging early expansion.
Yes.
What we're looking at is adding in a premium to overages. This is absolutely market standard, but we're being very cautious about it because our customers are the biggest of the big. They like predictability, they like budgetary management, they don't like penalties. We're going through this process to evaluate how to implement such a thing, but I do expect that we'll probably move in this direction and we'll have more to say about it probably in maybe as early as the next earnings call.
Okay. Yeah, it certainly feels like there's multiple benefits there. I guess, Steve, when you're talking to customers as well, Rick, you guys are, I would almost say, abnormal from an industry perspective. When you're talking to customers, what's sort of your feedback when you talk to customers?
Related to that point?
Yeah.
Yeah. I'd say, back to Rick's point, we are very friendly with that. There is an industry expectation that there would be there. Part of the goal is, from the product team, that we just want to keep giving them more and more reasons and ways to use consumption. So whether it's logs growing, the infrastructure business at the size it's gotten to, new analytics capabilities, new ways of monetizing AI, a lot of my conversations with them are more down that track in terms of how can they better plan and how can they consume more, which obviously ties back into rated consumption and ARR at some point. But no, I think for all those reasons, it makes-
Makes a lot of sense.
Yeah, for sure.
We also are very careful not to be thinking about this in a punitive way.
Right.
We are not doing monthly overages. It is long-term vision and value. We have extensive telemetry and portal access to show people where their consumption is. So they are going to know, "I am going to hit my commit in month 10.
Yeah.
You can plan for it as a result of it. Easy for us to get ahead of it, as long as there is more incentive on the part of the customer to say, "You know what? I do not want to pay a premium for overage, so I might as well just bring my expansion." We think it is-
It is going to hit ARR.
Which goes into ARR, which then
Yeah
has the ability to excel. This is precisely why
Yeah, I think it is
we're looking at that, as well as some of the other pricing changes that we're valuing.
Yeah, I think we would all welcome that.
Yeah.
You mentioned, Rick, you mentioned Arize. Steve, you were actively involved in that. What's up with Arize? Because there's a lot of vendors in that space. What is it about Arize, and why are you so excited about it right now?
Yeah, I could probably kill the rest of the time on this one. One great signal always, kind of a little bit to the partnership topic, is that we were in a lot of accounts together, not necessarily working with the same teams. Arize was in there talking to the AI engineering, data scientists, but we were getting that pull from customers on both sides, us on the engineering and SRE leadership, on working together more. There was a natural market movement in that direction. Second piece, though, we talked a little bit about end-to-end observability. I think that new audience of AI engineering and a little bit more access to development teams, that was something that was very appealing as well. It creates a new motion for us.
It gets us into a very influential and active space, and that will obviously play out in many different ways. It's an amazing team, what they've done with the community, what they've done with their open source projects. Great fit from that standpoint. We started the conversation a little bit with this, that we all work within an industry that can be very hype and hyperbole and all these things, but everything Rick said about agentic at the beginning is so true. The changes that we're seeing in the customer base, the workloads that they're driving, the initiatives, what it means to their businesses from an agentic system standpoint, Arize is kind of in that center of that activity right now.
But fundamentally believe that these adjacent spaces, they come together, and they need that end-to-end problem still solved, even though it might be the lens through the different buying audiences. There's a I talked to Rick early on, it just checked a lot of boxes for us.
Yeah.
Yeah.
Well, when you guys acquired it was $25 million of acquired ARR, but you have pretty good visibility to another 15-
Yeah
between now and year end. How much of that is just like what was in their pipeline, and any early indication of the multiplier effect within the broader Dynatrace sellers?
Yeah, I'll take that. What we've stated, what we put into the earnings call is $25 million, as you say, of acquired ARR. That goes into net new ARR in Q3.
Yep.
Just as you're thinking about models, for those of you who model out Dynatrace, you need to make sure that you're making the adjustment for $25 million of incremental net new ARR coming from Arize just on a startup one-time basis. Then, as you say, Matt, our projection is that that becomes $40 million by the end of the year, so adding another $15 million. A lot of this really is Arize pipeline, and so existent Arize pipeline that we're anticipating converting. One of the core threads that we're driving, and we're looking at multiple different integration threads with Arize. To keep it simple, I'd say there are three. One is go-to-market, one is the overall PLG motion and driving those capabilities, and then product alignment, product integration. On the go-to-market side, we've got 4,000 plus Dynatrace customers who are potential Arize customers.
What we're now adding is we're now adding those qualified opportunities into the Arize pipeline. And we have already now added well more than 100 registered qualified opportunities from the Dynatrace installed base into the Arize pipeline that aren't in that $40 million. Now, I'm not going to get ahead of my ski tips and say all those are going to close, because those have just started to move through the pipeline, and we don't have a lot of visibility yet as to sales cycle, those sorts of things. But it is a great indication, I think, of the opportunity for leverage to come.
Yeah, it seems like
It seemed like a great fit. Even from a new logo perspective, it just gives you a whole another-
Huge, yeah.
selling motion.
Well, as Steve said, we were trying to sell Dynatrace's AI observability, which was relatively early stage into existing customers of Dynatrace. We say, "Oh, look at that. You've got Arize in a commerce company, an automotive company, a bank, a communications company." It's like, wait a minute. Arize is already embedded in many of our customers, so it seemed very synergistic. We evaluated many of them in the market for consideration of acceleration of our roadmap, and we felt Arize came out well on top of the others.
The other driver, I mean, it's just infrastructure monitoring. I think it was $500 million in annualized consumption growing 30%. I mean, part of, I think, we all sit here and we see all these eye-popping numbers that you guys are putting up, and it's I think we all think the overall business certainly has an an opportunity to do more. Talk about just, I mean, just math. I guess, how do we think about these consumption numbers, like $500 million in annualized consumption? What is the mechanism for that to roll into actual subscription revenue growth?
Well, the way it's going to happen is you've got to get to an expansion. It's really pretty simple. That's where you would drive NRR growth, and the NRR growth would then yield additional net new ARR. Consumption will motivate an expansion. Expansion then will drive net new ARR in these respective areas. It is, logs is our largest grower. Infrastructure monitoring is next on the list. These are core areas of ongoing expansion that are going to result in, we expect, ARR acceleration.
Yeah. I guess then the logical sort of, with all these things doing so well, what does that say about the core, I guess? Because these feel all additive to me, and if the business is not going to accelerate, then there's something that's not doing well. I mean, what would you say to people that are like, "Oh, there's got to be something that's dragging down growth"?
Yeah, I mean, it's interesting. I do get asked this question a lot, and I would just simply say it's math.
Yeah.
Our full stack or our application performance monitoring business is just so much bigger than the rest of them that a few points of reduced growth below the mean in that are enough to outweigh the impact of substantially higher growth from much smaller businesses, even though those businesses are getting bigger. If you continue that math, what you are going to see is that as logs now approaches $250 million, as infrastructure monitoring is now growing in the 30s, over $500 million, those numbers begin to get big enough to move consumption overall for the company greater. As the consumption continues to hopefully continue to evolve positively, then that should lead down the road to an acceleration of expansions.
Okay.
That is the time lag that we talked about a little bit earlier, that because we do not recognize revenue and we are not evaluated on revenue as a rev rec basis based on consumption, there is this lag that you have to factor in. Because ironically, if we were actually doing rev rec and reporting on revenue and nobody cared about ARR, or we did not even report ARR, and we were reporting that on a consumption basis, we would be growing in the 20s.
Yeah.
That's what we're obviously trying to make sure actually results in the numbers.
You have Perform coming up in February. Is part of, obviously, you will see from the CFO perspective, but I mean, do you think there's a way to simplify the messaging here where there's just fewer metrics? Because some of your competitors don't talk about as many things as you.
No, I know. Well, we certainly have taken that feedback from you and others, I think appropriately so, Matt, to heart. I think there were a few quarters ago where we were trying to paint a picture, we'd released too many metrics.
Yeah.
We got enough feedback from investors saying, "Okay, thanks for your transparency, but
Yeah.
The but was, "Please simplify. I'm getting lost in the metrics." We radically cut back. We are continuing to communicate consumption because we think it's just a core metric of the business. The guiding lights that we're driving against, that we're suggesting that investors look at our net new ARR and overall ARR growth, and the result of that is NRR coming out of the installed base.
Okay. Those are pub-
Those are the core metrics to pay attention to, and we're trying to minimize any deflection-
So that it's-
around the noise.
Yeah. It's Rule of 50. I mean, that's kind of like, without-
We're driving.
Yeah, without preempting analyst day comments. That's still the framework that-
It is. I mean, heck, even last quarter, as we announced in earnings, we delivered a Rule of 48.
Yeah.
I mean, 16% ARR growth with 32% operating margin, and even higher than that pre-tax free cash flow. Operating at a Rule of 48 is a pretty strong set of metrics. Yet, our commitment is FY 2029 is durable Rule of 50. We believe we can get there, and that's how we're going to roll that out at investor day and explain exactly how we intend to achieve it.
It certainly seems like there's an upward bias. If you can get growth up a few points, I mean, it feels like 50 is not even necessarily an end goal. There could certainly be above that, given-
I'm not taking the bait on that.
Yeah. Okay. All right.
Yes.
We will see.
Yeah. I mean, make no mistake about it, that yes, the commitment for FY 2029 we have already made is a Rule of 50, but our internal focus is on growth acceleration.
Yeah.
It is not that you flick a switch and that happens immediately, but we do believe elements like consumption and logs and Arize, and these other, even our product roadmap to come, which we are excited about in a myriad of ways, is a growth driver.
We are out of time here, unfortunately. My takeaway is that it has been a lot of work that has led up to where we are today.
Yep.
New products, acquisitions, changing the sales force around, and it feels like it is a time to kind of harvest some of those benefits, and we certainly seem like the best days for Dynatrace.
I think that is well stated, and that is exactly where we are. It is, we wake up every day thinking about the same thing, which is growth acceleration and delivering against some of these metrics and converting it to shareholder value.
Well, good luck on closing out all these DPS contracts and everything.
There we go.
You got a lot of work in the second half, but it seems like you got a lot of opportunity. From all of us at RBC, guys, thanks.
Yeah. Thanks for having us. Appreciate it. Thanks, Matt.
Thanks for coming, Rick.
Thank you.