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

SDR Sales Alignment

  1. You are here:
  2. Handbook
  3. Marketing
  4. Revenue Marketing
  5. Sales Development
  6. SDR Sales Alignment

Purpose / Objective

The purpose of the Global Sales-SDR Alignment Framework is to provide an outbound guideline that helps identify goals, provide better alignment, and highlight expectations for both the Sales Development Representative (SDR), Strategic Account Leader (SAL)/Account Executive (AE) and Inside Sales Representative (ISR).

The alignment framework is designed to facilitate a successful relationship between SDRs and Sales ensuring both are properly positioned to achieve their goals. Reference: Sales Development and Sales page in Handbook for additional details.

Goals / Targets

Criteria for Sales Accepted Opportunity (SAO)

Enterprise (Sales Segment = Large and Named) SDRs have Quarterly targets composed of SAOs, Qualified Meetings and IACV Pipeline Contribution. Commercial (Sales Segment = Mid-Market &/or SMB) MM SDRs have quarterly targets composed of SAOs and IACV Pipeline Contribution, while SMB and PubSec SDRs have monthly SAO targets. Ramping SDRs have a target of 0 in their first month (onboarding/building foundation), 50% month 2 and then 100% in month 3 (considered fully ramped).

SAOs will come from both inbound and outbound leads and activities. See [SDR Compensation and Quota] (/handbook/marketing/revenue-marketing/sdr/#sdr-compensation-and-quota) for more details around SDR targets. SDRs will be required to qualify inbound leads and outbound contacts, leverage Force Management Command of Message principles, create Initial Qualifying Meetings (IQMs), update Salesforce (SFDC) with all notes/next steps and introduce the Sales into opportunities.

When and if an opportunity is accepted and moved to SAO but later needs to be merged to a larger parent opportunity within an account, the sales executive should follow these steps: Move Opportunity to Stage 8-Closed Lost. Select Closed Lost Reason as Merged into another opportunity and select Save. Once saved, copy and past the parent opportunity (one that it was merged into) into the Closed Lost Details field on the opportunity

SDR & Sales Alignment

Expectations and Strategic Process

Communication

Required: Weekly SDR-Sales Sync Meeting - Historically, our SDR/Sales pairings who have incorporated this meeting into their week, have been the most successful at driving new pipeline. Ideally, in the first sync, SDR and SAL create working agreement and share expectations and team goals.

  1. Schedule a 30 min - 1 hour weekly meeting. The purpose of the meeting is to strategize on account plans for outbound prospecting, review lists of key personas, discuss messaging approach, as well as discuss inbound traffic, review inbound lead flow, etc.
  2. Proposed Agenda for weekly syncs:
    1. SDR Inbound lead flow review (MQL, Qualifying and Inquiry fields) and Outbound ICP’s actioned and Outreach sequence review. What traction has been made at prioritized accounts? Any roadblocks?
    2. Sales review personal traction at prioritized accounts, review existing Opps, roadblocks, etc.
    3. Discuss any upcoming IQMs and IQMs that should be SAOs but are still in “pending” status
    4. Discuss any SAOs that have gone dark (Sales has made at least 6 attempts to contact: 3 calls/3 emails)
    5. Field & Corporate Marketing Issue Board review/plan
    6. Items to review/follow up on at next sync (SDR and Sales action items)
  3. For the first initial team meeting, create a working agreement and weekly agenda outline that the SDR and Sales can agree upon.
    1. Best Practice: SDR and Sales connect 10min pre-IQM to review notes and connect post IQM for a brief retro to discuss notes, follow-up and SAO status.
    2. Highly Encouraged, but not required is for SDR or Sales to create a Slack channel and invite the SDR, Sales Executive, Area Sales Manager, SDR Manager, Solutions Architect, and Technical Account Manager. The purpose of this channel is to have high-level communication regarding leads and opportunities as well as discuss questions.
    3. Please use chatter in SFDC to communicate changes and requests on existing opportunities.

Process Workflow

  1. SDR to nurture and qualify all inbound MQLs in their territory. Discuss lead flow with your Sales Executive.
  2. SDR to prospect into target accounts and provide Sales with updates/traction. SDR should share lists of key personas (ICP’s) being inputted into Outreach for prospecting.
  3. Sales should provide feedback on outbound Outreach.io sequences that SDR creates.
    1. Please note: SDRs do not create quotes, directly manage accounts and should not get stuck on a small list of accounts for too long.
  4. SDR to seek guidance and direction from Sales in regards to both inbound and outbound leads that the SDR is qualifying.
    1. Review and apply CoM principles
    2. A/B Testing in Outreach sequences
  5. SDR to review regional field marketing campaign board with Sales to form a strategy on how to best leverage recent and upcoming events.
    1. Field Marketing worldwide view: to find your regional view, please use the menu bar in the upper left corner of the board view
    2. SDR: Field Marketing Event Outreach & Follow Up
    3. Preparing for Field Events
  6. SDR to inform Sales of pending SAOs (in meeting and/or SFDC chatter)
  7. Review status of pending IQM’s, qualifying leads, target accounts the Sales has provided the SDR, SDR outbounding activities, and marketing events.
  8. SDRs should always aim to attend the initial meeting (IQM) so they can introduce the prospect to the Sales team (when possible, Chorus notetaker should also be included). If for some reason the SDR can not join, this should be communicated to the Sales team in advance. The SDR will be responsible for:
    1. Prior to IQM, the SDR should share any Pre-IQM notes with SAL (for Large/Enterprise SDRs please share IQM Event links with SALs). Start of IQM: Greet all guests and explain Chorus. "Hi, I'm sure you see GitLab notetaker on this call. We use a tool called Chorus that aids us in note taking and for training purposes. Do you have a problem with our call being recorded? I can always turn the recording off."
    2. The SDR should begin the meeting by recapping what they have discussed so far with the prospect, reviewing proposed agenda items that were included in the calendar invite and introducing the Sales Executive who will dive deeper into qualification/discovery.
    3. SDR assists with making sure the last 5 minutes of the meeting is reserved for setting up next steps.
    4. SDR responsible for updating opportunity in SFDC with notes from call and chattering Sales Executive on opportunity for either advancement or closure.

Account Prioritization

  1. Sales to work with SDR on target accounts for strategic outbound prospecting purposes.
    1. Discuss “wide” vs “deep” net approach and agree on a good capacity for SDR to begin with. Typically, new SDR’s start with around 3-5 accounts per Sales Executive and add additional from there depending on personal bandwidth. Targeted ICP contact lists are pulled for each outreach sequence that the SDR creates.
    2. Sales Executives share a list of accounts in their territory with SDR. They should review and prioritize a “top 10” list and discuss which accounts SDR should start outreach to first. Prioritization categories include but are not limited to: CE Users (version.gitlab.com), Industry Vertical, Executive/Board Connections, Current marketing engagement with account, etc.
    3. Since most SDR/Sales Team pairings have 2:1 or 3:1 mappings, SDR’s should discuss their plan for equal attention/work load for each Sales Executive, as well as how many accounts they’d like to initially start with..

Quarterly Business Reviews

It is highly encouraged for Sales to involve their SDR in QBR prep, planning as well as invite them to attend and speak during their presentation. SDR’s should carve out time to assist and contribute with Sales presentation slides.

GIT is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license
Edit this page — open Web IDE — please contribute. Creative Commons License