November 18, 2023

•   Planned: Not yet implemented in GitLab, but on our roadmap.
•   Minimal: Available in the product, but may not be ready for production use, yet.
•   Viable: Significant use at GitLab the company. CM Scorecard at least 3.14 for the job to be done (JTBD) when tested with internal users. No assessment of related jobs to be done.
•   Complete: GitLab the company dogfoods it exclusively. At least 100 customers use it. CM Scorecard score at least 3.63 for the identified JTBDs when tested with external users.
•   Lovable: CM score of at least 3.95 for the JTBD (and related JTBDs, if applicable) when tested with external users.
• Gray icons ( , , , & ) represent maturities calculated using our previous methodology. Purple icons represent maturities calculated using the new methodology explained above.

Stage lifecycle:

• Not yet available (typically year 0)
• Not used at GitLab Inc. (typically year 1)
• Majority of users work at GitLab Inc. (typically year 2)
• Majority of users don’t work at GitLab Inc. (typically year 3)
• Usable for most GitLab users (typically year 4)
• Users of other tools start to switch (typically year 5)
• Entry point for new customers (typically year 6)
• Best product in the market (typically year 7)