GitLab CFO on Remote Culture Success, AI Integration
58:41 Share

Brian, thank you so much for spending the next hour with us. I feel like what I'm about to do is unfair, but I expect that to happen throughout this entire hour. So here we go. That's just the way we roll. I'm going to screen share Brian's LinkedIn page. Brian, can we go on a little quick walking tour of your career and what led you here to GitLab? Yeah, absolutely. Thanks, Tom, and for the others for having GitLab on today. Appreciate you having us on the show today.

Before I get into my bio, it'd be helpful just to let the viewers know what GitLab does. Yes, please.

Absolutely. GitLab is the most comprehensive, intelligent DevSecOps platform for software innovation. We help developers be more productive, improve operational efficiency, we reduce their security and compliance risk, and we help them with their accelerate their digital transformation. We have approximately 50 million users on our platform, and we are one of the leading DevSecOps platforms out in the market today.

Can you just explain what DevSecOps is to somebody who doesn't understand that term? Yeah, absolutely. When people manage to deploy secure software, there's a number of different personas that touch. Typically, if you go back 10 years ago, developers would work on it, then the developers would actually toss it over to the security professionals. They'd come back with the security vulnerabilities, they'd go to operations for QA and testing and so forth.

GitLab enables everybody to work on it with a system of record in a single pane of glass. And so you can see exactly what's happening. So there's no one that has to play air traffic controller. An analogy that I'll use is, you know, I've taken, written several S1s, taken a couple of companies public,

I used to spend the majority of my time being an air traffic controller. Who has this section? Who has that section? When was it last updated and so forth. When I wrote the S1 for GitLab with the team, we use Google Docs. Everybody knew all the moves, add changes and deletes as a document was being put together and everybody could work on it in real time. GitLab increases cycle time for software development by 7x.

Thank you very much for that. We'll just go quickly through this. Talk to us about your time. We can just go to Brighton Park Capital Forward and how it led you to GitLab, and then obviously you have your board seat on id.me. Love to hear just a little bit about that, but then the whole hour is going to be GitLab. This is our Brian Robbins moment. Appreciate Tom. I've been a software CFO that have gone into several software companies and prepared them to go public. A number of them have actually been bought.

With that, I've been asked to be an advisor for different VC funds and private equity funds. I'm an advisor at Brighton Park Capital. They have over a billion dollars under management, and I help advise them on some of their software investments. I came to GitLab just because GitLab was the largest all-remote company pre-pandemic.

and one of the most public, public companies out there. We have a handbook with a lot of what we have published out in the market. And so you can go on our handbook and search a lot about the company. And we're a very transparent company that's out there. I recently joined a board called ID.me. ID.me is located over by where you guys are located at. Yeah, so happy to go into any further details about any of that.

That's great. Maybe I'll turn it over to Andy and Carl for the next questions and then I'll jump in after. Yeah, I can ask first. How has it scaled for the remote culture? You joined, it was already the biggest all remote company.

Has it been fine? Has there been bumps through the process since you've joined? You know, it's been a great experience. I was at a software conference one time, and this is during the height of the pandemic, and people were asking, hey, you know, should we be all remote or should we be in office? And at that point, it really dawned on me.

Most people spend most of their time deciding on the strategy of how they want to be versus change management. But when GitLab was founded from the start, it intended to be an all remote company and everything was documented in the handbook. And so whether you start as a CFO or whether you start as a BDR in sales, you all go through the same onboarding process.

Everybody, it's a self-led process where you go through videos, quizzes, you read papers, you learn about the culture of the company, you actually go and learn how to use GitLab and do merge requests. Since they were very deliberate about being all remote, everything was outlined.

Everybody had the same foundation and expectations when they joined the company. Being the CFO and hiring a number of new people to be on the team, if we were just based in San Francisco or New York or London, for example, the amount of people that you could hire would be on that geography, how far they live away from the office, what their commute would be like. Being an all remote company,

enables you to really hire team members from anywhere. And so we're located in over 65 countries today. We have over 2000 employees and it's made it really helpful to go through that process and really have, obviously the world is sort of your talent pool.

Brian, can you talk a little bit about just how the technology has shifted over the years since GitLab has been around, the AI impact just in general? And you gave a great analogy about Google Docs. I'm just wondering if you could do something similar to how development has changed maybe over the last few years and how GitLab has helped in that regard.

Yeah, GitLab as a whole has helped developers, security and operations professionals become more efficient. The Forrester Wave study, one of the studies that we did, if you buy GitLab Ultimate, the payback period on that is less than six months and ROI is over 480% in three years. And so the GitLab's mission is always being able to help people go through the software development lifecycle and do that more efficiently.

And so we have constantly looked at ways of doing that. We continually iterate on our software to allow releases come out to our customers that they can use to get the benefits of what we do. Over the last two or three years, we spent hundreds of millions of dollars in R&D putting that into the platform, allowing our developers to get more feature functionality for that software development lifecycle. AI is just another way of doing that.

We approach AI a little bit differently than other people. Our Duo enterprise, Duo is our series of AI products, if you will, basically injects AI throughout the entire software development lifecycle instead of just around code suggestions and code development. And so we looked at the entire problem set and came up with ways to actually help

allow AI with the process to enable our customers to do that more efficiently. I want to talk a little bit more specifically about the technical side with you and Carl jumping in some of those questions, but first,

Just your broad philosophical view at GitLab or Brian Robbins' view of employment going forward and what AI means. Obviously, remote work is a different work format. The Motley Fool has offices, but we allow all of our Foolish employees and contractors to select where they would like to work.

And that has opened up the opportunity for us to recruit talent around the world. A number of our leading AI practitioners at The Motley Fool are on contract around the world. We were able to find them in ways that it wouldn't have been possible if we were forcing everyone into a single zip code. We could never have brought this talent together.

So, but as we see that happening, we see a lot more interaction between full-timers and contractors, for example, or short contract advisors that have a specialized skill and come in over an eight week period and help to level us up in ways that we wouldn't have been able to do in a formal workplace structure. And then of course now cogeneration, automation, and this, the potential that we could have an apocalypse, you know, the employment apocalypse.

So do you subscribe to that or what do you think? I don't know if you have children or if you're ever teaching a class in college, what you would tell college seniors or college freshmen about what employment will look like for them over the next 10 plus years. - Yeah, I do have two boys, one graduated college, one's in college today. I think it's obviously the advice that you give your children is different than advice maybe in the work world itself.

Tom, it seems like your firm is very similar to our firm in the sense that we can employ people from literally all over the world and basically assemble the best talent pool to conquer the opportunities that we have in front of us today. And so there's a lot of similarities there. I think it's important today for people getting into the workforce and

people looking at how that's gonna change. To be technical in nature, there's a lot of advancements in AI, I think data sciences, a necessary requirement for a lot of fields that people go into, especially in the tech world. And so I think we're very similar to your beliefs as it relates to remote work and the ability to recruit from all over the world.

We'll go to the technical side now, then we're going to bring up your financial statements later and ask you a few questions about them so we can learn directly from you. I'm curious just more specifically and then turn it to Carl about the integrations with AI tooling and GitLab's integrations and what sort of

competitive challenges you face with the relationship between GitHub and Microsoft. And I can't, developers can't easily use Cursor or Windsurf with GitLab. So what do you see as the future of GitLab's position in the market? I would say certainly given the substantial competitive advantage that Microsoft and GitHub have together.

It's a great question. Two different things let me answer, Cursor, Windsurf, and then Microsoft and GitHub. There was a lot of questions on the earnings call related some of the press at Cursor, Windsurf, and some of the M&A activity in that field has generated.

we pick up where they leave off. Cursor and Windsurf is really into the code suggestions and code generations. But once you actually develop, and it's located primarily in the IDE, once you actually develop that, then you need to have a system to plan, manage, deploy, secure, package, the rest of the software development lifecycle. The more code that is created,

I'm a firm believer will create more complexity. The more complexity is you need an integrated platform that has a single pane of glass to look over the entire software development lifecycle. I think the platforms today are well-positioned with all the code that's going to get created.

there has been a lot of questions around developer seat count and what will impact seat count over time, especially as it's related to the AI that's coming out. A simple equation to me is you have developers times productivity equals output,

and one of two things will happen. If productivity goes way up, you assume output's going to stay constant, then developer seat count will go down. If developers stay constant and productivity goes way up, you can bank on a lot of output increasing.

And every company today has to become a software company, regardless of what vertical you're in. If you're in transportation, manufacturing, federal sector, whatever sector you're in, software is a differentiator.

giving customers more data, where your package is at, when it'd be arrived, how many stops your delivery drivers away, they're shopping more, they're more informed. I'm a big believer that the developer seat count will remain relatively the same, output will increase, but also with AI, you can actually reach different personas. There will be many more people doing developer-like functions with AI out there today.

I'll follow up on that. I'm a developer here at The Motley Fool. Just for all the viewers, there's these development tools, Cursor and Windsurf, where developers are using AI models to code a lot faster, get their throughput up a lot as Brian is saying. I'm on that first half where we're working in the IDE before deployment, and then maybe making changes after deployment and fixing things in production.

But with so much time spent in the IDE and you're saying GitLab helps a lot afterwards for all that work that comes after, do you not see that as a gap perhaps where maybe it would be great if there wasn't an easy integration or access for AI coding models with Cursor, Windsurf, or other tools just to allow easier access to that code for developers in that first section?

Yeah, absolutely. And thanks for the question, Carl. And so if you think about the GitLab platform, all the code suggestion tools set on top of that. And so GitLab is an open source tool. People can do co-creation in GitLab. And so a lot of our customers, they will write merge requests, software enhancements.

to the platform, which all customers get the benefit of. And so we have something called Code Suggestions today. It's built into our Duo product. We just announced before earnings that you'll be included in all premium and ultimate subscriptions, that you will get the ability to have that as part of your base plan to do that. And so whether you use Copilot, Curse, or Windsurf,

GitLab Duo code suggestions, all that sits on top of GitLab and can be used in correlation with GitLab. It's not a replacement, it's the combination thereof. We've been trying to think of different analogies to explain this to investors.

and folks that ask and one of the analogies that our CEO used during the earnings call was the difference between Excel and Snowflake. Excel, people are in the model, they're using the data, they're manipulating the data, but they use Snowflake more for the data warehouse, for broad or data science. Still relatively the same data, but used for different purposes.

Gotcha. Nice. I wonder if you can say if there's any differentiators between your AI coding product duo and something like GitHub Copilot and Cursor and WinServe and all these other AI coding copilots.

Yeah, I mean, they're all based on the underlying LLMs. One of the things that we have relative to our AI and code suggestions in general is we have the context of what you're doing within GitLab. And so we understand what's going on within your code, what corrections you're making, what security vulnerabilities you had. And so the more context, the knowledge graph that you have,

the better the suggestions are going to be. And so you still, you know, you'll still need a human to review it. You need to go through and look at quality and security and so forth. And so, you know, we're building knowledge graphs to go around our AI products that will give more context, which is a differentiator to some of the other products out in the market today.

I'm very bullish on Knowledge Graph, so you're pushing the right buttons here. I'm happy about that. Thanks, Kyle. I also saw that Duo had a partnership with AWS Q, which is AWS's platform and coding co-pilot system. I don't know if you want to talk about that for a second. Yeah, absolutely. April of this year, we announced general availability of GitLab Duo with Amazon Q.

The integrated offerings available as a bundle for GitLab Ultimate self-managed customers on AWS. Really what we're doing is we're bundling Amazon Q Software Development Agencies directly into the GitLab DevSecOps platform.

And so it's basically, once again, bringing in sort of the best of what we have, the best of what Amazon has, putting it together and jointly selling it to AWS customers and our customers. Some of the things that this partnership will do is help tackle some of the critical development challenges

such as autonomous feature development, legacy code-based modernization, security vulnerability remediation, quality assurance improvement, and other things. We're super happy about the partnership. This was announced on the main stage live. Amazon typically doesn't partner with a lot of companies in co-creation.

really think this will bring a lot of benefit to Amazon and GitLab customers. Summer is coming right to your door. With Target Circle 360, get all the season go-tos at home with same-day delivery. Snacks for the pool party? Delivered. Sun lotion and towels for a

Beach day delivered pillows and lights to deck out the deck. That too delivered just when you want them summer your way, quick and easy. Join now and get all the summer fun delivered right to your home with target circle 360 membership required subject to terms and conditions applies to orders over $35.

Brian, can you talk a little bit about, you mentioned that DevSecOps tries to solve overall in software development. Can you talk a little bit about more recently? What are some of the challenges, some of the big problems that your customers, your key clients are asking you for and what you're trying to solve? Some of those really meaty problems you're trying to solve right now.

It's interesting. I think there's a number of meaty problems. I think security is always top of most of the people's agendas, if you will. This past quarter, our ultimate product made up approximately two thirds of the overall mix of what we sold. Ultimate is our highest priced product and it really has advanced security and compliance features.

that our customers love about the product. And so, that's one. I think companies today, we're in a very dynamic environment, obviously, and companies today want to basically take the best of breed tool chains that they have, that they're constantly trying to integrate together to increase the software velocity.

you can do that in the GitLab platform. A lot of people come to us where they're eliminating a lot of these point solutions to get onto the platform to increase cycle time and to do software development better, faster, cheaper, more secure. Well, it's time for another game here. I'm going to do another screen share. In this case,

You will see that I have prompted this question on GPT. If you were the CEO, if you were CEO of GitLab and you wanted to 5X the value of the company over the next seven years, what exactly would you do in layman's terms and in less than 300 words? So I'm going to read each of these quickly. And then Brian, you can pick and choose any ones that you like or dislike, share how accurate you think it is and how much we just learned from this or whether it was a waste of time. If I were the CEO of GitLab and wanted to 5X the company's value in seven years, I would

Here's exactly what I do in plain English. Go all in on AI for developers. Make GitLab the default place where AI helps you write, test, review, and deploy code faster and safer. Not just an add-on, but build deeply into the product. Think co-pilot for the whole DevOps process. Number two, build native support for tools like Cursor and Windsurf. Partner up or pay to integrate GitLab into all the new AI dev tools. Get to

GitLab can't have a monopoly here. We need to be where tomorrow's coders are working. Number three, win enterprise trust with private AI. Sell GitLab as the safe place to use AI inside companies. Make it easy for CIOs to say yes to GitLab because their data code and models stay private and secure. Number four, make money from the free tier. Millions use GitLab for

free already, convert more of them with irresistible AI tools, usage-based pricing, and easier onboarding for Teams, and finally, be the Switzerland of software development. Position GitLab as the open neutral alternative to Microsoft. We're not pushing Azure, we're helping Teams ship better software no matter what Cloud AI model or stack they use.

In short, focus everything on AI powered software creation, turn the GitLab platform into an indispensable tool for modern teams and stop letting GitHub eat our lunch. I wasn't expecting the last line there. Anything that you'd like to reflect on there?

Particularly nasty last line by GPT in partnership with Microsoft, I say jokingly. Okay, which of these five stand out to you as persuasive? Well, thanks, Tom. I appreciate the games that you're playing. It's a very good list. You know, it's interesting. The list is really...

very similar to our top three objectives this year as a company that we've outlined on our previous earnings calls. Number one is focus on first orders.

We know once someone lands on GitLab, the benefit and ROI will be very high and that they'll continue to expand and grow in GitLab over a period of time. And so cohorts from 10 years ago are expanding roughly at the same rate as cohorts are expanding today. And we have a very high gross retention rate. So that's number one.

Number two is you give more value to our customers and that is going from premium to ultimate and you're building, you know, basically a product that enables them to realize the value of security and compliance. And three is investments in AI. And so if you look at,

the lists that you've come up with, they're very similar to our objectives that we talk about externally as well as internally that we go through every week.

I think five is really important, being the Switzerland of software development. GitLab is a public company that isn't aligned with one hyperscaler, is a diverse revenue stream. One customer doesn't make up more than 2% of our overall revenue. And we are developing for what's best for the DevSecOps market.

And we don't have other products that we're bundling together and selling a whole host of products together. And so we are the Switzerland of software development, which I think is really important as well.

Obviously, monetizing the free tier, we have a bunch of people in our free tier. We have the wider community of developers, which we think is very important from a contribution standpoint, from a brand standpoint, getting into education early. We have a number of people in colleges and universities using the product. So, yeah, I think the list is spot on and it aligns with the objectives within the company. So I appreciate the game that you played.

It's not the only one we'll play and thanks for playing along, Brian. We'll go back to Andy who has to exit in a few minutes. So Andy, the next two questions are yours. Tying back to the free side of GitLab, I'm just curious if you can give some insights into your go-to-market strategy, the differentiating, how you're thinking about selling, reaching more clients. Just educate us a little bit more about what GitLab is doing from a uniqueness perspective on the selling side.

Yeah, absolutely. We had a new CRO just join us this last quarter, Ian Stewart. He's really focused on, obviously, the go-to-market motions. There's a number of ways for GitLab to grow. Obviously, selling to new clients, expanding with our existing clients. We have a number of new SKUs that our clients can actually buy, such as

you know duo pro do enterprise this winter we have a gentic workflow coming out which be the dual agents we also have dedicated which is a single tenant saas that you can buy if you don't want to be in the public cloud you know most of ours run in the cloud today you know we have a partnership program a channel program we sell through hyperscalers you know we can expand geos and so

The market, the estimated TAM of the market today, and this is before all the AI and the adjacent TAMs that you may get into, is about $40 billion and it's growing at a relatively healthy clip. Once you add new personas in there with AI and other things that we talked about earlier, the market's only gonna get bigger.

And so I think we are well positioned as a company with our current product set being a Switzerland that we talked about a little bit earlier from a DevSecOps perspective to go out and execute in that market. Brian, I know you serve a lot of the Fortune 100, some of the largest clients. Just talk a little bit about the balance between serving large clients who are, what kind of large clients are you serving? What industries are you focusing the most on all the way down to some of the smaller clients?

Yeah, absolutely. If you look at the Fortune 100, about 50% of them, about half of them, use a GitLab product today. That could be in a division department. It could be, you know, it's usually a bottoms-up adoption. So it could be, you know, anywhere in that enterprise today. So, Brian, sorry, is that not through the CIO's office? Is that through a different kind of process that you go through? Yeah, there's two primary, two selling motions that I can talk about. One is a bottoms-up product.

adoption. The reason why our net dollar retention rate for cohorts 10 years ago is about the same as cohorts a couple years ago is because we're expanding within those clients by selling the different seats. We're doing tier upgrades and then also, you know, increased customer yield. And so one motion is the bottoms up motion where a engineer within a division department

will buy just for that division department. Typically, that will be on a credit card. It's a relatively small purchase. Then it will go from that department to the next department to the next department. Then it will change personas. It will go from an engineer to an operations person. Then a lot of people will use it from an operations perspective. Eventually, when it gets to the security,

department, they'll look at what we have in premium versus what we have in ultimate. In ultimate, we got vulnerability assessment, fuzz testing, container scanning, a number of different things. And they'll want to upgrade to ultimate to get the advanced security features. And so then we'll have an upsell in that department. That's our bottoms up motion. We do have top down motions, which typically go through the CIO office that you alluded to.

We talk about UBS, UBS at a wall-to-wall implementation. Their CIO put out a press release on purchasing GitLab and all the things that we're doing with them. And that's where they do an implementation across the entire enterprise. And so we have both selling motions, bottoms up and top down. We will now go to the financial statements. I think we will lose Andy. Thank you so much for spending some time here, Andy, with us.

What we'd like to do, Brian, is it's our opportunity to learn about how you see the company, to learn about GitLab, and then also to learn about how to read financial statements in a way for many of our members. We have a good continuum of investors at The Motley Fool. Some of them are retired CFOs of public companies.

Others just made their first investment three days ago. So we try to reach all of them in different ways here on Fool24. So let's just start with the balance sheet here. What's one or two of the most important things that you focus on looking at this balance sheet? Obviously, it's a liquid cash-rich situation that GitLab is in. So talk to us about the balance sheet.

- Yeah, for a public company where we're valued at today, we have a very clean balance sheet. In the quarter that we just reported, first quarter, we generated over $100 million of free cash flow. And so you can see our cash balance

You know, we have over a billion dollars of cash on the balance sheet and cash and equivalents as well as short term investments. And so, yeah, obviously that from a company perspective and an investor perspective, I think that's really important. The company, you know,

doesn't have any debt per se as a debt structure you know we have obviously liabilities on the balance sheet such as you know accounts payable and and payroll to be accrued and paid and bonuses be accrued and paid you know we um from a bad debt perspective you know you know we bill our customers typically net 30 net 45 days we have a very good collections very low bad debt

But from a balance sheet perspective, it's relatively pretty easy and very clean. We always collect up front, so we have a big deferred revenue. And so whether we sell a one, three, or five-year deal, we collect up front. And so we recognize that as a liability, and then we'll work that off over time as we deliver the service.

Two quick follow-ups. One, can you talk about, I mean, this is a beautiful balance sheet. Can you talk about how organic GitLab is in growth and why no acquisitions? Obviously, you'll see to the extreme end of the continuum in technology, you see what Salesforce has done. They've essentially acquired their way.

You know, somewhat brilliantly, really. I mean, you'd have to say it's been an unbelievable success story. It hasn't necessarily drawn off of a lot of internal organic innovation and growth relative to other companies, given how much acquiring of businesses they do. So why hasn't GitLab made acquisitions? What's the what's the leadership thinking there? You know, we have a corporate development team.

They're out looking at different deals all the time. We've made a number of acquisitions, but they've been relatively small in size and typically pre-revenue. And so one of the things with GitLab is we think it's so important to be on the same code base and not to actually attach a lot of modules to it.

Part of GitLab is you have this single pane of glass where everybody can see everything is happening at the same time. It's fully integrated. Any acquisition that we do, we'd uproarate the software and rewrite it within GitLab very quickly.

And so if we were to go out and acquire a company that $100 million in revenue or $500 million in revenue, that customer base is expecting that they're going to be-- you have a contract to supply that product. And that customer base is going to expect that product under certain terms and conditions.

it's very difficult to deprecate and rewrite it, put it in the GitLab platform if you have these large contractual installed bases. And so most of what we're doing in M&A is buy versus build analysis.

and time to market and Aqua hires. And so, you know, we look to for the companies that we acquire, you know, they're relatively small and it's buying the technology and then rewriting that and putting it back into GitLab and offering that as a feature functionality to our customers. Do you think, and have there been acquisitions that are really geared to attract young developers using AI tools that might be the future developers at Fortune 100 companies?

All of our acquisitions, we have a great team doing our corporate development analysis, reaching out, looking at the market. We have a product roadmap of where we're going. Obviously, some of that includes AI, some of it includes security, some of it's around your package product. They're looking at all types of acquisitions.

of which AI is a part of that. As we go through and look at it, AI developers may come on board as part of M&A. - Thank you. Last question on the balance sheet, just for a simple one for clarity for our investing members.

What's the difference between cash and cash and equivalents in short-term investments? And why do you sit $255 million in one and $849 million in the other? Yeah, it's the accounting definition of how you have to classify it on your balance sheet. So short-term investments are, you know, we have two banks that we primarily do our investments with. You know, typically the yield is greater than cash, but cash is cash.

and short-term investments give us a little greater yield. We have investment policy. I'm sure it's found in our handbook and at some place on what we invest in, but it's to basically increase the yield of the return of the balance that we have.

Thank you very much for that. We'll go to the income statement. Any reflections? And it's great. We still have Andy Cross here. And Andy spends so much time in the financials companies. If you have a follow up on this, Andy, but what stands out for you looking at the quarterly report ended April 30th on the income statement, Brian?

Thank you for pulling this up. You know, we grew revenue 27% year-over-year, I think, which is top quartile for growth in software companies. I also am very proud of how we've done on gross profit. You know, we reported a non-GAAP gross margin of 90%. We've been able to maintain that. Our SaaS revenue has grown 35% year-over-year. It now comprises about 30% of our total revenue.

And we've done that with getting increased operating leverage in the model. And so one of the things that we set out when we went public is we said one of the objectives for the company is number one objective is the growth, but we'll do that responsibly. And we've been able to deliver increased operating leverage in the model every quarter. When somebody says they're not GAAP profitable, there are investors who, if they saw negative EPS,

they simply wouldn't invest. Speak to somebody to explain to them how the model works and why it shows up as a negative gap, negative income, but positive free cash flow. - Yeah, absolutely, Tom. We have a gap to non-gap reconciliation or 8K. And so you can look at all the tables and what goes in and out of that. But the biggest item that we non-gap out is stock-based compensation. And so that's not an actual cash charge.

But it's a P&L charge. And so our compensation philosophy from a company and being a newly public company is a combination of cash and stock for team members. And the stock based compensation is a charge that you need to take to your P&L. And that's the biggest difference between GAAP and non-GAAP reconciliation.

Brian, can you quickly just describe the license business and as a percentage of total sales, it continues to go down. Will you eventually see that as almost zero going forward and once you get big enough?

It's a great question, Andy. We try to meet customers where they're at. You can basically buy GitLab as self-managed, which is on-premise, which is licensed, or you can buy it SaaS and host it. As I mentioned a little earlier in the call, our SaaS business grew 35 percent year over year.

currently makes up 30% of our revenue. Companies are looking, they like our SaaS product because they can get basically stood up quicker. It's a lower total cost of ownership. A lot of people are familiar with buying SaaS today. Because of the revenue recognition policies, we follow revenue recognition standard called ASC 606. We have to recognize a portion of our self-managed upfront, which goes into our license components.

because SaaS is growing quickly. That's why you don't see license growing as quickly. But we don't compensate different for our reps, whether they sell a self-managed or a SaaS license. We want to go in and have a consultative sales approach, go in, talk about the benefits of GitLab, and then let the customer decide, do you want to buy it in our Cloud or do you want to buy self-managed and put it in your Cloud?

And we charge the same price for that because once they get to that point, we don't want them to have to go through another several weeks of analysis on how much will it cost for us to host it versus GitLab hosting. We do this every day for a number of our customers and we can do it very efficiently. And so that's part of the reason why our SaaS business has grown so quickly.

As we head towards the cash flow statement, I'm going to drop in a personal question about your work approach at GitLab, Brian, almost seeming out of place, but I just can't not ask it for whatever reason. That is, down a continuum of 1-100 where 100 is maximally strategic as CFO and one is maximally accounting discipline as CFO, like deep finance numbers. Where do you place yourself? Where do you like to operate as a CFO?

Do you like to be in the brainstorm, idea generation meetings? Do you like to be updated when things have been rolling and you help to optimize and refine them? What's best suited for you? That's a great question. It's really interesting how this has changed over time.

And so CFOs used to be very operationally focused and when Sarbanes-Oxley came about due to the things that led to that, they became very accounting focused and so forth. I find myself more focused in operations

and really aligning myself with the CRO and sort of go to market. And so, yeah, I learned at a very early age that, you know, if sales are going well, go to market's doing well, you know, that's really what can drive the shareholder value of the company.

And so, you know, like to be strategic and focus on operations. But obviously, as a public company CFO, compliance and accounting and closing the books and all that is extremely important as well. So it's hard to give a percentage between the two. But I think, you know, in today's age, you have to be very dynamic and understand the business, understand the growth levers.

the drivers for shareholder value and help do the resource allocation around the company to get the best return for dollars invested. But then you also need to do that in the most compliant way and report out to shareholders as well. And so, you know, I think they're both really, really important. And, you know, I find myself partnering with the CRO a lot on go-to-market initiatives.

This episode is brought to you by Amazon Business. How can you free up your team from time-consuming office tasks? Amazon Business empowers leaders to not only streamline purchasing, but better support their teams so they can focus on strategy and growth, free up your teams, and focus on your future. Learn more about the technology, insights, and support available at amazonbusiness.com.

Thank you. Now we cruise down to the cash flow statement. For newer investors, this is usually the most confusing of all, but this is where you can net out and see that the company is generating over $100 million in operating cash from operating activities. And you come back up, and Brian was mentioning the stock base compensation at $55 million. I'll ask a question about that in a second. But

What stands out for you on the cashflow statement? - Once again, I think our financial statements are extremely clean and easy to understand. I think the most important thing for an investor to understand on a cashflow statement, especially cashflow from operations is you basically start with the P&L, then you go back and you add back and subtract all the non-cash events to see how the company did on cashflow from operating.

Investing for us is super simple, it's a change in investments. And so I think we have a very simplistic cash flow statement from a company perspective. Out of curiosity, what was the $1.7 million charitable donation of common stock?

Yeah, thanks for that, Tom. GitLab has an every quarter donate stop to the GitLab Foundation. I sit on the board of the GitLab Foundation as well. The GitLab Foundation is a foundation that it's a standalone foundation, not part of GitLab.

a nonprofit that really focuses on investing to get earnings power return for people that can't get those. For every dollar invested, we have to get a certain amount return. And so we do a number of investments all around the world.

I encourage you to go look at the GitLab Foundation website. It's a very data-driven process foundation, and we get a lot of requests from other foundations to basically help them measure the impact, the social impact that they're making and the return that they're making.

Thank you. On the stock-based compensation, one of the statistics we use as investors at The Motley Fool is to take the stock-based compensation as a percentage of gross profit to look and try to get some association between what that grant is getting is driving in terms of growth up towards the top line of the business.

And we're certainly proponents of having ownership across the entire employee base. Every Motley Fool employee owns shares of our company, and that's pretty much been true for we've been in business for about over 30 years. We're a private company, so we have an internal market system, all SEC approved. It's quite interesting, but that's a topic for another time.

55 million as a percentage of 189 million is nearly 30%, which would be at the higher end of the range of most technology companies. So maybe explain your thinking as to why it's 55 million instead of 35 million or 75 million. Sort of the view, I know there's no perfect answer there. A lot of factors go into it, but why is GitLab sitting at a higher rate of granting within the overall growth dynamics of the business?

Yeah, this is something obviously at the board level and company level is discussed on a quarterly basis. We look at our comps relative to all the other companies as well. And we actually probably sit right in sort of the average of tech companies today.

It's a form of compensating our employees, cash and stock-based compensation. And as a newer public company, we have stock options that are out there that they come up for the best and we recognize SBC charge related to that. But as a percentage,

you know, that number has slowly dropped and, you know, something that we're focused on become gap profitable as well. One of my favorite thinkers on compensation once told us, as I mentioned, we often go contract people to be advisors for us. I think companies significantly underdo this. Many people would like to help.

particularly if they have some affiliation with the company or some connection to the industry, particularly if they're in semi-retirement or retirement or in between. I mean, just generally, people will give you an hour, five hours. Steve Jobs once gave a very eloquent statement about calling and asking for help. And he had done that, I believe, as a 12-year-old or 11-year-old calling. I think it was Bill Hewlett of Hewlett Packard and actually ended up with a summer internship there because of it. Basically said, you should be calling people

- Right. - All the time. Well, one of the compensation advisors I spoke to years ago said, "You know, the most important thing about compensation is to not make it too much of a focus relative to peers. Get in the zone and work on your mission. Make sure the highest performers that are most passionate about your business

getting the rewards that they deserve but you don't need to go into big outliers it sounds to me from doing your comparisons to other technology companies that that's generally gitlab's compensation philosophy true or false yeah absolutely you know i would say true if you focus solely on compensation uh you're gonna lose the team member right and so you know it's part of the brand the mission that the company is after and

though everything else around it. And so, you know, GitLab being fully remote, we have a lot of top performers that don't want to drive two hours a day to and from the office. Instead, they can be productive at home and actually be adding value to the company. And so you don't want to compete solely on compensation.

We used to have a compensation calculator that was made public. We had to take it down because the accuracy of it and some of the people that were feeding our sources of that weren't happy with the data and how accurate it was. But we do have a compensation philosophy. It does include compensation, but there's a number of other things in that. But I think the important part is, from a team member perspective, is what do they want to accomplish? How can they personally and professionally develop

and help lay out a path for them to accomplish that. One more question for me here as we move off the financials and then back to Carl on the technical side. Amazon came out recently. This is going back to kind of my apocalypse question previously, but Amazon came out as a dominant, very massive, growing company.

cash generating business said, we expect to succeed and grow, but do so with a smaller workforce than we actually have today. This is so unusual. This is such an outlier in business history that you would have the largest

let's say 10 of the largest companies in the world with all massively liquid cash heavy balance sheets saying we're reducing our workforce. I mean, that you would actually have layoffs at the magnificent seven companies

when there's not any clear negative headwinds or business reason for doing so. I guess I'm coming back and asking this question again about, do you see similar dynamics at GitLab? You talked about maybe same seat count unemployment and more productivity, but are you starting to see that already or you're making those projections?

You know, there's, you know, obviously we go through an annual planning process and look at the tools that we have available to help make us more efficient. I think that a lot of those companies where they say that they're laying off employees, they're actually laying off in one area to hire in another area because I think the skill sets are changing and they're adapting to what's happening in the macro environment and how to change with that.

And so some AI tools out there may be great at call center, you know, at call center requests. And you may be able to do that through a very intelligent bot and actually answer 80 to 90% of the questions, you know, in the call center automatically through the bot, through generative AI, you know, and actually satisfy your customer. And so you may be able to reduce your call center agents by a certain amount, but then they're taking part of that and it's a higher price per

and investing in AI. So the headcount isn't necessarily growing, but they're still making an investment in areas for technology innovation. And so, you know, I think each company is different. It depends on the company, where they're at in their life cycle and what they're investing in and what they're trying to accomplish. - Thank you. Carl. - Yeah, I'll pop in. I like that metaphor about the call center. And I actually wonder to pivot back to your product,

I know you have Duo, I know you mentioned there's agents coming later in the year. I wonder what will that call center metaphor look like for GitLab so that companies can actually increase their usage of it through agents, increase their throughput with perhaps less people?

- Yeah, it will be interesting from GitLab's perspective, there's a lot of development, a lot of feature functionality to continue to work on. And so I could see things that we automate, we'll continue to reinvest back in the product in different ways as well. And so I would say we aren't too dissimilar to the companies that you mentioned, the Magnificent Seven on sort of what they're doing and how they're changing, obviously different scales and magnitudes.

And so it will be to lesser of an effect, but we're looking at how people work today, how our product, we dog food our own product, obviously. And so the impact and savings that we could make, and so we'll re-pivot those investments in other areas for higher impact with that savings.

Okay, nice. Just to be direct, I wonder what your roadmap is, if you could talk about it for the agent side. Your product, the way you talked about the Google Docs for DevSecOps, there's all these different teams looking through one pane of glass working on different parts of the same software for different reasons. Will each team have agents that help them in their productivity in your platform work on this software? Is that the right view?

Yeah, absolutely. And so we are, you know, we're developing a number of different agents that will, you know, these dual agents will do functions that people would normally do, but that they can be done automatically. And so it will make them more productive for those functions so they can focus on other functions.

other areas. And so think of an agent as a non-human doing what a human would otherwise do to actually get more, you know, increased cycle times, increased productivity, get more code published and deployed. And I know we already talked about a solid partnership with AWS, exactly about that, what we're talking about. Do you see any future partnerships with others like Oracle or Google or other platforms?

- We're always looking at for partnerships on how they're win-win. A lot of partnerships are more marketing press versus win-win for both parties. And so we're really deliberate about the partnerships that we enter into and make sure that we can get to general availability, that we have sales targets associated with them, that both parties have skin in the game and that they can be beneficial to our customers.

And so I think there's a number of partnerships over time, but there's a high bar to basically get over to make announcements around those partnerships.

Yeah. Speaking of partnerships, the AI labs are like the top dogs these days, at least from my viewpoint. Everyone wants partnerships with them. I wondered if you can call out if you have any partnerships if you're using Anthropic, OpenAI, Mistral, or what models are powering Duo, for example.

we've announced this, but currently today, Anthropic is one of the LLMs that we're using. One of the great things about GitLab is you can be model neutral. And so we have used and tested a number of different LLMs. And so with GitLab being a pure play switcherland DevSecOps platform, we're actually creating those models and the results specifically for that ecosystem.

Our team will constantly look at models that come out, the results that they produce, the code that comes out of that, and use the best model for our customer base today and in the future. Okay, nice. Now, like a future thinking question,

if you had to describe GitLab's product with AI top of mind, of course, in this conversation in two years from now, what does that experience look like for a developer? I think it's funny, Tom, the game that you played asking chat GPT or whomever you asked around the five things.

I think being that Switzerland for the software developer for DevSecOps is really important and that will be done through humans, through agents to create a use case and an experience for the developer that would be seamless, highly effective and great payback to really enable them to do their job with joy and satisfaction.

Well, we're down to our final few questions, and these are helpful ones for us as investors as well. What companies do you admire? It could be anything. It doesn't have to be companies that GitLab works with directly, although please feel free to share any of those. You could simply say, I absolutely love all of my experiences with Airbnb in my personal life. What are a few different public companies that you admire?

They're all for different reasons. But I look at a number of different companies for what they do, their metrics, best practices and so forth. Some are for personal reasons, some are for investment reasons, and some are from a GitLab perspective. There's a number of different companies I look at, but like I said, all for different reasons. Is there a company you admire?

out there? I don't want to give a particular company. Okay, that's great. I think there's a number of great companies out there. It's great to learn from people who've been there, done that, from that perspective. Excellent. Anything you can share on your own investment style or what have you taught your children about investing?

You know, my investment style being a CFO is fairly conservative. And so, you know, I'm, you know, in a lot of bonds and index funds and diversity is very important. You know, for my kids, I thought it was really important for them. You know, one of the things that my father did for me as a young age was introduced me to a stockbroker. I don't know if they're called stockbrokers anymore. But, you

At age 14, I gave my son some money and basically introduced him to a gentleman that helps manage my money and basically wanted him to understand how to read financial statements, how people invest. There's a Warren Buffett style of investing. There's a technical aspect of investing. And so both of my kids are very astute in the markets and follow the markets very closely and have their own

small investment portfolio that they track and monitor and trade in, you know, so they can just understand it. And so I encourage people to get your kids involved early and to give them exposure to the market. And obviously you've made some investments in private companies in your life. So for somebody who's thinking about making private company investments, any guidance for them or any thoughts that you have on how to do that most effectively?

you know it's it's tough when you focus most of your time and as a public company cfo you don't have a lot of time to follow the private markets and so a lot of my private investments have been relatively small uh and been through a friend-to-friend network if you will um and you know it's been basically given a small amount of money based on a thesis that they're going to go try to solve but um you know private markets are you really take a lot of time to follow

the founders, the technology, how things are evolving and so forth. I'm sure you guys have on your website a lot of great material around that. Thank you for that. And given that companies remain private so much longer, it does almost require individuals to find opportunities to get onto platforms and make some private investments. Although, of course,

It's still a very rich public market, abundantly great companies around the world as well, and easier access to companies around the world as well. GitLab is an eight-time recommendation in our real money portfolios of The Motley Fool. It's a $6.7 billion market cap. It has about a billion dollars in cash and no debt on the balance sheet. It has great top-line growth rates. One of the really interesting factors in life in the public markets is to follow how top-line growth rates drive equity returns.

Obviously, there are examples of companies that got out over their skis, had massive demand and no hope of ever generating cash, a positive cash flow out of it and fell apart. But in general, demand is a really important factor for long-term investors. And at The Motley Fool, we typically hold our investments at least five years and teach others to do the same. I'd love to just close, Brian, final question with what are you most excited about in the, let's just say in the year ahead, starting on this day to this day, 12 months from now, what are you most excited about at GitLab?

Yeah, I think GitLab is really well positioned in the DevSecOps market. As I mentioned, we have over 50 million people on our platform today. We give a great return for investment on our ultimate product, and we enable people to build software better, faster, cheaper, more secure. Not only are we growing, we're doing that more effective quarter over quarter, and you can see the operating leverage in the business.

As you look at growth, I look at growth relative to when you can break that inflection curve and continue to add operating leverage in the business. And so with 90% non-GAAP gross margins and great free cash flow generation, I think we're well positioned to make the investments that we're making in AI as well as in security for the benefit of our current customers as well as our future customers.

Well, Brian Robbins, thank you so much for the hour. We learned a lot more about GitLab than we've learned so far. We've tried to learn as rapidly as we can. We have all of our AI engineers like Carl, all of our techies and all of our investors working together to understand these companies better and better. And this hour certainly helps us a lot. So thank you so much for this time. Thanks, Tom. Thanks, Carl. Really appreciate you having me on the show today.