Gitlab hero border pattern left svg Gitlab hero border pattern right svg

The Procurement Team

On this page

Team members can purchase goods and services on behalf of the company in accordance with the Signature Authorization Matrix and guide to Spending Company Money. However, all purchases being made on behalf of GitLab that are not a personal expense, must first be reviewed by procurement, then signed off by a member of the executive team. This ensures GitLab can appropriately plan for spend and assess vendor risk.

What if the Vendor I am working with doesn't require a contract?

  1. Even if your vendor doesn't need a contract, a Vendor Contract Issue is still required under Requesting Procurement Services below.
  2. The Vendor Contract approval process is designed to protect both you and the GitLab and the vendor.
  3. In this event we can and will provide terms to govern the transaction based on the level of risk.

Prior to Contacting Procurement

Prior to engaging Procurement, please review the below guidelines:

  1. Review the market capabilities defined by your overall spend before selecting your vendor.
  2. Before sharing details and/or confidential information regarding our business needs, please obtain a Mutual Non-Disclosure Agreement from the potential vendor(s). Refer to the Signature Authorization Matrix for signing authority.
  3. All vendors must adhere to the GitLab Partner Code of Ethics. Inform your vendor(s) it is mandatory they contractually adhere to this if they would like to do business with us. (Note these are typically not required in event related agreements unless the vendor is providing services).
  4. Identify your bid requirements based on your estimated spend:

    $0-$100K: No bid

    $101K - $250: 2-3 Bids

    Greater than $250K: RFP

  5. Open a vendor contract approval issue based on the choices under Requesting Procurement Services. Do this BEFORE agreeing to any business and/or pricing terms.

Requesting Procurement Services

Start working with the Procurement team by opening a vendor contract approval issue based on the type of purchase below. Procurement will not approve the request if the request is incomplete and/or missing information.

Contact Procurement directly in Slack via #procurement if you have any questions.

1: Purchase Type: Software or vendor that will process GitLab data

  1. Open a Vendor Contract Approval issue with this template to begin the process.
  2. Create this issue BEFORE agreeing to business terms and/or pricing.
  3. It is preferred we negotiate the best pricing up front to keep our ongoing costs to a minimum across our long-term relationships with vendors.
  4. If you have a field marketing or event contract where confidential data will be shared, use the above template.

A video tutorial of the issue creation process can be found HERE

2: Purchase Type: Existing vendor true-up/expansion/renewal

  1. Open a Vendor Contract Approval issue with this template 90-60 days before the existing contract expires.
  2. Create this issue BEFORE agreeing to business terms and/or pricing.
  3. It is preferred we continue to evaluate supplier pricing at the time of renewal to keep our ongoing costs to a minimum across our long-term relationships with vendors.
  4. This can include addendums or PO adjustment that either do or do not change pricing.

A video tutorial of the issue creation process can be found HERE

3: Purchase Type: Field Marketing and Events withOUT Confidential Data

  1. Open a Vendor Contract Marketing & Events Approval issue with this template
  2. Examples for this template type include marketing events, programs, sponsorships, catering, hotels, swag and services that do NOT involve the processing or sharing of data.
  3. If you will be sharing confidential data with the vendor, please use the template under Purchase Type #1 above.

A video tutorial of the field marketing and events issue creation process can be found HERE

Deep Dive on the Vendor Contract Issue Process

Procurement will not approve a contract issue until all other approvals have been received to validate the appropriate approval process and policies have been followed. In the event procurement approves an issue prior to other approvals in an attempt to avoid being the source of a backlog, procurement will comment in the issue that their approval is "subject to remaining approvals". At this point it is the responsibility of the issue owner to follow the remaining process to obtain contract signature.

  1. Legal is responsible for reviewing vendor contracts and will adhere to legal playbook.
  2. A contract cannot be signed until it has been approved by the legal team. Once the legal team approves the contract, legal will upload the contract with the approval stamp. Contracts will not be signed unless the legal approval stamp is included.

Security Engagement for Vendor Contracts

  1. Security is responsible for reviewing vendor security practicies and will adhere to the Third Party Vendor Security Review Process.
  2. The Security Compliance team needs 3 business days to complete this review from the time they receive all necessary documentation from the vendor
  3. A contract cannot be signed until it has been approved by the security team. Once the security team approves the vendor and/or identifies gaps in the vendor's security practices for negotiation, security will provide their approval in the issue.
  4. Consult the Data Classification Policy to understand whether your contract will need security review. Any contracts that will share RED or ORANGE data will need security approval prior to signing. Additionally, an annual reassessment of vendor's security posture is performed as part of the contract renewal.
  5. Complete a Data Protection Impact Assessment; please note that this will be done in partnership with GitLab's Data Protection Officer and reviewed by Security Compliance during the Security Review.

Capacity & Back Log

In the event you have an issue that hasn't received a prompt response from procurement, requestor should tag Aleshia Hansen in the #procurement Slack channel and provide:

  1. Link to the Vendor Contract Approval issue; and
  2. Timeline

In the event the procurement team is out of office (as highlighted in PTO calendar or Slack), and the matter is time sensitive, requestor should contact #legal channel in Slack and provide:

  1. Link to Vendor Contract Approval Issue; and
  2. Reason for escalation, with timeline for requirement(s)

Legal will assign a team member to approve the procurement portion of the issue.

Vendors & GitLab

Vendor Onboarding

Vendors will be required to create an account within Tipalti in order to receive payment.

Vendor Performance Issues

If there are performance and/or quality issues from an existing third-party vendor, procurement can support the resolution and/or re-evaluation of a replacement vendor. Please log an issue and assign a.hansen for next steps.

Documentation

Contract Templates

Procurement KPI

Deliver quantified savings of > $3,000,000 over a rolling 12 month period.

Cost savings are achieved through the procure to pay process. Savings are calculated as the savings achieved by comparing the initial vendor proposal price to the final purchase price. In the event of a contract renewal, in addition to the above, savings can also be calculated as the savings achieved by comparing the previous cost per unit (eg. user, business metric, etc.) to the final cost per unit. Savings negotiated at the cost per unit level are also cost savings to be calculated as savings. Note these savings are not directly tied to budget.

Aligns with the following core business objectives:

Procurement Main Objectives

Procurement operates with three main goals

  1. Cost Savings
  2. Centralize Spending
  3. Compliance