The purpose of this page is to provide clear guidelines around GitLab's FY23 GTM Rules of Engagement in the following areas:
For more information on terms and other sales information, please visit GitLab's Go to Market page.
Effective FY24-Q1
NOTE: Working a Lead, Contact, Opportunity or Account does not ensure ownership. Before investing any effort, it is the responsibility of the sales rep to confirm that an account listed as owned by them in SFDC is in fact in their territory.
Additional information on Trade Compliance can be found on the Legal HB Page for Embargoed Countries
The data sources used to properly segment and route an account are defined and explained in the Account Demographics section of the handbook. If the data tools have failed to provide employee count and/or address information, the account segment and/or territory will remain Unknown until resolved through manual research and a link to a reputable data is provided to the Sales Operations team to confirm. Follow the process to request changes to the Account Demographics inputs if the account information is missing or wrong. If the employee count is unknown or blank and manual research cannot confirm, Sales Operations will mark the account as SMB with a placeholder of -1 employees in order to get a Territory to populate and assign the account to an account rep. Any disputes must follow the exception process below.
Only active Field Sales (AE/SAE) members can own accounts. The exceptions to this rule include:
Account ownership will be determined by the Sales Segment and Address. All children accounts in a hierarchy will be owned by the Global Account Owner of the Corporate Hierarchy regardless of physical location unless the child account has been marked as a Named Account
, Holdover
or Holding Company
.
The following two policies apply to account ownership in the middle of the Fiscal year:
Important Notes
All Accounts in a hierarchy will adopt the MAX Segmentation of any account in the hierarchy. Expanded definitions and examples can be found in the handbook’s Systems Terminology Definitions.
An account that is owned by a Sales Rep with a headquarters outside of his or her designated geographical territory. Named accounts are identified by the Named Account Checkbox on the Account. Named Accounts are owned and worked by the designated Strategic Account Executive (SAE) or Account Executive (AE) along with all records (LEADS and CONTACTS) associated with that Named Account and any related Child accounts within or added to SFDC. Named accounts will be reviewed annually to determine if they should be moved to the Global Account Owner at that time or remain Named.
An account that has been identified as important for the Area, Region and Segment and where we want to focus our sales efforts. Key Accounts may also be marked as Named Accounts. Each Strategic Account Executive should have 15-20 Key Accounts on average in their territory. Key Accounts are identified at the beginning of the fiscal year by the ASM, RD or VP of the specific region and will be reviewed annually. Any changes to the Key Accounts list would need to be reviewed and approved by ASM, RD and VP of the region. The 'Key Account' field will be checked for these accounts.
An account that is identified as Public Sector Worldwide. Once identified, the assignment of these accounts will be according to the Government Rules of Engagement.
Mid-Market accounts are covered by three Sales motions: First Order (New Business) accounts, Named accounts, and Territory accounts:
First Order
accounts will be passed over as a Named Account
once an initial deal is closed won. It's important this transition occurs in a timely manner after initial deal closure, to start business expansion efforts ASAP.An account that is owned by a local account rep regardless of the Global Account Leader. These accounts are identified by the Override Hierarchy Routing check box on the account. We must have agreement from both ASMs via SFDC Chatter in order to move an account to a different owner than the Global Account rep. Split hierarchies will be reviewed annually to determine if they should be moved to the Global Account Rep at that time. - Considerations for transferring an account to a local rep: If the decision-making power, end users, PO and Terms (or a majority combination) are confined to the child account, the Ultimate Parent owner should hand off the account to the appropriate territory owner as this would be in the best interests of the customer and for GitLab. Follow the Exception Process to request Account Ownership Change.
An account that is being held by a Sales Rep that has been promoted or moved to a new territory. Holdover accounts will be marked using the Holdover Expiration date field. An account rep can only have a holdover account for 90 days. Any account that needs to be held over longer must have manager approval from both the requestor's current manager and receiving manager of the account owner.
An account that clearly has their own buying authority and purchasing process.
Holding Company Name
field. Ownership & segmentation will be based on the individual account attributes and NOT the Holding Company or PE account attributes.Accounts that are categorized as an independent Franchise or Consultant are considered standalone Accounts. As such, they will not be parented and the corresponding number of employees will not count towards the HQ Total Employee Count.
Accounts that have had employee count and/or address information updated that would require a region or segment change. Timing on when the account will move will follow the escalation process since there is a potential it could affect CSM and quota assignment.This includes changes to the Ultimate Parent details as a result of a merger, acquisition or move of headquarters. Accounts marked as Named or Key Accounts at the beginning of the year, will remain with the current account owner for the fiscal year.
Accounts created in Salesforce by a list load or through a data enrichment tool such as Zoominfo. Only Sales Operations has the ability to create new accounts because they must be parented and processed through LeanData to properly segment and assign to the appropriate territory. These will then be assigned to the correct account owner regardless of who requested or imported the account. Contacts will be linked by SDR’s during their normal workflow. For more information on this process you can check the Steps to create an issue for an account list import. To request a new account be created that is not from an enrichment tool or a list load please open an issue in the Sales Operations Project.
Sales Admin Owned Accounts: When new accounts are created due to web portal purchases, they are temporarily assigned to the Sales Admin User and are changed to the correct (and active) Sales User in the following cadences: - For accounts with known attributes (employees and location), the account gets routed to the correct owner via the Account Demographics process - For accounts without known attributes (employees and location not identified), the account is manually reviewed by Sales Operations twice weekly and assigned to the correct owner. - If Sales Operations is unable to identify enough attributes to correctly assign the account, it will remain in Sales Admin owned and allocated to SMB for crediting.
All Embargoed Accounts will remain in Sales Admin per ROE for Banned Countries
For Accounts where there's an OSS/EDU/Startups opportunity, ownership of that Account will remain with the active Field Sales (AE/SAE) member. However, the relevant Community Program DRI will manage the OSS/EDU/Startups relationship and will be identified in a separate field on the Account called Community Program Owner.
In order to ensure Rules of Engagement are being enforced the following fields will need to be updated by Sales Operations: Account Owner, Named Account, Key Account, Holdover Expiration Date along with the ability to create a Parent/Child. To request a change to any of these fields chatter on the account or if there are more than 10 accounts open an issue in the Sales Operations Project.
Any request to transfer an account for any reason must follow the outlined exception process and timeline.
Quarterly Review
in the Account Reassignment Status
field. Accounts that have CARR must be flagged to be reviewed at the quarter to review the sum of CARR on all of the AEs accounts requested to move.If the sum of CARR for all requested accounts is under $50K the accounts can be moved as agreed upon. If the sum of CARR for all requested accounts is over $50K Sales Operations will work with Sales Strategy to evaluate the potential impact on AEs quota and work directly with the ASM an accounts will remain with the current owner until a decision is made. Flagged accounts can be tracked in the Sales Ops: ROE Dashboard.Requested holdover accounts will have the expriation date and next approved owner populated 90 days from date of approval from all parties.These accounts are monitored on the Sales Ops: ROE Dashboard.
Holdover Expiration Date
field to the Proposed Account Owner
Accounts will be reviewed annually prior to the Fiscal Year planning process and territory carving.
Understanding Opportunity Assignment, Rules and Definitions
The following criteria make a deal eligible for a holdover:
Enterprise
Commercial
All Segments
Within a Region under one ASM (or acting ASM), it is the ASM's responsibility to obtain and document agreement in chatter between the two AEs in that region.
Within a Geo under one Sales VP, it is the Sales VP's responsibility to obtain agreement between the two ASMs in that Geo and document in chatter.
Holdover Expiration Date
fields on the Opportunity and are monitored on the Sales Ops: ROE Dashboard.Understanding Order Type Assignment, Rules and Definitions
Source of Data: The account attributes used to properly assign Order Type are defined and explained in the Sales Term Glossary section of the handbook.
Common Manual Override Scenarios: Although Order Type is generated automatically on an opportunity, there are common scenarios in which it could require updating via a manual override:
Process to Request Order Type Changes: In the event that Order Type needs to be changed, please chatter @sales-support on the opportunity with details as to why the change is being requested. This will trigger a case, which will be reviewed by the Sales Operations and Deal Desk teams.
Best Practices
Case Review Process
Holdover Expiration Date
for 90 days from date of approval on the Opportunity.Quarterly Review
in the Account Reassignment Status
field so the account will show up on the Sales Operations Quarterly Account Review DashboardQuarterly Account Review Process
Holdover Expiration Date
for 90 days from date of approval on the Opportunity.Quarterly Review
picklist value from the Account Reassignment Status
Holdover Account and Opportunity Review Process
Account Owner
and remove the date from the field.Holdover Expiration Date
after transfer of ownership (Note that this cannot be removed from accounts past stage 6)Annual Review Process
Order Type Review
Sales Admin Owned Review and Owner Change Process
Steps to add AE names to open/closed opps owned by Sales Admin (Easy Fixes)
Steps to add AE’s to Closed Opps and accounts owned by Sales Admin (Hard Fixes)
### Process to Request Updates to Territory Ownership
#### Territory Ownership (Sales)
/assign
command.Warning: Updating these tables without updating Operations will not be reflected in our various systems causing all reports and routing to be incorrect!
Questions? Ask in the #sales Slack channel and ping @sales-ops.