GitLab (GTLB) Q1 FY27 earnings call: guidance and Q&A

How is GitLab performing competitively against GitHub, particularly with recent innovation, and are win rates and pricing holding up?

GitLab sees a strong opportunity, especially with enterprise customers. While migration is slow, Q1 saw a notable increase in enterprises adopting GitLab, leading to a small but meaningful improvement in win rates and 30% higher new logo growth. GitLab is also partnering with an AI lab to rebuild Git infrastructure for 100x scale, anticipating future agentic engineering needs.

“In Q1, we saw a notable increase in enterprises looking to adopt GitLab as their platform, including new first orders as well as consolidation within our existing base. That did result in a small but meaningful improvement year-over-year against historical win rates.”

asked by Matthew Hedberg · answered by William Staples

Given expected benefits from sales capacity in H2, but also macro headwinds and potential disruption from Act 2, what is the increased conservatism embedded in the guidance?

Guidance reflects prudence on four key items: no meaningful macro bounce-back, continued pressure on the price-sensitive cohort (20% of ARR), no material revenue contribution from DAP in FY27 (focus on adoption), and potential near-term disruption from Act 2 organizational changes, despite efforts to protect sales and engineering.

“So I'd say the 4 things, again, so 2 carries over from last quarter. We don't -- still while we saw some strong performance in PubSec this quarter. We still don't expect an immediate bounce back. while we're very, very pleased with the results that we're seeing on DAP so far, we're not expecting material revenue there. And then the additional new pieces are the RIFs and the execution risk.”

asked by Oscar Saavedra · answered by Jessica Ross

How does GitLab plan to monetize the emerging cohort of non-technical users (product managers, designers, security teams) using the platform, and do current SKUs meet their needs?

GitLab is seeing a notable increase in requests for additional seats for non-engineering users who contribute code using agentic tools. The company plans to use its existing seat-based pricing model for these users, as their value and requirements for agentic engineering across the software lifecycle are similar to engineers.

“We currently are in several conversations along those lines, and we're putting forward the same seat-based pricing model that we provide for engineers, given the value and the requirements are the same.”

asked by Radi Sultan · answered by William Staples

Why did an AI lab choose to partner with GitLab on rebuilding Git infrastructure for scale, rather than competing or doing it in-house?

GitLab is a leading contributor to open-source Git and serves several AI labs as a customer. Its position as a serious DevSecOps vendor for over half of the Fortune 100, with hundreds of thousands of organizations using GitLab, makes it an attractive partner for AI labs seeking to deliver a great experience to their customers through GitLab.

“Number one, we are, I believe, the leading contributor to the open source Git community today. And we also serve several of the AI labs with GitLab.”

asked by Ethan Drake Weeks · answered by William Staples

Can management elaborate on seat compression trends and how new monetization models will offset this?

Seats are actually growing this quarter, despite some churn/contraction from layoffs and M&A. The new GitLab Credits consumption program is helping capture new AI budgets and delivered the highest net ARR quarter for AI ever, outperforming previous Duo offerings. This new monetization is additive and provides flexibility.

“Actually, we've seen seats growing this quarter. Obviously, with the growth that we delivered, we did see seats growing. That's our primary monetization model today.”

asked by Cole Erskine · answered by William Staples

Where specifically will restructuring savings be reinvested to drive the architectural strategy, and how will ROI be measured?

Savings will be reinvested in three areas: people (investing in retaining talent for Act 2), technology (accelerating architectural bets and R&D resources), and process (reviewing processes for AI leverage and speed). ROI measurement is too early for details, but the company will be intentional with clear guardrails and trade-offs, believing the market opportunity is too significant to miss.

“So we're really looking at it in 3 places: people, technology and process.”

asked by Matthew Calitri · answered by Jessica Ross

How does GitLab feel about attrition and retaining 10x engineers after the restructuring, and what gives confidence in avoiding customer disruption?

The restructuring was carefully planned, starting with the 'why' and 'what' before the 'how,' including a voluntary departure program to align team members with the new direction. Sales capacity was protected, and R&D investment is planned to grow. Customer disruption is expected to be very limited, with no sales presence in exited geographies and deliberate communication plans for affected customers.

“We were very careful in protecting our sales capacity to ensure that we can continue to deliver on the targets that we've set for this year. And as we shared, we're also investing in team members and in particular, in R&D, we actually expect to grow our ability in that in the coming quarters.”

asked by William Kingsley Crane · answered by William Staples

Clarify the discrepancy between strong gross bookings and lower sequential RPO growth.

Gross bookings (guidelines) grew 12% this quarter against a tough prior-year comp, impacted by seat contraction from layoffs and M&A. RPO growth is affected by market uncertainty leading to customer hesitancy for longer-term contracts, though GitLab offers flexibility. The company is incentivizing multi-year contracts but also evolving monetization with Flex. Overall retention remains above 90%.

“Yes, first on guidelines, there's -- those were at 12% growth this quarter, which was coming off a really tough comp. We had 35% growth in Q1 of FY '26.”

asked by Nicholas Altmann · answered by Jessica Ross

Is the decline in deal duration purely macro-driven, or also influenced by pricing changes and consumption model concerns?

Multi-year contract hesitancy is driven by market uncertainty, rapid changes in software engineering, and AI spend shifts, leading customers to prefer shorter agreements. GitLab offers flexibility for both multi-year and single-year agreements. The changing unit economics for developers and the upcoming Flex program are also factors, allowing customers to manage spend thoughtfully.

“The first is, especially in our category around software coding, there is a lot of uncertainty as the software engineering life cycle changes as new tools emerge as increasing spend shifts to AI and customers see all of those options and especially in budget, in situations where budget is tight. They're choosing to make shorter agreements because the space is changing so fast.”

asked by Lucky Schreiner · answered by William Staples