The Buyer Experience encompasses all of the systems, processes and interactions that influence the experience of a person purchasing and managing a GitLab subscription. This includes customer-facing tools and services, such as the GitLab webstore and Customer Portal, as well as internal processes that impact the customer experience, such as the contracting process and billing.
The GitLab Buyer Experience Group (BEG) is comprised of leadership from Sales, Revenue Operations, Billing, Product and Pricing. This unified team evaluates new strategic initiatives, develops necessary processes and ultimately operationalizes changes to the Buyer Experience.
This team evaluates all initiatives and makes prioritization decisions based on the impact to the Buyer of the GitLab product. This Buyer interacts with unique areas of the product (webstore, customers portal, marketplaces, reseller portals) and a range of functions (internal sales, billing, support, resellers). To properly prioritize initiatives to improve their GitLab experience we need a group of decision makers with a broad view into these tools and our operations.
The Buyer Experience Group Internal Handbook page captures internal-only information, including an up-to-date project tracker.
|Deal Desk Handbook||Standard Quote Configuration (new subscription, amend subscription, add-on quote creation, upgrade or product switch during subscription term, renewal, channel deals, true-ups, co-terms, Starter/Bronze End of Availability, SuperSonics, Professional Services), Non-Standard Quotes (Contract Resets, Concurrent Subscriptions, Multi-year Deals, Ramp deals), Alliance Marketplace Private Offers, and more.|
|Sales Order Processing||Account and opportunity creation, quote configuration, approvals process, opportunity booking requirements, closing an opportunity.|
|Internal Support||Submitting all requests around licensing, subscription, trials, and grace periods.|
|Licensing FAQ||Common questions around purchasing, licensing, billing, contacting sales, and more|
|Finance and Legal Authorization Matrix|
|Billing, invoice and payment requests||Zuora contact change, Zuora entity change and effects on SM/SaaS subscriptions, cancellations, downgrades, refunds, invoices, payments, credit card removals, renewal reversals, split payment requests|
|CustomersDot Access and Use by Sales||Logging in, information available in CustomersDot, seat reconciliations for a customer, usage data for a customer|
|Troubleshooting: True Ups, licenses + EULAs|
|Cloud Licensing (Internal)||Internal handbook information about Cloud Licensing|
|Cloud Licesing Overview (External)||Why Cloud Licensing, data collected, customer pre-requisites|
|Quote-to-Cash systems documentation (EntApps)||Overview of systems, EntApps Architecture, Process Flow Diagrams, Entity Relationship Diagrams|
|Fulfillment Direction||Fulfillment overview, 1-year plan, responsibilities, roadmap, OKRs, PIs|
|Fulfillment Development Sub-Department||Team members, stable counterparts (PM, UX, Quality, Security, EntApps, Field Ops, Sales, Billing, Customer Success, Support Engineering), project management processes, and more|
Over time, we will organize our information by looking at the process stages, and consider the various order types and purchasing channels.