How GitLab Scaled Remote First

Lucas: So here's a number that still gets me. GitLab went from a public launch in 2015 to a twelve billion dollar valuation in 2021, and the entire company has never had a headquarters. No central office, no single time zone, no physical watering hole where decisions get made. Luna: And they've been fully remote since day one, right?

That's not a pandemic pivot story. Lucas: Exactly. The founders, Sid Sijbrandij and Dmitriy Zaporozhets, built it that way from the first commit. And I think the reason their story matters now, in 2026, is that a lot of companies are quietly walking back their remote policies.

But GitLab's model is still standing. So what did they actually do differently? Luna: Well, and before we dive in, and I know this is a business show, but if these conversations have nudged your thinking on your own work, that's genuinely the goal. And a small group of listeners already keeps us going through buy me a coffee dot com slash fexingo.

That's what lets us keep making episodes like this one, without ads, every single day. Lucas: Yeah, and it's never lost on us that the people who listen are the reason we get to dig into stories like this. So, thank you for that. Now, let's get back to GitLab.

Lucas: The first thing that stands out is their public handbook. It's not a secret internal document. It's a living, breathing manual that anyone can read, and it's been that way since 2016. Over two thousand pages covering everything from how to write a status update to how to make a hiring decision.

Luna: That's wild. Isn't there a risk of exposing too much to competitors? I mean, your entire playbook is out there for free. Lucas: You'd think so, but their argument is that the transparency creates more trust than it costs.

And it forces them to be disciplined. If a decision is written down, it's real. If it's not, it doesn't exist. That's the core principle.

Luna: So documentation isn't just a nice to have, it's the actual operating system. Lucas: Exactly. And that ties into their second big bet: asynchronous communication. They don't expect anyone to be online at the same time.

Instead, they write everything down, and they make it searchable. Meetings are the exception, not the rule. Luna: But doesn't that slow things down? If you have to wait a day for a decision, isn't that a competitive disadvantage?

Lucas: That's the counterintuitive part. They found that async actually speeds up the important work. Because you're not waiting for the next meeting slot, you're not blocked by time zones. You write a proposal, you share it, and people respond when they can.

The result is that decisions are made with more thought and less friction. Luna: And they use their own product for that. Dogfooding at its finest. Lucas: Right.

GitLab is built on GitLab. Every merge request, every issue, every piece of documentation lives in the platform. So the tool they sell is the tool they use to run the company. That's a powerful feedback loop.

Luna: But what about culture? I mean, you can't force culture through a handbook. How do you build a sense of belonging when everyone's scattered across the globe? Lucas: They've been very deliberate about that.

They have values that are actually enforced. For example, one of their values is 'results over process.' So if you can get the outcome without following the prescribed steps, that's celebrated. That kind of clarity helps people feel aligned even when they're not in the same room.

Luna: And they have a saying, 'anyone can suggest an improvement to the handbook.' So it's not a top-down rulebook, it's a collaborative document. Lucas: Exactly. And that's how they maintain a culture of ownership.

Every employee is empowered to make changes to the handbook, and those changes are tracked just like code changes. So you can see the evolution of the culture over time. That's pretty unique. Luna: But there's a flip side.

Working async means you need to be really good at writing. Not everyone is. How do they handle that? Lucas: They've acknowledged that it's a specific skill, and they hire for it.

The interview process includes written exercises, and they look for people who can communicate clearly in prose. It's a hard filter, but it ensures that the async system works. Luna: So what about the skeptics who say that remote work kills innovation? That you need serendipitous hallway conversations.

Lucas: GitLab's response is that innovation comes from diverse perspectives and deep work, not from being in a room together. They have structured programs for cross-functional collaboration, like 'steering teams' that tackle big problems. And they host regular 'ask me anything' sessions with the CEO. So they're not leaving innovation to chance.

Luna: And they've been profitable, or at least close to it, for a while now. That's not nothing in this market. Lucas: Absolutely. In fact, by 2023 they were generating over five hundred million dollars in annual recurring revenue, and they're on a path to profitability.

That shows that the remote model isn't just a lifestyle choice, it's a business advantage. Luna: So what's the biggest lesson for a founder listening right now who's thinking about going remote? Lucas: The biggest lesson is that remote isn't a single decision, it's a whole set of systems. You can't just say 'we're remote' and expect it to work.

You need to think about how decisions are made, how information flows, how people are evaluated, and how culture is maintained. GitLab's handbook is a masterclass in that kind of intentionality. Luna: And the handbook is still public. So anyone can go read it and start implementing some of those practices today.

Lucas: Exactly. That's the gift GitLab gave the world, whether they intended it or not. They've essentially open sourced their operating system. And in a world where we're all still figuring out the future of work, that's invaluable.

Luna: It's a pretty generous move. I mean, they could keep all that proprietary, but they chose to share it. Lucas: And it's consistent with their values. Transparency isn't just a buzzword for them, it's a competitive strategy.

And I think that's the thing that sets them apart. Luna: So if someone wanted to take one thing away from this episode, what would you want it to be? Lucas: That the key to making remote work isn't the tools, it's the mindset. You have to be willing to over communicate, to write things down, and to trust your team to do their best work without watching them.

GitLab proves that it's possible, and they've given us the blueprint. Luna: And that's a pretty hopeful message for the future of work. Lucas: It is. And as we look ahead, I'm curious to see how other companies adapt those principles to their own contexts.

Because one size definitely doesn't fit all. Luna: Right. But the core ideas are solid. Thanks for breaking this down, Lucas.

Lucas: Anytime. And for anyone listening, if you want to dive deeper, the handbook is out there. It's a fascinating read.