The All-Remote Startup Guide: How GitLab Built a $10B+ Company With Zero Offices (2025)
Remote Isn't a Perk — It's an Operating Model
When GitLab went public in 2021 at a $14.9 billion valuation, they did it without a single office. No headquarters. No regional hubs. No WeWork memberships. Just 1,500+ people in 65+ countries, working from wherever they wanted.
That wasn't an accident. It was a deliberate operating model — one that GitLab calls "all-remote" to distinguish it from companies that merely tolerate remote work. Their framework has been studied by Harvard Business School, published in the Journal of Organizational Design, and adopted by thousands of startups worldwide.
This guide distills GitLab's all-remote handbook — one of the most comprehensive public documents on remote work ever created — into an actionable framework for founders building remote-first companies.
GitLab's Remote Numbers
The Remote Manifesto: 9 Principles
GitLab's remote manifesto isn't a list of perks — it's a set of operating principles that fundamentally change how work gets done. Each principle represents a deliberate choice that favors distributed teams over colocated ones.
Hiring from all over the world over a central location
Your talent pool isn't limited to people within commuting distance. You're competing for the best people globally — and offering them the ability to stay where they are.
Flexible working hours over set working hours
When you have team members across 65+ countries, "9 to 5" doesn't exist. Instead, you empower people to work when they're most productive — whether that's 6am or 10pm.
Writing down and recording knowledge over verbal explanations
If it's not written down, it didn't happen. This is the single most important principle for remote teams. Verbal knowledge is trapped in time zones and fading memories.
Written processes over on-the-job training
On-the-job training requires someone physically present. Written processes can onboard a new hire in Tokyo while the author sleeps in Toronto.
Public sharing of information over need-to-know access
Default to open. GitLab's entire handbook is public — 2,000+ pages anyone can read. Internally, information is shared unless there's a specific reason not to.
Opening documents for editing by anyone over top-down control
Anyone can propose a change to any document — including this handbook. It's a wiki, not a decree. This creates collective ownership and catches errors faster.
Asynchronous communication over synchronous communication
Meetings should be the last resort, not the first instinct. Async communication — written updates, recorded videos, documented decisions — respects everyone's time zone and focus time.
Results of impact over activity put in
Nobody cares how many hours you logged. The only metric that matters is: did you move the needle? This eliminates presenteeism and rewards efficiency.
Formal communication channels over informal communication channels
Hallway conversations and watercooler chats are invisible to remote team members. All meaningful communication should happen in searchable, shared channels where anyone can find it.
All-Remote vs. Remote-Friendly: Why the Distinction Matters
One of GitLab's most important contributions to the remote work conversation is the distinction between all-remote and remote-friendly. These are fundamentally different operating models, and confusing them causes most remote work failures.
🏢 Remote-Friendly (Avoid)
- HQ is the center of gravity. Decisions happen in offices. Remote people are "dialing in."
- Two-class system. Office workers get facetime with leadership. Remote workers feel like second-class citizens.
- Meetings assume colocation. Whiteboards, hallway follow-ups, and in-person brainstorms exclude remote participants.
- Information flows through proximity. You learn things by being in the right room at the right time.
- Culture favors presence. Promotions, raises, and interesting projects go to people who are "visible."
🌍 All-Remote (GitLab Model)
- No center of gravity. Every team member operates with equal access, regardless of location.
- One class. Even the CEO works from home. No one has an unfair advantage from physical proximity.
- Meetings are digital-first. Everything is designed for a screen. Documentation captures all decisions.
- Information flows through documentation. If it's not in the handbook, it doesn't exist.
- Culture favors output. Impact is measured by results, not hours in a chair or face time with the boss.
💡 The Hybrid Trap
Most companies that say "we're hybrid" are actually remote-friendly with a strong colocation bias. GitLab's position is clear: hybrid is the worst of both worlds. It creates a two-tier system where remote employees are structurally disadvantaged. If you're going to do remote, go all-in — or don't do it at all.
The Documentation-First Culture
If there's one principle that makes everything else work, it's this: write everything down. GitLab's handbook is over 2,000 pages — and it's all public. Every process, every policy, every decision framework is documented.
This isn't bureaucracy. It's the opposite. Documentation eliminates the need for meetings where someone explains something that could have been a page. It removes the bottleneck of "ask Sarah, she knows how this works." It makes onboarding fast because new hires can read rather than shadow someone for two weeks.
📝 What to Document (Start Here)
Day 1 (Even as a Solo Founder)
By Employee #10
Async Communication: The Remote Superpower
Most companies treat communication as synchronous by default — Slack messages expecting immediate replies, meetings for every decision, "quick calls" that eat up everyone's day. GitLab inverts this: asynchronous is the default, synchronous is the exception.
🔄 The Async Decision Framework
Before scheduling a meeting, ask: "Can this be resolved asynchronously?" If the answer is yes — and it usually is — use one of these instead:
For decisions:
Write a proposal in a shared document. Tag stakeholders. Set a deadline for feedback (e.g., "If no objections by Friday, we proceed"). This eliminates 80% of meetings.
For updates:
Record a 5-minute Loom video. It's faster than writing and more personal than a doc. The viewer can watch at 2x speed or skip sections that aren't relevant.
For brainstorming:
Create a shared document with the prompt. Give people 48 hours to add ideas independently. Then schedule a 30-minute call to discuss the top ideas — not generate them.
For feedback:
Use threaded comments in documents or PRs. Everyone can review on their own schedule. The feedback is automatically documented and searchable.
⏰ When Synchronous IS the Right Call
Not everything should be async. Use real-time communication for:
The Non-Linear Workday
One of GitLab's most radical ideas: the non-linear workday. Instead of working 9-5, team members might work 7-11am, take a 3-hour break for exercise and family time, then work 2-6pm. Or they might do their best creative work at midnight.
This isn't about working less — it's about working when you're at your best. The result is higher productivity, better mental health, and team members who don't have to choose between their career and their life.
📅 Non-Linear Workday Examples
Works 8am-12pm (deep coding), 3pm-6pm (reviews and meetings with US east coast). Mid-day break for lunch with family and a gym session.
Works 10am-2pm (design work), 8pm-11pm (async reviews with Europe/US). Afternoon free for personal projects and childcare.
Works 7am-11am (overlap with Europe), 1pm-5pm (overlap with US west coast). Lunch break for exercise and errands.
The key: What matters is not when you work, but that your team knows your working hours and that async handoffs are clean.
The GitLab Test: 12 Questions for Remote Readiness
Inspired by "The Joel Test" for software teams, GitLab created a 12-question test to evaluate whether your remote setup is actually working. Score yourself honestly — each "yes" is worth 1 point.
📊 The GitLab Test
Score: 10-12 = Remote-mature. 7-9 = Getting there. 4-6 = Remote-friendly at best. 0-3 = You have offices with Zoom links.
Remote Management: What Changes
Managing a remote team requires different muscles than managing a colocated one. GitLab's framework for great remote managers centers on three shifts:
Shift 1: From Presence to Output
You can't see who's at their desk. And that's fine — because seeing someone at their desk never told you they were doing great work anyway. Measure output: features shipped, problems solved, customers helped, revenue generated.
Practical tip: Replace "Are you working?" with weekly async updates where each team member shares: what they accomplished, what they're working on, and what's blocking them.
Shift 2: From Synchronous to Async-First
Every meeting you schedule is a tax on everyone's time. Before booking a meeting, try writing a document. If the document generates enough discussion, maybe then it's worth a 30-minute call to resolve the remaining questions.
Practical tip: Cancel all recurring meetings for one week. See which ones people actually miss. The ones nobody requests back? They were wasted time.
Shift 3: From Implicit to Explicit
In an office, culture spreads through osmosis — new hires absorb norms by watching others. Remote teams don't have that luxury. Everything must be explicit: values, expectations, feedback, career paths, communication norms.
Practical tip: Write a "Manager README" — a short document that tells your team how you work, how you give feedback, your communication preferences, and what matters most to you.
Combating the Remote Risks: Burnout, Isolation, and Anxiety
GitLab is transparent about the downsides of remote work. Without deliberate effort, remote teams face real risks:
🔥 Burnout
When your office is your home, it's hard to "leave work." The commute used to be a transition ritual — now there's nothing separating work from rest.
GitLab's fix: Explicitly encourage end-of-day routines. Close the laptop. Go for a walk. Change your clothes. Create a physical and psychological transition.
🏝️ Isolation
Humans are social animals. Without daily in-person interaction, loneliness creeps in — especially for people who live alone or are new to a city.
GitLab's fix: Budget for coworking spaces. Schedule optional social calls. Create Slack channels for non-work interests (pets, cooking, gaming). Fund team get-togethers 1-2x per year.
😰 Anxiety
Without visible cues, remote workers often worry: "Am I doing enough? Does my manager think I'm slacking? Am I going to get fired?"
GitLab's fix: Over-communicate expectations. Regular 1-on-1s with clear feedback. Public recognition of good work. Make it psychologically safe to say "I'm struggling."
The Remote Startup Toolkit
You don't need 20 tools to run a remote startup. You need a few that you use incredibly well. Here's the essential stack:
Communication
Documentation
Hiring Remotely: What's Different
Remote hiring opens up the entire world as your talent pool. It also introduces challenges that office-based hiring doesn't have. GitLab's approach:
Test for async communication skills
The best remote workers are strong writers. They can explain complex ideas in writing, give clear async feedback, and document their work without being asked. Include a written exercise in your interview process.
Evaluate self-management ability
Remote work requires discipline. Ask candidates about how they structure their day, handle distractions, and maintain focus. Look for evidence of self-directed projects or freelance work.
Consider time zone overlap
You don't need everyone in the same time zone, but you do need enough overlap for meaningful collaboration. GitLab recommends at least 3-4 hours of overlap between team members who work closely together.
Invest in onboarding heavily
Remote onboarding is harder than in-person. GitLab assigns every new hire an "onboarding buddy" — someone who's not their manager and exists purely to answer questions and provide social connection during the first 90 days.
The Financial Case for All-Remote
Beyond the culture and talent advantages, all-remote makes financial sense — especially for startups that need to stretch every dollar of runway.
💰 Cost Savings (Real Numbers)
$11,000
Average annual savings per remote employee (Global Workplace Analytics)
$0
Office lease, furniture, utilities, snacks, cleaning, security
2-3x
Wider talent pool at competitive (not SF/NYC) salaries
25%
Lower turnover rate for remote employees (Owl Labs)
The Bottom Line
GitLab proved that you can build a $10B+ company with zero offices, 1,500+ employees, and 65+ countries. Their framework isn't theory — it's a battle-tested operating manual refined over a decade.
The core lesson is simple: all-remote isn't about where people sit — it's about how information flows. If information flows through documentation, async communication, and transparent processes, location becomes irrelevant. If information flows through hallway conversations and meetings, you'll always be at a disadvantage outside the office.
As GitLab puts it: "Remote is not a challenge to overcome. It's a clear business advantage."
🚀 Building a Remote Team? Find Investors Who Get It
Not every investor understands remote-first companies. Find VCs and angels who've backed distributed teams and understand async culture. Search 100K+ verified investor profiles on Datapile.
Search Investors →Tagged with
Investor Outreach Template Pack
Get our proven email templates, pitch frameworks, and investor research guides — used by 1,000+ founders.
- Cold email templates that get 40%+ open rates
- Follow-up sequence frameworks
- Investor research checklist
