This is the product direction for GitLab's Fulfillment group. If you'd like to discuss this vision directly with the Product Manager for Fulfillment, feel free to reach out to Mike Karampalas via e-mail, Twitter, or by scheduling a video call.
The Fulfillment Team at GitLab focuses on creating and supporting the experiences that enable our customers to purchase, upgrade, downgrade, and renew licenses and subscriptions. We are constantly striving to make the billing and payment processes simple, intuitive, and stress-free for our customers and GitLab team members. We believe that engaging in business transactions with GitLab should be minimally invasive and when noticed, should be a positive, empowering, and user-friendly experience.
We also partner with the Growth Groups to enable experimentation and product improvements focused on making it easy for people to try, buy, grow, and stay with GitLab.
We follow the same prioritization guidelines as the product team at large. Issues tend to flow from having no milestone, to being added to the backlog, to a directional milestone (e.g. Next 3-4 releases), and are finally assigned a specific milestone.
Our entire public backlog for Fulfillment can be viewed on the issue board, and can be filtered by labels or milestones. If you find something you are interested in, you're encouraged to jump into the conversation and participate. At GitLab, everyone can contribute!
We don't want our customers to be surprised about billing and user management. Customers should be fully aware when they're taking an action that will require additional payment.
We want customers to easily understand what (and who) they're paying for. Over the next two quarters we will provide instance admins and group owners with tools to find the users they are being billed for.
The Customers Portal should be easy-to-use and provide a consistently delightful experience that matches our other offerings.
The Customer Portal should use our Pajamas design system
We are in the early phases of moving towards a simpler approach for how self-managed instances purchase and apply a license. We recognize that the current process is less than ideal for our customers, as well as our GitLab team members. The requirement to log into the Customers Portal to purchase, renew, and access your license key can be frustrating and difficult and we want to make that process an afterthought.
What we would like to do is create a license sync that will allow customers to regularly sync their license and user counts with GitLab to streamline purchases and renewals as well as enable us to provide more flexible billing options for our customers.
At the same time, we understand that not all of our customers are running instances that can connect to the internet or have requirements against sharing any kind of information. In those cases, we need to ensure customers have the option to continue to purchase and apply licenses as they do today.
We are just beginning the technical discovery phase of this effort and we hope to have an initial iteration ready by mid-2020. If you would like to discuss this, or anything else Fulfillment related, please reach out to Amanda Rueda via e-mail.
