GitLab Strategy

"Strategy is a commodity, execution is an art." — Peter Drucker


GitLab was created because Dmitriy needed an affordable tool to collaborate with his team. He wanted something efficient and enjoyable so he could focus on his work, not the tools. He worked on it from home, a house in Ukraine without running water.

We think that it is logical that our collaboration tools are a collaborative work themselves. More than 1000 people have contributed to GitLab to make that a reality. We believe in a world where everyone can contribute. Allowing everyone to make a proposal is the core of what a DVCS (Distributed Version Control System) such as Git enables. No invite needed: if you can see it, you can contribute.

In summary, our vision is as follows:

We believe that all digital products should be open to contributions, from legal documents to movie scripts and from websites to chip designs. GitLab Inc. develops great open source software to enable people to collaborate in this way. GitLab is integrated and opinionated collaboration software that everyone should be able to afford and adapt. With GitLab, everyone can contribute.


Change all creative work from read-only to read-write so that everyone can contribute.


Everyone can contribute to digital products with GitLab, to GitLab itself, and to our organization.

  1. To ensure that everyone can contribute to digital products we make GitLab joyful to use. It is integrated and opinionated collaboration software. Because there is no need to string together multiple tools you spend less time, have less frustration, there is less bikeshedding, and you get more results.

  2. To ensure that everyone can contribute with GitLab every person in the world should be able to afford it and adapt it. GitLab CE and are both free as in beer so everyone can afford it. comes with free private repos and CI runners, so you don't even have to host it yourself. People should be able to adapt GitLab to fit their needs. That is why GitLab CE is also free as in speech; we distribute the source and use MIT Expat license. But open source is more than a license, that is why we actively help our competitor Perforce to ship GitLab as part of Perforce Helix, and are a good steward of GitLab CE. And we keep all our software open to inspection, modifications, enhancements, and suggestions.

  3. To ensure that everyone can contribute to GitLab itself we actively welcome contributors. We do this by having quality code, tests, documentation, using popular frameworks, offering a comprehensive GitLab Development Kit, and a dedicated GitLab Design Kit. We use GitLab at GitLab Inc., to drink our own wine and make it a tool we continue to love. We celebrate contributions by recognizing a Most Valuable Person (MVP) every month. We allow everyone to anticipate, propose, discuss, and contribute features by having everything on a public issue tracker. We ship a new version every month so contributions and feedback are visible fast. To contribute to open source software people must be empowered to learn programming. That is why we sponsor initiatives such as Rails Girls and Lean Poker.

  4. To ensure that everyone can contribute to our organization we have open business processes that allow all team members to suggest improvements to our handbook. We hire remotely so everyone with an internet connection can come work for us and be judged on results, not presence in the office. We offer equal opportunity for every nationality. We are agnostic to location and create more equality of opportunity in the world. We engage on Hacker News, Twitter, and our blog post comments. And we strive to take decisions guided by our values.


  1. Ensure that everyone can contribute in the 4 ways outlined above.

  2. Become most used software for the software development lifecycle and collaboration on all digital content by following the sequence below.

  3. Complete our product vision of an opinionated and integrated set of tools based on convention over configuration that offers superior user experience.

  4. Offer a sense of progress in a supportive environment with smart colleagues.

  5. Stay independent so we can preserve our values. Since we took external investment we need a liquidity event. To stay independent we want that to be an IPO instead of being aquired. We want to triple ARR (Annual Recurring Revenue) in 2016&17, and double it in 2018&19&20 (T2D3), in order to IPO in 2020.


We want to achieve our goals in the following order:

  1. In 2015 we became the most popular on-premises software development lifecycle solution and we want to continue that.

  2. We want to become the most revenue generating on-premises software development lifecycle solution

  3. After on-premises we want to become the most popular SaaS solution for private repositories (a complete product that is free forever is competitive since network effects are smaller for private repositories than for public ones)

  4. After private repositories we want to become the most popular SaaS solution for public repositories. This market has a strong network effect since more people will participate if you host your public project on a site with more people. It is easier to overcome this network effect if many people already use for hosting private repositories.

  5. Our BHAG is to become the most popular collaboration tool for knowledge workers in any industry. For this we need to make the git workflow much more user friendly. The great thing is that sites like Penflip are already building on GitLab to make it

While we achieve our goals one by one this doesn't mean we will focus on only one goal at the time. Simultaneously we'll grow our userbase, get more subscribers for EE, grow, develop options, realize our scope, and make version control usable for more types of work.


  1. Founder control: vote & board majority so we can keep making long term decisions.

  2. Independence: since we took financing we need to have a liquidity event; to maintain independence this needs to be an IPO rather than an acquisition.

  3. Low burn: spend seed money like it is the last we’ll raise, maintain 2 years of runway.

  4. First time right: last to market so we get it right the first time, a fast follower with taste.

  5. Values: make decisions based on our values, even if it is inconvenient.

  6. Free SaaS: to make the most popular SaaS in 2020 it should be largely free.

  7. Reach: go for a broad reach, no focus on business verticals or certain programming languages.

  8. Speed: ship every change in the next release to maximize responsiveness and learning.

  9. Life balance: we want people to stay with us for a long time, so it is important to take time off, work on life balance, and being remote-only is a large part of the solution.


  1. Open source user benefits: significant advantages over proprietary software because of its faster innovation, higher quality, freedom from vendor lock-in, greater security, and lower total cost of ownership.

  2. Open Source stewardship: community comes first, and share the pie with competitors.

  3. Innersourcing is needed and will force companies to choose one solution top-down.

  4. Git will dominate the version control market in 2020.

  5. An integrated tool is superior to a collection of tools or a network of tools. Even so, good integrations are important for network effects and making it possible to integrate GitLab into an organization.

  6. To be sustainable we need an open core model that includes a proprietary GitLab EE.

  7. EE needs a low base price that is publicly available to compete for reach with CE, established competitors, and new entrants to the market.

  8. The low base price for EE is supplemented by a large set of options aimed at larger organizations that get a lot of value from GitLab.

General 2016

  1. Work with our strategic alliances to increase awareness and sales.

  2. Open up everything we can, including an open Chef repo, and marketing issue tracker.

  3. Publish our processes and plans in the handbook or link from there.

  4. Keep hiring self-directed people that experience the freedom to suggest changes.

  5. To preserve culture we should over communicate and regularly discuss our values.

  6. Drop minimum basic subscription user count to 1 user. DONE

  7. Foster leadership that stresses radiating knowledge in code, documentation, and blog articles. Work on leadership development to promote from within where possible.

  8. Spread monthly version cadence to operations and maybe marketing by setting monthly goals within these teams.

Technology 2016

  1. Make something people want: merging community contributions is the priority and at least one person will work on that fulltime.

  2. Ship the features in our direction

  3. Ship with the full scope before the year ends.

  4. Improve code quality, look and feel, usability, and performance.

  5. Implement effective development processes and leadership.

Revenue 2016

  1. Triple ARR

  2. Enable sales to provide more effective product demonstrations, share use case stories and create custom solutions and proposals.

  3. Increase revenue globally, with a focus on APAC, by developing channel sales program (value-added reseller and OEM).

  4. Increase our average deal size through upsell to higher plans, selling multi-year deals and increasing seats sold.

  5. Increase adoption and revenue within accounts through the creation of a Customer Success organization

  6. Increase salesperson capacity and productivity by creating specialized roles, in sales we'll have account executives, senior accounts executives, and regional sales directors. In Customer Success we'll have account managers (on quota and work with named accounts) and success engineers (not on quota, work with named accounts, will not do product support, work primarily via email/web-conferencing, provide pre-sales support, guide their accounts through our features, installation, implementation, integrations, roadmap, and best practices).

  7. Account Executives specialize in upsell EE from CE, competitive sell against GitHub or Atlassian and educational sell from SVN/Clearcase or top-down sell to CTO.

  8. Intense one month onboarding program (GLU, GitLab, Udacity, TrainTool) to prepare new salespeople to add value faster to the buying process.

Marketing 2016

  1. Automation: automation will bring predictable, growing, and well-prioritized leads.

  2. PR pitch: opinionated and integrated set of tools based on CoC offers a superior UX.

  3. Needs to win hearts and minds with excellent developer advocacy.

  4. Show that we can test big projects (Rails, etc.) faster than Travis CI.

  5. Announce we'll sponsor every diversity in tech event with at least $500. DONE

  6. Introduce 'everyone can contribute' as our why and tagline. DONE

  7. Hire partner marketing and product marketing people (release posts, website, and sales enablement).

Finance 2016

  1. Globally integrated finance with NetSuite.

  2. A great subscription system that is loved by sales.

  3. Need enough cash, raise if terms are great.

  4. Efficient finance that enables team, sales, etc.

  5. Efficient legal counsel with expert people and short cycles.

  6. Within 2016 we'll switch from TCV to ARR as the metric for bonuses.

  7. Monthly incentive for the whole company ($100 dinner) if we make our sales goal. DONE

People Operations 2016

  1. Develop great recruiting, hiring, onboarding, offboarding practices with full time Sr. Director of People Operations and Coordinator(s).

  2. Maintain company in compliance and adopt / adapt policies as the company scales with a globally distributed team.

  3. To support our great culture, institutionalize feedback as being near-continuous and mostly informal.

  4. Adopt a coherent approach to OKR's, performance management, and compensation management.

  5. Develop job levels with promotion criteria, including criteria on team and company collaboration.

  6. Sponsor initiatives and hire in countries that have low opportunity.

Service Engineering 2016

  1. Provide a great support experience with reliable and fast response times for customers.

  2. Respond to all community communication and recognize community members who provide a lot of support to others in the community.

  3. Make service engineering onboarding and training a mostly self-guided experience that scales.

  4. Empower users through improved documentation, training, tutorials, and community engagement.

Production Engineering 2016

  1. A highly available that feels fast and has little downtime.

  2. Free CI runners for everyone for at least as long as our credits last. DONE

  3. Continuous Deployment of master to via packages.

  4. Solutions for performance measurement, logs, including tools for alerting when something goes wrong, that ship with EE.

Partnerships 2016

  1. Most partnerships are not public but people working at GitLab Inc. can find them in the 'Partnerships' Google Doc.

  2. We'll hire a Director of Strategic Partnerships. DONE

  3. The reseller partnerships are especially important here.

  4. We also want to get shipped as official Debian package. DONE