This page is meant to provide insight into how we consider and allocate our investment across our Product Hierarchy.
We have a framework we use to assess the investment level for each DevOps stage. The three investment drivers are as follows:
Each driver is scored on a 1-5 basis. Here is a description of how each driver is scored.
| Score | Usage Driver Key | Revenue Driver Key | SAM Driver Key |
|---|---|---|---|
| 1 | <10k SMAU | Not a driver of paid sales | <200m SAM over the next three years |
| 2 | 10k-50k SMAU | Used by paid customers, but not a major element in paid sales | 200m-500m SAM over the next three years |
| 3 | 50k-100k SMAU | Key element in Starter+ sales | 500m-1B SAM over the next three years |
| 4 | 100k-200k SMAU | Key element in Premium+ sales | 1B-2B SAM over the next 3 years |
| 5 | >200k SMAU | Key element in Ultimate sales | >2B SAM over the next three years |
We score enabling groups differently. Their Criticality of Use score replaces their Usage score and their Degree of Enablement replaces their SAM Score. Enabling groups utilize the same scoring methodology as DevOps stage groups for their Revenue Driver score.
As for DevOps stage scores - each driver is scored on a 1-5 basis. Here is a description of how each driver is scored.
| Score | Criticality of Use | Degree of Enablement |
|---|---|---|
| 1 | Non-essential to use of GitLab | Enables < 25% of the DevOps Market |
| 2 | Non-essential but becoming more critical | Enables > 25% of the DevOps Market |
| 3 | Essential but not required | Enables >50% of the DevOps Market |
| 4 | Heavily recommmended for use of GitLab or GitLab.com | Enables >70% of the DevOps Market |
| 5 | Required for use of GitLab or GitLab.com | Enables entire DevOps Market |
The following table provides scores for each of our DevOps stages and a comparison of the total score to our current development spend allocation as defined by the percentage of total individual contributor developers in product groups.
| Stage | Usage Driver Score | Revenue Driver Score | SAM Driver Score | Combined Score | % of Total Score | Stage Dev | Stage Dev % | Score/Spend Difference |
|---|---|---|---|---|---|---|---|---|
| Manage | 3 | 5 | 2 | 10 | 11.9% | 29 | 16.96% | +5.1% |
| Plan | 5 | 3 | 5 | 13 | 15.5% | 20 | 11.7% | -3.8% |
| Create | 5 | 3 | 3 | 11 | 13.1% | 33 | 19.3% | +6.2% |
| Verify | 5 | 2 | 3 | 10 | 11.9% | 23 | 13.45% | +1.5% |
| Package | 2 | 2 | 1 | 5 | 6.0% | 6 | 3.51% | -2.4% |
| Release | 4 | 2 | 2 | 8 | 9.5% | 6 | 3.51% | -6.0% |
| Configure | 1 | 1 | 3 | 5 | 6.0% | 7 | 4.09% | -1.9% |
| Monitor | 1 | 1 | 4 | 6 | 7.1% | 7 | 4.09% | -3.0% |
| Secure | 2 | 5 | 5 | 12 | 14.3% | 36 | 21.05% | +6.8% |
| Protect | 1 | 1 | 2 | 4 | 4.8% | 4 | 2.34% | -2.4% |
Note: Enablement and Growth stages and groups aren't included, as they don't have specific target markets, and don't have a dedicated SAM. Therefore, they can't be compared directly with feature-function stages and aren't included in this analysis.
| Stage: Group | Usage Driver | ASP Driver | SAM Driver | Total | % of Total | Group Devs | Group Dev % | Score/Spend Difference |
|---|---|---|---|---|---|---|---|---|
| Manage: Access | 5 | 4 | 1 | 10 | 3.0% | 10 | 5.08% | +2.1% |
| Manage: Compliance | 1 | 5 | 5 | 11 | 3.3% | 7 | 3.55% | +0.2% |
| Manage: Import | 1 | 3 | 1 | 5 | 1.5% | 5 | 2.54% | +1.0% |
| Manage: Optimize | 2 | 2 | 3 | 7 | 2.1% | 7 | 3.55% | +1.4% |
| Plan: Project Management | 5 | 4 | 5 | 14 | 4.2% | 9 | 4.57% | +0.4% |
| Plan: Product Planning | 2 | 5 | 5 | 12 | 3.6% | 11 | 5.58% | +2.0% |
| Plan: Certify | 2 | 2 | 4 | 8 | 2.4% | 0 | 0.0% | -2.4% |
| Create: Source Code | 5 | 4 | 5 | 14 | 4.2% | 8 | 4.06% | -0.2% |
| Create: Code Review | 5 | 4 | 5 | 14 | 4.2% | 11 | 5.58% | +1.4% |
| Create: Editor | 4 | 2 | 3 | 9 | 2.7% | 7 | 3.55% | +0.8% |
| Create: Gitaly | 5 | 4 | 1 | 10 | 3.0% | 7 | 3.55% | +0.5% |
| Create: Ecosystem | 5 | 4 | 5 | 14 | 4.2% | 0 | 0.0% | -4.2% |
| Verify: Continuous Integration | 5 | 3 | 4 | 12 | 3.6% | 7 | 3.55% | -0.1% |
| Verify: Pipeline Authoring | 5 | 3 | 4 | 12 | 3.6% | 5 | 2.54% | -1.1% |
| Verify: Runner | 5 | 3 | 2 | 10 | 3.0% | 6 | 3.05% | +0.0% |
| Verify: Testing | 4 | 2 | 3 | 9 | 2.7% | 5 | 2.54% | -0.2% |
| Package: Package | 3 | 2 | 4 | 9 | 2.7% | 6 | 3.05% | +0.3% |
| Release: Release | 4 | 3 | 4 | 11 | 3.3% | 6 | 3.05% | -0.3% |
| Configure: Configure | 2 | 2 | 4 | 8 | 2.4% | 7 | 3.55% | +1.1% |
| Monitor: Monitor | 1 | 1 | 4 | 6 | 1.8% | 7 | 3.55% | +1.7% |
| Secure: Static Analysis | 4 | 5 | 5 | 14 | 4.2% | 7 | 3.55% | -0.7% |
| Secure: Dynamic Analysis | 2 | 5 | 5 | 12 | 3.6% | 7 | 3.55% | -0.1% |
| Secure: Composition Analysis | 3 | 5 | 5 | 13 | 3.9% | 6 | 3.05% | -0.9% |
| Secure: Fuzz Testing | 1 | 1 | 5 | 7 | 2.1% | 5 | 2.54% | +0.4% |
| Secure: Threat Insights | 4 | 5 | 5 | 14 | 4.2% | 7 | 3.55% | -0.7% |
| Secure: Vulnerability Research | 4 | 5 | 5 | 14 | 4.2% | 4 | 2.03% | -2.2% |
| Protect: Container Security | 1 | 2 | 2 | 5 | 1.5% | 4 | 2.03% | +0.5% |
| Enablement: Distribution | 5 | 4 | 5 | 14 | 4.2% | 8 | 4.06% | -0.2% |
| Enablement: Geo | 3 | 4 | 3 | 10 | 3.0% | 8 | 4.06% | +1.0% |
| Enablement: Memory | 3 | 2 | 3 | 8 | 2.4% | 4 | 2.03% | -0.4% |
| Enablement: Global Search | 3 | 3 | 3 | 9 | 2.7% | 3 | 1.52% | -1.2% |
| Enablement: Database | 3 | 1 | 3 | 7 | 2.1% | 3 | 1.52% | -0.6% |
For non-DevOps and Enabling stages we still track our overall investment, but don't attribute score or score/spend differences.
| Stage: Group | Group Devs | Group Dev % |
|---|---|---|
| Manage: Access | 10 | 4.63% |
| Manage: Compliance | 7 | 3.24% |
| Manage: Import | 5 | 2.31% |
| Manage: Optimize | 7 | 3.24% |
| Plan: Project Management | 9 | 4.17% |
| Plan: Product Planning | 11 | 5.09% |
| Plan: Certify | 0 | 0.0% |
| Create: Source Code | 8 | 3.7% |
| Create: Code Review | 11 | 5.09% |
| Create: Editor | 7 | 3.24% |
| Create: Gitaly | 7 | 3.24% |
| Create: Ecosystem | 0 | 0.0% |
| Verify: Continuous Integration | 7 | 3.24% |
| Verify: Pipeline Authoring | 5 | 2.31% |
| Verify: Runner | 6 | 2.78% |
| Verify: Testing | 5 | 2.31% |
| Package: Package | 6 | 2.78% |
| Release: Release | 6 | 2.78% |
| Configure: Configure | 7 | 3.24% |
| Monitor: Monitor | 7 | 3.24% |
| Secure: Static Analysis | 7 | 3.24% |
| Secure: Dynamic Analysis | 7 | 3.24% |
| Secure: Composition Analysis | 6 | 2.78% |
| Secure: Fuzz Testing | 5 | 2.31% |
| Secure: Threat Insights | 7 | 3.24% |
| Secure: Vulnerability Research | 4 | 1.85% |
| Protect: Container Security | 4 | 1.85% |
| Growth: Activation | 0 | 0.0% |
| Growth: Conversion | 0 | 0.0% |
| Growth: Expansion | 0 | 0.0% |
| Growth: Adoption | 0 | 0.0% |
| Growth: Product Analytics | 0 | 0.0% |
| Fulfillment: Purchase | 11 | 5.09% |
| Fulfillment: Provision | 6 | 2.78% |
| Enablement: Distribution | 8 | 3.7% |
| Enablement: Geo | 8 | 3.7% |
| Enablement: Memory | 4 | 1.85% |
| Enablement: Global Search | 3 | 1.39% |
| Enablement: Database | 3 | 1.39% |
| Enablement: Infrastructure | 0 | 0.0% |
| Learn: Machine Learning | 0 | 0.0% |
| Mobile: DevOps for Mobile Apps | 0 | 0.0% |
| Deploy: Five Minute Production App | 2 | 0.93% |
Changes to this page are made by adding new values to the single sources of truth (categories.yml and stages.yml) and then editing this page in order to display those values in table form. Be sure the definition for any column value is defined in stage and category attributes and that the column headers link to those definitions.
The process for making changes requires you to submit a merge request to the stages.yml for the specific keywords that have changed and provide the data source for that change. Assign the merge request to the EVP or VP of Product and slack #product for approval/merge. You can reference the Release Stage update for an example.
