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.
spk18: Thank you for joining us today for GitLab's fourth quarter of fiscal year 2024 financial results presentation. GitLab's co-founder and CEO Sid Sibrandi and GitLab's Chief Financial Officer Brian Robbins will provide commentary on the quarter and the fiscal year. Please note, we will be opening up the call for panelist questions. To ask a question, please use the chat feature and post your question directly to IR Questions using the drop-down menu. Before we begin, I'll cover the Safe Harbor Statement. During this conference call, we may make forward-looking statements within the meaning of the federal securities laws. These statements involve assumptions and are subject to known and unknown risks and uncertainties that could cause actual results to differ materially from those discussed or anticipated. For a complete discussion of risk associated with these forward-looking statements in our business, please refer to our earnings release distributed today in our SEC filings, including our most recent quarterly report on Form 10-Q and our most recent annual report on Form 10-K. Our forward-looking statements are based upon information currently available to us. We caution you to not place undue reliance on forward-looking statements. and we undertake no duty or obligation to update or revise any forward-looking statement, or to report any future events or circumstances, or to reflect the occurrence of unanticipated events. We may also discuss financial performance measures that differ from comparable measures contained in our financial statements prepared in accordance with US GAAP. These non-GAAP measures are not intended to be a substitute for our GAAP results. A reconciliation of these non-GAAP measures to the most comparable GAAP financial measures is included in our earnings press release, which along with these reconciliations and additional supplemental information are available at ir.gitlab.com. A replay of today's call will also be posted on ir.gitlab.com. I will now turn the call over to GitLab's co-founder and Chief Executive Officer, Sid Sabrandi.
spk22: Thank you for joining us today. We had a strong fourth quarter with 33% revenue growth. We now have 96 customers with ARR over 1 million, up from 63 one year ago. And we continue to see that large enterprises like Barclays and Blue Halo are standardizing on GitLab. Speed, productivity, and security are critical for our customers. With GitLab, customers see seven times faster cycle times with 80% fewer code defects. Today, I'd like to discuss our progress this quarter in three key areas. First is our security and compliance capabilities. From secure source code management and security scanning to GitLab dedicated, our platform helps customers establish more secure and compliant software development practices. Second is our AI offering, GitLab Duo, which integrates AI throughout the software development lifecycle. And third is our enterprise agile planning offering, which expands our platform to users outside of software engineering. Let's start with security and compliance. These are at the heart of our platform and set us apart from the competition. This quarter, we released remote development workspaces into general availability. These workspaces are consistent, reproducible environments that help developers get started faster. This also increases security because it limits the need to clone code to end-user devices. Customers come to GitLab to replace security point solutions. With most point solutions, code isn't scanned at the time it's written. That causes friction for developers and increases the time required to find and fix vulnerabilities. T-Mobile recently moved 25,000 projects into GitLab over just two months and increased their security scans to hundreds of thousands per month. Now that they are integrated into GitLab, T-Mobile is looking forward to leveraging GitLab Duo to increase engineering efficiency even more. OXA, a global provider of autonomous vehicle software, upgraded to GitLab Ultimate in the quarter. The company wanted to modernize multiple developer and security tools, including version control, CI, CD, and more. With GitLab Ultimate, OXA is now able to detect potential security issues earlier in the development process, which is a major gain for OXA, which works in a complex and safety-versed environment. Another example is CACI International, a national security company and a leader in agile software development. GitLab allows CACI to deliver more efficiently in an agile development environment and makes it easier to comply with emerging federal regulations. GitLab Dedicated is our single-tenant SaaS solution for customers who need to comply with data isolation and residency requirements. I'm excited to see adoption grow since we made it generally available last year. Organizations like Southwest Airlines are choosing GitLab Dedicated to get the best of both worlds. The security of a single tenant environment plus the benefits of a SaaS offering that's updated and backed up by GitLab. Onto AI, secure AI is a core part of our platform vision. We enable our customers to adopt AI responsibly. AI helps teams write more code faster. But more code isn't better if it's not secure and high quality. That's why GitLab Duo helps teams not only write code, but also understand code and fix vulnerabilities more effectively. Having the broadest DevSecOps platform allows us to add more AI features and deliver more value to our customers. In a recent OMDIA market radar report on AI-assisted software development, GitLab Duo had the most currently available features for any DevOps platform. Organizations like NatWest, UltraGaz, and Magic Leap have invested in GitLab Duo to help them drive efficiency while also ensuring robust security and code quality. Another example is a major telecommunications company in Asia that was looking to boost productivity with AI-powered features, not only in coding, but across the entire software development lifecycle. After testing code suggestions for one month and seeing positive results, in Q4, the company invested in thousands of GitLab Duo licenses to improve engineering productivity. After releasing GitLab Duo code suggestions into general availability last quarter, we recently released the beta of GitLab Duo chat. GitLab Duo Pro now also includes organizational controls that help companies adopt AI responsibly, and we are now selling GitLab Duo Pro for $19 per user per month. We recently launched the GitLab AI Transparency Center to enable our customers to confidently harness the potential of AI with GitLab. The AI Transparency Center documents how we built GitLab Duo Pro to accommodate the right model for the right use cases. It also demonstrates our commitment to transparency and protection of customer data and intellectual property. I'd now like to discuss our improvements in enterprise agile planning. We're hearing from more and more customers who want to rethink how they do planning. They want the planning in the same platform where the engineering work to deliver on the planning is happening. Early in Q4, we launched a new enterprise agile planning queue. Now customers can get even more value out of GitLab by bringing everyone into a single secure platform. For example, a leading 3D modeling software company upgraded to GitLab Ultimate in Q4 and purchased additional enterprise agile planning seats so they can move their sales team out of Jira and onto GitLab. Finally, on the leadership side, we're excited to welcome Sabrina Farmer as Chief Technology Officer. Sabrina has 25 years of experience and joins us from Google, where she was directly responsible for the reliability and performance of Google's products and infrastructure. I look forward to the impact Sabrina will have across the company. In closing, we're well positioned to win in the estimated $40 billion market opportunity in front of us. I'd like to thank all our customers, partners, team members, community members, and investors for their support. And with that, I'll turn it over to Brian Robbins, GitLab's Chief Financial Officer.
spk06: Thank you, Sid. And thank you again for everyone joining us today. I'll start with a brief recap of our full year and quarter results. In FY 2024, total revenue grew 37% to $580 million. Our growth continues to be driven by our land and expand motion. Our dollar base net retention was 130% in Q4. We delivered on break-even free cash flow a year ahead of our commitment with free cash flow of $33 million in FY24. In addition, on a standalone basis, excluding the impact of Jihu, RJV, and majority-owned subsidiary, we recorded our first year of non-GAAP operating profit. We're thrilled to have achieved these milestones. These are a testament to our philosophy for responsible growth. Our fourth quarter revenue grew 33% year-over-year, and we delivered over 1,900 basis points of non-GAAP operating margin expansion. Looking back at the quarter, I want to share some of the areas we've been closely monitoring. These include customer buying behavior, contraction, and ultimate performance. In comparing Q4 with Q3 of FY24, we have seen improved buying behavior across all customer sizes. In particular, performance with our enterprise customers exceeded expectations. We had a record quarter for 100,000 ARR and 1 million ARR customer net ads. While the spinning environment remains cautious, we believe we are starting to see buying behavior normalize with accelerated adoption of our DevSecOps platform. Churn and contraction during Q4 also improved for the fourth consecutive quarter and is even better than levels we saw six quarters ago. And finally, we continue to see strong growth in Ultimate, our top tier. Ultimate represented over 50% of Q4ARR bookings driven by customer wins for security and compliance use cases. Now, turning to the numbers for the quarter. Revenue of $164 million this quarter represents an increase of 33% organically from Q4 of the prior year. We ended Q4 with over 8,600 customers with ARR of at least 5,000 compared to over 8,100 customers in the third quarter of FY24. This compares to over 7,000 customers in Q4 of the prior year and a year-over-year growth rate of approximately 23%. Currently, customers with over $5,000 in ARR represents approximately 95% of our total ARR. We also measure the performance and growth of our larger customers, who we define as those spending more than $100,000 and $1 million in ARR with us. At the end of the fourth quarter of FY24, we had 955 customers with ARR of at least $100,000 compared to 874 customers in Q3 of FY24. This compares to 697 customers in the fourth quarter of FY23, a year-over-year growth rate of approximately 37%. At the end of FY24, we had 96 customers with ARR of at least $1 million compared to 63 at the end of the prior year, which represents a year-over-year growth rate of 52%. As many of you know, we don't believe calculated billings to be a good indicator of our business. Given that prior period comparisons can be impacted by a number of factors, most notably our history of large prepaid multi-year deals, this quarter total RPO grew 55% year-over-year to $674 million. CRPO grew 40% to $430 million for the same timeframe. We ended our fourth quarter with a dollar-based net retention rate of 130%. As a reminder, this is a trailing 12-month metric that compares the expansion activity of customers over the last 12 months with the same cohort of customers during the prior 12-month period. Non-GAAP gross margins were 92% for the quarter. SAS represents over 25% of total revenue and grew 52% year over year. we have been able to maintain a best-in-class non-gap gross margins despite the higher cost of SAS delivery. This is another example of how we continue to drive efficiencies in the business. We saw improved operating leverage this quarter, largely driven by realizing greater efficiencies as we continue to scale the business. Q4 non-GAAP operating profit was $13.2 million, or 8% of revenue, compared to a loss of $13.8 million, or negative 11% of revenue in the fourth quarter of last year. This includes an operating loss of $2.1 million for Jihoo. On a standalone GitLab basis, Q4 non-GAAP operating income was $15.3 million, or 9% of revenue. Cash from operating activities was 24.9 million in the fourth quarter of FY24, compared to a 11.7 million use of cash in operating activities in the same quarter of last year. Free cash flow was 24.5 million in the fourth quarter of FY24, compared to negative 12.8 million in the same quarter of last year. Free cash flow is defined as net cash from operating activities, less cash used for property and equipment, excluding non-recurring items. Turning to guidance, I'd like to make a couple of comments. First, we're entering our third year as a public company. As I mentioned, we're seeing normalization buying behavior as a result. I expect our guidance philosophy to be less conservative this year than in the first two years. We want to communicate the right expectations and are sharing guidance accounting for the current environment. Second, as a reminder, every year we evaluate our standalone selling price, or SSP, which determines our upfront revenue recognition rate for licensed revenue. We have not finished our SSP analysis for the new year, so we have not factored any change to SSP in the FY25 guide. We will share an update at the next earnings call once we have the results of the SSP analysis. With that said, our guidance for first quarter of FY2025. We expect total revenue of $165 million to $166 million, representing a growth rate of 30% to 31% year-over-year. We expect a non-GAAP operating loss of $13 million to $12 million. The loss includes an approximately $15 million expense related to our in-person company-wide summit. As an all-remote company, we're thrilled to bring team members together in the same location for the first time since 2019. And we expect non-GAAP net loss per share of $0.05 to $0.04, assuming 158 million weighted average basic shares outstanding. For the full year FY 2025, we expect total revenue of $725 million to $731 million, representing a growth rate of approximately 26% year-over-year. We expect a non-GAAP operating income of $5 million to $10 million, and we expect non-GAAP net income per share of $0.19 to $0.23, assuming $168 million weighted average diluted shares outstanding. We believe that our continued focus on responsible growth will yield further improvements in our unit economics. We plan to be free cash flow positive again in FY25, excluding any non-recurring cash tax payments related to the bilateral advanced pricing agreement. There are a number of drivers we believe will fuel our business in FY25, which we have included in our guidance. At our core, we see that continuing to deliver customer value with our DevSecOps platform aligns our success with our customers' success. Additionally, in April last year, we raised the price of our premium tier for the first time in five years. Thus far, customer behavior has been in line with our expectations, and we expect to be 10 to 20 million in incremental revenue in FY25. Another driver is GitLab Dedicated. GitLab Dedicated allows us to serve companies in highly regulated industries with complex security and compliance requirements. We continue to sign large enterprises on dedicated. For example, a leading U.S. airline expanded on dedicated with a seven-figure deal during Q4. The final driver for FY25 is the monetization of our AI capabilities. GitLab Duo Pro is now on the market at $19 per user per month. Separately, I'd like to provide an update on Jihu, our China joint venture. Our goal remains to deconsolidate Jihu. However, we cannot predict the likelihood or timing when this may potentially occur. Thus, for modeling purposes for FY25, we forecast approximately $15 million of expenses related to Jihu compared with $18 million in FY24. In closing, I'm pleased with our business momentum driven by our market-leading platform approach and commitment to capturing our large market opportunity. We hit major milestones for free cash flow and non-GAAP operating income profit while growing the business. I'm proud of the consistent execution at FY24. With that, we'll now move to Q&A. To ask a question, please use the chat feature and post your question directly to IR Questions. We're ready for the first question.
spk18: In the essence of time, please limit yourselves to 1 question. Our 1st question comes from Rob at piper sand.
spk04: Great thanks for taking my question and I'll ask the kind of the broader economic outlook question right now, because Brian, you did indicate. Improved buying behavior, record deals above $100K, above $1 million. And we have seen some unevenness out there. There's still some layoffs happening in high tech. And if I look at your open recs, it does appear you've somewhat accelerated hiring over the last couple months. Maybe frame for us, is this your view that things have bottomed in the economy? And maybe provide high-level thoughts around just planning for the upcoming fiscal year relative to sales capacity or other functional areas that you're putting these bodies into. Thanks.
spk06: Yeah, absolutely, Rob. Thanks for the question. You know, we are seeing customer buying behavior normalized with particular strength in enterprise. This showed up in our numbers this quarter. A couple examples I'll go through. One is we're seeing strong expansion within the existing customer base. With dollar-based net retention, we had an uptick up to 130% from 128% last quarter. Churn and contraction also continues to improve. It's even better than rates that we saw six quarters ago. In terms of investing in the business, as we said, we're long-term focused as a business, and we plan to continue to grow responsibly. The areas that we're adding new headcount within the company are sales capacity and key R&D roles. Thank you.
spk18: Next we'll move on to Koji from Bank of America.
spk15: Hey guys, thanks for taking the question. I wanted to ask a question on operating margin guidance. You finished the year here, the fourth quarter at 8% operating margin, guiding the full year next year at 1%. And then Brian, given your comment on maybe a little bit less conservative in the guidance for next year, can you maybe walk us through some of the upcoming levers to drive operating margin expansion from here? Thank you.
spk06: Yeah, absolutely, Koji. You know, we mentioned in the prepared remarks, you know, we're having our in-person summit this year. That's in first quarter. The estimated expense for that is $15 million. We haven't had an in-person event at the company since 2019. And being an all-remote company, it's really important that we have that. Also, in the guidance numbers, we have Jihoo, which is roughly $15 million as well. And so for the full year, we guided positive 5 to 10 million, and that includes a 15 million for Jihoo, as well as a 15 million for the in-person event.
spk18: We now move to cash at Goldman Sachs.
spk13: Thank you very much. Great finish to the fiscal year. Sort of reversal from how we started out, ending on a very strong note. So nice to see the net expansion rate metric rebound. I think you're one of the very first in software to see the rebound in net expansion rates. CRPO, RPO, all this looks good. Sid, with I shouldn't say new head of sales, but you have a new head of go-to-market for this full fiscal year. What are the changes we should be expecting as a result of the introduction of new products, quotas, competitive win rates, new product contribution, pricing? There's so many things that are happening at GitLab that are all quite positive, right? How should we rank order the impact of those things in your growth algorithm for this year? Thank you so much.
spk22: Yeah, thanks, Kaj. We're super excited that Chris is doing so well. Him joining is evolution, not revolution. So he is continuing the line. We continue to focus on the customers where we can have the most impact, which are typically the largest customers in regulated industries. And we're super excited about the things you mentioned, all the extra things that we now have that we can start selling. Duo Pro we introduced, but also the planning features that allow customers to put their planning in the platform as well, the Enterprise Agile planning queue and get a lot dedicated. I think all these extra offerings we can have are a great addition on top of Ultimate, which is more and more important to us and which resonates more and more in the market.
spk13: So Brian, one for you, and then I'll finish up. With all these levers that Sid is talking about, why is the guidance seemingly conservative? Or is it just that you're discounting the effects of these new features and products because we just don't have enough data and you're waiting for it to play out? How should we characterize the guidance? Thank you so much.
spk06: Yeah, thanks, Cash. We do have a number of growth drivers for FY25 and beyond. I think you've named a number of them. It takes a while to build pipeline and close deals on new products. And so the total number of revenue that we have for next year for it to make a meaningful impact in a radical business model is going to take a little while for that to come to fruition. And so we've put all the new products into the guidance. They're relatively new, and so didn't want to put a lot in right now. With the premium price increase, we're still saying that's roughly $10 to $20 million of incremental revenue in FY 2025. And then we have dedicated enterprise agile planning and Duo Pro as well. So lots of new growth vectors for next year. It'll just take a little while for them to impact the top line.
spk18: We'll now move to Ryan at Barclays.
spk05: Thanks for taking the question. One for Sid and one for Brian. Sid, and guys, thanks for the continued partnership with Barclays. Look, just on the early indications of Duo Code, Sid, we'd love to hear how demand has trended there. And then how do you think about monetizing AI outside of Duo Code? Like, are you seeing customers who are interested in AI also more interested in your security features or up-tiering to Ultimate? And then for Brian, just really quick, we'll have to hear what the incremental price increase contribution was to the fourth quarter. Thanks.
spk22: Yeah, thanks for that, Brian. So Duo is resonating in the market, and we were really pleased with the Omnia report that we had more AI features than any other platform. We could add value in more cases. And you talk about security and Ultimate, we have the most comprehensive security offering of any DevOps platform that allows us to also release more AI features. And some of these features are not in Duo Pro, but they're part of Ultimate. So Ultimate now has more and more AI features. So AI is helping to drive Ultimate as well. because ultimate number one reason why people buy that is because it helps them get more secure and every feature that is in ultimate and that is now getting enhanced with AI that AI we give to the customers of ultimate by default thanks then Brian just real quick if um if you can highlight the incremental price increase contribution to the fourth quarter thanks
spk06: We haven't broken out towards the fourth quarter. We just said for next year, it will be roughly 10 to 20 million in incremental revenue is what we included in our guidance. Okay. Thanks, guys. Appreciate it.
spk18: Next, we have Joel Atruist.
spk23: Thanks for taking the questions, and congrats on the great execution. Sid, just one for you on, are you seeing any increased conversions around Agile planning with the Atlassian server end of life approaching?
spk22: Yeah, for us, it's a new market. And Brian just talked about new markets. They start slowly and then they accelerate in the outer years. But we talked about a customer switching from Jira to GitLab again in the last quarter. So that's really exciting that we get to talk about that and we see an increasing pipeline. If customers are able to bring planning to the same platform, they don't have to create all these different connections between their planning tooling and their software creation tooling. With GitLab, it works by default. It's a better experience. There's less ceremony that they need to do. It is one interface, one data source, and that's appealing to customers. We're very excited about our enterprise agile planning SKU that we can sell along with the rest of GitLab. Thank you.
spk18: We'll now move to Pendulum at JP Morgan.
spk19: Great. Hey, thank you very much for taking the question. Two-part question for Brian. How much of the RPO growth of 55% is driven by price versus any elongation in contract length? Any way to kind of understand the components of that? And then on pricing, I know you're not giving up the Q4 number, but you have closed out FY24 now. Is it possible to understand the pricing benefit for the full year in dollar terms? Is it 1%, 2% of growth, any help you can provide at all?
spk06: Yeah, let me start first with the RPO growth at 55%. CRPO growth was 40%. And so overall, we had a really strong quarter and happy with the performance in the quarter from a bookings perspective. You know, as we previously stated, billings and RPO within a quarter are not good indicators of our core business momentum, that they can fluctuate relative to revenue based on the timing invoices and the duration of the customer contracts. We did have a number of multi-year deals this quarter, which contributed to the RPO growth. On the pricing benefit, you know, I've said $10 to $20 million for next year. We haven't broken out what it is by quarter and don't plan to do that going forward.
spk08: you thank you we now have nick at scotia bank awesome thanks guys um so you guys talked about how um buyer behavior is normalizing contractions improving um but kind of going off pendulum's question around the premium price increase and that the impacts that's kind of had to the model if you look at nrr and you sort of backed out the price increase Or is that kind of down, excluding the price increase?
spk06: Yeah, I can happy to go through what is the buildup in the dollar based net retention rate. And so super happy that the dollar based net retention rate went up this quarter to 130 percent. We break it down between seats, price and tier. So 40% of that was related to seats, 40% was related to price, and 20% was related to tier. Not too dissimilar from last quarter. It's just a little bit different last quarter. Churning contraction also continues to improve. As I said earlier, it's even better than rates that we saw six quarters ago. Awesome. Thanks, guys.
spk16: Appreciate it.
spk18: We now have Greg at Mizuho.
spk16: Okay, thank you for taking the question. So obviously it's incredibly early in your AI journey, and this isn't very applicable to the Q4, but can you tell us how the uptake for GitLab Duo has been so far, both in terms of the introductory price for the first couple of weeks and for the regular price that kicked in on Feb 1? Thank you.
spk22: Yeah, thanks. I think customers have been responding well to Duo, so they're mostly excited about the breadth of our Gen AI capabilities, including things like vulnerability summary, vulnerability resolution, root cause analysis. And an example is that a major telco in Asia, they wanted to boost their AI workflow across their entire development lifecycle. And they saw positive results after testing code suggestions. And in Q4, they committed thousands to thousands of GitLab dual licenses to improve engineering productivity all the way through the process. Okay. Thank you.
spk18: Now we'll move to Shebly at FBN.
spk14: Yeah, thank you very much. So I think in prior quarters, you noted that sales cycles for the SMB mid-market had been elongated. And this quarter, you said enterprise did better than expected. So did SMB continue to be more challenged? Did the sales cycles improve? Just elaborate on what you're seeing in the SMB mid-market segment.
spk06: Thanks for that shabbily you know we're seeing customer buying behavior nor normalizing across the board. We didn't break out the sales cycles for SMB and mid market in particular, but, as I said, that turning contraction it's best that we see in six quarters and sales cycles have normalized across the board.
spk14: Thanks.
spk18: Our next question comes from Carl at UBS.
spk21: Okay, great. Thanks. Maybe for Brian. Brian, to your comment that you're electing to take a less conservative posture on the guidance, maybe a two-parter. Why? What's the logic there? Is it just that GitLab's now a bigger organization and across a bigger scale and customer base, you've just got a little more precise visibility? Is that it? Or is it in reaction to the environment? And then I've got a quick follow-up on the same subject.
spk06: Yeah, thanks for that, Carl. You know, going into our third year as a public company and also seeing the normalization of buying behavior will just be less conservative in the guidance that we're giving out. Okay.
spk21: And then I guess the follow up would be, did you make that change for the fourth quarter such that the, you know, the beat you just put up in the January quarter might, you know, we can look as a kind of a start of this more conservative guidance posture or is it more going forward?
spk06: No, it's more going forward. I'm very happy with the bookings this quarter. You know, we had the largest bookings quarter in company history. There's many firsts within the quarter, largest hyperscaler contribution, largest first order, largest ultimate. And we had a greater number of $1 million plus deals. There was some linearity in the quarter. Things came more back in, in the quarter than expected. Okay. Awesome. Thank you.
spk18: Now move to Matt at RBC.
spk09: Hey, Greg, thanks for taking my question. Congrats on the results. You know, you mentioned a number of the drivers in the prepared remarks. One that I don't think you talked about was free to pay, and I know there's been an increased focus on that. Any update on that sort of focus? Because it really does feel like that's a real long tail opportunity, but curious if there's anything to mention there.
spk06: Yeah, thanks, Matt. You know, we are getting a lot of free-to-paid conversion. However, the numbers are relatively low, so they don't come into the base customer count. And if you look at the overall sort of ARR that they're contributing, it's relatively small at this point.
spk18: We'll now move to Peter at Bernstein.
spk00: Thank you. And congratulations on another great quarter. Really looking forward to the momentum you're seeing. Maybe I build on an earlier question around Duo. Can you help us kind of understand how the attach rate initially is working? And, you know, as you look at customers and their use of the product, are you seeing that type of, you know, thing where it's getting into people's workflows and kind of the accelerating usage? Or is it still more kind of in experimental stages with customers. And then I guess maybe the adjunct to this is if you look further forward, what do you think makes it sticky? In other words, like once people really get in there, is it going to be easy to switch away eventually? Or is there some reason why this thing like just really becomes like a tick in the system?
spk22: Yeah, to answer your last part of your question first, we're excited about the amount of AI features we can add to GitLab because we have the broadest platform. We can address the most use cases and us, according to the Omnia report, kind of addressing more use cases than any other DevOps platform. That's why I think it's going to be more sticky rather than less sticky. The feedback so far has been positive. Customers like NatWest have invested in GitLab to help drive efficiency and at the same time ensuring robust security and code quality. Our customers have reported efficiency improvements upwards of 50%, still early in the AI journey, and we expect further iterations as we expand Duo across the lifecycle. Thank you.
spk18: We'll now move to Gil at DA Davidson.
spk17: Thank you. So stepping back a little bit in terms of margins, you're going to do more than 700 million of revenue this year, and you have 90% gross margins. At your scale, isn't there more margin upside at this scale? I think you may have gotten a little bit of a pass when you were growing more than 30%, but if we're guiding to closer to 25, 26 percent revenue growth. You gave a lot of margin expansion last year. Shouldn't there be more margin expansion this year?
spk06: Yeah, Gil, thanks for the question. Super happy with the operating leverage that we've been able to get in the model. This is our second quarter of non-GAAP operating income positive. If you look for the full year FY24, we generated roughly about $33 million of cash. And even with Jihoo for the full year, we're almost non-GAAP operating income, you know, break even. And so there's two things I talked about in the prepared remarks that go into the guidance number that we gave for FY 2025. The first thing is our in-person summit, which will be a $15 million expense in first quarter that we didn't have last year. And then the second thing is we have, you know, Jihoo that's still in our numbers, which is a non-cash expense, which is roughly $15 million as well. And so for the full year, $5 to $10 million is the guidance. And there's $30 million sort of in those numbers. One's non-cash Jihoo, and the other is the in-person summit that will happen in first quarter. Got it. Thank you. Yep. Thank you.
spk18: We'll now move to Derek and Colin.
spk07: Great, thanks. Hey, Brian, this is for you. I guess just looking at these numbers, really impressive, 40% CRPO growth. That was an acceleration from 34%. Last quarter, you had a two-point uptick in that revenue retention rate at 130. I guess in the context of this, it looks like your guidance of 25% to 26% revenue growth for fiscal 25 would be conservative. There's two questions. Are there any drags in the model we should be aware of that may not be reflected in the backlog or the trailing 12-month NRR numbers? And then is it fair to say you think that growth tailwinds from pricing and from AI will be higher in fiscal 26 versus fiscal 25?
spk06: Yeah, thanks for that, Derek. As we stated earlier, billing as an RPO is not a great indicator. They're directionally correct. Super happy with the quarter overall. The points that you made, obviously, are all true and valid. The revenue growth of 33% are guided 26% next year. That factors in the buying behavior and the normalization that we've seen in the market. We do have a ratable model. And then, you know, being a, you know, entering our third year as a public company, you know, that's when we're, you know, we set our guidance laws to be less conservative than the prior two years. And so, you know, I think the setup with the new products and a normalization of buying behavior, as well as the metrics that we put up this quarter is a good setup for next year.
spk07: And just on the follow-on, with price tailwinds, would you comment on whether they would be bigger in fiscal 26 versus fiscal 25?
spk06: By the nature of the RADABLE model and then the step-up that you get, I would anticipate 26 to be bigger than 25. Thank you. Yep. Thank you, sir.
spk18: We'll now move to Alan at Wolf Research.
spk02: Hey guys, thanks for taking the question here. I wanted to follow up on the comments provided around normalizing trends. Looks like customers with over 5,000 ARRs accelerated more than 23%. And while you pointed out strength in enterprise, can you just kind of give us the story in the quarter with respect to enterprise versus last few four? Was there a higher volume of smaller deals or more big deals? And can you help us think about what a good year would be with respect to that customer?
spk06: Yeah, a couple different points there that I'll talk about. One is the 427 that we add in base customers has pretty much been our run rate. As we indicated in the past, we try to make the selling as well as the buying as friction-free as we can. And so we don't set a quota for ultimate versus premium. um nor do we say you have to sell you know gitlab.com versus self-manage and so you know the amount of customers that come out within a given quarter is just sort of an output of how the quarter gets put together i did mention you know very happy the bookings this quarter we had a number of first and first order expansion ultimate hyperscale or contribution and really happy with the 100k customer ads as well as a greater than 1 million customer ads, which was up 52% year over year. Thank you. Thank you.
spk18: We now move to Gray at BTIG.
spk03: Great. Thanks for taking the question. So a follow-up question on the price increases that we've been talking about. You're implementing the price increases on GitLab Premium in two phases. The next one kicks in in April. So just how should we think about the net benefit of this second phase versus the first phase? And specifically, is it safe to assume that the second phase has less churn
spk06: and therefore a greater net benefit relative to what we've seen so far yeah thanks for your question gray you know overall we're pleased with the results of the price increase the impact of the premium price increase exceeded our internal expectations we went through and modeled that prior to doing the price increase and for fy 2024 It came in above what we modeled internally. And so, you know, what we told you for FY 2025 was 10 to 20 million of incremental contribution in revenue over FY 2024. And we've built in the benefit that you've alluded to on the churn and sort of the second tier and so forth of what the assumptions are for that.
spk03: Okay.
spk06: Understood. Thank you. Thank you.
spk18: We'll now move to Mike Agnita.
spk11: Hey, thanks for getting me on here, guys. Brian, I think first question for you, just with the guidance, a bit of a two-parter here, but I know you're talking about how there's less conservatism in the guide now. And I just want to make sure I'm clear. Is that the first part? Is that for both revenue and OPEX as far as the implied cost structure there, or is it more just for the revenue? And then I guess the follow on to that, I know the company is like really beat the drum as far as profitable scale. And so even if I X out the 15 million of Summit, and I'm not going to back out Jihoo just because it seems like a recurring cost until you, I guess, take it out as a consolidated statement. But there's still a massive uptick in the implied op ex when I think about your guidance. And that's really what I'm trying to square on my side.
spk06: Yeah, thanks. You're correct. We have been very consistent, you know, since the IPO roadshow is our number one objective is to grow, but we'll do that responsibly. You know, the less conservative, you know, we've, you know, have, you know, beat the profitability um pretty handedly every quarter and so it's more directed at the top line than the bottom line um but we still want you know the number one thing at the company is still to grow and we'll do that responsibly and so um you can expect that from us
spk11: Thanks for that. And then just a quick follow-up too. I know in the Q&A, I think you had called out from a linearity perspective, the quarter seemed to be a little bit more back half-weighted. And so just curious, again, we're trying to get our arms around this guidance here. Was there any change in customer behavior or purchasing patterns as we moved into, we now have call it a month or two under our belt for the current quarter or were things relatively unchanged as far as the spending patterns you're seeing?
spk06: Yeah, thanks for that. We typically haven't commented sort of up into earnings. We comment sort of up into the quarter closed. And we did see normalization, you know, across the entire, you know, across enterprise, mid market and SMB. And I've also mentioned that we saw a churning contraction, you know, back to what we've seen six quarters ago. And so that, you know, obviously gave us some confidence to give the guidance that we gave. Thank you. Thank you.
spk18: We'll now move to Jason at William Blair.
spk20: Yeah, thank you. Hey, guys. Nice to see you both. Brian, just trying to square, I guess, with everybody else, the guidance with the less conservative posture comment. In particular, if NRR is trending up and is around 130%, doesn't this imply that NRR would have to decline from here for revenue growth to be in the mid-20s?
spk06: There's a number of factors that go into our guidance. You know, we build it from a bottoms-up perspective. And, you know, I would just say that, you know, what we reported was actuals and what we're guiding to is guidance, right? So it's not comparing apples to apples.
spk20: Okay, and then I want to squeeze one in for Sid, because Sid, you're just sitting there. Nobody's asking you any questions. It's not right. But really, I know you've covered this, but can you just refresh us quickly on GitLab's key differentiators versus GitHub? I know there's a lot of questions always on GitLab versus GitHub, but just talk about where you are today on differentiation and where you expect to be going forward.
spk22: Yeah, thanks for that opportunity. So we're winning deals against GitHub because we have the most comprehensive platform. In security and compliance, only we have DAST, the dynamic scanning, the container scanning, the API security, and the compliance management, the ability to prove that you've done all of that. For example, T-Mobile moved 25,000 software projects to GitLab in two months, and then they were able to start hundreds of thousands of security scans online. In planning and management, only we have enterprise agile planning, value stream management, DORA metrics. And because we are better able to address those use cases, we're also able to build AI features that build on that. For example, the ability to explain vulnerabilities and to have the AI suggest a fix. So we're really bullish in competing because we have the broadest platform and because that enables us to do more with AI. Thank you.
spk18: Next, we have Kingsley at Canaccord Genuity.
spk12: Hi, thanks for taking the question. When we speak with customers, we hear that consumption associated with compute minutes has the potential to be a really meaningful part of a customer's total spend once they start adopting products like CICD. How often are compute and storage considerations factoring into a customer upselling into premium and ultimate? And how do you expect newer products like GitLab Duo Pro or enterprise agile planning to affect these needs?
spk22: So GitLab does have consumption pricing for that. For us, it's not a material part of our revenue yet. We do allow people to bring their own runners, so to bring their own compute to bear for CI and CD. We expect a lot out of our new SKUs, but the impact is going to be seen over time. So for Duo, the AI features, for planning, for dedicated, the biggest impact is not going to be in the coming fiscal years, but in the outer years. Great. Thank you.
spk18: We'll now move to Yifu at Kantor Fitzgerald.
spk01: Thank you for taking my question and congrats on a very strong finish. Questions for either Sid or Brian. It's more of a back to basic question. I know Sid mentioned at the beginning of the call that consolidation is very healthy, right? At GitLab, I was wondering, can you discuss what are the legacy solutions you're consolidating and what are we in now and how much is left in the tank? And I have a quick follow up for Brian as well.
spk22: Yeah, if you're looking, for example, at enterprise agile planning, by far the most popular incumbent is Jira from Atlassian, and we're in the very early innings. We've only just started offering this, and we're very encouraged by the progress. A leading 3D modeling company upgraded to GitLab Ultimate in Q4, and they purchased additional enterprise agile planning seats so they could move their sales teams out of JIRA and into GitLab, but it's early innings. Our market share there is just starting to ramp up and it will take some time. Thanks for the question.
spk01: And then, Brian, quick follow-up is other cloud native software companies, they guide based upon what they see the last couple of quarters. I was wondering when you build your fiscal 25 guidance, how did you do so did you look at your trends how it was like last year the last couple quarters i want to get your thoughts on that and that's different
spk06: Yeah, no, absolutely. You know, fourth quarter of last year, there was a change in the quarter or two prior to that. And so we actually looked just, you know, relatively short term opposed to over four quarters. Since the buying behavior has more normalized and churning contraction has been back to where it was six quarters ago, we looked over, you know, the entire year to develop our FY 2025 plan. Okay. Thank you for that, Brian.
spk01: Thank you, Sid.
spk06: Thank you.
spk18: Our final question comes from Adam at Raymond James.
spk10: Okay, save the best for last. Sid, I want to talk about the growth drivers. Monetizing AI and GitLab regulated were two things that were brought up on the call. I think we've tackled profitability with Brian to death here, so let's do growth. When you think about the AI piece, you've said in the past, you know, 25% is spent on coding and 75% is spent on other tasks. I think a lot of attention gets paid to coding with AI. So I'm just curious your observations and feedback, especially on that other tasks piece and how you built that or continue to build that into the product. And then on GitLab regulated, if you just remind us of, you know, how to potentially size that and the timing for the impact of that. Thank you.
spk22: Thanks. Yeah. So you're exactly right. Developers spend 25% of their time coding and we're helping them with code suggestions, but there's also all these other tasks we can help them with. 75% of their time is spelled elsewhere. And for example, GitLab helps you to review an issue. So if there's an issue like this is what you got to work on, GitLab will help you to summarize that issue. There might sometimes be hundreds of comments from stakeholders and it will help you kind of digest all of that. And for every developer, there's a security or operations person that we can make more effective as well. For example, GitLab allows you to not only kind of see what vulnerabilities you have, but the AI will help you explain what the impact is and how you could potentially remediate it. We're super excited that the Omdia market rate of report shows that we have 38 out of the 43 areas where you could have AI features in a DevOps platform. We have them covered already. That's the best coverage of any vendor. And that's possible because we have the broadest platform to build that on.
spk10: Get lab regulated was the other one, just sizing and timing.
spk22: Brian, you want to take that? I'm sorry, can you repeat the question?
spk10: Get lab regulated as another key growth driver that you spoke about here on the call. I was just wondering if you could maybe talk about the sizing of that and the timing for that growth driver into the model.
spk06: Yeah, no, absolutely. We talked about a number of growth drivers for this year and new products that were launched. We didn't break out the contribution by driver. And we also noted that, you know, with the ratable revenue model and how much we got into an annual revenue for the year, that would take time for these to make a contribution to the top line.
spk10: Got it. That's helpful. Thank you.
spk06: Thank you.
spk18: That concludes our Q4 FY24 earnings presentation. Thanks again for joining us and have a great day.
Disclaimer