Please ensure you read the Commercial Sales onboarding page.
Below is a list of resources considered highly valuable for continuous learning and development by Commercial Sales team members at GitLab. Note that some of these resources are not publicly available, so consult a fellow teammate for access where necessary.
When traveling please consider ROI of both any costs plus your time: If you are going to an event you think first:
Given the rough calculation above, you've to be committed driving/booking enough Net ARR at the event prior to you going to the event Note: this doesn’t mean you can’t get travel approval without booking meetings. It means once you get travel approval it is on you to go get people to the event/meetings to create pipeline.
The ultimate purpose of attending any GitLab field event is to gain insight and add value. Sid Sijbrandij, our CEO, talks about the importance of conferences and events here. He believes the main goal of GitLab team participation should always be to connect with our customers and prospects and not to solely attend presentations. Trip notes are our internal process for tracking and capturing this data.
Trip notes are required for the entire Commercial Sales Team anytime a team member travels for the company while working at GitLab. We believe it would be fun and valuable if you also shared trip notes when you traveled for personal reasons; however, that is up to your discretion.
Please follow the best practice process and use the trip note template as a format to prepare for your future trip.
Customer AMAs: Meetings for GitLab team members with current customers that provide an opportunity to ask them about anything in regard to their experience with GitLab
Customer Meetings: Sharing the best practices for conducting any kind of external meeting at GitLab
Trip Notes: allows team members who attend field events to track and capture data in order for the rest of the team to gain insight
Doing Business with Partners/Channels: Guidelines on how to work with partners and resellers in order to ensure value is maximized in these areas
How to Handle New Customers After They Purchase: Best practices for handling new GitLab customers based on the scope of their purchase
Technical Evaluation of Customers: How to properly evaluate a customer’s current technical environment in order to create organizational alignment and prescribe how GitLab can best solve their problems
For a complete list of our Give Back Projects and other Onboarding assignments our team is working on, please click the private link here.
New team members should familiarize themselves with The Required 7. These are the 7 tactical skills required to be an excellent Commercial Sales Account Executive:
Channel-Managedin the opportunity title
A recording Chorus license is mandatory for all Commercial Account Executives. Our intent is to record customer calls for the following reasons:
Laws around recording differ from states to state and country to country. Therefore, it is required that every Account Executive take the steps below on every customer call. The Account Executive is responsible for ensuring the steps below are followed.
Failure to follow the above is not acceptable in any situation.
Allocate times of your day in four ways:
Next Stepsshould contain only the actions you will take next: no dates, no history, just the Next Steps
Next Steps, the
Next Steps Historywill automatically capture your prior
Next Steps, applying a date stamp and storing them in reverse-chronological order
Next Stepsfield, the next time you update
Next Stepsyou will need to clear the field completely and input only your Next Steps
It is required that all opportunities above $10,000 (Mid Market) and $5,000 (SMB) in total amount (not Net ARR) will have a custom slide deck that is shared with the customer or prospect. The custom deck must be attached to the opportunity by pasting the deck link in the SalesForce field 'Link to Custom Pitch Deck' on the opportunity home page. This will enable Mid Market Account Executives and SMB Account Executives to capture critical account information. Additionally, this will facilitate selling on value rather than features.
Customer Agreed-upon Agenda
Calculated ROI of GitLab v. Next Best Option
Two options (rough plans) with GitLab going forward
Non-Custom Single Application pitch to the customer
Full capture of the customer's feedback on the 'Single Application' slide
SMB Account Executives "SMB AEs" act as Account Executives and the face of GitLab for SMB prospects and customers. They are the primary point of contact for companies that employ between 1 to 99 employees. These GitLab team members are responsible for working new business in their territory as well as handling the customer journey for new and existing customers. SMB Account Executives will assist prospects through their evaluation and buying process and will be the customer's point of contact for any renewal and expansion discussions. Please read through the SMB handbook page for more information.
Zendesk: Managing incoming requests received through support.gitlab.com
The goal and focus of working Zendesk tickets for the SMB team is to help with upselling and renewals
Within timezone (WIP), the Support team is responsible to take the lead on all incoming ZD tickets in the Upgrades, Renewals, and AR (refunds) queue. In off-hours, the SMB team will triage and handle any tickets which will breach during their timezone.
Support will take the lead on all incoming requests in the queue and only forward to the sales owner when:
Note: if you need access to a system, open an Access Request
License Key Management for On-Premise Trials & Subscriptions
GitLab.com Trials & Subscription Management
First, forecasting, down to even the opportunity level, is a routine exercise for accuracy, not motivation or aspiration. Each week on Wednesday it is required to update five values in Clari by close of business (5 PM) local time. This is Renewal Loss Best Case, Renewal Loss Best Case, Gross Net ARR Best Case, Gross Net ARR Commit, and Net 50/50. At this time, it is required to double-check pipeline cleanliness and always follow the close date conventions listed here.
The three close dates:
Example: It's April 23rd, a new business Mid-Market opportunity is identified for a company at 410 employees and growing at an unknown rate (unclear due to being an agency). The company completed their evaluation with a trial ending this month, there are defined problems initially trying to solve, with some people who have used GitLab before.
Detailed instructions on how to handle problems with licenses and subscriptions can be found in these instructions and resources.
More information about sales order processing can be found in the Business Ops handbook section.
Midmarket Account Executives are the primary point of contact between prospective and existing customers of GitLab within a space defined as mid-market, which currently works with companies that employ between 100 to 1,999 employees. These GitLab team members manage the spectrum of project sizes, ranging from small fast growing teams in smaller agile organizations to complex enterprise projects advising on the journey with GitLab to achieve specific business outcomes.
Mid-Market AEs work closely in tandem with the business development team and sales management to manage a broad book of business spread over a large opportunity value range and focus on exceeding client expectations.
MM Key Accounts First Order AE (MMKAFO): These AEs work on the highest potential accounts that are not currently customers of GitLab. Once the customer has signed its first contract, the customer is transitioned to a MM Key Account Named AE. However, if an account is won by this team and is deemed to be low potential it will be passed to a MM Territory AE. The rough guideline for these accounts is more than 500 employees total and more than 100 combined employees in engineering and IT. We don't refer to MM First Order accounts as "Named Accounts", because First Order accounts can either go to Named or Territory AEs.
MM Key Accounts Named AE (MMKAN): These AEs work on current customers that have been deemed to be high spending (high CARR) or have the potential to be high spending (high LAM). To be successful the MMKAN AE must expand their accounts more than the standard expansion rate for their named list of accounts. The named list for each MMKAN AE will grow through the fiscal year as the MMKAFO AE wins new high potential customers.
MM Territory AE: These AEs work geographic regions of accounts that have not been vetted to be MM Key Account First Order AE or MM Key Account named AE. The role sells to both prospects and current accounts.
"MM Key Accounts" can be used to refer to MM Key Accounts First Order and MM Key Accounts Named collectively. MM Key Accounts are the sub-set of MM accounts with a higher LAM and potential LAM.
It's expected from the Commercial Sales Team to follow the Account Ownership Rules of Engagement This section provides step by step clarity on how to follow the ROE.
Account leveland cc VP Commercial Sales to review
Neverask the customer/prospect to provide information on the company size
It is a requirement for the Commercial Sales Team to tier their accounts using the fields on the Account Object. This helps prioritize the accounts to go after when prospecting for new or expansion. Please see below definitions specific to SMB and Mid-Market AEs.
Co-selling is the responsibility of both the Account Executive and their Area Sales Manager to join sales calls together. This is to ensure the best client/prospect experience, along with jointly finding the highest potential within that account. Area Sales Managers have an expectation to log a minimum of 5 co-selling calls per rolling 7 days, although we are aiming to achieve closer to 10-12 calls over a rolling 7 days.
The GitLab partner network is ready to work with GitLab Account Executive's in order to extend the customer selling and services capacity offered by Commercial Sales. Channel's approach to this is called Partner Co-selling and working with Partners involves building a simple, clear, mutual customer opportunity plan establishing “who will do what, when?”.
GitLab has a mature Partner network with good coverage of GitLab-trained Sales and Technical resources. There are a few ways in which AEs will work with a customer including a Partner.
email@example.com the link to the opportunity requesting quote-to-order support (chatter alias coming soon)
The Center of Excellence (COE) in the Commercial Sales context refers to the team's research and development of a particular focus area to drive new initiatives and improvements across the organization.
Why call it Center of Excellence?
Here are the past active topics for individual team members on COE alignment. This center in its first iteration started with the team's QBR in 2019.
Mid-Market Key Accounts First Order Team (MMKAFO) Tactics and Definitions
The MM Key Accounts First Order Team is comprised of Account Executives that work on the highest potential accounts that are not currently customers of GitLab. Once the customer has signed its first contract, the customer is transitioned to a MM Key Account Named AE. However, if an account is won by this team and is deemed to be low potential it will be passed to a MM Territory AE. The rough guideline for these accounts is between 500 and 1999 employees and more than 100 combined employees in engineering and IT. We don't refer to MM First Order accounts as "Named Accounts", because First Order accounts can either go to Named or Territory AEs.
It is the goal of this team to make the first transaction with GitLab:
After the first transaction is closed by the MMKAFO team, the First Order AEs are responsible to kickstart the handover process. Below are the responsibilities of the Mid-Market Key Account First Order team and the Mid-Market Key Account Named team.
Note 1: Once the account is handed off to the new AE, the new account owner is responsible for the success of the account. This includes any troubleshooting, support, ticket escalations, etc. The exception to this will be if there are any billing issues that arise on the initial order. Because billing issues related to the first order are assigned to the account owner. In some cases, the First Order AE can better fix such problems. In these cases, Named AE can re-assign the issue to the First Order AE for resolution.
Note 2: If a First Order account is deemed to have low potential (fewer than 100 total users), it should be assigned to a Mid-Market Territory Account Executive. If in question, the First Order AE should involve their ASM, Regional Director, and VP of Commercial to determine if the account should be assigned to a Mid-Market First Order AE or a Mid-Market Named AE.