The role of field marketing is to identify and support critical sales and marketing opportunities through field marketing avenues and to bring the GitLab brand to life.
Field Events
To find out what upcoming events GitLab and our resellers will be involved in please visit our Events Page. If you have any questions or an event suggestion for us please email events@gitlab.com.
Field Event Goals
Sales Acceleration
Engaging with existing customers
New growth opportunities
Demand
Education
Market Intelligence
Test out new messaging or positioning
Product Direction
Event Lifecycle
Evaluating Potential Field Initiatives
Price/ Budget and what will the ROI be.
Location - top cities for developers and can we tag on another event or customer meetings?
Attendees - who’s attending? Is it the right audience for us? Enterprise vs Community. Will there be decision makers in attendance?
Size - try to reach a large audience.
What will our presence be? Who can/ can we go, participate, speak, booth?
We want to emphasize enterprise events but also remember our community.
Suggesting We Sponsor an Event
If there is an event or conference you think would be a perfect fit for us to get involved in or sponsor based on the "evaluating and event" criteria above, the process for submitting that suggestion goes as follows:
Please only request event support/ sponsorship if your engagement fits the following criteria:
The event will further business aims of GitLab (see event goals).
The event has an audience of 250+ people (the exception being meet-ups - see below for more info on meet-ups)
The event is a more than a month away.
If your event fits the criteria above and you would like support from marketing, create an issue in the marketing project using the Events template.
Fill out any relevant information you have and tell us what potential growth opportunities can be gained from investing in this event. Someone from Marketing will be in touch about to discuss your request further within one week.
How We Decide Who Attends Which Events?
FM determines how many staffers we need and if the event is more enterprise focused or community. Enterprise- we try to send more marketing/ sales. Regional Sales Managers select staffer based on who has most potential contacts in area or going to event. Community - send more developers, subject matter experts, and dev advocates.
See who is in the area who might be a good fit for the audience.
FM lean towards those who might be thought leaders, specialists, or more social in that specific sector.
FM aims to bring minimal staff to keep costs and disruption to normal workflow low. We take into account what value everyone will provide as well as staffing balance. Please check with your FM rep if you would like to or would like to suggest someone participate in an event.
Event staffing list will close 2 weeks before commencement of event.
Where do we keep contracts realted to Field Marketing after they've been signed?
All contracts are stored in the Marketing Ops folder. Sorted by year, then by region.
Where can I find out more about how to speak at an event?
Call for papers are posted in the #CFP Channel on Slack. Follow channel for updates on speaking opportunities.
If you want like to speak somewhere and would like assistance building our your proposal please contact content@gitlab.com.
Pre-Event
Event Content/ Design
Assess individual event content needs. Most events will need…
Social copy + design
Social ad or InMail copy + design
Swag designs
Pre and post event talking points for sales outreach
After event wrap up email(s)
Additional blog or content to support event strategy
Updated one pagers
Targeted slide decks and demos for specific event audience
Event Outreach
Email signatures - starting 6 to 4 weeks before event for those attending event and XDR team.
Get attendee list and contact customers and prospects before event using talking points from content with goal of setting up meetings/ demos at the event. Invite them to anything specific we have happening at or around event.
If there is not an attendee list process is as follows:
Target speakers for outreach
Utilize previous years attendee list. That person may not be attending, but their colleague might be. Ask for intros.
Follow event hashtags to see who will be attending
Join local meetup and pre event events (this works well for large events like AWS)
Join LinkedIn Groups and slack channels dedicated to event
Download event app and engage with attendee via app.
You can search for relevant talks and see who has registered for talks that might apply to potential customers.
SDRs/BDRs will help set up in person meetings to occur at event in coordination with assigned account reps.
Scheduling Onsite Meetings (pre event)
There will be a spreadsheet with suggested meeting slots. AE's and XDR's are responsible for adding any meetings they have set with prospects or customers.
The AE that sets the meeting will be responsible for completing the designated client meetings prep sheet. This sheet is intended to provide everyone attending the meeting with any background info on the prospect/ customer they should know going into the meeting, as well as any objectives or things to cover in said meeting. This sheet can be found in Google Docs as well as in every event issue.
The AE that sets the meeting will be responsible for creating the contact record in sfdc and adding that contact to the associated campaign.
Meetings should be capped at 3-4 GitLabbers in attendance. We want to minimize disruption and get by with only the folks that will be most impactful to the meeting. Avoid million dollar meetings.
If an exec is expected to be in meeting, AE will check for interest with prospects or customers and if there is, hand off to the EA team to handle scheduling. EA team owns scheduling all exec meetings and engagements
The AE will provide the EA team with a 1-page background on the meeting (company, attendees, focus for them and focus for GitLab + last minute contact details - phone and email) 1 week prior to the meeting
The AE that hosted the meeting will be responsible for updating the contact record with notes from the meeting and possibility doing hand off to account owner if they are not owner.
Event Operations Checklist Before Event
Add event to events page. Instructions on how to add events can be found here
Create issue for event in Marketing Project on gitlab.com (use events issue template).
Set up event campaign in Salesforce. The campaign must include event budget and goals for # of leads and # SCLAU. Other goals should be established and documented in the campaign for # meetings at event, and attendance at planned activities such as VIP dinners, lunches, etc., as applicable.
Team should add members to campaign to be invited to event, using the appropriate Campaign Status:
Invited = You have personally invited the person to the event.
Nominated = Marketing will invite the person on your behalf. They will receive invitation email pre-event plus any confirmations/reminders if they register.
Registered = The system will automatically update to this status once someone completes they form on the Registration Landing page. This is a system applied status not for manual additions to a Campaign.
Set up post event follow up campaigns.
After Event Survey created and email template ready to go out first work day back after event. Includes details on lead follow-up and how to add business card details.
Social media to go out during event scheduled.
Plan for what to do with any remaining swag/ collateral.
Final Event Team prep meeting to go over talking points, assets, and scheduling.
Promoting Events Social
Use social media to post as soon as committed to attending an event.
Possible Targeted Social Ads (media source depends on target audience and attendance goals). Timing depends on call to action.
Schedule tweets one week before event and one to go out at event promoting presences and any relevant content.
At Events/ In the Field
For events where a field marketing representative cannot be present, he/she will assign an onsite lead. The FM manager will be responsible for coordinating with this person and getting them any info they will need to help run event in their absence. This person will be the venue point of contact as well as responsible for set up and tear down. They will also be in charge of ordering swag from the "small event swag campaign"- see swag section below. A list of their specific responsibilities will be found in the designated event issue.
Employee Booth Guidelines
Perfect your Pitch
Most people have two ears and one mouth. Successful pitching is 2 parts listening to 1 part talking. Be engaged and interested in folks that visit. Be genuinely curious about their story. Understand them first before you start telling them about us.
A great way to start is to offer a handshake and say,
"Hi, my name is [your_name]”
“Hi I’m [their_name]”
“[their_name, are you familiar with GitLab?”
“Yes”
“Thanks for using us, are you using just the source code management or are you also using the built-in GitLab CI/CD?”
“No” - “Great, in a nutshell we <140 character description> - for example, what company do you work for?”
“Company X”
And what’s your role at company x?
“Title X”
Tailor your pitch to their specific experience. Ask about what tools they are using today, what they like or dislike about those tools.
Working at the booth is a great place to try out different ways of explaining technology and trying out different value propositions to see what resonates the most.
Know some stock answers
You can ask them which talk they’ve heard so far has been the most interesting.
Close the deal
Figure out what the next step for this person is. Are they a decision maker at a large org?
If a conversation is running long, get his/ her info and schedule a time to chat or follow up at a later time outside of the booth. The goal of the booth is to make initial contact and connections.
Give a personal follow up
Stand at the front of booth facing the crowd.
Don’t make folks walk into the booth and seek you out. Stand out at the front. Make eye contact and smile at folks walking by. If they stop or pause you can ask them, “Are you familiar with GitLab?”
Hangout outside the booth.
Too many GitLabbers in the booth discourages other folks from coming by. The booth can be a great place to meet up, but don’t hang out there. Move the conversation to a near by lounge or social area.
When you are at the booth keep conversation with your coworkers to a minimum.
When you are at the booth focus on serving the attendees.
Do not do normal daily work in the booth- the booth is not a place for taking calls, or responding to emails. When you are at the booth you are on booth duty and that is is.
Keep an abundant tidy stash of swag out
During slow times, restock swag and tidy up booth.
Keep the booth clean.
The booth should be clean and organized at all times.
Avoid eating meals in booth, please keep lids on beverages and out of sight.
If we have the bandwidth or the traffic is slow do not be afraid to walk around to other booths and talk to people. Make friends we could partner with, create interesting content with, or just have friendly beers.
If press comes to the event feel free to put them in contact with CMO.
Engage the competition.
Be friendly and polite to competitors to come by the booth.
Don't forget your business cards.
Scanning Best Practices
Be an active but polite Badge Scanner
Don’t reach for the badge without first asking if you can scan someones badge and don't lead a conversation with can I scan you. Ask folks politely, “Would you appreciate a follow up email?” or “Mind if I scan your badge?” Many folks will say, “yes.” If they say, “Not really.” You can say, “Great, we don’t want to clutter up your inbox. You can always go online to about.gitlab.com if you’d like to check back in with us.”
Trade scans for all swag if the attendee consents. If we have the space and staff, someone should be in charge of distributing and organizing swag, and scanning folks who come by for swag.
Take good notes:
Your initials (This way the email can be more personalized to say, “We saw you chatted with [name] in the booth.”) Add your initials + “follow up” if you personally can send them an email within a week of the conference.
The tech stack (what tools they are using)
Any specifics needed in the follow up (schedule a call, send docs for X, interested in Y, etc.)
Tag the lead hot, mild, (cold)
Hot ==
Mild ==
Cold == everyone else. A lead will be cold by default.
Wear at least one piece of branded GitLab clothing. If you prefer to wear something dressier than the GitLab branded items available that is also acceptable. Feel free to wear our sticker on your shirt.
If the conference is business casual try some nice jeans (no holes) or dress pants.
Ideally booth shifts will be around 3 hours or less.
Staff more people during peak traffic hours.
Avoid shift changes during peak hours.
Aim to staff booth with individuals with a variety of expertise and backgrounds- ideally technical and non-technical people from various departments should be paired.
Send out invites on the Events & Sponsorship calendar to booth staff with the following information:
Time and date of event, booth, and shift
Suggested attire
How he/she can find his/her ticket
Any instructions on using or locating lead scanner
Let them know of any contests happening
How to get a hold of you
Link to events handbook
Any relevant event set up or clean up
Post Event
Add event debrief to event issue in marketing project. The debrief should include the following if applicable:
Was the event valuable?
Would you go again/ should we go again?
Did we get good leads/ contacts? What was the audience profile like?
Best questions asked and conversations. Trends in questions asked.
Was our sponsorship/ involvement successful? Did we go in at the proper sponsorship level?
How was the booth set up?
How was the booth staffing?
Did the booth get enough traffic?
Booth location and size
How did our swag go over?
Did we have enough/ too much?
Contests
Did the contest(s) effectively build our brand and connecting with our target audience?
Send all leads and contacts with any relevant notes on interactions/necessary follow up to Field Marketing Manager (FMM) for your Region within 36 hours of event close.
When the list is received from conference, the Sales team will have 24 business hours to review and claim FIVE records per rep, prior to list upload. If for any reason you cannot meet this deadline ping Marketing Operations (MOps) or your regional Field Marketing Manager (FMM).
Records that are part of an existing named Account will be assigned to the named Account Owner by default.
Data integrity is everyone's responsibility and we ask if you see that an Account you own and the Account Name does not match what is listed in Salesforce, please correct to match so the list upload attributes that record appropriately.
List upload will be done within 48 hours of list being received by conference organizers. All records will be added to corresponding Salesforce campaign as CONTACTS and either get the status of:
Campaign Member Status = Member & Contact Status = Raw: if there are no notes on the spreadsheet
Campaign Member Status = Engaged & Contact Status = Inquiry: if there is specific follow up or notes on the spreadsheet
The Engaged CONTACTS are considered Tier 1 and should be contacted immediately with as much personalization as possible.
Notes on upload: When the list is uploaded, if any new record is associated to a known account they will be assigned to that account owner, but if the record does not belong to any known account they will be enriched using Clearbit. Using the Total Employee count & any regional information enriched, assigned as follows:
Strategic & Large = Regional Director
Mid-Market = Appropriate Mid-Market Sales Rep
SMB = Appropriate Customer Advocate associate
If record cannot be enriched with enough data to route correctly the record will be assigned to Sales Admin for the SDR Leads to review and reassign.
The account SDR will handle and document follow up (within one week of list upload) and pass on lead to AE/AM when appropriate.
If the AE/AM would like to do any personalized outreach to event records they will be responsible for coordinating efforts with SDR and documenting any activity and updating statuses in Salesforce. AE's will have one work week to take care of outreach and update the Contact Status. If not activity has happened in the first week SDR's will take over outreach.
Check for existing account records before engaging contacts. Salesforce cannot fuzzy match records and only matches records using the Email Address field as the unique identifier. A LeanData workflow will be leveraged to match & merge duplicates or variations but no automated system is perfect.
Marketing will send out one email to ALL event CONTACTS in Campaign (within 3 business days of event close).
The Sales Rep (or delegated SDR) will send a follow up email to their claimed records and owned account contacts (within 3 business days of event close). The Contact Statusmust be updated to reflect outreach status.
FMM campaign owner will check in on campaign and Contact Status one week, 2 weeks, one month, and 3 months out from event assisting in any additional nurturing efforts to move the needle forward.
Swag for customer/ prospects
Anyone with access to Salesforce can send swag through Salesforce directly. Please review sending swag to customers paramaters. Instructions on how to do so below:
Create general task for whichever contact you want to send swag to. You need to create a task and save it before the "order swag" button will show up as an option in the task menu.
Go into created and saved task and click the button that says "order swag".
If you do not see the window pop up for ordering, please check your pop up settings and verify pop ups are not being blocked.
Previous step will bring up a printfrection page where you can order desired swag. (please note not all swag is listed in sfdc, for more options email emily@gitlab.com).
We have GitLab stationary/ note cards- leave note in swag slack channel of you would like a batch to send notes to prospects/ customers/ community members.
Terminus is an ABM hub that uses banner ads to target people who work at specific companies of our choosing, with the goal of creating general awareness and pushing specific content. It is best used paired with other field strategies to get our foot in the door and build awareness. Not usually used on in isolation to close an opportunity, but can be used to influence it.
Creates awareness in specific companies. This tool integrates with Salesforce, so it can only pull from existing accounts in the system. It is best used to target strategic and large accounts. It can target an industry, specific business, or even a specific department in that company. We can get pretty granular with targeting- please reach out for specific requests and questions to events@gitlab.com.
How to suggest a terminus campaign?
Go to the marketing project and find the terminus issue template. Add in all relevant information. Let us know what companies, industries, or sectors you are trying to target when and paired with what larger field presence.
