The Customer Success department is part of the GitLab Sales function who partners with our customers to deliver value and positive business outcomes throughout their journey with GitLab.
The team can be reached in Slack channel (internal only).
To deliver value to all customers by engaging in a consistent, repeatable, scalable way across defined segments so that customers see the value in their investment with GitLab, and we retain and drive growth within our enterprise customers.
The "Customer Success Vision Page" provides the long-term view of company wide success to which the customer success will be building in partnership with the value centers of the GitLab organization (i.e., Marketing, Sales, Product/Engineering, Support, Finance and IT).
Our large and strategic customers are in need of an ongoing partnership that combines expert guidance with flexibility and adaptability to support their adoption and continuous improvement initiatives.
These customers expect that partner to provide a streamlined, consistent and fully coordinated experience that encompasses the full span of their needs as well as the fully lifecycle of the relationship. Need to focus on 4 main areas in order to grow in our existing accounts as well as land large and strategic:
Opportunity to improve the overall awareness of GitLab in order to promote and evangelize our brand and solution in a meaningful way to provide big business impact to our customers so that they believe in our vision and strategy.
Ensuring paying customers are successful in their onboarding in order to gain adoption and get the most out of our platform and remain happy, paying GitLab team-members and brand advocates.
Collecting and making use of customer data and insights is key to customer success. It’s important to do more with data and when necessary share back with customers, which in turn helps and encourages our customers to improve and drive adoption.
Utilizing built-in monitoring instrumentation and a scalable HA architecture, The Customer Success team helps ensure implementations of GitLab are operating at peak performance as organization scale and adopt more features.
See the Playbooks Page
Terrain Mapping discovery engagements provide customers with the benefit of GitLab's experience with DevOps methodologies, Git, GitLab, CI, CD and monitoring by brainstorming a high level, first draft discovery of the elements of a success plan to address various challenges. They are also mapped to professional services that can help with some of the elements identified in the engagement.
See the Terrain Mapping Engagements Page
The account team is comprised of the Strategic Account Leader/Account Executive, Solutions Architect (Enterprise), and Technical Account Manager.
SA owns 1) pre-sales technical evaluation and relationships prior to the initial sale and 2) tier upgrades and new business units (i.e., connected new) within an existing customer. TAM owns 1) post-sales customer relationship and 2) license upgrades within an existing customer.
As a Solutions Architect, Technical Account Manager, or Professional Services Engineer, it is important to be continuously learning more about our product and related industry topics. The education and enablement handbook page provides a dashboard of aggregated resources that we encourage you to use to get up to speed.
TAM-Created, Enablement Focus:
SA-Created, Hands-On Focus:
Visit this page for more info on using Salesforce within Customer Success.
Visit this page for more information on using Gainsight within Customer Success.
Outside of Engineering the Customer Success team has the largest concentration of tooling development capability. The team has unique needs that can't always be solved by GitLab's single DevOps platform. However, it is important to dogfood and avoid dogfooding anti-patterns. As a result the Product organization heavily weights internal customers when considering prioritization. If you are considering building tooling in support of Customer Success priorities outside of GitLab, please follow the dogfooding process.
In an effort to keep AWS spend down initiatives are being taken automatically clean up our AWS account. This account is primarily used as a proof of concept for IaC and creating demos for GitLab customers. An automated cleanup script is currently being tested that will tag, shutdown and delete old resources as they are no longer needed. The automation will:
By customer or internal request, we sometimes develop tools to automate certain GitLab tasks using the API. The resulting tools and scripts are publicly available for everyone to use and contribute to in the GitLab CS Tools group.
Community of Practice are cross-functional groups of SME's (or aspiring to be!) within the CS organization dedicated to a topic within GitLab or the broader DevOps space. The goal is to build assets, best practices, demonstrations, and share experiences we learn from prospects and customers. In turn, CoP will build broader technical depth within our CS organization to better advise our customers and influence our product roadmap.
Customer Success team members maintain a FAQ to keep questions customers ask documented in a place where everyone can view and contribute to.
Customer Success has a few standing meetings:
The different groups within CS also have standing meetings, including meetings for the SAs, PS, and TAMs groups, regional groups, and social calls.
Following the latest GitLab release, once a month on the All CS Team Call, we have a few volunteers to discuss and/or demo new features from the most recent release:
|12.9||Dismissing Multiple Vulnerabilities||Sameer Kamani||Solutions Architect||Public Sector||Video|
|12.9||Group Export and Import via API||Sameer Kamani||Solutions Architect||Public Sector||Video|
|12.9||High Availability with Gitaly (alpha)||Sophie Pouliquen||Technical Account Manager||Enterprise East||Video|
|13.0||Gitaly and Praefect||Simon Mansfield and Christiaan Conover||Solutions Architect, Manager, TAM||EMEA and Enterprise East||Video|
Exportable Vulnerabilities Reports
WAF SIEM Integration
|Chloe Whitestone||Technical Account Manager||Enterprise East||Video|
|13.0||AWS ECS Auto DevOps||Mark Cesario||Solutions Architect||Enterprise East||Video|
|13.0||Terraform Plan View in MR and HTTP Terraform State Backend||Jamie Reid||Technical Account Manager||Enterprise West||Video|
|13.1||Fail Fast Testing||Vladimir Ten||Technical Account Manager||Enterprise West||Video|