## Problem Statement Enable Growth team to contribute more effectively to trials work in CustomersDot (CDot) by improving team onboarding, simplifying key endpoints, and establishing clear collaboration patterns with the Provision team. ## Context Building on the work started in [customers-gitlab-com#13619](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/13619), we need to improve Growth's ability to work effectively in CDot for trials-related work while maintaining appropriate collaboration with Fulfillment/Provision team. ## Goals - Onboard more Growth engineers to CDot development - Simplify and improve observability of CDot endpoints that Growth frequently works with - Increase test coverage for GitLab-CDot communication on Growth-focused endpoints - Establish clear collaboration patterns with Provision team for trials work ## Success Criteria **Growth team capabilities:** - [ ] Multiple Growth engineers onboarded and comfortable working in CDot - [ ] Improved observability for CDot endpoints Growth works with (trial workflows) - [ ] Increased test coverage for GitLab-CDot communication on Growth-focused endpoints - [ ] Simplified endpoint implementations for common Growth use cases **Collaboration model:** - [ ] Decision framework documented for when Growth contributes directly vs. when to engage Provision: - **Growth contributes independently:** Changes isolated to trial-specific logic (eligibility, duration, UX, tracking) - **Engage Provision team:** Changes affecting billing, subscriptions, provisioning, or shared infrastructure - **Judgment call:** If uncertain about blast radius or domain complexity, consult with Provision before proceeding - [ ] Escalation paths defined for priority conflicts: 1. Growth contributes directly (for changes not requiring deep Provision domain knowledge) 2. Leadership-level reprioritization (for blocking dependencies) 3. Resource allocation adjustments (headcount, borrows, re-orgs) **Technical outcomes:** - [ ] Growth-focused CDot endpoints are well-documented and observable - [ ] Test coverage improvements for critical Growth workflows **Note:** Deep provisioning/billing work remains owned by Provision team. Growth will focus on trials-specific functionality and collaborate with Provision on boundary areas. # Stakeholders - Growth team (Acquisition group) - Fulfillment team (Provision group) - @bishwa @dstull @gdoud @ghosh-abhinaba