The goal of the Customer Reference Program is to provide opportunities for customers to share their story on how GitLab has helped them overcome the challenges, blockers and pain points within their organizations. The Reference Program Managers work as a conduit to help connect customers with opportunities by balancing customer requests with company demands. By providing a single point for outreach to customers, the CRP team prevents customer burnout, sales team burnout, and ensures a diversity of customer stories are shared publicly.
Team of Experienced Customer Reference Professionals who are focused on building relationships within GitLab and with customers.
The team gathers and builds information and relationships with the purpose of distilling these impactful insights into action.
To manage our customer reference relationships like the precious resources they are to the maximum, quantified & qualified benefit for both customers and GitLab.
Quick links grid
|Quick Reference Links|
|Adding new reference customers||Requesting a reference for a sales call|
|Customer Case Studies - Customers Page||Case Study Board - search by Usecase, Value Driver, Product replacing, etc|
|Customer Events - Process and Support||Customer Logo Approval form (02.11.2021)|
|Customer Reference Collection||Customer Case Study Slides (individual slides per case study)|
|Peer Reviews||Customer Advisory Board|
|Offical Letter Welcoming Customers to Reference Program||Customer Insight Page (Case Study Process)|
View information around customer reference pool, keep track of the latest case studies and find out how the Customer Reference team is helping share customer success stories.
Some examples of the types of assets we'd use as customer references once we have approval from the customer:
* What led you to GitLab, what problems were you trying to solve? * Why did you choose GitLab and what other tools were you using or considering? * What has been your experience with GitLab? * How did you make the business case for GitLab and what metrics have you seen improve? * What have you heard from GitLab users, what was their adoption curve like? * What has been the most unexpected success you have experienced? Adoption rates? Improved speed?
Please access the resources below to search for suitable references to send to your prospects/customers.
It is critical and the Customer Reference Management team’s responsibility to optimize our reference customer engagements to balance:
By default, we will request a customer support reference call (sales/analyst relations/public relations) no more than once per quarter per customer. In support of event speaking and/or other participation support (field, alliance, digital, community, etc.), we will request customer support at a maximum of once every two quarters per customer. The CRM ultimately decides if the reference request is suitable for the proposed customer based on a number of factors including but not limited to:
To request customer speakers for various activities, please view detailed process here
To create a general request for the Customer Reference Program, open an issue on the Customer Reference Program Board in the Strategic Marketing Project.
GitLab understands the value of our customer relationships and values customers that are willing to share their success with our team. We have a logo permission form that we require be signed before we promote the customer relationship using the customer logo. We understand and respect that corporate logos are considered intellectual property and are owned and licensed by the respective organization.
Customer Slide in the Pitch Deck
This slide is reviewed and updated on a 6 monthly basis by the PMM team and the Reference team. The CRM creates the review issue and works with the assigned PMM to review new logos and create a revised slide. Once the strategic marketing team approves the new slide; the CRM creates an issue for the brand team to review the slide. The CRM co-ordinates with the Pitch deck editor to update the new slide into the pitch deck.
Customer Case Study Slides Once the case study is published, the CRM creates a stand alone slide in the WIP folder, at the end of every quarter, the CRM raises a design review issue for the brand team to approve the new case study slides in WIP. When the new slides are approved by the design team; the CRM migrates these new slides into the Case Study Deck.
Full Customer Logo Deck The CRM reviews the deck above on a 6 monthly basis; working with the PMM team to update the deck. The CRM creates an issue for the brand team to review and publishes a new version of the customer logo deck. The CRM manages the versions of the deck and tracks the new additions.
The CRM will review the customer case study page on a quartlery basis reviewing the content and the customer grid.
Purpose: To reflect our customer base we use customer logos to promote organizations that are using GitLab
Customer logos appear on our website and other marketing and promotional materials. To respect the intellectual property of companies that use our product, we request a signed permission form to use their logo. To request logo usage from a customer, please send the Logo permission form to the appropriate member of the customer organization. Please note this approval form includes permission for logo usage in case study/video and social promotion activities as per prior customer agreement.
Information about the GitLab Customer Advisory Boards is found on the CAB page
Learn about our Peer Review Management Program
The Customer Reference Team has created appreciation swag for customers to thank them for their support and for engaging with us in reference activities. Availability of these items is limited and managed by the Customer Reference Program team. For customers in the Americas, please reach out to Jen For EMEA-based customers, please reach out to Fiona