As a Sales Development Representative (SDR), you focus on outreach, prospecting, and lead qualification. To do so, you need to have an understanding of not only product and industry knowledge, but also sales soft skills, and internal tools and processes. This handbook page will act as a guide to those topics as well as general information about the SDR team.
Please acknowledge any Slack messages from your managers in your Slack channels, if you have nothing to say at least be creative and funny with emojis so that they know that you are seeing their requests and updates and are talking to an empty room!
SDR Issue Board: used to track relevant GitLab issues involving the SDR team. This is a global issue board and will capture all issues in any group/sub-group in the GitLab.com repo when any of the following scoped labels are used.
SDR Event Tracker: used to track upcoming events globally.
SDR- issues concerning the SDR team. This label will typically be removed and changed to one of the below labels once accepted by our team.
SDR::Priority- projects that we would like brought into RevOps meeting for feedback/next steps from other teams
SDR::Planning- Discussion about next steps is in progress for issues concerning the SDR team
SDR::In Progress- SDR action item is presently being worked on
SDR::On Hold- SDR project is put on hold after agreement from SDR leadership team
SDR::Watching- No direct SDR action item at this time, but SDR awareness is needed for potential support/questions
SDR::Enablement Series- Label to track and monitor upcoming topics for the SDR enablement series. All of these issue roll up to this epic.
SDR::AMER Event Awareness- Americas SDR awareness is needed for potential support/questions in regards to events
SDR::APAC Event Awareness- APAC SDR awareness is needed for potential support/questions in regards to events
SDR::EMEA Event Awareness- EMEA SDR awareness is needed for potential support/questions in regards to events
SDR Pub Sec- PubSec SDR awareness is needed for potential support/questions in regards to events
SDR West Staff Request- Utilized when a West SDR needs to be assigned to an issue
|SDR onboarding page|
|Sales handbook page|
|Sales resources page|
|Go to Market page|
|SDR Manager resources page|
|SDR job family/levels|
In your first month at GitLab we want to help ensure you have everything you need to be successful in your job. You will go through enablement videos, live sessions and activities covering a wide range of getting started topics.
The SDR team will conduct enablement and training on a wide range of topics such as workflow/processes, campaigns, alignment with other teams, tool training, product training, etc. SDR enablement sessions are scheduled on an as needed basis and will be made available for SDR teams to consume asynchronously.
To view previously recorded SDR Enablement content, you can view the SDR Enablement Video Library here
As part of your onboarding, you will begin an SDR Technical Development course with our Senior Sales Development Solutions Architect. The goal of this course is to enable you to be more comfortable having technical discussions - specifically when it comes to GitLab’s use cases. Each level of the course is tied to our levels in the SDR role.
One of our Values is being handbook first. In order to align the SDR organization more closely to this ideal, below are suggested steps. Please remember that the Handbook is a living document, and you are strongly encouraged to make improvements and add changes. This is ESPECIALLY true when it comes to net new solutions that should be shared so that the whole organization has access to that process. (aka The DevOps ideal of turning "Localized Discoveries" into "Global Knowledge".)
|SDR job family||Information on the SDR role and requirements for level progression|
|SDR onboarding page||Overview of SDR onboarding that includes an overview, process, expectations, and manager responsibilities|
|SDR Manager resources page||SDR Manager resources & links|
|SDR Territory Alignment||This document is currently the single source of truth for SDR/Territory Alignment|
|Enterprise SDR Outbound Process Framework||Outbound process framework for the Enterprise SDR team. Note: These vary by team and geo|
|SDR Outreach Sequence Library||Approved Outreach sequences for GitLab value drivers, use cases, personas, and campaigns|
|SDR Enablement Videos||Enablement videos and how-tos for SDRs|
|Marketing Resource Links||GitLab whitepapers, ebooks, webcasts, analyst reports and more for Sales & SDR education|
|Marketing Events + Gated Content Assets + Webcasts||SDRs can use this sheet to refer better understand the marketing assets that are being consumed by prospects. To view the ungated content, click on the link in the Pathfactory or PDF/YouTube columns. Note: Sharing non-gated assets requires SDR manager approval|
|GitLab Buyer Personas||Resource to help GitLab sellers better understand our buyers and audiences|
|Sales handbook page||GitLab Sales team handbook|
|Sales resources page||Link to the Sales quick reference guide with links to learn more about the various sales teams & initiatives|
|Weekly sales enablement||These sessions take place every Thursday and SDRs have an open invitation to participate|
|Go to Market page||Link to GitLab's go-to-market strategy including: definitions, processes, and record management|
|Sales Training handbook page||Link to GitLab sales training|
|Command of the Message||"Command of the Message" training and the GitLab value framework|
|Most commonly used sales resources||Sales resources page|
|Flash Field newsletter||Learn more about sales' weekly newsletter|
The SDR team aligns to the Commercial and Large sales teams. These teams are broken down into three segments: Large, Mid-Market and SMB which are based on the total employee count of the Global account. *Note: The commercial sales team includes both Mid-Market and SMB. This segmentation allows SDRs and Sales to be focused in their approach and messaging. The segments are aligned to a region/vertical and then divided one step further via territories in the regions. Our single source of truth for determining number of employees is DataFox followed by Zoominfo.
SDR Team Breakdown
Geo = SDR teams that align directly to sales territories and AE/SALs that work a geo territory
* EMEA Commercial (MM & SMB)
* EMEA Enterprise
* AMER SMB
* AMER Mid-Market
* AMER West Enterprise
* AMER East Enterprise
* AMER Named East Enterprise (includes LATAM Enterprise)
SDR quota is made up of the following depending on sales segment:
Activity & Results Metrics
While the below measurements do not impact your quota attainment, they are monitored by SDR leadership.
As an SDR, you will be focused on leads - both inbound and outbound. At the highest level, a lead is a person who shows interest in GitLab through inbound lead generation tactics or through outbound prospecting.
SDR Assignedfield, lead routing, Drift alignment/team
What is considered a Qualified Meeting?
A Qualified Meeting is a meeting that occurs with a prospect who is directly involved in a project or team related to the potential purchase of GitLab within a buying group, either as an evaluator, decision maker, technical buyer, or influencer within an SDR Focus Account. To be considered qualified, the meeting must occur (prospect attends) and new information must be uncovered that better positions the SAL and Regional SDR to create an SAO with that particular account based on the SAO Criteria as stated in the handbook. The Required IQM Fields must also be populated in order to receive IQM meeting credit.
Qualified Meeting Process
A “New Event” IQM gives an SDR the ability to track every meeting that is scheduled and held in Salesforce without having to prematurely create a net new opportunity. SDRs can tie any event (IQM) to an existing account, opportunity, etc. The purpose of creating an IQM in salesforce is to provide the ability to track how many IQMs are being created per SDR and what the results are of these IQMs.
The purpose of creating an Initial Qualifying Meeting (IQM) in Salesforce is to track top of funnel pipeline meetings that are booked, occur, and convert to Sales Accepted Opportunities (SAOs). SDRs can track every meeting that is scheduled and held in Salesforce without having to prematurely create a net new opportunity prematurely. SDRs can tie any IQM to an existing account or opportunity from a Lead or Contact record.
How to create an IQM in SFDC
Within Salesforce there is a button titled “New Event” which you can access in the global actions bar on your Salesforce “Home Screen”, and in the “Open Activity” section of any Lead, Contact, Account, and Opportunity record. This image will show you where to click!
If creating an Event: IQM under a Lead or Contact record, click the event button in the global actions bar and complete all relevant fields which should include your pre-IQM notes in the description field.
Once a meeting with a prospect is confirmed, the SDR will send either a Google calendar invite to the prospect (include their SAL) and/or send a meeting in Outreach.io with a proposed agenda. SDR should share Event IQM SFDC link with SAL prior to IQM occurring - scheduling a pre/post IQM sync is best practice.
Once the IQM occurs, then the SDR can add their Post-IQM notes to the Description Field and update the Event Disposition accordingly. If the IQM meets criteria and has next steps, then it's an SAO and the SDR should convert Lead to Contact record and create new opportunity with same process as outlined in Handbook. If the IQM occurred and the SDR/SAL/AE uncovered helpful information but ultimately, there are no next steps, the the SDR should disposition Event IQM as Qualified Meeting (do not create a new opportunity). If Event IQM was a no-show and/or needs to be rescheduled, then SDR owns reaching out to prospect to reschedule and dispositions Event IQM accordingly.
How to Create an IQM in Outreach
In Outreach, you have the ability to book a meeting directly from a prospect overview. Even better, this can be done while you’re on a call with a prospect or immediately after without having to leave Outreach.
Select “book meeting” from the prospect actions menu. For a visual/video walkthrough of this process take a look here.
Note: Booking a meeting from Outreach will automatically pull the following fields directly into an SFDC event object:
The following fields are required and should be updated in real-time as IQMs are scheduled, occur, and convert to SAOs.
The GitLab marketing team uses digital channels - social media, email, mobile/web apps, search engines, websites, etc - as well as in-person marketing activities to meet potential buyers where they are. When people interact with GitLab, we use lead scoring to assign a numerical value, or points, to each of these leads based on their actions and the information we have about them. Once a lead reaches 90 points, they are considered a Marketing Qualified Lead or MQL.
SDRs are responsible for following up with MQLs by reviewing their information, reaching out, and working with them to understand their goals, needs, and problems. Once you have that information, you can use our qualification criteria to determine if this is someone who has strong potential to purchase our product and therefore should be connected with sales for next steps. As you are the connection between Marketing and Sales you want to make sure every lead you pass to the Sales team is as qualified as possible.
These MQLs will show up in your lead views in Salesforce. The views, listed below, allow you to see your leads in a categorized way to simplify your workflow. Leads are routed to you and flow into your views via the tool LeanData which takes each lead through a series of conditional questions to ensure it goes to the right person. Even though all SDRs leverage the same views, they will only show you leads that have been specifically routed to you. You will be responsible for following up with all of the leads in your MQL views by sequencing them using Outreach.io. Once sequenced, their lead status will change and they will move from your MQL views allowing you to have an empty view. Managers monitor all views to ensure they are cleared out. If you choose not to work a lead please unqualify it and state your reasons in the lead record.
My Inquiries (ALL): All Inquiry leads assigned to the SDR will appear in this view, based on the SDR's SFDC login
My Inquries (Job Title): This view filters Inquiry leads based on key job titles. It also filters by the lead's activity in the
last 60 days
My Inquiries (Person Score): This view filters by lead activity in the
last 60 days, by if a lead has a
Behavior Score greater than or equal to 30 pts, by if a lead has a
Demographic Score greater than or equal to 15 ptsand lastly if a lead is in
Inquirystatus. Please note this view will become more useful over time and after score degradation has been active for longer (current as of Dec 2020)
Matched Account GTM Strategyof:
Account Based - Net New
Mobilefields, have activity within the
last 60 daysand have not given an adequate Nurture reason
Lead/contact statuses allow anyone in Salesforce to understand where a lead is at in their journey. The automation mentioned below is all done through an Outreach.io trigger.
Inactive contactcheckbox, signifying that this person no longer works at the company, any running sequence will automatically be marked as finished.
IMPORTANT: For Mid Market SDR reps, if the account your lead matches has the account type 'customer,' this lead will need to be worked by your aligned AE. Update the lead owner and tag them in Chatter if they have to action the lead. You can determine this via the LeanData section in Salesforce or by leveraging the 'Find Duplicates' button at the top of the lead in Salesforce. Look to see if the account this lead belongs to has a CARR value (total annual recurring revenue this customer brings) associated with it. Lastly, you can search for the account to look for the CARR value. Convert the lead to a contact and attach it to the customer account on conversion, this will hand the lead over to the AE and remove it from your lead view.
Find Duplicatesbutton at the top of the lead page. The Find Duplicates page lists Matching Accounts where you might find the
SDR Assignedor otherwise the Account Owner to determine which SDR the lead should go to.
SDR Assigneduser is acceptable.
Outreach & Marketo
If the lead is yours to work based on all of the above, sequence them in Outreach using the master sequence that correlates with the Last Interesting Moment. You can also look at the initial source and Marketo insights to get a holistic view of what a lead is looking into. There is an Outreach collection of sequences for inbound leads for each region. These collections contain a master sequence for nearly every inbound lead scenario.
Technical questions from leads?
Qualification criteria is a minimum set of characteristics that a lead must have in order to be passed to sales and become a Sales Accepted Opportunity (SAO). You will work to connect with leads that you get a response from to obtain this information while assisting them with questions or walking them through how GitLab might be able to help with their current needs. The qualification criteria listed in the linked handbook page below aligns to the 'Qualification Questions' sections on the LEAD, CONTACT, and OPPORTUNITY object in Salesforce. In order to obtain an SAO you will need to have the 'required' information filled out on the opportunity including documented 2-way communication on the Contacts in the Opportunity.
When a lead meets the qualification criteria and you have an IQM/intro call scheduled with your AE/SAL, you will convert the lead to an opportunity.
The end user account determines the SDR alignment: If you are the SDR assigned to the 3rd party lead, please gather the information in point 1 and pass the lead to the correctly assigned SDR (the SDR assigned to the end user account) who will complete points 2-6
We use a the chat platform Drift to engage site visitors. As an SDR, you are expected to be active on Drift throughout your work day. The tool's handbook page will walk you through guidelines, best practices and troubleshooting.
The Community Relations team owns GitLab's Education, Open Source and Startups programs. When a lead fills out the form to apply for one of these free community programs, Salesforce
Lead ownership will automatically change to the
Community Advocate Queue. If this Lead was in an Outreach sequence, it will automatically be marked as finished.
The Community Operations team (a sub-team of Community Relations), and the Program Managers for each program, will then work to qualify the lead. If the Lead does not end up qualifying for one of the programs, they will be passed straight to sales.
@Christina Hupyand for OSS and Startups:
Outbound lead generation is done through prospecting to companies and individuals who could be a great fit for our product. Prospecting is the process of finding and developing new business through searching for potential customers with the end goal of moving these people through the sales funnel until they eventually convert into customers.
You will work closely with your dedicated SAL or AE to build a strategy for certain companies; or parts of your territory or personas you as an aligned team want to focus on. It is crucial that you are very intentional and strategic in your approach and always keep the customer experience in mind. When reaching out, offer value and become a trusted advisor to ensure we always leave a positive impression whether there is current demand or not.
You can focus on Closed Lost Opportunities once they are older than 30 days, in line with the Sales Handbook Opportunity Stages
You can focus on Leads 60 days after the date of their last hand-raising activity if you inherit a geo/region Active vs. Passive
Focus account: an account in which you as an SDR have developed an account plan with your AE or SAL and are actively focusing on via outbound prospecting.
Focus Accounts should be kept up-to-date in Salesforce in real-time, the SDR Target Account box checked as soon as you begin the account planning process. If the account does not have activity associated with leads/contacts over a 30-day period, the account should no longer be focused on and the SDR Target Account checkbox should be unchecked.
If you check the targeted checkbox, you are committed to:
The SFDC prospect database is split into five segments: Core users, free GitLab.com users, trial prospects, current customer "leads" and other prospects. We have checkboxes for these, most of which will automatically populate. However, the
Core User checkbox in Leads and Contacts needs to be checked by the SDR or Sales rep once the prospect has confirmed in writing or on the phone that they are using Core as we cannot rely on our product analytics alone as it does not cover all users.
IMPORTANT: EMEA reps, old leads/contacts for EU nations can only be called or emailed if they were in our system from May 2018 or later. Any lead/contact that was brought into our system prior would need to opt in to communication. Any new leads/contacts can only be called or emailed if they have been brought in from ZoomInfo. You can also leverage LinkedIn Sales Navigator.
The SDR outbound framework (sample is linked) will walk you through both strategy and execution of outbound prospecting.
Persona-based Messaging: Used for focusing on specific titles or personas
Business Resilience Messaging Revamped value driver messaging for companies impacted by the pandemic
Value Driver Messaging: Developed to align to the GitLab value framework
The SDR team will assist the Field Marketing and Corporate Marketing teams with campaign and event promotion and follow up. Learn more about Field or Corporate Marketing via their linked handbook pages. When these teams begin preparing for an event, they will create an issue using an issue template. Within that template is a section titled ‘Outreach and Follow Up’ for the SDR team to understand what is needed from them for each event.
When our Field Marketing Managers (FMMs) begin preparing for an event or micro campaign, they will create an issue using a regional issue template. If they need SDR Support they will open an SDR Request issue and the FMM will loop in the appropriate SDR manager(s) on this issue as well as fill out/ensure the following sections are accurate:
Once the sections are populated and up to date, the SDR manager is looped in. They will then elect an SDR with bandwidth to begin completing the steps in each of the above sections. The SDR will:
The corporate process is the same as the field process detailed above with the exception that they have a separate issue when looping in the SDR team for assistance that will link to the larger event issue.
Event Follow Up
SDRs have found particular success when organizing campaigns alongside regional Field Marketing Managers to ensure repeatable tactics and measurable results. The workflow below outlines what that process would entail should it be determined that you leverage this motion.
Step 1: Speak with your SDR Manager to identify the Field Marketing Manager (FMM) assigned to your SAL’s & AE's/Territory/Targeted Accounts. Set meeting with FMM to discuss existing Campaigns in motion, your ideas for Campaigns, and previously successful Campaigns (15 minute meeting over Zoom). Example of a Successful Campaign
Step 2: Once you've identified a Campaign to launch, working closely with your FMM (FMM will create an Issue in GitLab related to the campaign), and go into Salesforce Reporting to generate a targeted Contact list for the campaign.
Workflow for creating a Salesforce report (Screenshots below): Go to Reports -> Create New -> Make a Report under Contacts & Accounts -> Add Fields (SDR Assigned equals SDR Name & Title Contains: Software Development, DevOps, Engineering, Security, Operations) -> Custom Date Range = from: last two years up to: the last two weeks (see example) -> Run Report Please note, you can use this same Report workflow for generating a Lead Report. Simply select Leads from the New Report Options. Before you run the Report, please make sure that the Report Options -> Show is showing All Contacts/All Leads not My Contacts/My Leads by clicking the drop down and selecting All Contacts/Leads.
Insert Screen Shot
Save your Report by clicking the Save As tab. Make sure to Save Report under Sales Development Representatives folder and add a Unique Report Name (see example)
Insert Screen Shot
Add Campaign name from SFDC Campaign that is listed in the Field Marketing SDR specific Issue. Example: 20200909_TShirtSurveyOutreachCa -> Member Status = Member -> Click Add.
Insert Screen Shot
Your Report for your FMM Campaign is now complete! Keep your Unique Report Name in mind for when you upload Report to Outreach (see Step 4).
Step 3: It's time to generate content for your Campaign in Outreach. Note, if the Campaign previously ran, use existing content (FMM will confirm). Otherwise, work with your FMM and SDR Manager to delegate the resources you need to create content for the Campaign. Outreach Campaign Example
Step 4: Bulk add Contacts or Leads pulled from Step 2 to the Campaign in Outreach (ensure Campaign content is revised and reviewed by SDR Manager and FMM). Workflow for Bulk Creating a SFDC Report in Outreach for Sequencing: In your Outreach 360 view, in the top left corner select Actions -> Select Bulk Create -> Select SFDC Report and type in your Unique Report Name
Insert Screen Shots
Select Next, then re-map any missing fields. Once Report is Uploaded and you are in Prospect View, select the Prospects you want to Add to Sequence and then add to the Campaign Sequence. You have now uploaded your Target Contact or Lead List SFDC Report into Outreach and Sequenced List into Campaign for Outbound prospecting!
Step 5: After Contacts or Leads are loaded into the appropriate Campaign Sequence, alert your Manager and FMM in the appropriate issue for review before activating (FMM approval recommended to start Campaign in Outreach).
Step 6: Check the Campaign daily in Outreach throughout duration to ensure all tasks are completed. Provide updates in the Issue created in GitLab by the FMM related to the campaign (updates can include IQM conversion rate, Open rates, IQM to SAO conversion rates, etc.)
Step 7: Upon commencement of the Campaign, post a final update in the Issue that includes your results (updates can include number of IQMs, Open rates, IQM to SAO conversion rates, etc.)
Step 8: Recommended to schedule 15 minute meeting with FMMs to recap Campaign and provide feedback (this meeting can focus on final results, and if Campaign should stop, continue, or be revisited in the future).
Optional Post Event Follow Up: Continue to monitor Contacts and Leads uploaded into the Campaign for lingering results (there are sometimes stragglers on Campaigns that respond after the Campaign has concluded). An easy way to monitor is setting one or two tasks in Outreach for 2 weeks and 4 weeks after the Campaign has concluded.
Account-based marketing (ABM) is a marketing strategy in which a company identifies key accounts that they want to pursue. Unlike traditional marketing efforts, instead of focusing on an individual, an ABM strategy focuses on an entire company, treating each account as its own market.
The SDR team is a CRITICAL part of account-based marketing. Without SDR's hard work and account knowledge, ABM efforts would stall. In an Account-Based Marketing world, the total number of SDR activities (calls/e-mails) may decrease, but the relevance and personalization of interactions increases significantly. With SDR customization and careful prospect handling mixed with ABM marketing efforts, we will be able to land and expand our account list.
Learn more about ABM at GitLab by going to the Account Based Marketing handbook page!
The ABM team has created three Outreach Sequence templates based on our research and work with consultants that can be found in the ABM folder in Outreach. These templates are meant to be cloned to ensure settings and steps carry over. Once cloned, feel free to use the content from other sequences to populate your cloned sequence but please ensure you leave manual step types for additional personalization. The main priority is having the correct steps and number of steps that align with the template use case. The three templates are as follows:
When working with an ABM account, SDRs are expected to thoroughly research these accounts and develop a strategy. The following topics should be researched and documented in Salesforce for each focus account:
Uncover general account information
Review history with GitLab
Understand intent and buying signals
Discover the right prospects
Know your vertical(s)
Work with Sales to determine and documented outreach strategy
Note: It is the responsibility of the SDR to coordinate and document outbound plays, tactics, and to ensure that all communication with accounts and prospects is logged or documented.
If you have an ABM account, you will need to follow this outbound workflow to ensure we are properly measuring and tracking all outbound efforts. There is also an unfiltered YouTube playlist that walks you through the tooling workflow step by step.
Discovering new prospects is an important part of ABM account development. In order to do this in an efficient and organized manner, we recommend using the Focus Persona Segments and process listed below.
Please note: these should be imported as LEADS, not contacts
|Team||Account Set||Marketing Support & Strategy||SDR Outreach & Strategy||Outbound Leads||Inbound Leads|
|Named SDR||~30 accounts / SAL. Specific accounts owned and worked by the designated SAL and paired SDR regardless of corporate headquarters.||Marketing tactics and events drive MQLs to SDRs. SDRs align with marketing to craft specific messaging based on marketing tactic.||Focus on net new account-centric and persona-based outreach based on sales alignment to educate and create internal champions that align with the GitLab value drivers and use cases.||Gather specific prospects in ZoomInfo and LinkedIn Sales Navigator based on GitLab's role and persona information.||Receives inbound leads based on account alignment as listed in account set column.|
|Geo SDR||All remaining accounts. Alignment is a mix of territory-based, account-based, and round-robin depending on team and region.||Marketing tactics and events drive MQLs to SDRs. SDRs align with marketing to craft specific messaging based on marketing tactic.||Focus on net new account-centric and persona-based outreach based on sales alignment to educate and create internal champions that align with the GitLab value drivers and use cases.||Gather specific prospects in ZoomInfo and LinkedIn Sales Navigator based on GitLab's role and persona information.||Receives inbound leads based on account alignment as listed in account set column.|
We currently have 3 SDR's focused on supporting the PubSec ISR's in the US. Their alignment is as follows:
|Evan Mathis||National Security Group (NSG 3-6)|
|Evan Mathis||Civilian (Brandon Brooks onboarding/shadowing)|
|Evan Mathis||State, Local, Edu (SLED)|
|Josh Downey||Department of Defense (DoD Agencies/Army/Navy (Brandon Brooks onboarding/shadowing), Airforce)|
|Josh Downey||National Security Group (NSG 1,2)|
|Josh Downey||Systems Integrators (SI)|
PubSec SDRs have a different workflow from other SDRs in that they do not convert leads into opportunities. They input qualification notes on the lead record after their intro call and then set up the IQM with the ISR. The ISR converts the lead into the opportunity to ensure the opp is assigned to the correct account. Once the ISR has determined our SAO criteria has been met, they are responsible for putting the SDR on the opportunity and moving the opportunity into discovery.
The PubSec SDRs will work closely with PubSec FMM's and MPM's on pre and post event outreach. For events that are limited in attendance capacity, the PubSec ISRs will own pre and post event strategy, not the SDR's.
SDR PubSec Issue Board - used to track relevant GitLab issues involving the PubSec SDR team. This is a global issue board and will capture all issues in any group/sub-group in the GitLab.com repo when any of the following scoped labels are used.
SDR Pub Sec- Issues concerning the PubSec SDR team. When PubSec FMM's/MPM's add this tag to an event, these issues will appear on our board. When applicable, the PubSec SDR manager will create a SDR follow up issue and relate it to the event issue so that marketing members can easily track our work.
SDR Pub Sec:: FYI- Needs attention.
SDR Pub Sec:: In Progress- Related work needed is in progress.
SDR Pub Sec:: Completed- Related work is completed and ready for SDR manager to review/close.
SDR Pub Sec:: Revisiting- Campaign is being revisited and additional outreach is being done.
SDR Pub Sec:: Evan FYI- Issues pertaining specifically to Evan.
SDR Pub Sec:: Josh FYI- Issues pertaining specifically to Josh.
The Enterprise Named SDR team (Amer-based) is responsible for creating qualified meetings and sales accepted opportunities for Strategic Named SALs. Their focus is on Large ‘Named’ accounts with a land and expand strategy. The team is composed of SDRs who focus on account-centric, persona-based outreach, strategic outbound prospecting, social selling and creative outreach to educate and create internal champions that align with the GitLab value drivers and use cases.
|Named SDR||Ryan Kimball||Josh Rector, David Wells, Patrick Byrne|
|Named SDR||Matthew Macfarlane||Sean Billow, Chip Digirolamo, Jordan Goodwin|
|Named SDR||Steve Cull||Larry Biegel, Mark Bell|
|LATAM Enterprise SDR||Leo Vieira||Jim Torres, Carlos Dominguez|
AMER Named SDR
Named SDRs are responsible for:
Named East SDRs should be in constant communication with the SALs that they support. When taking on new accounts or supporting a new SAL, it is the responsibility of the ABM SDR to set up a kickoff call to:
Recurring SAL<>SDR meetings can be scheduled or take place on an as-needed basis.
Slack is encouraged for informal communication, but anything related to strategy, approach, or outreach should be documented.
Account Scoring & Prioritization
The next step after identifying all of the Net New focus accounts in a region is to prioritize them. The scoring model below should be used to determine the Net New Account Tier which will help guide prioritization and prospecting efforts using the Outbound Prospecting Framework (below).
A Tier Accounts - Have at least 4 out of 5 qualifiers below
B Tier Accounts - Have 3 out of 5 qualifiers below
C Tier Accounts - Have 2 out of 5 qualifiers below
D Tier Accounts - Have 1 out of 5 qualifiers below
F Tier Accounts - Have 0 out of 5 qualifiers OR zero direct revenue potential in the next 3 years
Account Scoring Qualifiers:
Outbound Prospecting Framework
|Tier||Goal||Priority Level||Outbound Tactics|
|A Accounts||Conversations, IQMs, MQLs||High (60% of focus)||Hyper-personalized, simultaneous outreach, creative, direct mail, ads, groundswell, events|
|B Accounts||Conversations, IQMs, MQLs||High (30% of focus)||Hyper-personalized, simultaneous outreach, creative, direct mail, ads, groundswell|
|C & D Accounts||Conversations, MQLs||Low (< 10% of focus)||Automated role- / persona-based outreach, groundswell|
|F Accounts||Eliminate from SDR focus account lists||Low (< 2% of focus)||Do not focus on or attempt to qualify|
Hyper-personalization - This is the concept of combining real-time data extracted from multiple sources to create outreach that resonates with prospects on an individual level. The desired outcome is to establish relevance with a prospect as a first step towards a conversation.
VIP (prospect) - A Very important top officer, executive buyer, C-level prospect, or important influencer. For these individuals, hyper-personalization is required. Examples: CTO, CIO, CSIO, C-level, IT Business unit leads, VPs, strategic project leaders.
Influencer (prospect) - An individual prospect that is suspected to be involved with IT decision-making, tooling, teams, roadmap, strategic projects, and/or budgets. Examples: Director or Manager of DevOps / Engineering / Cloud / Security, Enterprise Architects, IT buyers, SysAdmins, purchasing managers, and product owners.
User (prospect) - A prospect that has limited influence within an IT organization. Examples: Developers, Engineers, QA, consultants, and business users.
Groundswell - An outbound strategy focused on filling the top of the funnel by generating engagement, opt-ins, MQLs, and uncovering intent signals. This strategy typically incorporates more automation than other more direct outbound prospecting tactics. The strategy should be used with lower-level prospects and lower tier accounts.
Snippets - Content created for SDRs to use to create hyper-personalized sequences, one-off emails, or to use for reaching out to prospects via LinkedIn.
Warm Calling - The method used to strategically incorporate phone calls and voicemails into an outbound prospecting workflow. The idea is optimize outbound productivity by only using the phone to call engaged, validated, and/or VIP prospects.