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

Product Vision - Fulfillment

On this page

"When technology delivers basic needs, user experience dominates." - Donald Norman

This is the product vision for Fulfillment. Fulfillment manages a variety of categories that are important for GitLab's ongoing success. Right now, these categories include Licensing and Transactions.

If you'd like to discuss this vision directly with the Product Manager for Fulfillment, feel free to reach out to Luca Williams via e-mail, Twitter, or by scheduling a video call.

Category Description
🎁 Transactions How our users purchase GitLab Plans and add-ons, and how they manage their account information.
πŸ’Œ Licensing How we fulfill our users purchases of GitLab Plans through license key distribution.

⛡️ Overview

The overall vision for Fulfillment is to provide GitLab’s customers and GitLab with an invisible user experience when handling their license keys and managing their purchases.

Billing, account management and license keys can be confusing, boring and time-consuming. We want these things to be easy and frictionless so you can focus on enjoying our product. In addition to our customers, we also prioritise the experience of GitLab Team Members (and Resellers). In order for our GitLab Team Members and Resellers to provide a great service to our customers, the administration and 'behind-the-scenes' user experience of our billing and licensing services are held to the same standard as the rest of our product.

Due to the fact that the group is responsible for collecting and storing personal and billing information, we also need to ensure that Fulfillment's services meet all compliance, security and privacy requirements.

πŸš€ Transactions Priorities

πŸ”₯ Current focus

Priority Focus Why?
1️⃣ 🎊 Self-service upgrades for GitLab.com (SaaS) This is a first iteration towards enabling our customers to fully serve themselves when performing any billing tasks. We receive a significant number of requests per week from customers who would like to upgrade a Plan so implementing this would not only reduce workload on GitLab Team Members, but it would also improve the overall user experience and potentially reduce churn.

πŸŽ‰ Next up

Priority Focus Why?
2️⃣ An improved free trial sign-up experience for GitLab.com (SaaS) users A free trial is often the first interaction our users have with our Product and therefore could be a dealbreaker for them. Currently, the free trial experience as a whole is confusing, lengthy and frustrating and this issue to improve the sign-up flow of our GitLab.com free trial is our first iteration towards creating a delightful and exciting first-look experience into GitLab as a product.
3️⃣ An improved purchase experience for GitLab.com (SaaS) users Similarly to the free trial experience, our purchasing flow needs a serious refresh and this issue aims to significantly reduce the friction and frustration for our GitLab.com users who need to do business with us.
4️⃣ Automatically bill for newly added group members on GitLab.com One of our goals in Fulfillment is to create a fair billing experience for our users and this issue is an iteration towards that goal. By implementing this, we can begin to shape a multi-directional billing flow that ensures our customers are fairly billed for what they use, and GitLab as a company accurately receives payment for the services provided.

πŸš€ Licensing Priorities

πŸ”₯ Current focus

Priority Focus Why?
1️⃣ Allow users to download their license key from the transactions portal This issue is a small but significant step towards unifying our Self-Managed customers' billing and licensing experience. Currently the only way for folks to access their license key is to have a GitLab Team Member email it to them - this issue removes a considerable amount of friction around that process and allows users to have more control over their own license key management.

πŸŽ‰ Next up

Priority Focus Why?
2️⃣ Maximum Users should always reflect current counts True-ups are a huge friction point for many companies and GitLab is not unique in this regard. This issue aims to provide more clarity to both users and GitLab Team Members who are helping customers understand the true maximum user count on their instances. This will provide a more seamless and accurate billing experience for both sides.

How we prioritize

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!