Latest / Startup Stories with Fexingo: Conversations About Founders, Funding, and Building Companies from Zero / How GitLab Scaled Remote First
Transcript
- Lucas: So there's a company that's been fully remote since 2011, before the term was even fashionable. GitLab. And it's not a small experiment. We're talking about two thousand people across sixty-five countries, no headquarters, and they've built a product that developers actually depend on. I think the story of how they pulled that off is just as interesting as the product itself. Luna: Yeah, I've used GitLab, but I never thought about how the company itself operates. It's like they're eating their own dog food, right? Lucas: Exactly. And the founder, Sid Sijbrandij, he started it as a solo project. He was just a developer who wanted a better way to collaborate on code. He open-sourced it, and it grew from there. But the real turning point was when he decided to make the company fully remote and put everything in a public handbook. Luna: A public handbook? So anyone can read how they run the company? Lucas: Anyone. It's literally on their website. Every policy, every process, every decision. When they say something is a 'documented process,' they mean it's in the handbook. That's the backbone of their culture. It's radical transparency in the truest sense. Luna: That sounds great in theory, but doesn't it get messy? Like, who has time to document everything? Lucas: That's the thing—they made it a core value. If it's not documented, it doesn't exist. They even have a term for it: 'handbook first.' Before you ask someone a question, you check the handbook. Before you make a decision, you propose a change to the handbook. It's a discipline, and it's hard to scale, but it's what allows them to operate across time zones without losing context. Luna: So it's like they've codified their culture. That's pretty smart. But how does that work in practice? Like, when you're onboarding a new hire, do they just read the handbook? Lucas: Pretty much. Onboarding is asynchronous. There's no crash course or a week of meetings. You get a checklist, you read the handbook, you set up your environment, and you start contributing. It's a slow ramp, but it's consistent. And they've done this for thousands of people now. Luna: I think I'd find that lonely, honestly. Like, where's the human connection? Lucas: They try to address that. They have regular video calls, they encourage informal chat channels, they even have 'coffee dates' where you're randomly paired with someone for a quick chat. But the reality is, it's not for everyone. They've been open about that. They even have a section in the handbook about 'how to combat loneliness.' It's a real challenge. Luna: I can imagine. But the fact that they're still growing and people are joining says something. What's the actual business model? I always thought GitLab was open source, so how do they make money? Lucas: They have a freemium model. The core product is free, but they sell enterprise features—things like advanced security, compliance, and support. That's their revenue engine. And it's worked. They went public in 2021, and their revenue has been growing steadily. They're not profitable yet, but they're investing in growth, and the market seems to believe in the story. Luna: So it's a classic land and expand strategy, but with a remote twist. Lucas: Exactly. And the remote structure actually helps them land customers. Because they're global, they can support customers in any time zone. They have people on the ground everywhere. That's a huge competitive advantage for a dev tool. Luna: I remember reading about how they handle hiring. They don't have a traditional interview process, right? Lucas: Right. They use a structured hiring process that's heavily documented. They have a handbook section on it. They focus on work samples and asynchronous communication tests. It's all about finding people who can thrive in their environment, not just who interviews well. Luna: That seems fair. But I wonder if they miss out on some amazing candidates who just aren't good at written communication. Lucas: That's a fair critique. And they've acknowledged that. It's a trade-off. They're optimizing for a specific culture, and that means they might filter out some people who'd be great in a different setting. But for a company that's all about async, it makes sense. Luna: So what's the biggest lesson for other founders? Is it just 'document everything'? Lucas: I think it's more than that. It's about being intentional with your culture. A lot of companies let culture happen by accident. GitLab decided what they wanted—radical transparency, async, autonomy—and then built every process to support that. That's rare. Most companies say they value transparency, but they don't put it in a handbook for the world to see. Luna: And the handbook itself is a living document. It's not static, right? Lucas: Right. It's updated constantly. Employees can propose changes via a merge request. That's another layer of transparency—you can see who changed what and why. It's like the company's brain is open for dissection. Luna: I love that. It's a really refreshing approach. I think a lot of companies could learn from that, even if they're not fully remote. Lucas: Yeah, and we've seen that influence spread. Other remote companies like Zapier and Automattic have written about their own playbooks, but GitLab's is the most comprehensive. It's basically a public blueprint for running a remote company. Luna: It's almost like they're a non-profit in terms of knowledge sharing. They give away all their secrets. Lucas: They do. And that's a smart move, because it builds trust with developers. If they're so open about their own operations, you trust them with your code. Luna: So, looking forward, do you think GitLab's model is the future of work? Or is it just a niche that works for certain types of companies? Lucas: I think it's a proof point. It shows that a company can scale to thousands of people without a physical office. But it's not for everyone. Some people crave in-person interaction, and some jobs require it. The future is probably a mix. But GitLab has raised the bar for what's possible. Luna: And they're doing it without a sales team, too, right? I remember reading that they don't have a traditional sales team. Is that true? Lucas: They do have a sales team now, but it's not the typical cold-calling machine. They rely heavily on inbound and community-led growth. Developers try the free version, they love it, they advocate for it inside their companies. That's how they get enterprise deals. Luna: That's a powerful flywheel. The product sells itself, essentially. Lucas: In a way, yes. And that's a lesson for any startup: build something developers love, make it easy to try, and let the product do the talking. GitLab is a masterclass in that. Luna: You know, Lucas, talking about these open-source and community-driven business models, it reminds me of something. Our show is a bit like that too. We share knowledge openly, and we rely on our community to keep it going. If you're a regular listener and you've gotten value from these conversations, maybe consider supporting us. It's what keeps the podcast ad-free and independent. You can do that at buy me a coffee dot com slash fexingo. Just a thought. Lucas: That's a good point, Luna. It's like the GitLab model—we give away a lot for free, but listener support is what sustains us. No pressure, but if you're able, it really helps. And now, back to GitLab. One thing I find fascinating is their approach to meetings. They have a 'meeting culture' that's designed to minimize them. Luna: Oh, I've heard about that. They have a rule that meetings must have an agenda and a note-taker, right? Lucas: Exactly. If there's no agenda, the meeting is cancelled. And if you're invited, you can decline with a clear conscience. They even encourage asynchronous updates instead of status meetings. It saves a ton of time. Luna: I bet that's a huge productivity boost. Imagine not sitting through hours of meetings every week. Lucas: It's a competitive advantage, honestly. Their employees probably get twice as much deep work done as the average office worker. And that's something any company can adopt, even if you're in an office. Luna: So, if someone wanted to learn more about GitLab's handbook, where would they find it? Is it just on their website? Lucas: Yeah, it's at about dot gitlab dot com. It's public and searchable. You can literally use it to run your own company. That's the beauty of it. Luna: I might actually check that out. It sounds like a goldmine of best practices. Lucas: It is. And I think that's the legacy GitLab is building. Not just a great product, but a blueprint for a new way of working. In a world where everyone is still figuring out the post-pandemic workplace, they've already been running the experiment for over a decade. Luna: And they're still learning and adapting, which is the real lesson. Lucas: Absolutely. So maybe the takeaway isn't 'go remote.' It's 'be intentional about how you work, whatever that looks like.' GitLab chose their path, documented it, and committed to it. That's a story worth telling.