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

Product Direction - Fulfillment: Subscription Management

  1. You are here:
  2. GitLab Direction
  3. Product Section Direction - Fulfillment
  4. Product Direction - Fulfillment: Subscription Management

Last updated: 2024-10-22

Mission

Deliver an easy, informed, and reliable experience for customers to purchase GitLab products, manage their subscriptions, and view billing details and contacts.

Overview

The Subscription Management team is responsible for providing customers with the self-service tools and features needed to purchase GitLab products and efficiently manage their subscriptions and accounts.

Key focus areas

  1. Empower customers to purchase new products and make changes to their subscriptions without requiring assistance from GitLab support or sales teams.
  2. Automate subscription management with features like Quarterly Subscription Reconciliation (QSR) and Auto-Renewal to streamline processes for customers and internal teams.
  3. Continuously improve the Customers Portal to ensure a seamless and intuitive experience for all user types, including self-service, sales-assisted, and channel partner customers.
  4. Given the global commerce functionality, support compliance, legal, and tax related efforts to safeguard revenue and meet regulations.

By focusing on these areas, the Subscription Management team aims to reduce friction in the subscription lifecycle, improve customer satisfaction, and support GitLab's overall growth and retention goals.

Target audience and experience

Feature overview and maturity

Feature Maturity Description To reach the next Maturity level
Purchase subscription 😊 Viable First time and repeat purchases of Gitlab.com and Self-managed subscriptions, as well as add-ons such as Storage, Compute Minutes and Duo Pro.  
View subscriptions 😊 Viable Gitlab.com, SM, Dedicated subscriptions can be viewed in the Customers Portal.  
Renew subscription 😊 Viable Gitlab.com and SM subscriptions can be renewed with a credit card.  
Auto-Renew subscription 🙂 Minimal Gitlab.com and SM subscriptions can be auto-renewed, certain exclusion apply.  
Add seats to a subscription 😊 Viable Gitlab.com and SM subscriptions can have seats added with a credit card.  
Remove seats from a subscription ✖️ Not Planned  
Upgrade a subscription 😊 Viable Gitlab.com and SM Premium subscriptions can be upgraded to Ultimate with a credit card.  
Downgrade a subscription ✖️ Not planned  
View invoices 😊 Viable All customers that purchased directly from GitLab can view their invoices.  
Pay for the invoice ✖️ Not planned, but evaluating the need.  
Manage payment methods 😊 Viable All customers that purchased directly from GitLab can view and manage their credit cards.  
Quarterly Subscription Reconciliation (QSR) process 🙂 Minimal QSR will process for some use cases of SaaS and SM subscriptions (Self-Service and Sales Assisted) that are opted into QSR.  
Special UX for Channel Partner customers 😊 Viable Channel customers are able to login, manage contact information, view subscriptions and licenses. They get directed to the GitLab Partner to make subscription changes.  
Emails/In-app notifications related to subscription management 🙂 Minimal    

Legend:

Roadmap and Planning

Current opportunities

Opportunity Solution(s)
Purchase flows in the Customers Portal lack a consistent user experience and scalable technical implementation. The process for buying Premium or Ultimate differs significantly from purchasing products like Storage or Compute, as well as from upgrading or renewing. This inconsistency increases the engineering team's workload in building and maintaining these various flows. We are working to unify all purchase flows in the Customers Portal to enhance scalability and improve the user experience.
The self-service renewal and auto-renewal process does not support all subscription use cases. Although GitLab's product offering now includes several renewable subscription add-ons, only subscriptions with a single renewable product are capable of being renewed. We are working to update renewal flow to accommodate all renewable products in the subscription.

Next opportunities

Opportunity Solution(s)
Customers would like the ability to add extra subscription contacts to their accounts without contacting Support. We plan to enable customers to invite multiple billing account managers to the Billing Account.

Future opportunities

Opportunity Solution(s)
Customers often find Upcoming Renewal emails confusing, as they tend to be irrelevant, unclear, and lacking actionable information. Move subscription renewal emails out of Zuora and into CustomersDot. This will allow us to limit which emails are sent, and customize their contents.

What we recently completed

Most recently completed projects are shown first.

  1. Combine multiple rate plans for the same product during renewal.
  2. Improve the purchase flows in the Customers Portal following the migration from .com.
  3. Move purchase flows from .com to the Customers Portal.
  4. Support for 3D Secure authentication for credit card payments.
  5. New Navigation for the Customers Portal, which enables BillTo/Sold contact management and displays Billing Account Managers.
  6. Updated subscription display in the Customers Portal so that it's more user friendly and scalable for various product offerings.
  7. Allowing customers that puchased via Reseller to access Customers Portal.
  8. Renewal discounting functionality in preparation for the GitLab Premium Price update.
  9. New subscription display in the Customers Portal for ramp subscriptions.
  10. Research on the renewal experience and existing processes, involving both internal teams and GitLab customers, to understand and enhance the overall renewal process.
  11. Subscription auto-renewal for all major use cases.
  12. Improved transparency into the overages and related billing for SaaS customers at the time of adding users.

Reference to OKRs, Epics, Issues and Boards

Some content is confidential and therefore won't be visible.

Edit this page View source