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

Analyst Relations

Analyst relations at GitLab

Analyst relations (AR) is generally considered to be a corporate strategy, communications and marketing activity, but at GitLab, because of our mission that everyone can contribute, we view the analyst community as participants as well. The primary owner of Analyst Relations at GitLab is Strategic Marketing, as they are the conduit between the analysts and the internal company information.

Industry analysts usually focus on corporate or organizational buyers and their needs rather than on those of individual developers. At GitLab we view them as a marketing focus for those markets. They amplify our message to a different group than our traditional developer communities, although there is overlap to some degree between those communities.

How we interact with the analyst community

Examples of how we engage with analysts include:

How we on-board a new analyst to the GitLab Analyst Relations community

How we off-board an analyst from the GitLab Analyst Relations community

Responding to vendor product comparison reports (e.g. MQs or Waves)

Process for responding to vendor product comparison reports (e.g. MQs or Waves)

Before the questionnaire arrives:

When the questionnaire arrives:

When the draft report arrives:

When the report is published:

Accessing analyst reports

Most analyst companies charge for access to their reports.

Analyst reports that can help you deepen your knowledge

As part of XDR and Sales Enablement, some analyst reports are educational - they can help you build your understanding of the market. We've collected some of those articles to share with you here. These are behind the firewall and for use of employees where they have access rights. If you have any questions on access, please contact Analyst Relations.

The complete list of documents by topic can be found here.

Which analyst relations team member should I contact?