Welcome everybody, and thank you for joining us. I'm Arti Vula , and this is Jaiden Patel. We are on the JP Morgan equity research team covering enterprise software. It's a great pleasure to be here with Rick McConnell, CEO, Jim Benson, CFO, and Dan Zugelder, CRO of Dynatrace. Rick, Jim, Dan, really appreciate you guys coming back to TMC.
We'll start off on a good note. You guys finished fiscal 2026 surpassing $2 billion in ARR, fourth consecutive quarter of 16% ARR growth, and a fiscal 2027 guide that bakes in net new ARR acceleration. It's been a banner year for you guys. Just to start off, why don't you guys give a quick introduction and just let us know what Dynatrace is solving for the world's enterprises today and how that's evolving in the AI world.
Sure. Dynatrace is in the $75+ billion observability space. Observability is targeted at enabling enterprises to run their software better. Think about us as helping to prevent incidents, to remediate incidents, and to optimize your environment. This is what observability software generally does. We often think of Dynatrace's vision in delivering the world software that works perfectly. That would be our objective. Obviously, as we evolve so rapidly into an agentic world, this brings a huge array of new opportunities to the observability space because agents enable us to actually take action and to execute those actions in a more autonomous way. You can imagine systems that are self-healing effectively to enable software to always work better than it's worked before.
I'm sure we'll talk more about this, but it is a very, very exciting space that we believe is a tailwind or receives a tailwind from all that is happening in AI based on the expansion of workloads, the drive toward autonomous operations, and in general, the necessity of delivering software that works perfectly.
That's great. I think the self-healing part is a good way to describe it. I'm sure we'll touch on it. You know, the more that AI-accelerated code gen, I think it's made that observability even more important and critical and something that you need, a third- party can do it excellently to do it. Let's just start with the fiscal 2027 guide. You know, Jim, if we think about the nuances from the earnings call last week, the guide implies net new ARR growth of 16%-23%, accelerating from 12% FY 2026, reported ARR of 15.5%-16.5%. That range from 16%-23% of the ARR, it's wide.
Can you give us a sense of what drives the high end versus the low end of that and, you know, what you can control in that equation?
Yeah. I'll start with, you know, fiscal 2026 was a year of firsts. You mentioned in your opening remarks that, we had consistent ARR growth of 16%. We grew net new ARR 12% in fiscal 2026. We haven't done that in three years. One of the things I've talked to investors about is the phases that we've been going through. Fiscal 2025 was a fix year where we did some things on the go-to-market side. Fiscal 2026 was stabilize, and fiscal 2027 was accelerate. I've talked about that over time, and we've just completed the stabilize phase, and there's a lot of momentum going on in the business. We've talked about logs. Logs is well over $100 million, growing four consecutive quarters well over 100%.
We think that will continue, so that will continue to be a tailwind for us. When you look at our guide, we view it as we just finished a year of 12%. We have a sales organization that is in year two of their, I would say, maturation phase. There's a lot more room to run—
Yeah.
—relative to productivity within the sales organization. We mentioned logs. Dan will probably talk about it in a bit around platform consolidation. End-to-end observability is certainly something that more and more enterprises are looking to do. That is certainly a tailwind. Relative to the range, I think what you see is that at the low end of the range, it still implies an acceleration of net new ARR growth of 16%, and you mentioned 23% on the high end. Some people have asked me, they said, "Geez, you know, Q4 landed a little bit lighter than maybe people would have thought." I would say it did land a little bit lighter than our internal expectations. I'd say largely that is we had softness in our EMEA market, notably in the Middle East.
You know, the difference between growing double- digits and growing nine is a few million dollars. When I look to fiscal 2026, there's a lot of momentum building in the business, and we expect it to continue. All the things that I just mentioned will continue. Relative to a range, I mean, our range is usually 1 point of, you know, plus or minus. I think what you get at the high end of the range is a continuation of what we've been doing in building. Even at the lower ends of the range, you're getting that. I think you know that historically I've used the word prudent. That was called out on the earnings call. This guide is no different than any other guide I've provided every year.
There is an internal plan, and then there's a haircut for what we do that we're gonna tell the investor community, and it's no different than what it always is. Obviously, we gotta see how the year progresses. I mentioned in the call that we would be a little bit more half one weighted. Just to clarify that, our historical linearity is like 44% of our net new ARR in the first half, 56% in the second half. That doesn't mean we're gonna do more net new ARR in the first half. It just means maybe we'll do a couple points more, maybe 46%, 54%. It's because we have strong forecasted pipeline entering the year.
You know, our pipeline visibility is always tighter in a three to six-month window than it is 12-month window.
Yeah.
We actually just believe there's just a lot of tailwinds, and as the year progresses, we'll update, you know, our outlook accordingly.
Yeah, just to be 100% clear, your guidance philosophy essentially is unchanged from what you guys have done historically?
That's right.
Yeah. Yeah. If we just double-click on that, you know, 9% net new ARR growth in Q4, and then going forward, I know you mentioned there was some softness in the Middle East. Assume the Iran conflict doesn't help that situation. If you can just talk about, okay, if you have, you know, those slight headwinds, out of those tailwinds that you're seeing, which ones do you think are gonna be able to drive a lot of that? You know, what should give investors confidence in what we're seeing through the rest of the year?
I think the biggest one is I think we will continue to do what we did with logs. Our expectation is that logs will continue to double. We ended the year well over $100 million. We have a lot of confidence that we will continue that trajectory, that we have the right product with the right pricing and packaging at the right time. I think we've shown it in an ability to go into our install base and sell it, and actually even introduce new logos. I think logs will be a big source of it. I do think we'll continue to see workloads grow with end-to-end observability. More existing customers and new customers looking to consolidate. One, we can save them money. You're consolidating multiple vendors, and you can save money just through software costs.
Beyond that, we allow their environment to run more efficiently, because once you're on Dynatrace, you have a platform where you have deterministic answers to figure out issues, as opposed to people chasing alerts and dashboards. It really is just a continuation. This is not like new plays. It really isn't. It's a continuation. Dan can talk about the go-to-market model is largely unchanged. We're gonna go down with our strategic accounts. We've had Fortune Global 500. We'll probably go down another 100, 150. We'll four to five reps in that part of the pyramid. You'll have fewer accounts per rep. We'll get better penetration. The penetration that we've had in those accounts since Dan made those changes, it's the fastest growing—
Yeah.
—segment that we've had in the company, and it's about running that play again.
Yeah.
We think that that will continue to be another source of productivity improvement.
Yeah, having the continuation of the existing tailwinds feels a little bit more comfortable than anything new having to kind of layer in.
One other thing that I would mention is that, you know, that we've been at the Dynatrace Platform Subscription for a while. We now have over 75% of our ARR on that contracting vehicle. A little over 60% of our customers. Fiscal 2027 is the first year where you're actually gonna go through three annual reset cycles. We haven't had that in the past.
Yeah.
The first year of DPS was fiscal 2024. Most of our DPS customers are three-year cohort classes. They are coming up for their actual renewal in fiscal 2027. There's a significant percentage of our installed base with DPS that is gonna go through either a renewal or an annual reset. It's a huge opportunity for an expansion for us—
Yeah.
—for all the reasons we just said. Consumption is growing at a very rapid clip. It's been growing north of 20% for well over four quarters. If we can continue with that, again, it'll be a source of expansion opportunity.
Yeah. Yeah. Sounds like a lot of upward pressures in the right direction. You know, touching on some of the other things you were talking about, Dan, I think this is your wheelhouse. You know, Dynatrace, you guys started this go-to-market transformation a couple years ago, shifting reps to focus on four or five accounts in the Fortune 500, building the partner motion, comp plan, you know, changes. You know, as Jim said, you just finished kind of the stabilization phase. When you're looking at that pipeline coverage entering FY 2027 is healthy enough to guide net new ARR modestly to accelerate, one of the themes in our partner work is that the pipeline quality matters more than the quantity. I assume you guys kind of have the same perspective.
Can you talk about what you're seeing in terms of that quality and how you measure it? Is it the stage progression, deal velocity, close rates? What is giving you confidence in that pipeline?
Yeah. I think it probably starts with the methodology and the inspection, the quality of what goes in, you know, the approach we take with that. The analytics play a role as well. The, you know, the motion for Dynatrace, if you go back a few years ago, was a very different selling motion regarding pipeline. It was a very mid-level enterprise engagement, typically very feature-based. Over the last three years, it's transformed into a much more enterprise value selling motion.
Yeah.
We have a different approach, a pretty dramatic different approach. That's matured at this point. We understand what goes into our pipeline. We understand, you know, the risks of what matures, what doesn't, at what pace. I think it's just the maturity of the motion that gives us the confidence in the pipeline.
That's great. I wanna turn it over to Jaiden here, but Rick, compliment on the enterprise motion, on the shift to the left, you know, developer side. You got DevCycle, MCP Server, Cloud Code, Cursor. Is this an evolution of the enterprise motion or a different velocity engine kind of targeted AI natives and the AI native buyers?
Great question. Definitely the power of the "and."
Yeah.
Learned this from my earlier career in Cisco, and we're always talking about the power of the "and," this is definitely it. We don't foresee a shift from the enterprise to AI natives, for example. We believe that it is the enterprise plus AI natives.
Yeah.
We have been working very diligently over the last 18 months to build developer capabilities into the platform, and you've seen those over the last two quarters through a myriad of announcements related to integrations, for example, into AWS, Bedrock AgentCore, into GitHub Copilot, into Cloud Code, into a myriad of different other elements. All of these enable our platform to be more developer ready. We didn't grow up on the developer side like some others in our industry. We grew up in the enterprise side focused on IT Ops selling to the CXO. This is why, out of our customer base, we have an average selling price of now about $500,000. It's because they are large end-to-end enterprise deployments.
These customers use us to make sure that their software always works, and they want to deliver end-to-end observability at multiple levels. Completely integrated data lakehouse, integrated fully across logs, applications, infrastructure, real user monitoring, et cetera, then integrated for all personas. This is what we do better than anybody. This is Dynatrace's superpower. We want to take that superpower that we've delivered to the enterprise and bring that to the developer community, bring that to AI natives, that really is the next step in our evolution as an organization.
Great. You know, Dan, I think this one's for you. Let's talk a little bit about the disconnect between, you know, what we hear from investors and what customers or what you're seeing with customers. You know, one consistent theme we hear from investors is that customers are more reluctant to spend because of all the uncertainties due to AI. A lot of this discussion centers on the application side, but I think it's worth touching on here. Dan, I assume you're the one across the table from CIOs and CROs every week. What do customer conversations actually sound like right now versus what we're hearing from the investor community?
Well, I think there has been, I don't know if it's new, there is cost concerns. People are looking to That's why consolidation has been such a play, is that, you know, no question it gets people's attention when you're saying, "I'm taking two or three tools and making them into one, and there's going to be a 10% to 15%, 20% cost saving." There's an attractiveness of that conversation. When you can couple that with saying, "I'm gonna give you a better outcome," that's usually the combination that people are looking for. We're not looking just to do things to cut costs, but if we can deliver a better observability outcome.
I think as we enter AI, and we just came out of our sales kickoff, I reiterated that our motion of tool consolidation cost out, and logs is a great example of that, where we sometimes take 40%, 50% cost out because of combining logs with metrics and traces. You just need less of them in a more efficient way. That it does resonate with our customers, there's no question. It has been, and I think it continues to get people's attention. What you do in this world that's been created with AI is a fantastic tailwind because you're creating then budgeted new projects out there, they're AI projects, that need observability.
You continue to run your entire play around tool consolidation, the enterprise end-to-end observability, and now we have a motion that we've added that is more about saying going after these specific AI projects that need observability. You have a little bit of a bespoke process in go to market, and then you have our very mature enterprise market. That's created additional opportunity for us. Rick talked about the AI natives that have their own specific market as well. AI has created additional markets in it for observability for sure.
You know, the one thing I would add, just to append to Dan's remarks is we absolutely believe that observability is a beneficiary of AI evolution, of AI first organizations. It is critical in our view that in an AI first world you need more observability, not less. We do not see observability as a market and infrastructure environment which is going to get disintermediated by AI. Quite the contrary. We see that in our existing customer base, maybe 30% or so of workloads are actually observed in a sophisticated way, like using Dynatrace. In a probabilistic world where you're using lots of LLMs, agents to build software, we believe that you actually need more observability to oversee those workloads than not, number one.
Number two, we bring incredible context, billions of interconnected data points in real time, very specific to a particular organization's environment. Number three, we bring domain expertise of understanding that environment specifically and how that environment is operating. Observability is going to benefit from a tailwind in AI, not just in deployment of AI natives, but also in the enterprise itself, where obviously enterprises are deploying more and more AI workloads that are inclusive of AI, largely built by AI, coded by AI, and over time will be operated by AI in a very agentic world headed to an autonomous environment. All of these factors are driving an environment for observability that has become more and more mission critical to organizations day by day.
Of course it's our commitment to do everything we can to be a beneficiary of this trend for observability overall at Dynatrace.
Yeah, it seems like there's a lot of AI tailwinds that are benefiting the business on top of the execution that you guys are providing. Jim, on that point, when do you expect these AI tailwinds to meaningfully contribute to accelerated growth?
I think we're already starting to see it, but you gotta remember that the way our model works is you're signing up customers on a contract with DPS, and then they have three one-year commitments, and then they push consumption to it. The underlying component of DPS is consumption. It's not a seat-based model, it's a consumption model. Now we recognize revenue ratably, but we consume based on, you know, what customers are, what workloads customers are adding and the growth in those workloads. We're already seeing some of the benefit that, again, I mentioned that it's been over four quarters that consumption is growing north of 20%. The way to think about that is that, and I think this is where people sometimes struggle, is why is ARR not growing 20%? It's a lag.
There is a lag with just the nature of the way the DPS contracting model works. If you can continue to grow consumption north of 20%, you will see a convergence of ARR and consumption over time.
If I Jim, our selling motion is just as much about bringing workloads onto the platform as it is expansion of ARR because it's the, you know, it's the preemptive piece of expansion on ARR. Our salespeople are out there just trying to get workloads onto Dynatrace, whether AI workloads, whether they're logs, whatever, expanding to more applications in general. Their motion is like, "I know if I get more consumption, when that, when that DPS comes for renewal, that will give the fuel to that fire to be able to expand more." You can understand how we are very consumption-based, even though we're an ARR or an ACV and ARR as far as the way we measure the business. The focus is knowing is all on consumption.
The other thing that I would say is that we have integrated account teams that, you know, that Dan's account reps are the quarterback for. We have customer success teams. They are measured on consumption. They are compensated on consumption. Dan has bespoke strike teams for bespoke product areas. They are measured on consumption. They are compensated on consumption. This consumption mindset is, exists throughout the company, and I'd say we continue to run plays now. There's gonna be plays on consumption. Again, at its core, get them on the DPS platform. Have teams of people work with them to get more value, to Dan's point, reps ensuring they find new workloads. We got customer success teams that are helping ensure that they're getting value out of the different product areas, and then specifically on the strike teams.
They're on the front end with sales on deals, and they're also on the consumption side around driving more consumption. I'd say we have a lot of the ingredients in place. They've been in place now for a year. I think it's led to what has been stabilization, and we're quite confident that it will now lead to acceleration.
Great. Let's tackle sort of the bear case on observability head-on. Rick, this question, you know, is for you.
I always give the bear case to Jim. I'm just kidding. Just kidding.
You know, the question that comes up most often on our end is this outstanding, you know, idea that as the cost of code goes to zero, customers can use OpenTelemetry plus vibe coding to roll their own observability layer, and an LLM can reason over that telemetry. We've written, you know, tens of times that we think this thesis is off base. You know, better to hear from you than anyone else. You know, what is your thoughts on that, why is that true or not true?
Yeah, I mean, I sort of gave the precursor to this answer already, so I think I can do it briefly. The starting point is I sort of oversimplify to bifurcate the world into application seat-based software with standardized workflows and highly dynamic software, infrastructure software that needs to take real-time data into account. These are very different models. In the former case, it is much easier to vibe code a standardized workflow than a highly dynamic workflow based on context. That is sort of the underlying thesis. Our view is the combination of significant domain expertise, highly specialized for organizations like JPMorgan, you know, for example, or the largest organizations on the planet, to be able to integrate and observe their environments is absolutely mission critical to those organizations.
Are you really going to rely on a vibe-coded standardized piece of software that doesn't have the same degree of domain expertise, doesn't have the same degree of real-time context based on billions of interconnected data points, doesn't have the ability to oversee or observe probabilistic models? By the way, there's an even added element here. For the history of Dynatrace, we have been focused on a particular question or answering a particular question for our customers, that question is it working? If you think about what does observability do, is it working or maybe is it working well? Is it optimized? That's what we've been focused on.
In an LLM world of models that are providing input to allow trustworthy actions to take place through agents, you have to answer a separate question and that is it correct? In other words, is the information coming from models actually accurate so that it can be trusted and implemented? We have customers that are using us in payment terminals that have to work every time. They need agents to be able to take immediate action, to provide corrective action to make them work. We have banks who are using them in mobile, using Dynatrace as part of mobile apps to assist customers to transfer money from one account to another. That's gotta work every single time. Whether it's healthcare, manufacturing, there are use cases in each of these environments that are critical to be driving trustworthy outcomes based on AI and LLM inputs.
You, you simply can't rely upon an LLM to provide that degree of context, that degree of domain expertise to support an environment that then was created with a standard vibe code. It just isn't gonna work. If there's one answer to all that, I would say context is it.
Great. You know, on that point that, you know, these tools need to just work, you know, the place where that makes the most sense is the enterprise, right? Dan, this one's for you. The most striking thing in your recent quarters is the consistency of seven-figure deals, $200,000+ new logo lands, and as you said, roughly $500,000 ARR per customer, which Jim has framed as having a path to $1+ million over the long term. You know, a partner told us that, you know, consolidation is the only conversation that matters right now. CIOs are tired of paying for five tools that overlap. Is that sort of the right read on buyer mindset right now?
Consolidation, they is definitely on their top of mind. It, you know, I mentioned this before, it is obviously cost.
It's obviously has to do with if you're a C-suite, up to the CEO of organizations, there's a major outage. CEO will be, first question is, "What's the problem?" Obviously. That CIO, if they cannot answer that question very quickly, their job is on the line. That is when you have a fragmented observability stack, it means that answer becomes that much more difficult, because everybody's looking at their individual tools and saying, "I'm good." They're asking the question, they're going around the room, people are answering, "I'm good, I'm good." Somebody at the top saying, "We have a major outage going on right now." We deliver that so you have visibility across your entire application and infrastructure stack. The consolidation plays on a cost basis.
There's no question it plays on a delivering a better outcome. I think that trend is not going away. Some of the C-suite I speak to all the time is that they're just trying to continue to pull things together, pull optimized costs, but deliver a better outcome. That's been there. I think it's catching wind. I think there's a lot more. Logs have played a big role in that, if you look at it, we were, 18 months ago, we really weren't playing in the logs business, that's accelerated this view of a better outcome. Most people are using some of the traditional log providers, that was redundant to observability. It was actually, it's fairly low-hanging for them.
I would just add that it seems to me that the Holy Grail that Dan and I hear from CIOs, CTOs, CXOs, basically every day is they wanna get to autonomous operations. They wanna get to autonomous operations because the cost savings are extraordinary, and by the way, they're having more difficulty finding headcount to actually manage environments rather than less. They need to be able to do more on an automated basis. By the way, to the extent that that can be predictive, it's even better, so that you eliminate issues before they even occur. In order to get to autonomous operations, you have to have, to Dan's point, end-to-end observability, because it is the confluence of elements that enables you to have confidence and trust in the outcome that enables an agent to take action.
If you don't have that degree of confidence and trust, you cannot rely on the agent to take the correct action. The mechanism to get to autonomous operations from accounts is to begin with end-to-end observability, and this is why last quarter, for example, 22 deals of greater than $1 million, which is pretty substantial for a run rate, all driven by really this end-to-end observability motion, all setting up not as the end, but as the mechanism to drive toward autonomous operations as we look at.
You know, you mentioned logs, you know, earlier, and a bit on this last question as well. You know, logs has, you know, definitely been one of the biggest surprises, positive surprises in the Dynatrace story over the last 12 months. You know, with over $100 million of annualized consumption, which, you know, growing north of 100% year-over-year. Rick, you were out there quoted in the ether around a $250 million number, which we interpreted as aspirational. The underlying question here is, you know, let's say we pass that $250 million. Where can this business grow? You know, what is the overall market here that you can, you know, drive this to be?
I'll start and then look to Dan and Jim to comment further. I mean, the logs business alone is a multi-billion dollar market. I mean, you look at Splunk, you look at others in this market, and it's already many billions of dollars of log observability. We believe that we absolutely believe that our business can continue to grow toward that billion-dollar mark, and over the course of enough time, even beyond that. The reason is because we believe that we have a solution that is better than a standalone log solution. Standalone log solution is focused only on logs. What we can do, which is consistent with what we've been discussing heretofore, are two things related to logs.
Number one, by integrating, as Dan was talking about, logs with traces, metrics, real user data, behavioral analytics, et cetera. You get a better outcome. You can see the entire environment. By seeing the entire environment inclusive of logs, you deliver a better outcome. Those answers that come from that better outcome lead to the autonomous operations of the environment that I'm describing. The second thing is you actually, because you have traces, metrics, logs, real user data, it actually is more beneficial to have multiple different data types than just more logs. You actually can, you can actually accumulate fewer logs, but when combined with these other data types, you actually end up in an environment where you get a much richer environment to be able to provide analytics that allow for things like auto prevention, auto remediation, auto optimization.
Better outcomes, lower price point, and you have lots of our existing customers that are using a log vendor for logs, us for observability, and they're increasingly moving that log workload to us in order to get the benefit of end-to-end observability that we've been talking about for all the reasons we've been discussing.
Great. I have one last question, and I can hand it off to Arti. Jim, this one's for you. We would be remiss not to ask about this. The Starboard team published a fairly detailed letter on April 28th, and both of you and Starboard have described the engagement as constructive. Rather than dwell on the letter itself, help the audience understand how you're thinking about the value creation framework for Dynatrace over the next several years.
Yeah, well, I mean, we think of value creation beyond and, you know, all investors, so that's, that's kind of how we're viewing Dynatrace, that we want to provide shareholder value for all. I think at the end of the day, when you think about what we're trying to do, everything we tried to build and outline was an acceleration in the growth of the business. This business can and should be north of what it has been delivering. For us, there's been a big focus, again, going back to my fix, stabilize, accelerate, putting things in place to go on the offensive to go after the opportunity. I think Dan talked about some of the, you know, the model we had before was good for when the company got to $1 billion.
In order, we needed a different model to be able to scale. When I think about acceleration, I think it's in our sights, and you've seen that, you know, for sure at the high end of our guide, we expect that that will happen this year. On the margin front, we are a rare company that operates at 29% or 29%, almost 30% operating margins. We've driven 400 basis points of leverage in the model. Each year we'll tweak it a little bit 'cause sometimes you'll make investments in one year, you'll get a return the following year. Driving efficiency and driving leverage is always part of the story, that Dynatrace is a balanced growth and profitability story, and there's a sequencing of when you would do that.
I think we've demonstrated that we can do that and we will do that. I mentioned in the call that we're driving 150 basis points of operating expense leverage in fiscal 2027, offsetting what is a near term gross margin headwind.
Again, margin and leverage, very important. We believe the shares are undervalued. We have significantly bought back stock. We increased the pace of our buyback 40% from Q3 to Q4. You know that we doubled the authorization to $1 billion in February. We believe that at these prices it's very attractive, and we will continue to put capital to use in the form of buyback. We generate a lot of cash flow. We have, you know, a fair amount of cash on the balance sheet, so accelerate growth, continue to focus on efficiency, you know, put your buyback to use at very attractive values, and I think that's what we've been doing.
Yeah. Well, Rick, Jim, Dan, it's been fantastic to have you guys here and sharing your insights with us. A lot of stuff going right in your business. We're really looking forward to where that goes. Thank you.
Thank you.
Yeah. Thank you very much. Thank you all .