The goal of the customer case studies program is to share and market the success of our customers. We do this by helping them craft their story in a way that makes them proud and excited to talk about their success with GitLab.
A formal case study produces a polished, finished document or video published on our customers page. Case studies can include multiple formats, including a web page, video, downloadable PDF, and associated blog posts.
A customer story is a blog post about how a customer solved a particular problem or received a specific benefit and are published on GitLab's blog. Customer stories can also be anonymous. e.g. "A large international financial services company used GitLab CI/CD to reduce build times from 1 hour to 10 mins."
Once you have a customer who either (1) has an excellent use case or (2) has committed to participating in a case study:
*If you included a case study as part of a deal, great! Set up a call with the content marketing team and the customer to go over how they plan to use GitLab and metrics the customer is willing to track. Set a follow up call in 3 months and again in 6 months.
standard(2-3 day turnaround) option.
case study - productionand assign to Content Marketing.
Staus-WIPand ping the Content Marketing Manager to review.
Possible quantitative metrics that the customer can be asked to share with GitLab include:
The customer case study should then be written by the Customer Reference Manager or Customer Content Manager, and the draft sent to the customer for their input and approval.
Other sections in the case study can be found on the customer's website or by searching the web - Sidebar summary, The Customer.
Following approval from the customer, the Design team should be sent a doc of the case study to include in the case study design template. The case study can then be published on our website.
Headline: The name of the customer and the benefit they gained from implementing our solution
Sidebar Summary: Summarize key points
The Customer: A brief introduction of the customer, not the solution.
The Challenge: What was the customer trying to change or improve. What regulations or market conditions drove the customer to search for a new solution. Share the steps the customer took to solve the problem, including other products and services they investigated.
The Solution: Detail the solution and how it aligns to the customers requirements. Also detail other solutions that GitLab interfaces with. Also include customer quote.
The Results: Detail how GitLab supported the customer to solve their problems. This is where the use of benchmarking metrics such as such as time saved, reduced costs, increased performance etc. are required.
About GitLab: Short paragraph on GitLab - about, solutions etc. Call to action of solutions offered.
Possible Additional Supporting Documents:
Case studies should put the spotlight on our customers and tell a story about the ways in which they help their own customers. In telling that story, we should detail how GitLab helps them get that job done. Case studies should include metrics, but a compelling story can be told without them if there aren't any available. If metrics are unavailable, consider including the customer's overarching results, such as increased collaboration or stronger relationships between developers and operations.
Case studies should always take high priority. Once a case study is initiated, it should take no longer than 1 month to turn around a draft for review. Once the case study has been reviewed and approved by the customer, it should take no longer than 5 working days to publish on the marketing site.