Elastic N.V. (ESTC) Earnings Call Transcript & Summary
August 29, 2024
Earnings Call Speaker Segments
Anthony Luscri
executiveThanks, everyone. Hello, and I appreciate you being with us this afternoon for the call where we'll go over Elastic's financial results for the first quarter of fiscal 2025. Joining us are Ash Kulkarni, our Chief Executive Officer, along with Janesh Moorjani, who serves as Chief Financial Officer and Chief Operating Officer. Once they've finished their prepared comments, we'll open things up for questions. We put out our press release earlier today after the market closed, and it's available on our website. You can also find the slides, which provide additional detail beyond this call, on the Elastic Investor Relations site at ir.elastic.co. During our discussion, we'll be making forward-looking statements, and those might involve predictions, estimates or expectations about demand for our products and solutions, our future revenue and other matters. Such forward-looking statements rest on factors we currently know about, are accurate only as of today's call, and carry risks and uncertainties that might lead actual results to differ materially. We take no responsibility for updating or revising these forward-looking statements unless the law requires it. I'd point you to the risks and uncertainties laid out in the press release we issued earlier today, in the slides posted on the Investor Relations website, and in the fuller descriptions found in our filings with the Securities and Exchange Commission. We'll also be talking about certain non-GAAP financial measures. You can find disclosures about non-GAAP measures, including reconciliations to the most comparable GAAP measures, in the press release and slides. A webcast replay of this call will be made available on our company website through the Investor Relations link. Our quiet period for the second quarter of fiscal 2025 starts when business closes on Wednesday, October 17, 2024. In the weeks ahead, we'll be taking part in the Citi Global TMT Conference, the Goldman Sachs Communacopia and Technology Conference, and the Piper Sandler Growth Frontiers Conference. With that said, I'll hand things over to Ash.
Ashutosh Kulkarni
executiveThanks, Anthony, and I appreciate everyone being here today. In Q1, our total revenue was up 18% compared with the same period last year. Cloud revenue rose 30% year-over-year, and our non-GAAP operating margin came in at 10.7%. Once again, we beat the upper end of the guidance we had given for both revenue and profitability this quarter. Our strategy of landing, expanding, and consolidating remains our focus. The count of customers who spend more than $100,000 with us increased to over 1,370. We also kept building strong momentum in generative AI opportunities, which helped us speed up growth in our search business. On top of that, our message about platform consolidation keeps resonating with customers. Even with that strength, we see this quarter as a mixed one for us, since the total volume of customer commitments we closed in Q1 came in below what we had expected. Regarding what affected the total customer commitments closed in Q1, we felt the impact of sales segmentation changes we implemented at the beginning of Q1 to sharpen our focus on strategic enterprise customers and high-potential mid-market customers. To put it more precisely, when the fiscal year started, we enlarged our strategic segment, placed more emphasis on selling into our biggest accounts by lowering the number of accounts each sales rep handles, and set up separate greenfield territories aimed at landing new customers in both the enterprise and commercial segments. These changes will ultimately help us grow our customer relationships and, over time, boost our wallet share with customers through our platform consolidation motion. That said, we underestimated how much the account transitions tied to these changes would affect us. This was particularly the case in the Americas, where the territory changes were largest, and we simply did not move deals ahead quickly enough to get them across the finish line. Separately, and to a smaller extent, tighter budget constraints among customers caused delays in closing deals in EMEA. Not one of these deals was lost, and we anticipate closing them in due course. Together with Mark Dodds and his sales leadership team, I have substantially increased the monitoring of deal progress in the areas where segmentation changes were greatest. With this added rigor, the deeper focus on our biggest accounts, and quite simply because reps have had more time to cover their new accounts, we are already seeing encouraging signs of deals moving through the sales funnel. Our enterprise engagements, especially with our largest strategic accounts, can generate significant large deals for us over the coming several quarters and beyond. These customers also hold the biggest budgets. As we look forward, we stay extremely confident in both the market opportunity and our capacity to successfully seize that opportunity. Our innovations are broadening our competitive differentiation. We keep strengthening our position as the platform of choice for building real-time GenAI applications. Our value and price advantage will remain a strength for us as customers consolidate onto Elastic for multiple use cases. Now turning to generative AI. Customer excitement and appetite for generative AI keep ramping up, with organizations moving steadily from brainstorming into trials and real deployment. The huge promise GenAI holds for reshaping how businesses operate only strengthens our belief in the path we've chosen and in our standing as someone who benefits over the long haul from this massive technological transition. It makes me quite happy that we closed Q1 with more than 1,300 clients leveraging Elastic Cloud for generative AI scenarios. And roughly 200 accounts within our group of customers spending greater than $100,000 are working with us on GenAI. Beyond that, as I noted before, we observed a broad pickup in our Search segment as additional customers picked Elastic to develop their AI-powered generative AI use cases. Every bit of this points extremely favorably toward what lies ahead for us as the Search AI company offering the top platform for creating real-time GenAI applications. To illustrate, during Q1, a prominent sales-enablement software firm committed to a larger agreement to leverage Elastic for embedding GenAI throughout its platform. Their copilot these days draws on ELSER, Elastic's own machine learning model built for semantic search, letting every one of their clients generate personalized, tailored material via retrieval augmented generation that is more accurate and quicker. This has lifted their customers' satisfaction and produced an increase of more than twofold in their Elastic consumption across the past 6 months. That firm picked the Elastic Search AI platform because of our hybrid search strengths and integration that runs smoothly without needing heavy model training or retraining. One more Q1 victory involved a worldwide transportation sector leader that struck an expansion agreement with Elastic via the Google Cloud Marketplace to revamp its security architecture and weave GenAI through every cybersecurity operation. This organization is going to roll out our AI-driven security analytics tools, including the Elastic AI Assistant, Attack Discovery and ESQL, with the goal of raising their event-processing capacity by 20%. Such cutting-edge tools let the enterprise automate detection, rank actionable intelligence and handle security threats efficiently, cutting manual work dramatically to boost operational efficiency. A sizable American law practice has entered a fresh agreement with Elastic, replacing an existing solution for vector search and retrieval-augmented generation. This firm is going to rely on Elastic to strengthen case preparation for its paralegals and lawyers via a new internal search application. That application will locate comparable cases for benchmarking, relevant case laws and properly reclassify misclassified cases, all intended to eventually raise revenue per case and lift win rates for their clients. Elastic got picked to replace the existing solution because of performance and scalability, since the organization presently holds close to 40 million documents and adds roughly 2 million each month. In each discussion I have with a customer, the worth that Elastic delivers is evident, and that's the reason we keep succeeding when it comes to consolidating platforms; we keep introducing new capabilities so that migrating away from incumbent options becomes simpler and taking up the Elastic Search AI platform becomes easier; over the past few quarters, ESQL — our strong piped query language — has been our lead offering, alongside our AI Assistant for security and observability. During Q1, at the Black Hat Security Conference, we took things further with the debut of Elastic Express Migration, a fresh incentive program that bundles together every migration service an organization requires and assists in reducing dual vendor expenses so that legacy SIEM and log analytics vendors can be left behind and the Elastic Search AI Platform can be embraced swiftly and effectively; we're happy with how we've stayed dedicated and worked to push out incumbent solutions; as an illustration, during the quarter we finalized a 7-figure agreement with a frontrunner in data security and compliance through the AWS Marketplace, replacing a rival offering. That business relies on the Elastic Search AI Platform to search, analyze and visualize enormous amounts of data spread across cloud environments, which lets their clients detect, mask and manage sensitive data so compliance is assured and risk is reduced. The pace and efficiency of this organization's data operations have improved already, beating their prior solution by as much as 120x. Elastic got the nod because of how quickly we search when spotting security breaches, satisfying the intricate requirements of tough security settings at the biggest and most powerful companies globally.
Ashutosh Kulkarni
executiveAdditionally during Q1, a top-tier data analytics and business intelligence provider entered into a fresh agreement to swap out an existing vendor's product in favor of the Elastic Search AI Platform. This organization's open-source intelligent offerings take in, enhance, and examine information from a variety of global sources, enabling law enforcement, government bodies, and enterprises to preserve lives and safeguard what is most important. Through selecting Elastic to assist in simplifying and merging scattered data repositories while producing more pertinent search results, they are able to lower expenses, boost developer efficiency, and enhance search performance. Now, moving on to Q1 breakthroughs. Our group kept providing features to broaden our edge over competitors in search, GenAI, observability, and security. Regarding search, we kept growing our leading role as a vector database and in the retrievable-augmented generation, or RAG, application. During the first quarter, we additionally refined scaler quantization, leading to quicker query speeds and a substantial decrease in memory needs. And we have incorporated backing for binary vectors. We likewise rolled out the Symantec underscore text field type, which streamlines the task of dividing big documents into chunks and generating text embeddings for every chunk, leading to a much easier experience for GenAI programmers. Lastly, we broadened our Symantec reranking features, which enhances our natural language search abilities for every user with a larger selection of AI model suppliers. We also brought out Playground to speed up RAG application creation with Elastic Search, entirely via an easy-to-use low-code UI-based process. Using Playground, programmers pick any of their information in Elastic Search to test and hone conversational inquiries with a generative model of their choosing. Following testing, Playground is able to export code ready for production to streamline RAG deployments anchored by proprietary information. On a similar topic, Elastic has consistently welcomed the strength of open source and is showing this through our declaration today that Elastic Search will be including the AGPL as a choice to license the no-cost portion of our source code that is presently available under the SSPL license. AGPL is an OSI-approved open-source license. And because of this, Elastic Search will once more be formally regarded as open source; this will generate even stronger involvement and uptake for Elastic Search in fields such as vector search within our < > community, further boosting our standing as the runtime platform for RAG and creating GenAI applications. This thrilling modification will be fantastic for our users and for our company over the long haul. In security, AI is reshaping the SIEM environment, with the conventional SIEM rapidly progressing into an AI-driven security analytics platform for the contemporary SOC, expanding upon Attack Discovery to automate threat probes and triage, which we had covered on our earlier call, we maintained our dominance in this field with our Q1 introduction of Search AI-powered Automatic Import. Automatic Import is a robust new feature to automate SIEM data onboarding by employing AI to deduce schemas and automatically produce the rules to take in data correctly. It works alongside our AI Assistant, which customers can keep using to translate their current SIEM rules over to Elastic. Taken all together, this meaningfully lowers both the risk and the work involved in consolidating on the Elastic platform; when it comes to observability, we keep shipping improvements that enhance the overall AI Assistant experience and give our customers more options, introducing support for Google Vertex with the Gemini Pro Model 1.5 connector along with custom index support for the AI Assistant knowledge base, which offers customers greater flexibility in how they take advantage of the AI Assistant. Last, we were happy to be named a leader in the 2024 Gartner Magic Quadrant for Observability Platforms. Partners play a vital role in our go-to-market strategy, and we're thrilled to be recognized as the 2024 Microsoft U.S. Partner of the Year, which highlights not only how strong our partnership is but also our shared commitment to helping customers speed up their AI journey without giving up the privacy and security of their proprietary data. To wrap up, we're highly focused on sharpening our sales execution over the months ahead. The opportunity ahead of us, our technology platform, our community, our sizable customer base and our team provide an incredibly solid foundation for us to build on. We stay dedicated to growing a multibillion-dollar business over time, centered on growth and profitability. With that, I'll hand things over to Janesh to walk through our financial results in greater detail.
Janesh Moorjani
executiveThanks, Ash. Once again in Q1, we beat the top end of the guidance we'd given for both revenue and profitability in the quarter. I'll start by going through the quarter's results, then walk you through what we expect for Q2 and for the full year. First quarter total revenue came to $347 million, which is up 18% versus a year ago, both as reported and in constant currency. Subscription revenue for Q1 came in at $324 million, also up 20% year-over-year on both an as-reported and constant-currency basis. Inside subscriptions, Elastic Cloud revenue reached $157 million, a 30% increase year-over-year as reported and in constant currency. For the quarter, Elastic Cloud accounted for 45% of total revenue. Overall consumption patterns in Q1 unfolded the way we had anticipated, with enterprise and commercial customers continuing to draw down against their annual commitments. Our self-service motion, which is mostly SMB customers on month-to-month arrangements, saw revenue stay roughly flat compared with the previous quarter. Month-to-month arrangements accounted for 13% of total revenue when it came to Elastic Cloud. We'll keep watching consumption patterns closely. Professional services revenue in Q1 was $24 million, up 1% year-over-year as reported and in constant currency. While professional services revenue can move around from quarter to quarter depending on when services are delivered, we don't anticipate much change in its mix over time. To give you more color on deal flow in the quarter, we didn't close as many deals as we had expected; the main reason was account transitions stemming from the segmentation changes we deliberately made in our sales organization, especially in the Americas, and to a smaller degree, tighter budget constraints in EMEA that we hadn't anticipated. Because our contract signings tend to be weighted toward the back end of the quarter, these problems became clearer to us in July. As Ash said, we didn't lose any of these deals, and we expect them to close over time. Ash has already gone through the specific steps we're taking in response. We're moving ahead with those actions in Q2, and we're confident that we're on track to get back to better execution. Our market opportunity is still large, and the Elastic Search AI platform is highly differentiated. Our GenAI traction is strong, and in the current environment customers keep looking for 2 consolidation opportunities. Looking at growth by region, APJ grew faster than EMEA and the Americas. We saw no meaningful shift in the competitive environment during the quarter. Our strategy of targeting customers with a greater propensity for growth is paying off, as our customer metrics show. We finished the first quarter with more than 1,370 customers whose annual contract values exceed $100,000; these larger customers give us a strong foundation for our land-and-expand motion as we build a multibillion-dollar company over time. Turning to customer additions more broadly. We closed the quarter with over 4,430 customers above $10,000 in ACV and roughly 21,200 total subscription customers. Our net expansion rate came in at about 112%, matching what we had anticipated for the quarter. Retention rates also stayed solid during the quarter; let me now shift to profitability and cash flow, where I'll cover non-GAAP metrics. Gross margin for the quarter landed at 76.3%, consistent with what we expected. Operating margin for the quarter came to 10.7%, exceeding our expectations, thanks to revenue outperformance and ongoing spending discipline. Diluted earnings per share for the first quarter was $0.35. Adjusted free cash flow margin was 18%, equating to roughly $64 million in free cash flow for the first quarter. Lastly, even though we don't formally provide guidance on cash flow, we still anticipate that adjusted free cash flow margin for fiscal '25 will come in slightly above the non-GAAP operating margin for fiscal '25. As you're aware, our adjusted free cash flow is calculated on an unlevered basis. Quarterly cash flow will swing around due to timing and seasonality, so we keep evaluating this mainly on a full year basis. Moving to guidance. Although we still see substantial opportunity across all our solutions and believe we're well positioned to seize it, we're revising our guidance to account for our first quarter performance and the current outlook. Regarding our guidance assumptions for the remainder of the year, we're assuming the macro environment stays consistent with what we observed in the first quarter; that covers EMEA, where we don't anticipate meaningful shifts in the broader environment. The shortfall on customer commitments in Q1 will have a direct effect on both self-managed and Elastic Cloud revenue this fiscal year. Going forward, we're implementing measures to tackle the problems we encountered in our sales execution and are seeing encouraging signs of progress, which gives us confidence here. That said, we're keeping a prudent stance in our assumptions around deal closures for the remainder of this year. Let me elaborate a bit more on Elastic Cloud revenue, although we still expect customers will consume against their commitments as we've observed for several quarters now, the slower start to the year in securing commitments will affect Elastic Cloud revenue. And we continue to assume that our self-service motion on Elastic Cloud will remain flattish in dollar terms for the rest of the year. When it comes to investments in the business, we've stated previously that we will balance revenue growth and investments, and we're taking steps to accomplish that. Since we believe the challenges we're facing are near-term and don't impact our core view on the market opportunity or our long-term growth potential, the actions we're taking to cut back on investments are equally measured. We're directing investments toward areas best positioned to drive near-term and long-term growth, especially in GenAI. Specifically within R&D, we'll keep investing in our platform road map. Our product differentiation is essential to our long-term success. When it comes to sales and marketing, we're going to keep adding sales capacity, though we'll concentrate on the areas where the biggest opportunity exists. In some of our other sales and marketing investments that don't involve interacting with customers, we'll pursue efficiencies, since we're able to cut back or push out that spending in the near term without giving up on our long-term growth. And last, we'll also pursue greater efficiencies across the G&A functions. Through all of these actions, we'll bring down fiscal '25 dollar spend by more than the drop in revenue, which means a higher non-GAAP operating margin for the year, and we'll accomplish that without harming our long-term growth opportunity; given the operating leverage built into our business model, we're also still well positioned to deliver higher operating margins as the business scales in the years ahead. With that context, for the second quarter of fiscal '25, total revenue should land in the range of $353 million to $355 million. At the midpoint, that's 14% year-over-year growth, both as reported and in constant currency. For the second quarter of fiscal '25, non-GAAP operating margin is expected to come in at approximately 13%, and non-GAAP diluted earnings per share should land in the range of $0.37 to $0.39, based on diluted weighted average ordinary shares outstanding of between $105.5 million and $106.5 million; for the full fiscal '25, total revenue should land in the range of $1.436 billion to $1.44 billion. At the midpoint, that's 14% year-over-year growth, both as reported and in constant currency. For the full fiscal '25, non-GAAP operating margin is expected to come in at approximately 12.5%, and non-GAAP diluted earnings per share should land in the range of $1.52 to $1.56, based on diluted weighted average ordinary shares outstanding of between 106 million and 108 million. To wrap up, although Q1 performance leaves us unsatisfied, our confidence in the potential for growth remains, and we believe we're still in the early stages of our growth journey. Over the coming months, our attention is on sharpening sales execution, and we'll keep driving profitable growth going forward. So with that, let's go ahead and take questions. Operator?
Matt Hedberg
analystAsh, I'll begin with you. You mentioned this during your prepared remarks, but I just wanted to dig deeper into what you believe are perhaps the most critical actions you're taking to enhance ELSER execution following segmentation, which appears to make considerable sense over the longer term. And can we think in any way about how long you're going to — how long it will take until we sort of witness gains when it comes to speeding up growth?
Ashutosh Kulkarni
executiveYes. I appreciate that question; this is something I've been pondering a great deal, as you might expect, what might we have done otherwise and what we're now doing otherwise. So there are 3 actions we're already taking. The first is that I've considerably boosted the oversight we're applying to how deals advance through the sales funnel. I'm collaborating directly with our CRO, Mark Dodds, and his sales leadership group on this. What we've also been doing secondly is simply pushing more concentrated attention toward our enterprise accounts. These are usually our biggest accounts, the ones holding the biggest budgets, and that has formed a major part of what we've increased. The third item is — and this is less an action as such, but rather the reality that as time moves forward, our reps are getting used to their new territories. They're establishing those relationships; and we're already witnessing indications of improvement as deals progress through the sales pipeline within these accounts. Beyond these 3 items I mentioned, there are a few additional things we were pursuing regardless. To begin with, you've — we've discussed our platform consolidation motion for a while now. It's a motion that has performed extremely well for us. To kind of keep speeding that up during this past quarter, around Black Hat, at the Black Hat conference, we introduced the Elastic Express migration program that assembled all the customer incentives, all the services incentives and everything we required technologically to assist customers in swiftly migrating onto the Elastic platform and truly accomplishing that with minimal risk and minimal effort. The other thing we've been pursuing for GenAI, considering all the success we've enjoyed there, is that we've established a small specialist team, a technical specialist team, that's assisting our customers in building their GenAI applications, helping them accelerate faster, the demand for their skills has also been extraordinary; so all of these factors give me confidence that within the next couple of quarters, we will return to our strong state of sales execution that we've had previously. This is my absolute #1 priority and my commitment.
Matt Hedberg
analystThat was quite thorough; now perhaps I can fit in just one more. We've clearly all been paying plenty of attention to what the competition opens up for you, and it genuinely seems as though you called out several wins this quarter along with new migration technology. What I'd like to know is whether there's a way you could put a number on the growth of that pipeline, perhaps? And I'm also wondering what exactly these migration tools are accomplishing. Could the channel take advantage of these as well, perhaps to speed up those replacements?
Ashutosh Kulkarni
executiveSure. Let me begin with the technology, and after that I'll cover the way we're scaling it all up. On the technology side, there's ESQL, the query language we offer, and it lets customers quite easily take the logic, the rules, the alerts they've built inside incumbent technologies and shift those over to Elastic. There's also the Elastic AI Assistant, which is able to assist in transferring all those rules, alerts, dashboards, and similar items. More recently we introduced automatic import, a capability enabling you to shift data streams very fast — for instance, onboarding data sources — and pull that data onto the Elastic platform. What it does is make use of large language models, applying AI to figure out the schema and generate every mapping required so those data sources get onboarded extremely fast. So every one of those technologies is a genuine help. The other piece of what we've been up to, as I said, is the program itself — customer incentives — since much of the difficulty customers face is typically the duplicate expense incurred throughout the transition period, and the program supplies incentives that help make things somewhat simpler. So how do we scale it? Naturally it's our sales team leaning into things; the pipeline has — the attention and enthusiasm surrounding it have both been really powerful. We launched that Express Migration program at Black Hat. From that point on, we've witnessed substantial interest in it. When it comes to partners, this happens quite naturally. And through our work with hyperscaler partners and with other partners too, we always aim to ensure those partners get leveraged so they apply a similar motion, which then helps push that momentum toward opportunities.
Brent Thill
analystBrent, I believe everyone would appreciate hearing additional details regarding the segmentation changes. So, when considering what proportion of your go-to-market team you replaced, is that a simple way to put it—like we swapped out half of our reps, or twenty percent of our reps now concentrate on different accounts? Is there a straightforward way to make this easier to grasp, so people understand what it means?
Ashutosh Kulkarni
executiveBrent, the place where we saw the biggest effect was the Americas across all verticals, with the exception of U.S. public sector. For us, U.S. public sector is its own separate team; and because of how those territories are structured, we left that area completely untouched. Beyond that, though, nearly every team across the Americas felt an impact. Put plainly, when I assess these adjustments, I remain convinced they were the correct ones. Having examined them from every angle we could think of, I'm confident they're right, since in many respects they align us with what leading companies in the industry do — specifically regarding how many accounts each salesperson handles, which fosters sharper focus. Where we fell short was in how we carried out the handoffs of those accounts. Looking back, I'd have spread those adjustments out over a longer period and phased them in more slowly, which is exactly where our attention sits today. Our attention is on thoroughly reviewing each of those accounts, collaborating closely with those reps as they get comfortable with their books of business, ensuring they ramp up fast and steadily build pipeline momentum. Honestly, from my perspective this is just a short-term disruption, and we're already making strong progress. Within a few quarters, I anticipate we'll return to the standard of sales execution we've always been used to.
Brent Thill
analystAll right. I simply want to confirm I caught that correctly. You altered each vertical with the exception of Fed.
Ashutosh Kulkarni
executiveWithin the Americas.
Brent Thill
analystSo I suppose the obvious next thing to ask, Janesh, is this: considering how big that disruption was, why did the guidance not include a larger amount of padding, so that you'd have given your team — and yourself — a bit of breathing room?
Janesh Moorjani
executiveYeah, Brent, good question. When we put the guidance together and considered how to frame it along with the assumptions behind it, we expected a certain amount of movement tied to this. And, look, like Ash mentioned, segmentation shifts occur as pretty much a routine thing at nearly every enterprise software company. What we did was clearly far bigger in scale. We did take that into account to some extent while constructing the guidance — we expected part of it. However, much of the effect we experienced came very late in the quarter. It showed up for us only during July, and by then it was somewhat too late to attempt any recovery within Q1; so, as Ash laid out, we subsequently implemented the corrective actions, and we're already beginning to observe early positive signals, and we anticipate getting back to our historical record of better execution over the coming couple of quarters.
Pinjalim Bora
analystSo once more, digging into what shifted and all of that, particularly regarding that commitment shortfall. It looks as though it's hitting cloud as well as self-managed. I'm attempting to figure out whether there were more commitments on one side versus the other? Did the pricing changes for self-managed, which I think took effect in May, play any part in this? And on the macro side, did you notice any heightened scrutiny around deals that got worse in July or afterward? Or would you characterize this mostly as sales execution?
Janesh Moorjani
executivePinjalim, it's Janesh here. Let me handle that one. You've got it right — the effect showed up in cloud and self-managed alike. It wasn't confined to a single format, since what it mirrored was the wider sales execution problem. As for the price rise we implemented at the beginning of Q1 and whether it contributed anything, my view is that it didn't, given that it was a single-digit price increase tied principally to the technology enhancements we had rolled out; therefore we saw no meaningful effect on customer commitments stemming purely from that matter. If anything, my sense is that the customer commitment shortfall came down to a wider sales execution problem. Even where revenue is concerned, when I consider Q1 revenue along with the outlook for the year, the price change was never meant to be a significant revenue driver for us this year, partly since it was a fairly small adjustment, a single-digit percentage increase, and it will only begin flowing into renewal contracts when renewal time arrives, and as you know, we also sign multiyear contracts. So that didn't serve as much of a driver for us here in — regarding the Q1 impact.
Pinjalim Bora
analystYes. Got it. One additional follow-up for you, Janesh. Could you discuss the real consumption run rate we're seeing among annual cloud customers, and how it's been trending compared with the committed consumption run rate? And perhaps also address the linearity of cloud consumption patterns over the last 3 months and into August.
Janesh Moorjani
executiveYes. Glad to cover that too. I'd say annual cloud consumption trends came through pretty well for us in Q1, in line with what we anticipated. Across both the enterprise and commercial segments, customers keep consuming at a good pace against commitments they've already made to us. That's a strong signal that customers who adopt cloud keep getting substantial value from our platform; and the challenge on cloud as we look forward is that since we secured a lower degree of new commitments in Q1, that will — that was, again, tied to the sales execution issues. That affects our broader revenue outlook; but as far as the rate of consumption goes, I'd say it was fine. On linearity during the quarter, as you're aware, we've historically not provided a monthly breakdown of the business simply because consumption patterns can fluctuate naturally from customer to customer. So we prefer not to lean too heavily on any single month's data; and so I won't break that out here or give specifics about August. But I'll simply say it unfolded consistently with prior patterns and with our expectations entering the quarter.
Mike Cikos
analystI also want to come back to what we discussed regarding segmentation. I just need to confirm that my understanding is correct. It seems that you spotted this problem fairly late in the quarter, once again, just given how things unfolded during those months. What I'm trying to figure out is, regarding the adjustments your team has made, at what point did they actually take effect? Did it happen in August, or was it toward the end of July? My reason for bringing this up is that I'd like to find out, if that's possible, I realize we are 4 to 5 weeks past the conclusion of the July quarter; however, have you observed any significant shift on your end as a result of these modifications related to segmentation?
Ashutosh Kulkarni
executiveTo put it plainly, the segmentation modifications were introduced when the fiscal year started. So on May 1, every one of those adjustments was implemented; and to be clear, as happens annually, which is standard for the majority of software businesses, most enterprise organizations similar to ours, a certain amount of territory adjustments will occur. This is a fairly routine thing to do. In our situation, as I said, on this occasion, those adjustments were bigger. And then when we — as we — as Janesh mentioned, we became aware of the effect it was creating in — later on in July. The moment we began noticing that, we started applying some of the remedial measures I described. The discipline we began applying to how we monitor the pipeline, really connecting with the salespeople who had the highest count of account changes, really examining how the pipeline was moving and advancing within those accounts, the emphasis on enterprise accounts and so forth. And from that point onward, as we have continued to make progress, we are already witnessing encouraging indicators; we are seeing deals move through the pipeline more effectively since, once again, the deals that fell out of the quarter out of Q1, they were not gone, they simply didn't finalize on schedule, a lot of them. And several of them have closed since then, and we anticipate the rest will close in the normal course; so that is our priority to ensure that we get all these measures implemented swiftly, and we are already observing that advancement. We are seeing the encouraging indicators, and that is what gives me the assurance that we will return to our previous level of robust sales execution within a couple of quarters.
Mike Cikos
analystGreat. And to confirm once more, I want to be sure I've got this right. So it's the mix of those adjustments you've made related to segmentation, plus the smaller amount of new commitments booked in Q1, that's really shaping how you see the guidance for the remaining part of the year — and the sense that this will probably need a few quarters to work itself out.
Janesh Moorjani
executiveThat's right, Mike, it comes down to the same thing. Our problems with sales execution showed up in the lower commitments we had. We simply didn't close enough deals. So it's the same thing. And you're completely correct that we believe and expect that, given everything we're doing, we'll get back to the stronger execution we had before within the next few quarters.
Tyler Radke
analystSo I suppose my goal here is just to revisit the details of that shortfall and get a clearer picture. From what I'm hearing, it was largely concentrated in the enterprise segment, which presumably handles those big renewal deals. Or at minimum, current customers. And so — I guess, if you're not encountering any issues around consumption, then is this implied reduction to cloud simply a matter of caution, given that you have somewhat reduced visibility into backlog? Or is your view that the deferral of these deals effectively postpones new use cases and new ramps from arriving on the cloud, and it's kind of a timing issue — could those commitments be needed for these use cases to ramp? Just help us get our heads around this, because it sounded like consumption was fine, and yet you're lowering, in a sense, your consumption projections for the whole year.
Janesh Moorjani
executiveTyler, perhaps I'll give that a try. So to start with, regarding where the impact showed up, it wasn't confined to the big enterprise accounts, because as part of all those segmentation changes, as Ash mentioned, we altered things throughout the whole Americas team, with the exception of public sector. So that affected quite a few commercial accounts and relationships, along with the changes in those areas as well; so the effect was broader than just one segment. Naturally, the enterprise segment feels it more, since those are usually bigger accounts with bigger deals and bigger transactions, while on the commercial side things move a bit faster. When it comes to the split between new workloads and expansions and renewals — our gross retention rates remained extremely robust; those were in good shape. We felt fairly confident about the renewals and the way we closed that business. So that portion was solid. What I believe really mattered was the incremental workloads, whether net new workloads that a rep is attempting to generate within existing accounts, or net new accounts we were trying to win, and that's where the impact showed up a bit more. Then, regarding consumption revenue and the way that unfolds — in our annual cloud motion, as you're aware, we sign a contract with the customer, the customer commits to us, and then over time they draw those commitments down as they consume against what they've committed; so the assumptions built into the model and into our guidance are that the pace at which customers consume against their current commitments was healthy, and we anticipate that it will stay healthy moving forward. But the reality is that we fell short on landing new commitments here in Q1, our sales execution problems are going to require a couple of quarters for us to resolve. And so that addition to the pool, in the form of new and expanded commitments, won't show up at the same rate we've seen historically. So because of that, there's a cap on how much burndown you're able to achieve, which in turn puts a ceiling on cloud revenue. That's the framework, and that's exactly how we've constructed the guidance along with the assumptions we've included for the remainder of this year.
Tyler Radke
analystI realize a ton of things are in flux here. What I wanted to follow up on, Ash, concerns open source — and clearly, within the GenAI ecosystem, open source matters enormously. I noticed, I believe just a few minutes ahead of the earnings release going out, that you made an announcement about an open source license, essentially adding AGPL for the source code. Could you discuss what makes that announcement significant, and also how you're approaching the strategies involved, especially given how much open source counts in the GenAI market?
Ashutosh Kulkarni
executiveYes. I appreciate the question. Look, this is — I hope it's evident to everyone that open source has always been our ethos. That way of thinking has shaped our behavior and our operations from the very beginning. That said, about three years back, we put certain license changes into effect, and those made it impossible for us to describe ourselves as open source. So we went with the term free and open instead, and there were very particular reasons behind that choice. As all of you know, a great deal has changed since then. AWS basically took the code, forked it, and created OpenSearch. Meanwhile, the ways we set ourselves apart — not just from OpenSearch, but from every other offering in the marketplace — have only kept expanding. So for us, that has been an extremely favorable development. Looking forward, the major opening in front of us is generative AI — specifically, becoming the go-to vector database that gets integrated into and powers each contemporary GenAI app currently under development. That strikes us as a huge chance. The figures I gave you demonstrate that meaningful traction has already been achieved, and our aim is to speed that momentum up even further. Bringing AGPL in as a license option means that everywhere developers usually look for open source software — every forum, every community hub — Elastic Search can now stand as an open source choice we're proud to offer them. And as more people adopt Elastic Search for vector database and vector search scenarios, our capacity to seize opportunities in the GenAI market over the coming years grows right along with it. That makes this essential for us. It's a deeply strategic move, and it has me genuinely thrilled.
Raimo Lenschow
analystYou already touched on this earlier in the call, Ash — regarding S3 and how customers are engaging with it. What are you seeing when it comes to those early trials beginning to turn into something more? And in what way does that assist you — might it be beneficial for you when it comes to the second half, in terms of bringing in new workloads? Is that something already playing a role that could provide support there? I also had a follow-up question for you both.
Ashutosh Kulkarni
executiveYeah. No, I appreciate that question, Raimo. Look, one point I brought up even during my prepared remarks is that our search business sped up this quarter; and as I consider every element driving that, the truth is that interest in search is rising again thanks to generative AI; many customers are putting these semantic search and RAG use cases into practice, and we've discussed before that a key early step is getting included when these applications are designed, after which those use cases and workloads expand. And as you observed this quarter, just as I said, we're witnessing faster growth in our search use cases, and that's really encouraging. It gives me a lot of confidence in our strategy. It gives me a lot of confidence in how we stand apart from competitors and in the fact that we're winning; so we're committing further. And over the long run, my feeling is this will prove extraordinarily valuable for our company.
Raimo Lenschow
analystAll right, that's great. Now here's one for Janesh. If you — I mean, consider this: when you've got to plan things out, a large number of your salespeople will likely have to essentially begin the year anew. So what's your thinking around costs and investments for the year, and how will that play out across the various quarters?
Janesh Moorjani
executiveYeah, Raimo, like I said before, our stance has consistently been that we'll strike a balance between growing revenue and making investments. And right now, we're putting measures in place to achieve that. However, given that the problems before us are short-term in nature, we intend to be prudent regarding how we handle expenses; so when I consider the investments being made in the business, our focus will remain on the areas where we can keep investing and put money in to fuel growth, in both the short run and the long run. A significant portion of that spending goes toward R&D, especially anything tied to GenAI. Then when it comes to sales and marketing, we'll direct investments toward areas where we can pursue targeted growth. And I believe we'll — we'll move somewhat more slowly in areas whose impact on growth isn't direct. Take, for instance, certain roles that aren't in selling, or other sorts of investments, such as those in the brand program and similar things. After that, we'll keep pushing for efficiencies on the G&A side, just as we've always done. That's really an ongoing process; and taking all of it together, on a full year basis we expect to cut our spending for the year by a larger amount than the drop in revenue, which results in a modest rise in non-GAAP operating income and margin. That's the path we've chosen; and as we work our way through the remainder of this year, and as we observe ourselves getting back to better execution across the coming couple of quarters, we'll then form a perspective on our investment philosophy past that point; but going forward, I still see opportunity for us to grow operating margins in the years ahead, since operating leverage is built into the business model.
Koji Ikeda
analystGoing back to sales execution, I realize a lot of attention has gone to the Americas, yet your international business is quite sizable as well. So my question concerns the international go-to-market strategy — more precisely, was a comparable strategy going to be rolled out internationally? And was it halted? Or, from the learnings you've gathered over the last few months in the Americas, are you applying those internationally through some similar change? I'm simply trying to get a sense of what to expect on the international go-to-market strategy.
Ashutosh Kulkarni
executiveYes, Koji, I appreciate the question. The way our international teams are structured is mostly around countries, correct? We have teams in various large countries, and then some of those get grouped into regions. Because of how big the Americas business is, the changes we believed were necessary for the long term mattered far more there, since the scale is much greater. When it came to international regions and countries, we felt quite good about how they were organized. So nothing was planned and nothing was done. Even within the Americas, in the public sector — since public sector operates quite differently depending on whether it's state and local versus federal, and in federal you have civilian, DoD, and so on — none of that was touched. Everything was in the Americas, outside of public sector, where we have the strategic segment, the enterprise segment and the commercial segment. Within those, we broadened the strategic segment. We increased focus on larger customers in the enterprise segment by cutting the number of accounts per rep, and then we set up separate greenfield opportunities to improve new logo acquisition. Those were the changes, and they were mostly in the Americas rather than in EMEA or APJ.
Janesh Moorjani
executiveAlso, Koji, I want to mention what we brought up before during our comments: to a smaller degree, certain deals in EMEA slipped toward the close of the quarter as a result of budget limits on the customer side, though this happened only to a smaller degree. And whether that ties to the macro or anything like that is simply too soon to determine.
Koji Ikeda
analystUnderstood. Then one more thing for Janesh. Looking at RPO, sequential growth during Q1 came in lower than what we saw in Q4. Historically, whenever the first quarter begins on a downward note, the self-managed piece of subscription tends to move in a fairly foreseeable way, so I'm wondering whether you could shed some light on how we ought to frame RPO alongside self-managed revenue?
Janesh Moorjani
executiveSure. Koji, that's a fair question. Taking RPO as a whole, my view is it simply mirrors the challenges we already described regarding how we performed across Q1. As we've noted, nothing has fundamentally shifted when it comes to our longer-term opportunity or the way we go to market. So we're eager to get back to executing more strongly. On what that specifically implies for self-managed, I wouldn't draw any particular link. Like I said, the problems we encountered in Q1 touched both cloud and self-managed, and as we get back to stronger execution over time, my expectation is that both would recover. Considering how revenue gets recognized, the upfront piece of a self-managed subscription represents a fairly modest share of total revenue for us right now, so it doesn't create any significant swings for us when it comes to lumpiness or revenue recognition.
Joe Vandrick
analystJoe Vandrick here, filling in for Patrick Colville. Ash, you said search picked up speed during the quarter; so I want to ask, does that imply security and observability did a bit worse than what was expected?
Ashutosh Kulkarni
executiveWell, the way I'd frame it is that basically every part of our business — search, observability and security — took a hit from the fact that we had fewer total customer commitments in the quarter. So the sales segmentation changes had an effect on all of it. It wasn't limited to particular use cases instead of others, all of it got impacted. Even so, our search business showed an acceleration, and that mostly comes from the success we've been seeing with GenAI use cases.
William Vandrick
analystThat's clear. For my second question, could you briefly discuss the competitive landscape — in AI enterprise search, why does Elastic usually come out on top? And beyond that, what's needed to drive much deeper adoption across your customer base for these GenAI search use cases?
Ashutosh Kulkarni
executiveYeah. Absolutely, of course. To start, this is a space where our brand reputation is exceptionally strong, correct? People see us as search authorities, and they see us as the Search AI company; so from that angle, this is a very obvious space for us. The thrilling part is that the space where our brand is most recognized happens to be the one experiencing an enormous revival of interest — rising interest — thanks to GenAI. Much of the data that ultimately gets utilized in these types of GenAI, RAG-style applications already resides in Elastic Search, meaning customers can very easily take advantage of our vector database functionality to convert that data into vector embeddings and then apply it in semantic search or RAG sorts of use cases. So there's genuine strength that comes from being the incumbent. That said, we also possess what I'd call one of the finest vector databases available, purely regarding performance and scalability. And what we hear from our customers is, first, we have a truly robust vector database offering. Second, we have numerous enterprise features — the whole overall set of capabilities surrounding hybrid search, reciprocal rank fusion, all the things we've introduced, plus the developer-focused capabilities that let developers more easily adopt and use our product here. All of this gives us the sort of competitive differentiation that we think will be very durable differentiation as time goes on.
Rob Owens
analystI'd like to dig a bit deeper into the security area and Elastic Express Migration, plus what you're up against from competitors — especially given that, as I see it, a sizable portion of that Splunk customer base might be winnable. What's the competitive picture, and how willing are customers to make a switch?
Ashutosh Kulkarni
executiveSure. Appreciate that, Rob. Regarding the competitive landscape — nothing has really shifted when it comes to our capacity to come out on top. Customers are showing plenty of appetite for moving off the incumbent players. What Express Migration is built to accomplish is pulling together not only the technologies I've mentioned previously — I've brought up ESQL, I've brought up Attack Discovery — but also the capabilities we announced not long ago around Automatic Import, which are built to make it simpler for customers to get those data flows and data sources onto Elastic. On top of that, the program features customer incentives. Our goal, then, is to cut the risk, cut the effort, and smooth the path for customers making the switch — that's where we've been focusing — and this also hands our sales teams plenty of material to bring to customers. It's simply a very natural thing for them to lead with. So I have strong confidence this momentum will keep going; and as I mentioned, the impacts — the near-term impacts we experienced from certain segmentation changes — the fixes fall within our control. We're already taking action on that. And with the sorts of things we're doing to drive migrations and consolidation onto our platform, I'm especially confident and excited.
Rob Owens
analystDo you have any perspective on doing the same thing — pardon me — when it comes to observability too?
Ashutosh Kulkarni
executiveBoth security and observability are areas where we're pursuing this. Clearly, when it comes to observability, log analytics is where the attention goes; for security, SIEM is the priority, though it isn't limited to security alone. We're noticing those identical patterns carrying over to each of the two drops; that's a wonderful inquiry, and it's precisely the way we're handling it.
Andrew Nowinski
analystI'll be brief. Could you quantify the number of deals, or the size of those deals, that fell out of the quarter? I'm just trying to get a sense of what the quarter might have looked like and what sort of cushion you have heading into next quarter.
Janesh Moorjani
executiveYes, Andy, I'll handle that. As a general rule, we don't tend to break out the amounts of customer commitments and orders and so on; but I'll simply say it was significant, since as you can see it clearly led us to shift the revenue figure here rather meaningfully; and although these deals are moving along well through the sales funnel, I wouldn't anticipate all of them closing in Q2. A number of these will take some time to close; and we're also still working through the corrective actions, while we've seen plenty of encouraging signs so far. As we've said, it will take a couple of quarters for us to return to a stronger level of execution than we've seen previously; and so when I consider the revenue guide for the year, it accounts for that stretch of time as well; so those are some of the factors that went into how I thought about the impact of the miss we had here in Q1.
Andrew Nowinski
analystAnd then one more question, as a follow-up. I suppose if your concern is that these deals won't be finalized within — will need longer than a couple — longer than 1 quarter to be finalized, it sounds like that might be somewhat beyond your ability to influence. It isn't really something you brought on yourselves by simply swapping the salesperson assigned to the account. What I'm asking is — do you have any worry regarding competition at any of these accounts where the deals got delayed?
Ashutosh Kulkarni
executiveNo. So this — competition isn't the issue here. Here's how I'd put it. Whenever an account changes hands, the new rep now needs to build those relationships and essentially take things over. That transition has to go smoothly, and that's the spot where we stumbled; and that's the thing we've been zeroed in on since then; so when we say that we anticipate getting back to being — getting back to where we're executing sales at full strength, what we actually mean is simply the amount of time required for a rep to get established, take over, and keep pushing forward; it has nothing to do with competition, since none of these deals have disappeared or become losses as far as we can tell. The only issue has been getting them finalized in Q1, and that's something we're working on right now.
Joel Fishbein
analystSo Janesh, I suppose this is really just following on from what Andy asked. When you put the guidance together, what was your process? And how much assurance can you offer that these figures will actually be met for the 2Q and for the whole year?
Janesh Moorjani
executiveRight, Joel. Regarding how we approached the guidance, the first thing is that we clearly took into account how all those Q1 transactions we thought would close ended up not closing — every bit of that is captured in the revenue guide. And since we now know about this problem and began implementing corrective actions in July, we have clearly built that into a more conservative internal outlook regarding how we anticipate deals closing. I touched on that during some of my earlier remarks too, when I mentioned prudent assumptions around deal closures for the remainder of this year, and we incorporate that into the guidance as appropriate. So when I think about the overall way we construct guidance, that hasn't shifted. A prudent approach has continued to be maintained by us; the philosophy itself hasn't fundamentally been altered. That said, looking across the steps we've taken, encouraging signs are showing up, with deals moving along well through the sales funnel. We're witnessing plenty of deep customer engagements as attention goes toward enterprise accounts. And like Ash mentioned, reps are now settling in nicely to their territories and establishing those relationships. Even so, we aren't assuming things snap back to normal right away when it comes to our overall performance. Our assumption is that fixing this will require a couple of quarters. That's the approach we've adopted for how we've constructed the guide.
Ashutosh Kulkarni
executiveOkay, thanks a lot for being here on today’s call. We’re putting a lot of attention on getting better at how we sell, and that is going to stay my top focus over the next few months. Our confidence in the potential for growth and the opportunity in the market is unchanged. Thanks so much, and enjoy your evening.
Operator
operatorThat brings us to the end of this call. We appreciate your joining us for today's presentation. You're welcome to disconnect at this time.
Read the full transcript via the API
You're viewing the first half of this call. Get the complete Elastic N.V. transcript — plus 132,000+ transcripts from 7,000+ companies, speaker segments, AI summaries and full-text search — through the EarningsCalls.dev API.
Get the API View API docs →This call discussed
For developers and AI pipelines
Programmatic access to Elastic N.V. earnings transcripts and 132,000+ others is available through the
EarningsCalls.dev REST API. Plans from $39.99/month — full transcripts, speaker segments,
full-text search, and the recently-added /api/v1/transcripts/recent polling endpoint for ETL pipelines.
More tools for stock research
OptionsBell: an unusual options activity scanner that tracks options flow across all US stocks and emails you when large trades appear in Elastic N.V. or any ticker on your watchlist.
StockMarketScan: a stock screener with alerts: 24 pre-built screens refreshed every 5 minutes, watchlists and email notifications. Both offer API and MCP access and fair monthly pricing.