This conference call transcript was computer generated and almost certianly contains errors. This transcript is provided for information purposes only.EarningsCall, LLC makes no representation about the accuracy of the aforementioned transcript, and you are cautioned not to place undue reliance on the information provided by the transcript.
spk01: Ladies and gentlemen, thank you for standing by and welcome to the HashiCorp's fiscal 2024 first quarter earnings call. At this time, all participants are in a listen-only mode. After the speaker's presentation, there will be a question and answer session. Please be advised that today's conference is being recorded. I would now like to turn the conference over to your first speaker today, Alex Kurtz, VP of Investor Relations and Corporate Development. Thank you. Please go ahead.
spk03: Good afternoon, and welcome to HashiCorp's Fiscal 2024 First Quarter Earnings Call. This afternoon, we'll be discussing our first quarter fiscal 2024 financial results announced in our press release issued after the market closed today. With me are HashiCorp CEO Dave McJanet, CFO Navam Willienda, and CTO and co-founder Arman Daggar. In conjunction with our earnings press release, we have published an earnings presentation that provides additional financial information about our quarter. We encourage you to review that presentation in advance of our call. You can access it on our investor website at ir.hashicorp.com. Today's call will contain forward-looking statements, which are made under the safe harbor provisions of the Private Securities Litigation Reform Act of 1995. Forward-looking statements include statements concerning financial and business trends, our expected future business and financial performance and financial condition, and our guidance for the second quarter and full 2024 fiscal year. These statements may be identified by words such as expect, anticipate, intend, plan, believe, seek, or will, or similar statements. These statements reflect our views as of today only and should not be relied upon as representing our views at any subsequent date. and we do not undertake any duty to update these statements. Forward-looking statements by their nature address matters that are subject to risks and uncertainties that could cause actual results to differ materially from expectations. During the call, we will also discuss certain non-GAAP financial measures which are not prepared in accordance with generally accepted accounting principles. The financial measures presented on this call are prepared in accordance with GAAP unless otherwise noted. A reconciliation of these non-GAAP financial measures to the most directly comparable GAAP financial measures, as well as how we define these and other metrics, is included in our earnings press release, which has been furnished to the SEC and is also available on our website at ir.hashicorp.com. With that, let me turn the call over to Dave. Dave?
spk17: Thank you, Alex, and welcome, everyone, to our first quarter earnings call for fiscal 2024. pleased to report first quarter results that exceeded our top and bottom line guidance with revenue of 138 million representing year-over-year growth of 37 and solid improvements in our profitability with our first quarter of positive free cash flow as a public company current non-gap remaining performance obligations reached 394.6 million dollars representing 29 year-over-year growth And compared to last quarter, we added 32 customers with greater than or equal to $100,000 in annual recurring revenue to reach a total of 830. Our HashiCorp cloud platform offerings reached $16.5 million in revenue, representing 12% of subscription revenue in the quarter. We remain excited about adoption trends as we continue to roll out new features and new capabilities during FY24. Against a challenging environment, I'm pleased with the solid Q1 results that the team delivered. However, macro challenges continue to impact our business, and I'd like to provide more color in what we're seeing in the market. During Q1, Armand and I spend much of our time speaking with customers. The key theme from these discussions, regardless of customer size, is the uncertainty that they are feeling about the economy and what it means for their own businesses. As we have mentioned in the last few earnings calls, we saw this budget uncertainty start in October of last year as higher interest rates began to impact our customers thinking about their FY23 budget cycles. This economic uncertainty is driving organizations to optimize their software spend. Procurement teams are scrutinizing many larger software purchases and stretching deal cycles. The deepening inspection of budgets is happening across all of our customer segments, but most noticeably in our largest customer deals. Despite these near-term challenges, we believe the long-term trend to cloud computing remains unabated. We continue to see demand for our products as customers continue to plan their cloud initiatives for the next several years. I would highlight the customer stories we have outlined in our earnings presentation on the IR site to give us confidence in our market opportunity and product fit. These customers include a large US-based financial services company, a back-of-office software platform, and a European stock exchange, all very diverse verticals and all very early in their cloud adoption journey. We are laser-focused on building trust with these customers so that we can be a central partner as they continue to invest in their cloud initiatives. In addition, our focus on adding larger new customers produced solid traction during Q1 as we added 26 net new Global 2000 logos, the largest number we've added in five quarters, and we continue to add a healthy number of greater than $100,000 ARR customers as well. These large customers are an important part of our future, and our model is built to grow our footprint with them as we become an increasingly critical piece of their infrastructure over time. So while we're seeing heavy budget scrutiny on our large expansion deals, these entry-level deals with large companies give us confidence about the long-term shift to cloud and our role as the enabler of that transition. We also continue to see strong and growing interest in Boundary, which we introduced late last year. As a reminder, Boundary solves a key security challenge for organizations by using identity secure remote user access. As I noted earlier, Arman and I spent much of Q1 on the road with customers. In nearly every meeting, customers proactively inquire about Boundary, which is a great signal as to the longer term opportunity we see for the product. Next week, we will host Hashi Days, our European user conferences, where we will make a series of announcements that highlight ongoing product innovation, particularly around cloud security automation. I look forward to sharing more details during next quarter's call. Before handing it over to Navam, I want to provide more detail on the announcements we made after the market closed today. First, we announced a reduction of our workforce by approximately 8%. I want to acknowledge that a lot of talented people who made meaningful contributions to HashiCorp are leaving the company. This was not a decision we made lightly and is part of a necessary effort that Navon will describe to reduce our operating costs to reflect the current customer spending environment. Second, we are excited that Susan St. Leger will be joining the company in July as president of our worldwide field organization. Susan is a master of scale and a deeply technical sales leader who understands how to make the most of complex product portfolios. Susan has been on our board since 2019, so she's already well acquainted with HashiCorp, our products, and our team. With Susan, we get the rare opportunity to work with an experienced leader who has done this multiple times, having most recently led the field organizations for Okta and Splunk, where she helped them each surpass a billion dollars in revenue. We have trust and confidence that her experience and leadership will serve our field and overall organization well, through the current economic conditions, as well as through our next phase of growth. I believe strongly in our opportunity given the long-term trend of cloud adoption and believe we are now better positioned to take advantage of that opportunity. And in line with the guidance we provided last quarter, we continue to operate against an aggressive goal to achieve profitability next fiscal year and remain on track to meet this goal. Now, I'd like to turn it over to Navam, and I look forward to answering any questions.
spk14: Thank you, Dave, and thanks again to everyone for joining us today. Our first quarter results showed solid progress in our fundamental customer adoption engine. Our process remains very consistent. Customers adopt our open source products throughout the organization. We land the organization as a commercial customer with a particular product. The customer expands its product usage and then extends into adjacent products. The success of this adoption engine drove our customer count to increase by 261 in Q1. and our 100k plus ARR customer count increased by 32. Our total customer count and 100k plus ARR customer count is currently 4,392 and 830 respectively. While the pattern of customer adoption remains consistent, as Dave mentioned, the economic headwinds we've noted in the past few quarters also continued into Q1. Combined with our typical first quarter seasonality, we saw ongoing pressure on customer budgets which caused slowdowns in customer behavior and elongation of sales cycles. The impacts were most acute among our larger contracts within our global customer segment, along with the large enterprise customer segment. In addition, one of our largest customers in the retail sector adjusted for some excess capacity and reduced a portion of their spend with us. The impact to our quarterly growth and net retention rates due to this customer spending adjustment was roughly two percentage points. Despite the adjustment, the customer continues to be very engaged with our team and remains one of our largest customers. We expect the current buying environment will create ongoing uncertainty in the pace of large customer expansions and extensions for the rest of the fiscal year. Accordingly, we have reflected these expectations in our full-year guidance. We've also widened the range of potential revenue outcomes given the overall purchasing environment. While we have shown ongoing diligence in managing our expenses, we are operating in a very cautious customer spending environment. As a result, we took additional steps today to reduce our cost structure through a reduction in force of approximately 8% of our workforce. Before making any employee reductions, we took a number of other carefully considered actions, including reducing our program spend and eliminating open but unfilled jobs. it is difficult to transition out valued employees who have helped build HashiCorp, and this was a very hard decision for the company. However, we also believe it is necessary to have the right spending and investment profile to navigate the current economic environment while also maintaining enough resources to deliver on our long-term plan. Following the reduction in force, which we expect to be materially complete by the end of Q2, we will begin to see the impact of these reductions in our free cash flow in Q3 of this year and beyond. We expect free cash flow margins of approximately negative 5% in FY24, followed by sustainably positive free cash flows on an annual basis the following year and beyond. Other than seasonally low second quarter cash flows, we're expecting all other quarters to have positive free cash flows. We are maintaining our target to reach non-GAAP EBIT profitability in the second half of FY 2025. With that, let's move on to our guidance. Our full guidance numbers can be found in our earnings presentations available in our ir.hashicorp.com website under Financials, Quarterly Results. I encourage you to read through the doc for full metric disclosures, share count disclosures, and GAAP to non-GAAP reconciliations. To summarize our guidance, For the second quarter of FY24, we expect total revenue in the range of $137 million to $139 million and a non-GAAP operating loss in the range of $46 million to $43 million. For the full year 24, we expect total revenue in the range of $564 million and $570 million and expect FY24 non-GAAP operating loss in the range of $113 million and $108 million. Thanks for your attention. Dave, Armand, and I are available to take any of your questions. Alex?
spk03: Thanks, Navam. With that, operator, let's go to our first question.
spk01: Thank you. As a reminder, to ask a question at this time, you will need to press star 1-1 on your telephone and wait for your name to be announced. To withdraw your question, please press star 1-1 again. Please limit yourself to one question. Please stand by while we pile our Q&A roster. Our first question comes from the line of Sterling Addy with Moffitt Nathanson. Your line is open. Please go ahead.
spk11: Yeah, thanks. Hi, guys. I'm curious, with Susan St. Ledger coming in to head up sales, is there an early sense of the extent or magnitude of the changes that you want to make to the go-to-market structure in terms of either approach or, you know, either staffing, et cetera? Because you also mentioned some changing in program spend as well. Thank you.
spk17: Thanks for the question. I think it's really about as we step back and think about this next phase of growth in front of us, we have the unique opportunity to bring in a go-to-market leader who has done that now multiple times in multiple different companies. And so we're super excited about that opportunity. And I think candidly, that's the aspiration. It's about setting ourselves up for the next generation of scale that we certainly envision ourselves progressing through as a strong independent company, and that's really what it's about. There's really nothing beyond that. Navalny had alluded to some program spend changes. I think we're just reflecting some program changes that we had made over the last quarter or so to try and just keep the cost relative to the revenue line, but not related to Susan.
spk11: Understood. Thank you.
spk17: Thanks, Sterling.
spk04: Next question.
spk01: One moment. Our next question comes in the line of Derek Wood with TD Cowan. Your line is open. Please go ahead.
spk08: Oh, great. Thanks. One question I'm getting from investors is if you're seeing customers move from commercial to open source, given the budget pressures out there, obviously there's those dynamics in your end markets. Just was hoping to get a sense of if you're seeing any of that or kind of what's your view on the risk of those kind of term dynamics as you look going forward?
spk17: Hey, Derek. I'll answer that one again. The short answer is no. The open source products solve a problem for an individual. The commercial products solve the problem for an organization. So, in a sense, they're fundamentally different products. And so, no. I think what we are seeing is very, very consistent with what we've been communicating over the last couple of earnest calls, which is As Arwen and I both have been traveling a ton, what we're seeing at the front end is very, very consistent in terms of interest in what we do, design when decisions are being granted to us, no change to the competitive environment. What we're really just seeing is increased scrutiny in the procurement process that is just difficult to predict, as we've indicated over the last couple of calls. And much like other vendors in the market, that is putting pressure on us, but that is no different than really anybody else. What I don't hear anybody doing is changing their plans. You know, the crypto cloud remains unabated, and I think as you sort of start to look at some of the numbers in our earnings report, you'll see we added 26 new global 2,000 customers, 32 customers over 100,000 in ARR, and another quarter of strong NDE, which I think really just speaks to that consistent long-term trend and really no material change otherwise.
spk04: Okay, thank you.
spk17: Thanks, Derek. Next question.
spk01: One moment. Our next question comes from the line of Michael Turretts with KeyBank. Your line is open. Please go ahead.
spk13: Hey, guys. I just want to try to get as much of a sense for what's changed as possible. You've held up extremely well during a period in which people have seen this type of scrutiny deal cycles extending, et cetera. And in fact, to some extent, cloud optimization seems to have benefited you in prior quarters. So is there anything that you feel like was an inflection point here that might have determined your outlook worsening for the year?
spk14: Hey, Michael. Hey, it's Navam here. Thanks for the question. So in terms of what's changed, I think the main points to talk about is what's not changed is the front-end environment, which is The pipeline activity, the pipeline creation activity still remains very strong. And Dave mentioned in the call, you know, very healthy quarter in terms of the G2K ads, 100K ads, and total customer ads. So the activity of cloud transformation efforts, cloud efforts, all those things remain similar. What happened in the first quarter, and this is a little bit of first quarter seasonality as well, the first quarter in a very long year in this new budget cycle, you saw a lot of headwinds, a lot of procurement pressures in the global segment and the enterprise segment related to very, very large deals or large deals. And that's reflected in the guidance range that we've given. So that's the material change we saw in the first quarter. But the main thing to remember with these large deals, and I'll give you an example of a first quarter deal that we were working on, and it was held up in procurement due to some procurement process issue. ended up closing in the second quarter as a multi-year deal using several of our products. So these deals don't get lost for competitive pressures. They don't get lost because the cloud transformation effort is canceled. It just elongates, and they happen when they move to the next. They happen in different quarters.
spk17: And maybe, Dave, let me just add kind of a subjective commentary. I think as you see on the Hyperscalers, there's a lot of scrutiny around anything related to the cloud narrative at the moment. And you see that in the hyperscaler results, and certainly that seemed to be more acute in the quarter based on what I saw externally than in previous quarters. We are fundamentally tied to the cloud transition, and that does cause things to get elongated as there's increased scrutiny on certainly larger transactions associated with anything cloud-related.
spk13: Thanks, David. And then Devon.
spk04: Thanks, Michael. Next question.
spk01: One moment, please. Our next question comes from the line of Ittai Kidron with Oppenheimer. Your line is open. Please go ahead.
spk16: Thanks, guys. I'd like to dig in into the retail customer that reduced portion of the spend. Just a few things around this. First of all, how big of a customer is it as percent of revenue to have a two-point impact? It must be quite significant. Customer can give some color on why they reduced spend or just not using it or didn't see value there. And, Navam, would it be fair to say that without this customer, you're actually, if I'm doing the math right, actually guiding in line to consensus for next quarter? Is that the right way to think about the magnitude?
spk17: Any time, Dave. Thanks for the question. I'll let Navam answer the math side of it. I'll answer the more subjective side of it. Yeah, I think as we shared in the prepared remarks, there's a retail customer that had procured entitlements really for peak season. It's probably a really good example of what's happening across the board around procurement and finance scrutiny. They ended up right-sizing that particular entitlement for that particular product for that particular application for their state, which is consistent with what other vendors have commented on. But in the sort of partnership environment, You know, that's something that we want to do with them. You know, I would just underscore that they remain one of our largest customers. They are a multi-product customer. We are super engaged with them. And also, it's very clear that they're very early in their cloud estate. You know, these are big companies that spend a lot of money on this category, but they're very early. So, net, it was an optimization that we certainly are partners in. I'll let Navon comment on the math.
spk14: Yeah, you know, it's a large customer relationship of ours, and I think I mentioned during the prepared remarks, it was about a 2% impact to our growth and net retention rates, about a 1% revenue impact. In terms of the guidance, I think the guidance is reflective of the general, you know, large deal movement that we're seeing in any given quarter rather than specific to this customer. So, This customer's impact was obviously reflected in the guidance as well, but it's more a relation to what's happening in the expand, extend, large contract side and the impacts of procurement and the CFO being part of that purchasing decision more and more this quarter and this new budget cycle.
spk16: Appreciate it. Thanks.
spk04: Thanks, Adai. Next question, please.
spk01: One moment. And our next question comes from the line of Tim Fish with Piper Sandler. Your line is open. Please go ahead.
spk10: Hey, guys. Thanks for the question. Just building off of Itai's question there, how much risk is there to other sort of large customers like this retail customer of reducing a portion of spend? You know, what kind of guarantees do you have that that doesn't happen, you know, next quarter or the quarter after? And, Navam, does this mean we should kind of expect this kind of – let's call it mid-teens kind of net retention rate in the period to continue forward, or should we get back to that greater than 120% kind of trailing 12-month long-term target? Thanks.
spk17: Hey, sure. Thanks for the question. Yeah, just really quickly on, you know, I think we have a pretty good view of the overall customer state, and I think our view is reflected in the guidance we have more generally of the guidance framework that Navam's shared. Retail is a very specific vertical, as you can imagine. I think we forget about the remainder of the estate.
spk14: In terms of the net retention rates, I point to there's a lot to be optimistic about after we get through this year's budget cycle, not whole. You've still got very healthy activity on the G2K. You've got very healthy activity on the 100Ks. These are all expansions and extensions that happen and also multi-product extensions that happen with our product portfolio and also the upcoming boundary product, which will impact our revenue going forward. So, no, I don't think that this is a new reality of what net retention rates would be. I think it's more a reflection of the purchasing environments along what's stopping sort of large contracts from proceeding to the finish line. Once these Once this budget cycle resets into the next one, I think we see the usual impacts of expansion, extension, and multi-product purchasing recover. So our long-term targets of being above 120%, which is the target we've set, remain intact, and we're very optimistic about that long-term.
spk04: Thanks. Next question.
spk01: One moment. Our next question comes from the line of Alex Zukin with Wolf Research. Your line is open. Please go ahead.
spk09: Hey, guys. Thanks for taking the question. I've got a multi-part first one and then just a clarification. So I guess if we think about some of these larger contracts, these larger deals, these longer sales cycles, are you seeing, like, is the incremental scrutinization that's being put on these deals, is it anything to do, you mentioned, Dave, about kind of similar dynamics within the hyperscalers. Is this customers pausing on cloud migrations? Is this a greater focus on cloud optimization before the next phase of the journey? What are you seeing in that dynamic that's causing that incremental friction? And then can you comment on what you've seen kind of in the month of May and June relative to how April and maybe March trended?
spk17: You know, thanks, Alex. It's super interesting because it's all so consistent. Like, if you think about the conversations that we've been having for the last seven months, they're the same conversations we're having now, which is, hey, we're going cloud. Those plans are unabated by the Global 2000. They are not slowing down. You know, they are engaging with us to say, yeah, we've created a platform engineering function. You guys are the basis of how we do that. It's just taking us time to and some friction to align the organization towards the consumption of that design wind, which is already in place. I had two conversations this week, one with a massive utility, one with an insurance company, where that was exactly the conversation. What's happening is that those design winds are being done, given the front-end consistency of the pipeline that we're seeing. What's not happening to the same degree is those things flowing through procurement. In some instances, it's a question of, the typical plan of buying slightly ahead of demand, which is what most companies do on the entitlement side, that's what's being stopped by finance departments specifically. So one could stand to reason, because we won those design wins, that that will flow through over the course of time. There's really no material change other than just literally like, it's almost like if you're towing a boat behind you, the boat's a little further behind because that part needs to get through procurement, but it's going in this direction without question. Maybe Armand has a point of view. He traveled, I think, nine weeks last quarter.
spk19: Yeah, I think maybe anecdotally, just to echo what Dave said, I think what we're seeing pretty consistently is going into this fiscal year, most of these organizations have locked their budgets, and the top focus for them is really in optimization and consolidation of vendors, focusing on right-sizing their estates. And so I think we continue to see that translate to the procurement pressure that you're seeing, especially around the bigger deals. But that said, I think all these groups are still engaging with us on you know, next product along, really thinking about, great, how do we architect tools like Terraform and Vault into foundational layers of our platform? You know, how do we start thinking about the other aspects of, you know, where we can help them on their automation journey? And I think in many ways, it's also accelerating the trend towards platform teams, right? Because I think these organizations are realizing if they're really going to get their hands around, you know, how do I do cloud efficiently at scale, you really need to have a central aperture for that. So I think it's accelerating a lot of those org transformations, and it's also accelerating, you know, the need to have standardization around the tooling. So, you know, I think, you know, all that speaks well to the pipeline, and I think that continues happening there.
spk17: I'd also just add, just to add to Armand's point, it is also occurring to a general shift towards consolidation of vendors during this cycle, which is certainly a net positive for us. As you're going through the design process, they are trying to rationalize in general their portfolio. As a multi-product vendor, it actually accrues very, very well to us. on the design wind side. And as long as we make those companies successful, you know, the right things will happen over the longer term.
spk09: Perfect. And then what about just on the monthly cadence question?
spk17: Yeah, I mean, I would suggest, you know, I feel it's very similar to me.
spk19: Yeah. Yeah. I don't think there's been a marked change. And I think this really speaks to the fact that these budgets are generally set on an annual basis for organizations. And I think, you know, that's reflected in our guide. I think it would be you know, for most organizations, unusual to reset their budget mid-year.
spk09: Perfect. And then just maybe a clarification question on the appointment of Susan to that role. Is she replacing someone? Is this a new role? Is there, you know, kind of contemplated meaningful changes to the go-to-market organization through the year, given she starts in July? Just any help that would be helpful.
spk17: Yeah, you know, obviously we're super excited about the opportunity to bring in Susan. Suffice to say, it was never about her availability. It was always about her availability and not our lack of interest and having her play that role as someone who's very uniquely positioned to do that. And I think, as I mentioned, as we think about the next phase of scale, you know, the billion-dollar number is the one ahead of us, and that's certainly where our energy is pointed. And we just think she's super well-positioned to do that. And so we're bringing her in as president of Worldwide Field Operations. We think this is the right time to introduce that role as we think about the next phase of growth. And that is more of a decision around a role requirement for us. So beyond that, no material changes. Obviously, her scope will be completely determined once she arrives full-time in the next month. But conceptually, it's just the addition of a new role, and the existing team will report it to her, and obviously she'll help us grow into the next phase and beyond. All right. Thanks, Alex. Next question.
spk12: Thanks for the help for that.
spk17: Got it.
spk12: We're ready for the next question.
spk01: Our next question comes from the line of Gary Powell with BTIG. Your line is open. Please go ahead.
spk21: Okay, great. Thank you very much for taking the question. If you can help me sort of dig into the revenue guidance more, I'd appreciate it. I think the full year guidance implies that you grow revenue around 11% or 12% in the second half of the year. Just how should we reconcile that against CRPO, which just grew 29%, and then how should we think about the potential for growth to reaccelerate at some point or maybe the timing of a reacceleration? I know that last one is going to be hard to call, but Any color would be really appreciated.
spk14: Yeah, thanks, Greg. Good question on the CRPO side. So the CRPO is obviously reflective of the front half seasonality compared to the back half seasonality. So when you think about it, we sell to large enterprise contracts. They're tail end weighted. So the back half is a much bigger impact to our revenue than the front half from a bookings perspective. So the CRPO growth rates will differ from the front half to the back half. So there is going to be a difference between the first quarter absolute number CRPO growth rate and what the full year revenue growth rate is just from a timing perspective because it implies what the bookings are for the back three quarters or the back half of the year. So we've factored in basically continued headwinds in the global segment and the enterprise segment in how we think about the revenue guidance. Now, I also caveated, this is really early in the year, so we'll execute every quarter and we'll give you updates as we move along. We're very optimistic about the front end, especially given what we're seeing in terms of customer activity and especially given what we're seeing from the field when Armand and Dave go and visit our customers. So at some point, we're going to be out of this budget cycle, and at that point, I think we move to normal purchasing cycles with our customer base, and that's where we feel we'll be back to our normal growth rates. But as Armand mentioned, budgets are set once a year, and we're reflecting sort of the current budget environment we're seeing until that changes, and every quarter will be an update.
spk21: Got it. Okay. Thank you very much. All right. Thank you.
spk04: Next question.
spk01: One moment. Our next question comes from the line of Mark Murphy with JP Morgan. Your line is open. Please go ahead.
spk20: Thank you very much. So seeing the heaviest scrutiny coming from actually your largest customers and then in the expansions is not what we would typically see. I think we would assume those are the customers that they know you, they trust you. they'd want to consume a larger footprint. Can you just double-click on that and maybe explain why we're seeing the behavior kind of shake out that way? And then as a follow-up, so what is the current number of $10 million ARR customers as of June? Would that number be sitting at two now?
spk17: Hey, Mark. It's Dale. Let me just answer the first one. Just so I understand or just so I clarify, yeah, I think the procurement friction we're seeing is a general commentary inside existing customers as well as new. I think we saw a very strong NDE in the quarter, which I think is reflective of those larger companies continuing to purchase incremental pieces from us. But certainly the cycles for them are slower than maybe they were a year ago, just given the constraints in their own business. But that's more of a general commentary than anything, but overall exactly what I would expect and consistent.
spk14: Yeah, Mark, on the large customer side, yes, it is one of our largest customers. One of our three $10 million customers slipped below the $10 million line. They still remain engaged and large, as I mentioned. So, yes, the count is now two.
spk02: thank you thanks mark next question one moment and our next question comes from the line of nick altman with scotia bank your line is open please go ahead great thanks guys um there were some good upside of margins in the quarter and with the eight percent headcount reduction I guess I'm a bit surprised why the margin guidance wasn't revised upward a bit more. So is there anything else there we should be thinking about or considering? And then just to clarify, was the RIF factored into the prior margin guidance?
spk14: Hey, Nick. Yeah. So just to clarify, the severance related to the RIF is factored into our current Q2, which impacts some of our margins. But overall, I think our EPS is guiding better than what we had previously factored in. And also note that it takes until the back half of the year after the first quarter actuals and the second quarter severance to work its way through and really see the impacts, the long-term impacts to your margins in the back half of the year. So that's what you're seeing in terms of the margins, margin guidance. But that being said, you know, our EPS guidance has picked up. And we expect to be, apart from the second quarter seasonality, you're always going to expect a second quarter dip in free cash flow due to the first quarter ACV seasonality. You should expect positive free cash flow for the rest of the year.
spk04: Great. Thanks. Next question.
spk01: One moment. Our next question comes from the line of Miller Jump with Truist Securities. Your line is open. Please go ahead.
spk07: Hey, guys. Thanks for taking the question. Maybe just one more to follow up on the headcount reduction. I was wondering, could you give any more color on which segments of the business you plan on reducing or that you have reduced headcount in? And then maybe just are there any segments where you plan to continue hiring for the rest of the year? Thanks.
spk17: Actually, let me ask the first part of the question. I'll let Vaughn answer the second. I just want to underscore this is a hugely difficult decision for us to make and the one we felt needed to be done. I just want to reflect back that we had gone through an investment cycle over the past four quarters very deliberately with an expectation of a certain demand environment to be in place, and clearly that different demand environment did not materialize, obviously with sales cycles extending just like for everybody else. But I want to make clear that because of that investment cycle, we feel that we're in a good position to deliver on the capacity required to deliver this year and next. So while certainly there were modifications across all sectors, we forget about the capacity that remains across all segments required to do what we need to do, both in R&D and in sales.
spk14: Yeah, you know, echoing Dave, this was a very difficult decision for us and not something we took lightly. We took many steps to impact spend before going down this path. And ultimately, you know, we still are a growth company, so we want to make sure we're invested in the long term. And we were very careful, you know, in the large impacts, when you think about the large organizations, which are sales and R&D, we maintained our investments in where we felt we needed the capacity to And in several geos or in certain product areas where we thought the payback was a little longer term, we took the action of understanding what the criticality of that business is and trimming it down. So overall, we are still very well staffed from a sales and R&D perspective to both deliver the quarters and also deliver the product roadmap. And we feel that the headcount that we have or the employee base that we have this quarter is sufficient for the year, so we don't feel like we're going to add unless, you know, the environment materially changes.
spk19: Understood. Thanks for the call.
spk04: Thank you. Next question.
spk01: One moment for our next question. Our next question comes from the line of Cash Rangan with Goldman Sachs. Your line is open. Please go ahead.
spk06: Hey, guys. I asked chat GPT what questions have not been asked by Mark Murphy and Alex Zookin, and it timed out, so I have to do some thinking on my own here. In seriousness, when you look at the net expansion rate, is the pressure coming from existing customers expanding more, or is it because of existing customers cutting down the scope of the deployment? We can just give some color. And also, is there a way to triangulate? Is that coming from Terraform or non-Terraforms out of the house? That would be great. And also, Susan obviously has got a great track record. She was at Salesforce, ran Marketing Cloud. She was at Splunk, president of World Wide Operations, I believe. Something pretty close to that. Okta, very, very different businesses, very different products. What do you want Susan to accomplish for Hashi? with respect to the data. Do you think she brings in that it's so critical for Hashi at this stage of the game? Thank you so much.
spk17: Sure. Hey, gosh, thanks, Dave. I'll answer the first one. I think I got it, and I'll try to get to the second. I think my observation is it's largely around the net new expansion pace. It's the rebuy cycles just because of that procurement pressure that we're seeing. Once deployed, our products are in the runtime path of applications, and that makes them generally long relationships with their customers, notwithstanding small optimizations here and there. So generally speaking, the NDE is, notwithstanding the one customer that Navar referred to, is just sort of a slight slowdown in the rebuy of next use case long, next product long. In terms of Susan, I think we're cognizant of phase shifts of a company, and we think about the next phase ahead, and it is an operationally different phase at a billion dollars in revenue, and that's really where we think Susan can help us, as opposed to anything specific about a product portfolio or type of go-to-market. There are very few people in the world available to do that, and she's at the very, very top of that list, so it's more generally a scaling question for us as a company, as you can see. You know, our customers are among the largest companies on the planet. We play a critical role for them. They're going cloud, and that is not shifting, and our relationships will be extremely long as a result, and we want to build the best possible companies to support them.
spk06: Wonderful. Thank you so much, and all the best.
spk04: Thank you, Cash. Our next question?
spk01: One moment. Our next question comes from the line of Patrick Walravens with JMP Securities, your line is open. Please go ahead.
spk05: Oh, great. Thank you. Hey, Armand, like at the beginning of the year, you were talking about how budget is aggregated across three layers for apps and data, and you thought there was a lot more variability in apps and data. How are you thinking about that division today? Is it still a helpful way to think about the business?
spk19: Hey, Pat, yeah, thanks for the question. I think that still is a useful way, and I think what we see in all these accounts is At the infrastructure layer, all of these teams are still committed to cloud. They're still moving ahead. I think they're taking sort of a moment to pause a beat and look at, hey, over the last three, four years, spending on cloud has been gangbusters. Where is there opportunity to optimize and consolidate and drive a little bit of efficiency in these estates? I think what we broadly see is a fairly large amount of waste in the cloud environments. But I think no one is really divesting from cloud as a strategy, right? So our view is it's like everyone's pausing, taking a beat to do that optimization, but really forging ahead on sort of a multi-cloud strategy. And I think in that sense, we expect infrastructure will sort of take that pause and then continue the growth as people move there. If anything, I think where we feel some optimism is I think with a lot of customers who are now interested in you know, leveraging some of the generative AI techniques. We actually think those will be drivers of net new cloud workload, and we're already seeing that. You know, there's a very large financial group we've been working with who has, you know, dramatically pulled forward and accelerated their efforts to get onto Azure for exactly that purpose. So that's bringing net new workload, expanding them to multi-cloud, and, you know, they're using Terraform and Vault and Confo to underpin, you know, that multi-cloud journey. So I think, you know, in that sense, we feel like there's going to be this optimization that, you know, you know, we're seeing broadly across the market, that'll take a pause, and then we'll continue to see workloads on cloud continue to grow, you know, at that infrastructure layer.
spk05: All right, great. Thank you. Navam, can I just, as a follow-up, how confident are you in your new revenue guidance?
spk14: Hey, Pat. So, yeah, I think we're very confident about our new revenue guidance. It factors in this elongated large contract cycle into, you know, the rest of the year. And, you know, as Armand said, we're optimistic about not losing out due to competitive pressure or losing out due to cancellation of the cloud programs. So, you know, we expect this large contract activity to occur as they will for the next three quarters. But as soon as the headwinds change, we should see return to normal. But the full year is reflecting our confidence in what we can achieve next year or this year.
spk04: Thanks, Pat. Yeah. Next question.
spk01: One moment. And our next question comes from the line of Sanjit Singh with Morgan Stanley. Your line is open. Please go ahead.
spk18: Thank you for sending me in. I had a question for Dave or Armand, I guess a jump ball, and it goes to the right-sizing of the environment, Armand, that you mentioned in a previous question. In your conversations with your customers, when they talk about optimizing their environment, right-sizing their environment, Could you give us a sense of what that entails? And from the feedback that you've gotten, how long does a right-sizing initiative or project take from what you're hearing from your customer base?
spk19: Hey, Sanjeev, thanks for the question. You know, it's a really good question. So I think the shape of it takes a few different forms, right? I think, you know, part of it what we see is you have development testing environments that have been relatively unconstrained, and some customers might be as much as 50% of their cloud spend. So I think there's one side of this which is really looking through those dev test environments, and a whole lot of it is orphaned resources, things that, you know, if developers set up an environment, left it running for three months, you know, you're paying the meter on that. So I think there's a lot of that happening in dev test where, you know, that takes a – you have to go through an inventory process, identify those workloads, and shut them down. Then I think on the other side, you have production environments. where you have, you know, kind of multiple forms of a voice take place. One is, you know, hey, maybe this needed to run on five servers, but it's really running on 10. Okay, can we identify that and sort of shrink the footprint down to five? You have other cases where it's like I'm running on a, you know, double extra large when really I should be on kind of a medium-sized capacity. So I think that also is a complex challenge if you have to inventory all the assets, really look through data and telemetry to understand where am I overutilized, where am I overdeployed? and then go through the change management to kind of right-size some of that. In terms of how long that takes, I think there's a fair amount of variability. And frankly, it actually goes back to the maturity of their cloud program. The programs that were least mature, they don't have a good handle on it. The data is not readily available to them. They don't have a central team that was responsible for driving that in a standardized way. And I think, in fact, this has been an accelerant of conversations for us around the value of standardizing on tools like Terraform and having a platform team. Because that central aperture gives me visibility of what workloads are dev tests, what workloads are production, it allows me to kind of do that instrumentation on usage. So for us, it's actually been a useful conversation driver on the importance of creating those sort of standardized layers. You know, I think for the teams and organizations that don't have that, it's a longer journey, right? They have to sort of get their hands around the problem, and there's multiple phases of identification, right-sizing, and change management.
spk17: If I could add just my side of the conversation, Sanjay, I think to me it's kind of two countervailing forces. One is, as Armand described, we see it. Obviously, we're doing it ourselves. There's a lot of cleanup of those orphan environments that we're all paying for and overspend. And so that is driving consumption down. At the same time, the velocity of new things going to cloud is not slowing. So at the same time as that is coming down, you're seeing an increase in the slope of the line of new things going cloud. In a sense, it's getting offset a little bit. Ultimately, Terraform is a critical element of how people actually solve that problem by putting constraints in front of the provisioning process. The irony being you have to get to the procurement function to put that in place, but that is certainly what people are doing.
spk18: That's a really helpful context. It seems to align broadly with how the hyperscalers are talking about how that's manifesting in our environment as well. Ultimately, we get to a place where New workload growth hopefully outpaces or surpasses the impact from optimization, so that's encouraging. I have one follow-up for Navam, and it goes back to the previous question around your confidence in the guide. I hear you guys loud and clear in terms of the longer sales cycles and the procurement process. We do have a new sales leader in place, and so I wanted to understand in terms of the magnitude of change in terms of the blocking and tackling of sales, territory alignment, comp, how much change is being instituted in the sales organization at a time where we've had a risk and then also the environment's a little bit weaker. So I just wanted to understand the magnitude of those changes and whether that creates incremental execution risks this year.
spk14: Yeah, thanks, Sanjit. The short answer is no, we don't see incremental execution risk with the addition of Susan. And in fact, we were optimistic about her impacts to the company and how she could help us grow into this new stage. Just as a reminder, when we took this very carefully, considered workforce reduction, we didn't overly impair the capacity in our core regions where digital transformation is the most advanced or the most furthest along. Rather, we looked at where the GEOs were that potentially were longer-term investments, and we right-sized those a little bit. Those were the large impacts that we saw on the workforce reduction plan. The existing sales leadership still is intact, and they will, as a unit, report up to Susan. So the org still is very stable, and we feel like there's no incremental risks with the changes. No incremental computational risks with the change.
spk18: Understood. I appreciate that context. Thank you.
spk14: Thanks, Andre.
spk01: Thank you, and I would like to turn the conference back over to Dave McJanet for any further remarks.
spk17: I'd just like to express my thanks for the participation from everyone here, and we certainly appreciate you dialing in and for all the questions. Look forward to speaking to everybody soon. Thank you.
spk01: This concludes today's conference call. Thank you for participating. You may now disconnect.
Disclaimer