ABM is a marketing strategy that concentrates resources on a set of target accounts. We create personalized campaigns designed to engage each account on a singular basis or a cohort of accounts based on specific attributes and needs of the accounts. The ultimate goal is for ABM to align with teams across Marketing and Sales to work in tandem to create personalized buying experiences for a mutually-identified set of high-value accounts — the goal for which is increased deal velocity and pipeline. Attainment of our KPIs and goals is a collaborative effort across interlocking teams.
More specific details to come in this section as we work with MS&A to build out an ABM specific dashboard.
To see an overview of the FY24 ABM Strategy, GitLab team members can review this epic.
ABM team focus countries can be found here in the internal handbook.
Our key account list consists of Mid-Market and Enterprise accounts that the sales/XDR org are also heavily focusing on while still adhering to requirements from Marketing leadership. We work with Sales Strategy to understand key accounts for Sales. We also connect with Sales leadership to review our ABM Key Account list to ensure alignment and awareness.
Requirements for our FY24 Key Account list can be found in the #fy24-strategy.
You can determine what accounts are part of the ABM Key Account list via the
ABM Tier field on accounts in SFDC. If this field is populated - the account (and the full hierarchy) is part of the ABM Key Account List. You can build a SFDC report using the
ABM Tier field to see the full list.
There are two types of ABM Key Accounts
These accounts will have a custom marketing campaign built specifically around the needs of the account. An ABM manager will bring together Sales, XDR, Field Marketing, Marketing Campaigns, and Product Marketing to discuss the goals and needs of the account. From there, the ABM manager will build out a campaign and work closely with the other stakeholders on the call to assist or lean into activities they have running. These accounts are nominated by AVPs. As there are only two ABM managers, the nomination is a rotation between AMER, US PubSec, EMEA and APAC. Once an account hits the aligned goals established during the kick-off call, the ABM marketing campaign will still run (perhaps a lighter version) but recurring syncs and spend will lower.
These accounts will be grouped together based on specific attributes (industry, competitive intent, role, buying stage, etc.) A custom ABM campaign will be created aligning to the attributes of the account grouping. ABM will also align closely with Field Marketing and Marketing campaigns to drive to specific events/assets. We will have an issue for each cohort of accounts and will provide relevant updates/key metrics for visibility to all stakeholders and sales teams.
Our slack channel #abmteam is used for team updated and quick questions.
The #integrated-marketing channel is used for interaction with the larger Integrated Marketing team, and the #im-hangout channel is used for weekly check-ins and connecting on a personal level.
With the new structure of Campaigns for FY24 including global vs regional Campaign Managers, this interlock will likely be iterative. As it stands today, we have recurring meetings with the global campaign managers to determine what content and tactics are coming. From there, we will use the data and our conversations with sales to determine what can be leveraged in our ABM specific campaigns. We have an issue/epic for each region that details channels, target audience, KPIs, etc. that will be shared with regional campaign managers as well.
Sync on current priorities and efforts between our teams to explore where there is potential for collaboration on lead tracking/handoff/retargeting in ABM accounts from demand gen efforts. This will help us avoid duplicative efforts to the same target lists.
Continue relationship over Tier 1 knowledge shares, but expand the scope of ABM/Sales collab to include Tier 2 cohorts - our Highspot page has been updated with relevant details to meet sales/XDR where they frequently go and ensure alignment with the ABM strategy.
Continue to test email as a channel for our ABM efforts - for Tier 1 (when we have enough opted in contacts) and expanding use of email into our Tier 2 cohorts.
In planning for Q1 of FY24, FM already had their plans set, so we are looking at opportunities to tie together on driving key accounts to their planned events. In planning for Q2, we are going to try a proactive planning approach on a regional level leveraging key account data, to align with FM’s timelines, rather than after their plans are set.
ABM-Priority::Top: Immediate action needed, aligned to OKRs, ABM strategy, or top leadership asks. This category will be limited because not everything can be a priority. Timeframe: Immediate action needed.
ABM-Priority::High: Not requiring immediate action, but aligned to OKRs, ABM strategy, or leadership asks. Timeframe: Within weeks.
ABM-Priority::Med: Requests submitted that align to OKRs or ABM strategy. Process improvements to fix broken processes, or improve ABM team efficiency. Timeframe: Within months.
ABM-Priority::Low: Requests submitted that would be helpful, but can be pushed for higher priority issues. Nice-to-have improvements for ABM team processes. Timeframe: No specific timeline.
ABM-Priority::TBD: Requests that have not yet been prioritized by ABM.
ABM: DRI is in ABM team
demandbase: any issues that are related to Demandbase ABM campaigns
mktg-status::triage: the issue will be evaluated to determine if full details are included, and ask questions as needed if the scope/details are not clear
mktg-status::blocked: there were insufficient details in the issue for work to be triaged
mktg-status::triagein order for the request to be reviewed again.
mktg-status::wip: the issue is assigned and moved into appropriate time-based milestone
mktg-status::plan: this is used for work that is in an earlier stage of planning and a specific request has not been made
We ask that teams request work using the following issue templates in the ABM project. These templates more clearly indicate what information and details are required in order for the request to be triaged and fit into an existing milestone.
Note on timelines: Requests will be committed to as bandwidth permits.
ABM Team Issues:
ABM manages their budget in Allocadia.