The GitLab Field team includes multiple functions: Enterprise Sales, Commercial Sales, Customer Success, Channel Partners, Alliances, Field Operations.
The Sales team is led by the Chief Revenue Officer (CRO). Reporting into this individual are the:
The Sales team is organized into Large, Mid-Market, and SMB segments. (Descriptions of Sales segments can be found in the Field Operations Handbook - Segmentation section.)
The people working with each segment and their quota are:
The GitLab Sales team embodies our CREDIT values in every aspect of our work. Specifically, we constantly work to overperform and achieve strong results. We prioritize efficiency in our processes and operations. We succeed because of transparent, cross-functional collaboration. We are committed to hiring for and celebrating diversity, and we strive to create an environment of inclusiveness and belonging for all. And, we embrace a spirit of iteration, understanding that we can always improve.
For information regarding the tech stack at GitLab, please visit the Tech Stack Applications page of the Business Operations handbook where we maintain a quick reference table of who should have access to various tools and the designated owner for each to contact with questions. To see a full list of the tools that make up our tech stack, visit the Tech Stack Details page.
Please use the Handbook as much as possible to document important information. You should also use the Handbook as a starting point for any questions. Read here for guidance on how we take notes on the GitLab Sales team.
Dogfood GitLab whenever you can – to collaborate on ideas, gather feedback, organize projects, and more.
When you have to use office applications, always use G Suite applications instead of Microsoft Office; for example, Google Sheets instead of Excel, Google Docs instead of Word, and Google Slides instead of Keynote or Powerpoint. Give the entire company editing rights whenever possible so everyone can contribute.
Please avoid contacting individuals directly so that discussions can be available for everyone to review and learn from. We strongly encourage every team member to review the GitLab Communication Handbook page upon joining the team, and occasionally return to it during your tenure here as a refresher. (You can also get certified on communication at GitLab.)
The Sales team works cross-functionally, both with teams within and outside of our organization. These teams include:
The Customer Success department is part of the GitLab Sales function and partners with our large and strategic customers to deliver value throughout their journey with GitLab. See our Customer Success page in the Handbook for more details.
The Inside Sales department is part of the GitLab Sales function and partners with the sales and customer success teams to deliver maximum value to GitLab customers throughout their journey with GitLab. See our Inside Sales page in the handbook for more details.
These teams help accelerate GitLab’s trajectory by connecting our business and customers to companies that can help compliment our product mission and/or drive customer adoption and usage of the GitLab platform. See our Channel and Alliances Handbook pages for more details.
This team sits within the Marketing department and provides territory support to Sales team members through outreach, prospecting, and lead qualification. Key priorities include:
See the SDR page in the Handbook for more details.
This team provides technical support to GitLab.com and Self-Managed GitLab customers. For an overview of support levels based on plan tier, see the Support Page. The Support → Technical Account Manager (TAM) escalation process can be found here.
During the sales cycle, potential customers who have questions that are not within the scope of Sales can have their queries escalated in different ways depending on the account size:
We work with the Product team to help drive the GitLab Direction based on customer feedback and needs.
When you hear of feedback or you personally have feedback, you are encouraged to comment within the issue, if one exists, or create your own issue on our Issue Tracker.
When you have an organization that is interested in a feature and you have commented in the issue and added a link to the account in Salesforce, please follow the process outlined on the Product Handbook to arrange a call with the product manager and account to further discuss the feature request.
If a client has a question or suggestion about a particular part of the product, find out which individual on the Product team you need to speak by looking under DevOps Stages on the Product stages, groups, and categories page.
SAL Promotion to Area Sales Manager
In advance of a SAL being promoted to an ASM, the SAL may choose as holdovers for 3 months from their promotion effective date opportunities which are greater than or equal to all of the following Salesforce opportunity characteristics: $100k Net ARR, Stage 3, 50% Probability, provided that the opportunity attributes are established in good faith. The holdover accounts must first be approved by the VP, Enterprise Sales and then documented with Sales Operations no later than the promotion effective date. The new ASM is expected to spend less than 25% of their time as an ASM managing the holdover accounts and is required to proactively incorporate the receiving SAL into the account so the transition is minimally disruptive to the account and maximizes GitLab’s opportunity to best serve the customer. Each individual holdover account will be fully transitioned to the receiving SAL on the opportunity close date (won or lost), 3 months following the promotion effective date, or upon the new ASM’s discretion, whichever comes first. Any opportunity which meets the listed qualifications and is closed won during the holdover period will result in commission credit to the ASM equal to the commission they would have received under their most recent SAL compensation plan. There will be no additional stacked ASM payout, although it will retire ASM quota. The receiving SAL will receive no quota or commission credit.
To standardize our messaging around Coronavirus and the impact it is having on our prospects and customers, please reference the below processes:
#covid in the SFDC Opportunity field [CP] Close Plan to indicate you have had this conversation with your prospect/customer and use this report to confirm your Opportunity is tagged correctly: COVID Mentions in CP Close Planc19 to any activity record where a discussion was held.GitLab's Export Control Classification (or ECCN) is 5D992.c. As a consequence of this classification, we currently do not do business in: Iran, Sudan, Syria, North Korea, Cuba and the Crimean region of the Ukraine.