Home / Transcripts / GitLab Inc. (GTLB) · September 3, 2025

GitLab Inc. (GTLB) Earnings Call Transcript

September 3, 2025

NASDAQ US Information Technology Software earnings

Earnings Call Speaker Segments

Cassidy Fuller-Patterson analyst
#1

Hello, and thanks for being with us on this call covering GitLab's financial results for the second quarter of fiscal year twenty twenty six. Joining me today are Bill Staples, who serves as our CEO, and Brian Robbins, our CFO. On today's afternoon call, we'll walk through a business overview, share commentary regarding our second quarter results, and offer guidance for the third quarter along with fiscal year twenty twenty six. Prior to starting, I'll go over the safe harbor statement. I'd like you to look at the note on forward-looking statements that appears on slide two of our deck and also in the earnings release we put out today — you can find both of those in the Investor Relations section of our site. In those documents, we talk about certain risks, uncertainties, assumptions, and other elements that could cause what actually happens to be different from what any forward-looking statements describe, as that term is defined under the Private Securities Litigation Reform Act. Just so everyone's clear, that disclaimer applies to everything we cover on this call and in the presentation. We'll also be going over some non-GAAP financial measures today. Those measures exclude certain unusual or nonrecurring items that, in management's view, affect how comparable the periods we're discussing are to one another. If you want more information about these non-GAAP measures, including reconciliations to the closest GAAP equivalent, please take a look at the earnings release and the presentation materials. At this point I'll turn things over to Bill. Bill?

Bill Staples executive
#2

Thank you, Cassidy, and hello, everyone. We're glad you could join us today. I'm glad to report that we had a solid second quarter. Revenue rose 29% compared with the same period a year earlier, reaching 236,000,000, while non GAAP operating margin came in at 17%. Before I move on to the broader business update, I'd like to note that we're leaving this year's revenue outlook unchanged and at the same time raising our non GAAP operating profit, which reflects how committed we are to growing responsibly and running the business with discipline. That takes into account the ongoing evolution of our go to market approach under new leadership, as well as a fresh perspective on small business. I'll share more specifics in a moment. Before we dive in, just a quick reminder that when we kicked off this fiscal year, we set three goals designed to concentrate our efforts on what we think will fuel our next phase of growth, along with improved operational efficiency, so that we can continue scaling and become a generational company in our category. So here's the current picture. Goal one is acquiring more new paying customers, especially in the mid-market and enterprise segments. For us to be a multi-billion-dollar growth business, we need to add new customers every quarter who can grow right along with us. Since the company was founded, every core cohort continues to expand with us at about the same rate, but the member sizes of our new business cohorts have been getting smaller. We've reached the point where we need to pair our growth initiatives with targeted actions aimed at bringing in new customers. Our approach involves creating two simultaneous paths: one driven by sales, and the other driven by product. On the sales-driven path, our CRO Ian Stewart has just completed his initial quarter and delivered impressive performance. He's steering a number of strategic initiatives meant to position us for continued scale as revenue grows past the billion dollar mark, among them building a global new business team that concentrates on first orders, plus a post sales motion supporting fast module adoption and value realization; we'll ramp this initiative over h two, aiming to start delivering benefits for f y twenty seven. New customer growth this quarter got a lift from our startup program, with a 72% quarter over quarter rise in the count of new startups joining, and 56% of those were AI companies. A great example of landing a new account is the q two agreement we signed with Chaos, a company delivering top-tier visualization and design tools that serve a range of sectors — architecture and design, media and entertainment, and product e commerce. After a very competitive review process, Chaos chose GitLab Ultimate because of our end to end DevSecOps offerings, including built in security scanning and SOC two readiness — both of which are highly important to Chaos' growth strategy following a number of recent mergers and acquisitions; when it comes to the product led side, we'll launch a growth motion focused on acquiring customers via a self-service experience. I'm glad to share that Manav Khuratna has joined us as our new chief product and marketing officer. Manav and I worked side by side at New Relic for four years. He's held executive positions spanning product led growth, marketing, and product management, and he's an expert in product led growth. During his time at New Relic, he built a large, high growth, self-service business from scratch that brought nearly 50% of customers to the overall base in three years. I'm confident in my ability to drive results at GitLab and expect this to gradually ramp over multiple quarters. Our second objective is to help customers realize the value of our platform faster, helping to drive revenue expansion. Here again, we're pursuing a dual sales led growth and product led growth strategy. Regarding the sales-led portion of our business, we have bolstered our team and rolled out several initiatives aimed at enhancing both sales and post-sales performance. These efforts encompass improved workflows, more advanced approaches to building pipeline, and management of pricing; additionally, we are upgrading how we train and enable our staff, especially in relation to AI. Furthermore, we are crafting fresh sales strategies that will drive more targeted outbound efforts, drawing on activities that have already produced positive outcomes for us. All of this is supported by a refined customer success and post-sales playbook, which is intended to speed up how quickly customers see value and how broadly they adopt our platform. When it comes to product led, signals for privately qualified leads will be sent to our sales force more and more by our product led growth motion; this will let them see the moments when our field can step in with customers and give better support as those customers move toward greater value. In Q2, we saw strong expansion results with accounts including Adesto, Clario, and Virgin Media O2. Consider Virgin Media O2, a leading UK mobile network operator — since 2022 it has increased its ultimate spend by more than five times, after embracing our full platform strategy. When you look at source code management, CICD, and security scanning, Virgin Media O2 is one of the most active users out there, and they just switched on GitLab Ultimate with Duo. GitLab Ultimate and our dedicated products are the purchasing options with the highest value that we offer. Ultimate now makes up 53% of our total ARR, and Ultimate was part of eight of our 10 biggest deals this quarter. Customers increasingly recognize what we offer on security and want that security built into how code gets developed. The security features of the GitLab platform remain a powerful driver of Ultimate adoption because customers find them so persuasive. A recent win with a major European fintech company shows this clearly. With Ultimate in place, they expect average recovery time to drop from a window of two to four days to just two to four hours, while also achieving full security scanning coverage on all of their projects. GitLab dedicated continues to see strong uptake as well, contributing about $50,000,000 in ARR, which represents 92% growth compared with a year ago. I'd like to walk through several additional examples from the quarter that highlight important customers and the value they're realizing from the platform.

Bill Staples executive
#3

During this quarter, we grew our ties with a major US bank, which moved up to GitLab dedicated once it saw positive results from GitLab premium. On top of that, they're rolling out 1,000 additional seats of GitLab Duo Enterprise, which lets them automate compliance enforcement and returns control to developers so they can innovate as quickly as they require. Take the Government Technology Agency of Singapore as another case — it relies on GitLab dedicated for its ShipHats platform, which powers Singapore's digital government services. In q two, GovTech Singapore broadened its deployment by bringing in GitLab managed hosted runners that are fully integrated with its dedicated instance. Through its ShipHats platform, this lets Govtech Singapore steer technical expertise toward enhancing developer experience instead of keeping infrastructure running. Last, our third objective involves speeding up customer focused innovation by concentrating on our core DevOps, security, and AI areas, with the goal of delivering higher quality, more complete market leading solutions across all three. I'm thrilled by how quickly our teams are innovating. Among the highlights from what we've shipped in recent months: 28 new features in GitLab premium, 33 new features in GitLab ultimate, and 11 new features in GitLab Duo Pro and Enterprise. Altogether that comes to 72 new features spanning our paid tiers and offerings; for instance, in core DevOps, we're making dependency management simpler through our Maven virtual registry, which is now in beta for GitLab premium and ultimate customers. We also shipped GitLab runner 18 dot one, a cornerstone feature of GitLab CICD pipelines, which we keep improving and investing in. Plus we've introduced immutable container tags, a new merge request homepage, and custom workflow statuses for issues and tasks. These additions widen GitLab's competitive edge over the best of breed solutions. When it comes to security and compliance, we keep bolstering our capabilities. As of today, customers can use GitLab's new CICD components to support SLSA level one compliance. We've also introduced PHP support for advanced SaaS, broadened SaaS coverage for GitLab Duo Vulnerability Resolution, added a new group overview compliance dashboard, and launched the beta of centralized security policy management. And we brought compromised password protection to a 100% of gitlab.com users, which helps safeguard all user accounts against credential based attacks. Our work to embed security seamlessly within development is a key reason large customers keep expanding with us. For instance, one of the largest wireless operators in The US relies on the security policies in GitLab Ultimate to carry out comprehensive shift left practices that automate security scanning, enforce guardrails across their CICD pipelines, and require merge approvals tied to scan results, all without slowing down innovation. In q two, they grew their GitLab ultimate deployment by adding 4,000 new users as part of their push to standardize on GitLab as the organization's primary software development platform for all engineering teams. Customers are genuinely enthusiastic about how fast AI tools are developing and what they promise. GitLab customers are actively trying out multiple tools and building their internal use strategies. The GitLab Duo Agent platform is striking a chord with buyers who find instant worth in our AgenTik AI features. To quote a senior software architect working at a top communications industry supplier: watching GitLab's agentic AI evolve alongside the new Duo agent platform has really impressed me. The ability to delegate tasks autonomously, plus the run tools functionality, are truly valuable additions to how we work. Our growth with Emirates, the biggest international airline on earth, shows how our integrated AI strategy with GitLab Duo Enterprise creates a competitive edge. Having weighed Duo against rival offerings, GitHub Copilot among them, Emirates chose to commit fully to GitLab, renewing its investment and moving up to Duo Enterprise. We're likewise gaining momentum with our GitLab Duo with Amazon Q product. Our AWS partnership hit a major milestone during this quarter with HFM, a worldwide retail broker that serves more than 2,500,000 client accounts. HFM began as a GitLab community edition user and wanted to swap out point solutions like Jenkins in favor of GitLab. Meanwhile, they were busy assessing AI code generation tools, among them Amazon Q Developer, Gemini, and GitHub Copilot. Our GitLab Duo with Amazon Q offering became the obvious pick, because it lets HFM take advantage of Amazon Q agents right where its developers already do their work inside GitLab's DevSecOps platform. Now let me turn to three questions I keep getting from investors lately about how AI affects us and what our strategy is. First, people have asked how our growth splits between pricing and seats. I'm happy to report that seats have driven over 70% of our revenue growth. In fact, over the last year we've watched paid seat growth rates accelerate at double digit levels. Every customer cohort since inception keeps expanding with us; we've shared this one time metric so you can grasp the trends we're seeing in the business. The second question concerns how AI will shape seat growth and monetization. Some assume AI will shrink engineering headcount and therefore hurt our seat growth. This quarter, we ran a third party survey covering almost 400 customers to get a clearer picture of how AI affects their GitLab usage. Among those we surveyed, 91% think AI native dev tools will boost their use of GitLab over the coming twenty four months. 88% anticipate their developer headcount will rise or hold steady over the next twelve months, and 78% of those expect it to rise. SeatGrowth is not where GitLab's monetization opportunity stops. Through the Duo agent platform, we let engineers work alongside AI agents and complete many tasks automatically and simultaneously, rather than by hand or one at a time the way they do now; we intend to charge for all that work through usage charges, whether the work comes from our agents or our partners' agents hosted and integrated into our platform. So our business model will shift from purely seat based to a hybrid seat plus usage based model. Once we go live, buyers will get a certain amount of usage bundled into their standard plans, which lets them get started with the Duo Agent platform without friction, then move to pay-as-you-go once that allotment runs out, or lock in extra consumption up front to unlock our most attractive rates. Last, I want to say more about how the competitive landscape looks. Every single month, it feels like another young company or a big new player turns up with AI code generation offerings. Through GitLab Duo Agent Platform, our positioning sets us apart from AI tools that concentrate on code generation. A number of separate studies have pointed to serious problems with the coding assistance available today. During this quarter, several reports came out indicating that code produced by such tools is not consistently of high quality or secure. Beyond that, research indicates that, when it is almost correct, code is not delivering the gains in developer productivity that organizations were counting on. Those mirror the very difficulties human engineers face already, and they sit at the heart of the mission GitLab was founded to pursue. Being an AI native DevSecOps orchestration platform, we gladly embrace both engineers and AI code generation tools.

Bill Staples executive
#4

Our platform enables engineers, along with the AI agents and tools of their choosing, to create, test, protect, and launch enterprise-grade software satisfying the strictest privacy, security, and compliance requirements worldwide. If you operate a business and wish to incorporate AI into your engineering workflow, our view is that GitLab is what you need. That's why, merely a few weeks back, alongside GitLab 18.3, we revealed AgenTic collaborations with Anthropic, OpenAI, Google, Amazon, and Cursor, plus we released native integrations for Cloud Code, Codecs, Amazon Q, Gemini CLI, and open source agents. We additionally introduced our initial model context protocol server, backed by partnership support from Cursor. These strategic alliances, in our view, strongly confirm the worth of our platform. Staying true to our origins, no other vendor offers this degree of interoperability. Weekly active usage of GitLab Duo has grown almost six times thus far this year, though starting from a small base. A quarter of that usage consists of new Duo users utilizing the capabilities bundled into premium and ultimate, unveiled with 18.0. Those users can now access Duo Agent Platform in beta. We remain on schedule to reach GA for Duo Agent Platform before this year ends. That goal is quite bold and ambitious, so I want to establish appropriate expectations. We will release once our quality threshold is met and customers are prepared to pay for the offering. Furthermore, keep in mind that adopting on-premises software such as GitLab may require patience. Roughly 70% of our revenue comes from self-managed deployments, and it frequently takes customers numerous quarters, occasionally years, to upgrade. Our adaptable deployment choices and lively partner ecosystem contribute to what sets GitLab apart. As a public company that isn't controlled by any single cloud hyperscaler, GitLab represents independence. The independence for our customers to develop software in whichever cloud they prefer, with whichever AI providers they select, and using whichever AI code generation tools they choose. That promise is one we alone make. Today, the world requires GitLab more than it ever has. In closing, I'd like to discuss the leadership announcement we made this afternoon. By now, you should all have seen that Brian Robbins is stepping down from his role as chief financial officer to take on a different opportunity. He will remain with us through September 19 to assist in ensuring a smooth transition. On behalf of the whole company, Brian, I want to express our gratitude for all your contributions and wish you the very best. We have begun looking for a successor and are lucky to have a deep pool of talent across our finance organization in the meantime; we anticipate naming James Shen, vice president of finance, as interim CFO, and elevating controller Simon Mundy to chief accounting officer. James joined us in 02/2021 and has been instrumental in shaping our business, strategy, and financial principles. We are confident this transition will be seamless. Honestly, the fresh energy and the new viewpoints that have come in with the people who recently joined have me genuinely enthusiastic — they're going to round out what our current team already brings in terms of experience and strength. When I look at how healthy this business is, where we stand competitively in the market, and how our AI strategy keeps getting stronger, I have real confidence. As each quarter moves along, I'll make sure you hear about our progress. So with that, I'll hand things over to Brian.

Brian Robins executive
#5

Thank you, Bill. This has been an opportunity that changed my life, and it has been a genuine privilege to help drive GitLab's growth and success during this part of my career. I want to express my gratitude to everyone at GitLab and to the board for working alongside me during my time here and for allowing me to be part of this journey. Sid and Bill, I appreciate the backing and confidence you've shown in me as a partner. Together, we established a category-defining leader and designed this company to operate at global scale, with margins improving and free cash flow being generated. Today, the world relies on GitLab more than it ever has. I have faith in what lies ahead for GitLab and I look forward to following our ongoing achievements for many decades. Let's now move on to the results. I'm happy with what we delivered in the second quarter, which brought 29% revenue growth along with substantial year over year expansion in operating margin. This ongoing growth highlights the tremendous value customers gain from our AI native DevSecOps platform. Revenue for the second quarter came in at $236,000,000, which is 29% higher than Q2 of the previous year. We currently serve 10,338 customers whose ARR is at least $5,000, and they accounted for over 95% of total ARR in Q2. Our bigger cohort of customers with $100,000 plus in ARR rose 25% year over year, totaling 1,344; our customer base remains diversified across both industry and geography, and no single customer makes up more than 2% of ARR. When it comes to expansion, we closed the quarter with a dollar based net retention rate, or DBNRR, of a 121%. Q2 DBNRR came from a mix of seat expansion at approximately 80%, higher customer yield at approximately 5%, with the remainder from tier upgrades. I want to restate a few of the onetime disclosures regarding seats that Bill covered. More than 70% of our revenue growth in f y twenty six comes from paid seat growth. And across the last four quarters, we've observed an accelerating double digit rate of paid seat year over year growth. Under 10% of the f y twenty six revenue growth came from the premium price increase. Let me take a moment to talk about how powerful our business model is. Our customer retention metrics keep demonstrating the strength and durability of what our platform offers. We sustain consistently strong net dollar retention rates throughout our customer cohorts. Most importantly, our historical customer cohorts keep expanding, which speaks to the value our platform proposition delivers even in difficult environments. Our 2016 cohort, now nearly a decade old, illustrates this pattern, expanding a 103.6 times in ARR since it began. This ongoing expansion from one of our oldest cohorts shows how powerful our land and expand model is, confirming that our customers keep getting value from our AI native platform well beyond initial deployment. Total RPO increased 32% year over year to $988,200,000, while CRPO increased 31% year over year to $621,600,000; we urge investors to view these figures across a multi quarter period. Non-GAAP gross margin came in at 90% for the quarter. The team keeps doing a solid job driving operating efficiencies, which allows us to hold onto our best-in-class gross margin even while our SaaS business scales up quickly, helped along in part by how strong GitLab Inc. dedicated is. SaaS accounts for roughly 30% of total revenue now and expanded 39% year over year. Yet again, we recorded a meaningful lift in operating leverage. Q2 non-GAAP operating income reached $39.6 million, versus $18.2 million during Q2 of last year. Non-GAAP operating margin landed at 16.8%, up from 10% in Q2 of last year — a gain of roughly 682 basis points year over year; we think our business model is quite strong, giving us room to keep investing while also widening operating margins. Adjusted free cash flow for Q2 FY 2026 totaled $46 million, with adjusted free cash flow margins of 20%, compared with $10.8 million a year earlier. We closed the quarter holding $1.2 billion in cash and investments, which gives us considerable flexibility to ride out market swings while still putting money into our AI capabilities, platform enhancements, and go-to-market organization. On a separate note, I want to share an update about Jihu, our joint venture in China; during Q2 FY 2026, non-GAAP expenses tied to Jihu were $3.3 million, matching the $3.3 million from Q2 of last year. Deconsolidating Jihu stays our objective. That said, we can't forecast the probability or the timing of when that might happen. So for FY 2026 modeling purposes, we're projecting roughly $18 million in expenses connected to Jihu, versus $13 million last year. Now let's move to guidance. For 2026, we anticipate total revenue between $238 million and $239 million, which works out to a growth rate of about 23% year over year; we anticipate non-GAAP operating income between $31 million and $32 million, and we anticipate non-GAAP net income per share between $0.19 and $0.20, assuming 171 million weighted average diluted shares outstanding. For the full year of FY 2026, we anticipate total revenue between $936 million and $942 million, which works out to a growth rate of about 24% year over year. We anticipate non-GAAP operating income between $133 million and $136 million, and we anticipate non-GAAP net income per share between 82¢ and 83¢, assuming 171 million weighted average diluted shares outstanding. We're holding our full year revenue guidance where it stands right now to account for the go-to-market organizational changes we're implementing that Bill discussed earlier; we view these changes as foundational for the company and expect they will set us up for strong future performance. On top of that, we're noticing incremental softness in SMB that we expect will last through the rest of this year. While GitLab continues to gain from consolidation versus point solutions, budget pressures overall are weighing on this segment. In light of that, we've raised our full year profit outlook, reflecting strong operating leverage in the business and a commitment to responsible, sustainable growth. To wrap up, our performance in Q2 leaves me encouraged. As the sole DevSecOps platform that's both cloud agnostic and model neutral, GitLab holds a distinctive place — offering broad contextual AI functionality covering everything from planning all the way to deployment, and able to operate in any setting, air gapped ones included. Our addressable market keeps expanding, and we're directing investment strategically toward areas we believe will generate value over the long term. We're achieving growth that's sustainable while also improving profitability and free cash flow. No matter what the market does, we're setting GitLab up for success over the long haul. With that, I'll hand things over to Cassidy, who will moderate the q and a.

Cassidy Fuller-Patterson operator
#6

Hello everyone. Right now, should you wish to pose a question, kindly utilize the raise hand feature on your Zoom toolbar, or should you have dialed in by telephone, you can hit 9. We ask that you keep it to a single question. Our first question comes from Rob Owens at Piper Sandler. After that, we'll hear from Matt Hedberg at RBC. Rob?

Rob Owens analyst
#7

Wonderful. I appreciate your taking the question. Since I've only got one, I'll bother Brian with a two parter here — congratulations, Brian. Bill, regarding the first part of my question, clearly, ever since you came aboard roughly nine months back, there's been considerable executive turnover. Perhaps you could just help us feel at ease about the direction — what is shifting, and what isn't shifting in your estimation, because when it comes to product development, go to market, and finance, I suppose you now have fresh leaders heading up each of those areas. And then, Brian, for your part, I value the conservatism you've shown concerning the go to market organizational changes and the added softness in SMB. Yet when I compare the first half with the second half, purely from a growth angle, you know, you recorded roughly 28% growth in the first half and merely 21% forecast in the second half. So is there additional conservatism we ought to assume is baked into the second half regarding these factors, or the identical level of conservatism with, I suppose, the actual situation you're observing in SMB? Thanks for fielding those, guys.

Bill Staples executive
#8

Thank you, Rob, for the question. I'll handle the first portion concerning the management changes. I feel genuine gratitude toward the numerous team members who've contributed to making GitLab the company it is today, Brian included. You know, my purpose here is to deliver stability and scale to GitLab. And the mix of new executives we've recruited alongside the seasoned team members already present forms a truly thrilling and vibrant setting that I think will assist us in scaling. The AI cycle AI cycle presents both an enormous opportunity and a risk should we fail to capitalize on it; so as our first billion in revenue comes into site, expanding toward our second billion and beyond is truly our focus. And I'm thrilled about the road ahead.

Brian Robins executive
#9

Absolutely. Thank you, Bill. Rob, I’ll spend just a moment on guidance. Regarding the second quarter, we’re happy with how we executed on the financial results and the metrics overall. Some outperformance came from linearity, so during this quarter we saw the strongest first month of bookings we’ve had in the past 2 years. More than 20% was booked in month 1, and the mix between SaaS and self managed was the reverse of q one. So, as you know, we recognized more of that in the quarter too. As you know, we increased profitability for the year. In Bill’s prepared remarks, he mentioned some of the changes Ian is making in go to market after being here for 1 quarter. So, just to be cautious, as we set the foundation for next year, we kept guidance unchanged for the full year. Mechanically, then, I took a little from q three and the remainder from q four, and that’s how the figure came together that you referred to in your question.

Rob Owens analyst
#10

Thanks.

Cassidy Fuller-Patterson operator
#11

Thank you; our next question comes from Matt Hedberg at RBC. After that, we'll hear from Kash Rangan at Goldman Sachs.

Matt Hedberg analyst
#12

Great. Thanks for taking my question, guys; and Brian, congratulations on all you've accomplished here, and best of luck at Snowflake. A lot of great commentary this quarter. Thanks for the one-time disclosures on seat-based growth. That's great to hear; and obviously, plenty of exciting things around the Duo Agent platform. I think we're all eager to hear about what the consumption element may add to that as we go, understanding it's going to take time to roll into the model. But I guess my question is, there are a lot of go-to-market changes that were announced here and kind of rethinking how to accelerate new customer lands. Guess how long — when should we expect some of those changes to take place and and ultimately drive sort of the positive implications that, Bill, you noted on the call?

Bill Staples executive
#13

Yeah. Great question, Matt. Thank you. Yeah. I'm really excited to have Ian join the team. He hit the ground running. Really happy with how the team handled the transition; it went really smoothly, and we're pleased with what the team did this quarter. Ian's a really thoughtful, strategic, and data-driven leader that's optimizing for both the mid to long term as we look past the billion revenue mark and setting up the organization to be able to scale to multi-billions in revenue while making the best of every quarter. So the changes that he's envisioning and kind of the timelines that we have in mind are really about ramping, kind of three things over H2 as we look to FY27 and beyond. Specifically, first, as I shared, we're focusing on a new ramping a new business division; this is really focused on first-order acquisition and post-sales motion to accelerate value realization and module adoption by enterprise customers that will ramp across H2, and then we hope to see some results early in FY27. Second, he's also evolving our enterprise sales motion with more sophistication. That means increasing our pipeline coverage and improving sales playbooks to account for the AI opportunity and stronger coverage of our entire product portfolio. It was only a few years ago we kind of had two SKUs, premium and ultimate. Now we've got a lot more in the bag and a customer journey to help, our customers navigate, and those are all really needed. Third, he's also looking at sales capacity; now we're good on capacity this year. Everything's in the guidance, but we're starting again to look ahead and make adjustments to help us scale beyond that billion-dollar mark. What that involves is items such as more extensive penetration within mature regions and our existing customer installations, bigger spending in expanding territories, plus additional vertical and specialty focus within how we cover the market. I'd say each of those represents a genuinely significant and strategic shift that we're steering throughout the second half window while we begin scaling up and getting ready for fiscal year 2027.

Brian Robins executive
#14

And, Matt, the sole additional point I'd make regarding that — you're entirely right — is that, you know, we held firm to the guidance for the entire year. Correct? So during Q2, certain one-off occurrences lifted that quarter, producing the beat. Consequently, we intend to implement those adjustments while still hitting the full-year revenue figure we pledged during the prior quarter.

Cassidy Fuller-Patterson operator
#15

Great. Thanks; our next question comes from Kash Rangan of Goldman Sachs; after that, we'll hear from Koji Akita at Bank of America. Cash? Cash, I think your microphone is muted.

Kash Rangan analyst
#16

Hi. Am I coming through fine?

Cassidy Fuller-Patterson analyst
#17

Yes.

Kash Rangan analyst
#18

Correct. That's great, thanks a lot, and I'm sorry for the mix-up — we had 4 earnings calls all running at once. So Brian, it's sad to watch you head off to a different opportunity. Bill, could you expand a bit on the go-to-market transition? Give us some additional detail on precisely what you're aiming to get done? And once the transition period is over, what does success look like in terms of hitting the results you want from a go-to-market standpoint? It's encouraging to see the business picking back up, so congratulations for that. Thanks.

Bill Staples executive
#19

Kash, regarding your earlier question, I already touched on a few of those adjustments, so let me quickly summarize them. First, there's a new business unit concentrating on first order motion and speeding up module adoption so value can be realized. Second, when it comes to our enterprise sales motion, we're boosting pipeline coverage and deploying sales playbooks throughout our product portfolio. Then third, we're pursuing greater sophistication in how we assess sales capacity; for this year, we already have everything required. Yet going forward, how do we develop to achieve deeper coverage in established markets, while also investing in growth markets, plus verticalization and specialization. All of those adjustments, once again, will ramp over the course of H2 as we aim toward FY 2027 and scale past the $1,000,000,000 mark.

Cassidy Fuller-Patterson operator
#20

Great, thanks. Our next question comes from Koji Ikeda at Bank of America, and after that we'll hear from Derrick Wood at TD Cowen. Koji, are you able to hear us?

Koji Ikeda analyst
#21

Yes. Am I coming through fine?

Cassidy Fuller-Patterson analyst
#22

How about now? I can hear you.

Koji Ikeda analyst
#23

My apologies for that. I'd like to ask about SMB. During the prepared remarks, you mentioned that SMB softness might continue through the remainder of the year. Part of me can't help wondering whether cogeneration tools or the other hyped dev tools available might be causing some budget reallocation among SMBs as they search for the tools that deliver the greatest efficiency gains at the moment. So from the SMB perspective, what are you actually observing that's behind that softness comment? How long might that softness last? And aside from macro conditions, what would need to occur for the SMB segment to expand? Perhaps one final SMB question: what share of revenue does SMB represent at present? Thank you.

Brian Robins executive
#24

Yeah. Koji, thanks for asking. I was going to mention its size. It's only approximately 8% of the overall business. So the size itself is fairly small. You know, after the price increase we did, we noted that SMB tends to be somewhat more sensitive to price. We've run several promos and promotions, and we've experimented a bit with pricing and packaging. So it landed lighter than we expected. It's essentially a no touch motion. It arrives via the web store. So we don't have a large team dedicated to pushing it, though we keep experimenting with pricing and packaging and similar things. So we simply wanted to flag it. It's something we saw in earlier quarters; it's a smaller portion of our business, and it's something we continue to monitor.

Koji Ikeda analyst
#25

Thanks.

Cassidy Fuller-Patterson operator
#26

Thanks. Our next question comes from Derrick Wood at TD Cowen, and after that we'll hear from Sanjit Singh of Morgan Stanley. Derek, go ahead.

Derrick Wood analyst
#27

All right. I'm on. Brian, congratulations on what comes next. My question is for Bill; Bill, you brought up that there are plenty of inquiries regarding the competitive landscape, and it was really interesting to learn some of what your survey turned up. One thing we hear often, and I'd love your take, is that some people are concerned these new AI coding vendors will expand from the IDE into additional portions of the life cycle where you all operate. So could you discuss how defensible your platform is, and what's your view on the danger of those vendors eventually going head-to-head with your main product, or the protection you all have?

Bill Staples executive
#28

Correct. Appreciate that, Derek. GitLab genuinely operates differently from tools that write code. Those tools produce code, and as we've mentioned before, that represents roughly 20% of what a developer does, whereas 80% of their effort goes toward handling modifications to that code throughout the software development life cycle so end users' requirements get met. That means we take over right where those code-generating tools stop. And, well, having strong concepts is fairly simple, but carrying them out and actually producing outcomes is the difficult part. Essentially, you can view GitLab as change management for source code, whether it originates from people or from AI-driven tools. Our adoption of such tools forms a core piece of the Duo agent platform approach. In the 18.3 release we shipped last month, for instance, we now have an excellent collaboration in place with Cursor, enabling smooth integration linking Cursor and GitLab, allowing code to move and giving developers a strong experience spanning both GitLab and Cursor. Beyond that, we've incorporated the command-line-interface-oriented code generation utilities that are extremely popular at present — things such as Cloud Code, Gemini CLI, and Amazon Q — and we're integrating them directly into GitLab. So those engineering groups are creating amazing development tools, the AI-driven kind. These now sit inside GitLab. Whether customers pick them or our own agents, it works smoothly inside GitLab, letting them leverage every bit of data and all workflows already present on our platform. So our view is that this is complementary, opening up additional possibilities for us rather than posing a competitive danger.

Derrick Wood analyst
#29

Got it, thanks.

Cassidy Fuller-Patterson operator
#30

Appreciate it. Our next question comes from Sanjit Singh at Morgan Stanley, and after that we'll hear from Brian Essex at JPMorgan.

Sanjit Singh analyst
#31

Thanks for fielding the questions, and congratulations, Brian. It was a pleasure working alongside you, and best wishes in your next position. Bill, I wanted to ask you something about the new logo, new business side of things. When I examine the absolute growth level — how quickly your existing customers are expanding — it's in double digits, which I'd call decent, likely around average or a touch better than average relative to the rest of software. But looking at the trend line across the last several years, I believe we've had a run of double-digit quarters showing year over year deceleration when it comes to customer ads and net new ads. So I'd like your prognosis on why that happened. And going forward, with the new leadership team coming in, what's your sense of the timeline for reversing that?

Bill Staples executive
#32

Yes. That's an excellent question, Sanjit. The reason our top company goal is centered on that initial purchase and bringing in new customers is exactly because of the pattern you pointed to. It's genuinely crucial for us to do this, since when you examine the cohort figures we provided, our twenty sixteen cohort has expanded at 100x. Each quarter, we create fresh cohorts that represent future growth; and, that has been slowing down. I would say the main reason is probably that we haven't given incentives or built a dedicated Salesforce aimed at first order. And we've allowed our reps, to deliver net ARR growth, you know, the the the manner in which, they can achieve that every quarter; and as time has passed, with our revenue base increasing, obviously, that has increasingly arrived via expansion rather than first order. That's the reason I said during the prepared remarks, it's time to even out our investments there and have more specialized sellers concentrated on first order along with a new product led growth strategy for bringing customers in through a self-service experience. Both of those, in terms of timeline, will start ramping now across H2 and we expect to see early returns from that in FY twenty twenty seven.

Sanjit Singh analyst
#33

Thanks for sharing your perspective.

Cassidy Fuller-Patterson analyst
#34

I appreciate it. Brian Essex from JPMorgan will ask the next one, and after that we'll hear from Gray Powell at BTIG. Brian?

Brian Essex analyst
#35

Hello there. Good afternoon, and thanks for letting me ask. Brian, congratulations from my side too. Bill, I'd like to know whether you might build a bit more on what came up in the prior question — specifically regarding Manav being hired, or rather named, as chief product and marketing officer. Did you notice any parallels or similarities involving New Relic in terms of how you expect comparable work to help GitLab alongside the go to market shifts you have planned? I'd really like to hear your view on how these efforts could influence the company's growth path, plus the costs tied to additional investment. Thank you.

Bill Staples executive
#36

All right, so here's the thing — I've spent roughly three decades developing tools and platforms for developers, and this space poses a genuinely distinctive problem, since you're dealing with an engineering community that feels strongly about the tools they choose. On top of that, they lack budget, so you have to run two plays at once: a top-down motion whenever possible, meaning conversations with economic buyers and relationships with the people holding the purse strings who manage those engineers, plus a never-ending push to connect with those engineers through fresh technology and innovation, earning their enthusiasm so they champion your offering internally. That's a shared trait linking New Relic and GitLab, and really, most tools built for developers. That's exactly why, when you look at how explosively new AI offerings such as Cloud Code and Cursor have grown, you witness the fast uptake and revenue expansion a product led growth model delivers, which later fuels greater enterprise adoption. Partly, this accounts for the gap you observe between those modern tools — which mostly embraced product led growth — and GitLab with Duo, which across its earliest years leaned toward a sales led motion involving a sales cycle spanning multiple quarters, a contractual commitment covering a full year, payment required upfront, and platform adoption. At present, each of those acts as a gating factor for our Duo strategy, and as a result, product feedback and iteration slow down. So by shifting toward this blend of product led growth and sales led growth — something Manav and I each bring years of experience to — we're quite confident we can capture the best of both worlds. We'll keep serving the big Fortune 100 accounts we have now through a high touch, sales led motion, while also boosting customer acquisition, adoption, and the pace of innovation thanks to a more direct feedback channel from customers via our product led growth motion.

Brian Essex analyst
#37

That’s really useful context, thanks.

Cassidy Fuller-Patterson operator
#38

Thanks. The next question comes from Gray Powell at BTIG, and after that we’ll hear from Mike Kikos at Needham. Gray?

Gray Powell analyst
#39

All right, great, thanks. I just want to confirm that you’re able to hear me clearly. I’m aware a few other people have run into some problems.

Cassidy Fuller-Patterson analyst
#40

Yes, we can.

Gray Powell analyst
#41

All right, great, thanks. Appreciate you fielding this. OK, I realize you've already heard plenty regarding the adjustments made to how we bring products to market and sell. I'm somewhat unclear on things, so apologies ahead of time. I'm going to pose yet another question. I'm merely attempting to understand the possible upheaval during the back half of the year; and, more precisely, in what way, and how severely, are your representatives seeing their assigned account bundles altered? And also, we're only midway through the year. So, are sales compensation plans being modified for fiscal twenty six? I'm simply attempting to reason through the operational details of how this functions.

Bill Staples executive
#42

Right. There's nothing different when it comes to the compensation plan. Nothing different regarding territories, and the assignments our customers get. What this comes down to is starting to scale up and bring on fresh teams, plus tweaks to enablement and training and the sales venue where they go out and perform each quarter. So I don't anticipate any disruption from them. All of that has been baked in as part of what we've built into guidance covering what's left of the year. And yes, we're eager to get positioned for a more robust fiscal year '27.

Gray Powell analyst
#43

All right. And just so we're clear, does it move to a hunter-farmer model, or — I only want to be certain. Sorry to keep pushing on this, but I really just want to

Bill Staples executive
#44

Right. That language does get used at times—hunters concentrating largely on bringing in new customers, while farmers lean more toward helping customers realize value and grow. You could view it that way, though it won't be an exact, clean split of that sort. Still, the incoming group will absolutely zero in on winning new customers, and that will be their sole priority; meanwhile, the colleagues we already have who handle current accounts are mostly centered on expansion, plus picking up new business when chances arise.

Gray Powell analyst
#45

Got it. All right, thanks a lot.

Cassidy Fuller-Patterson operator
#46

Thanks. Our next question comes from Mike Kikos at Needham. After that, we'll hear from Jonathan Rookhiver at Cantor Fitzgerald. Mike?

Mike Cikos analyst
#47

Hey there. This is Mike Kikos. Appreciate you guys taking the questions. I also neglected to follow up on go-to-market earlier, since it sounds like Sanjit's and Ray's questions are already heading in that direction. But on that go-to-market dynamic, could you help us understand how you're encouraging the right behavior by leveraging comp? My argument would be that GitLab historically chose to let reps pursue bookings or ARR, and that's likely what pushed us to over-index on expansion within the existing customer base while taking on risk around new logos. So how do you plan to leverage comp as a tool for that effort across these new initiatives? Then I have one more question.

Bill Staples executive
#48

Yeah. That's a really good question. Aligned compensation matters a great deal when it comes to producing the right behaviors and motivations. And, well, we've made some light touches to encourage new customer growth this quarter. It's mostly the same comp model we've used for years. And, you know, it works for a company at, I'd say, sub billion in scale and, obviously, since GitLab has benefited from a lot of fast growth. But as we now approach that billion dollar scale milestone and aim to reach the second billion and beyond, greater specialization is simply a natural evolution of the enterprise go-to-market motion. You know, we need to put investment behind new customer acquisition as a dedicated motion while still serving existing customers and driving expansion. We also need to push further specialization when it comes to verticals. We have a strong public sector business. We now have a solid financial services vertical too, and we'll keep building out those businesses as large customer bases with, you know, distinct go-to-market motion. So I'd describe what we're doing as really a pretty natural evolution for enterprise sales, and it's going to help position us for that second billion and beyond.

Mike Cikos analyst
#49

That sounds excellent, and I have one brief additional question. I realize that during the latter half of this year, you are bringing people on board and implementing these programs. Could you please restate how long it normally takes a newly hired person on the go-to-market team to become fully productive, simply so we can model their contribution to next year appropriately? Thanks very much.

Bill Staples executive
#50

Certainly. For an enterprise sales rep, the time needed to ramp up falls somewhere in the range of 6 to 9 months.

Cassidy Fuller-Patterson operator
#51

Great. Thanks. Our next question comes from Jonathan Rockhaver of Cantor Fitzgerald, and after that we'll hear from Romeo Lanschow at Barclays. Jonathan?

Jonathan Ruykhaver analyst
#52

Yes. Thanks. Brian, congratulations, and it was truly wonderful getting acquainted with you and collaborating with you. So, when I look at GitLab 18 and now the Duo agent platform, what really jumps out at me, I think, is simply how widespread AI is growing throughout the platform, and it isn't merely code suggestion and review. It also touches project management and orchestration. To my mind, it genuinely appears as though the value proposition is moving, or could move, away from those code suggestion tools toward, you know, a more platform-centric approach. So I understand it's early days with DuoAgent, but are there any telltale signs suggesting this kind of recognition may be starting to emerge? And you also brought up, I believe I read it somewhere, quarterly updates to the product. Any insight into where that innovation is headed with the Duo Agent platform would be appreciated.

Bill Staples executive
#53

Yeah. Thanks for asking that. It's genuinely thrilling to watch the Duo Agent platform come together. We ship something new each month, and Duo Agent platform arrived in 18.2. Then in the previous month, with 18.3, we added another group of fresh features and capabilities, which includes those partnerships I brought up involving Cursor, Anthropic, OpenAI, and Amazon; and we'll simply keep going month after month, widening both the reach and the caliber of Duo Agent platform. Every month, we also keep talking with customers and collecting what they tell us. And the responses have been overwhelmingly favorable. I get personally involved in conversations with customers nearly every week, both to hear what they think and to ensure they understand where our innovation is headed. And honestly, there are several things getting them enthusiastic. First, our platform strategy positions us perfectly for collaboration built around AI. Through the unified data platform, we deliver abundant context. And when it comes to AI, context reigns supreme. So we supply all of that context and can generate better agentic results while reducing inference expenses. The second item generating real excitement is our open ecosystem strategy. Being able to keep using GitLab while gaining native integrations with top AI dev tools wired straight into GitLab hands them the strongest set of options. They're able not just to run whichever cloud they prefer and work with whichever AI providers they prefer, but they can also reach and leverage the finest AI tools available in the market. And third, another piece of the value proposition from Git of DuoAgent platform that thrills them is that we offer far more than purpose built agents alone. We give them the means to build custom agents along with custom agent flows capable of addressing particular engineering problems they face — problems specific to their own business and their own software processes; and that's genuinely something, once again, that I have not witnessed any competing vendor deliver. Having spent 30 years building software, I can assure you that every engineering team confronts its own collection of problems that no general purpose LLM is able to fix; so by delivering a platform enabling that degree of customization and extensibility, customers will gain a phenomenal, AI based way to tackle their hardest problems. Truly thrilled about the data feedback we've received thus far. Once more, our target is GA by the close of this year, and I can hardly wait to watch what customers accomplish with it.

Jonathan Ruykhaver analyst
#54

Yep. That's useful. Thank you, Bill.

Cassidy Fuller-Patterson analyst
#55

Thanks. The final question today comes from Ramio Lenschow of Barclays.

Damian Cogen analyst
#56

Hey, everyone. This is Damon Coggin filling in for Raimo. Appreciate you taking the question, and congratulations on the new position, Brian. I noticed the subscription SaaS business accelerated to 39% in 2Q. Could you walk us through what's driving that result? Is it coming from the newer AI coding tools, or perhaps from how the GitLab sales team is executing? And then, if I may fit in one more. Did the quarter include any onetime items we ought to keep in mind? Also, should the implied April growth rate be treated as a proxy for growth in the coming year? Thanks, everyone.

Brian Robins executive
#57

This is Brian. Thank you. I'll, yeah. That's three questions rolled into one, so I'll take part a and c; and regarding the implied growth rate for April, we discussed how it stems from the go to market changes that are gonna position us for success in f y twenty seven and beyond. We kept full year revenue guidance unchanged, so we took a beat in '2 q and distributed it across three q and four q. So hopefully that gives you some insight into how the guidance was assembled. What was there was a I should've I didn't realize you were gonna answer three questions. There was

Damian Cogen analyst
#58

Are there any one-time items for Q2?

Brian Robins executive
#59

Yes. In Q2, two factors had an effect on the quarter. First was linearity. Our month one bookings were the strongest in 2 years, with over 20% of the quarter booked in month one. Normally, you know, month three tends to carry more weight. Also, our mix had more SaaS than self managed; it went back to historical norms. Actually, I have that backwards, self managed versus SaaS; with self managed, some revenue gets recognized upfront, so those are one time in the quarter. Then you asked whether we're doing anything differently on SaaS to push SaaS over self manage? How a customer buys the product makes no difference to us. We want to meet the customer wherever they want us to meet them. SaaS makes it so much easier for them to get up and running and gives them a lower total cost of ownership. So we see SaaS and dedicated. On dedicated, growth was 92% year over year. Both of them, you know, are a great motivation for customers, in our view. They don't have to have the infrastructure. They can get up running faster; they can realize their ROI quicker and so forth.

Damian Cogen analyst
#60

Thanks, everybody.

Cassidy Fuller-Patterson analyst
#61

Thank you. That brings our question-and-answer portion to a close. At this point I'd like to hand things over to Bill for some closing thoughts. Bill?

Bill Staples executive
#62

Thank you. As we bring today's session to an end, there are really 3 points I hope you'll carry away from this call, things I'm truly enthusiastic about. To begin with, the opportunity in front of us is massive and keeps expanding. Our financials are solid and show a powerful mix of free cash flow margin alongside revenue growth. Seats are expanding; within the dual agent platform, we're introducing an additional growth driver on top of seat growth by monetizing autonomous work performed. Next, we hold a genuinely distinctive value proposition through our unified dev sec ops platform, which becomes even stronger thanks to AI. Context is king, and that full life cycle context is exactly what our unified platform delivers. As the sole pure play cloud and model neutral independent public company providing DevSecOps, we bring the world independence. Build your software in whichever cloud you prefer, using whichever AI vendors and tools you prefer, and secure the very best experience for your engineers; and last of all, we're assembling a tremendous team, blending new executives with seasoned team members, all eager to push past the first billion in revenue and scale toward our second and beyond. Thanks for being on the call today. I can't wait to see all of you in follow-up conversations across the quarter.

Read the full transcript via the API

You're viewing the first half of this call. Get the complete GitLab Inc. transcript - plus 131,000+ transcripts from 7,000+ companies, speaker segments and full-text search - through the EarningsAPI REST API or hosted MCP server.

Get an API key View API docs →

For developers and AI pipelines

Programmatic access to GitLab Inc. earnings transcripts and 131,000+ others is available through the EarningsAPI REST API and the hosted MCP server. Quarterly plans from $162 - full transcripts, speaker segments, full-text search, and the /api/v1/transcripts/recent polling endpoint for ETL pipelines.