Field marketing includes event marketing and swag production.
Get GitLab team members out to meet people in the community. People that you meet in person are more likely to become evangelists for you.
If you go talk at small events you'll see that over time you get into bigger ones.
Evangelism (brand) - Talk to as many people as we can about GitLab. Our booth presence we must be friendly, knowledgeable, and outgoing.
Sales leads (revenue) - We will collect business cards and email addresses for potential leads.
Hiring (company) - Always be recruiting. See someone doing a great job of evangelism for another product? Ask that person for coffee.
Partnership (channel) - Organizations adding support for GitLab and/or shipping GitLab with their offering.
Product Direction - discovery of what the market asking for, in need of and willing to pay for.
Drive audience to any talks/ events we are having.
How We Evaluate Events
Location- tops cities for developers and can we tag on another event?
Attendees- who’s attending? Is it the right audience for us? entrepreneurs vs engineers.
Size- try to reach a large audience.
What will our presence be? Who can/ can we go, participate, speak, booth?
Can we pair this event with other local engagements?
We want to strike a good balance between: community and enterprise events.
For GitLab Employees
If there is an event you would like to attend, are attending, speaking or have proposed a talk please let the Field Marketing Manager know. We will try to support you attending the event in any way we can. Even if we are unable to sponsor the event you can likely still attend with your managers approval.
Remember we are way more likely to sponsor an event if you have solidified a speaking spot. So, if there is something you really want to attend propose a talk.
Calls for papers are posted in the CFP Channel on Slack.
If you do not have any GitLab swag and are going to an event, notify the Field Marketing Manager as soon as possible so we can try and get you a GitLab shirt to wear.
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.
If the conference is business casual try some nice jeans (no holes) or pants.
Clean, closed-toed shoes please.
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 genders- ideally technical and non-technical people of either gender can 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
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
After an Event
Fill out after event survey.
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?
Best questions asked and conversations
Was our sponsorship/ involvement successful?
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?
Did the contest(s) effectively build our brand and connecting with our target audience?
Make sure contacts/ leads gathered from event are with marketing and categorized under specific event campaign.
Sales team and BDR's will have 3 days after event lead list sent to claim leads and add notes before bulk after event outreach will occur.
Follow up with leads from event within 5 business days after event ends.
Catalogue of talks and speaker briefs we have done or can do and their run times. Contact firstname.lastname@example.org for access.
Ideally first meetups should be run by GitLab employees. If someone manages to have 3-4 successive events, the meetup itself will live on. It is much harder to start new meetups versus maintaining existing ones. So we should everything to keep existing events going.
We love to attend others meetup groups. If you would like someone from the GitLab team to stop by your event please email email@example.com.
We aim to have our swag delight and/ or be useful.
We aim to make limited edition and themed swag for the community to collect. Bigger events will have custom tanuki stickers in small runs, only available at their specific event.
We aim to do swag in a way that doesn't take a lot of time to execute => self serve => web shop
With a web shop you can just give people credit, they can pick what they want and provide shipping info.
Of course we love stickers. We are working on special edition stickers for contributors to be announced May 2016- being shipped right now.
We get a lot of requests to send swag, and we try to respond to them all.
Ask about the expected number of attendees, the best shipping address, and if they have a specific order in mind (if they're requesting on behalf of a small meetup group, for example.) If they do not specify, send black unisex tees when in stock.
Include the contents of the order, along with the shipping address in an email to our swag store managers. There is no need to add these amounts to the marketing budget spreadsheet because the swag store sends its own report of what was spent.
For orders of stickers in a quantity of 100 or greater, do not go through the swag store but rather use our Stickermule account. You will need the same information (address and order quantity). After placing the order, add the amount to the marketing budget spreadsheet.
We offer a $500 sponsorship to any group that aims to improve diversity in tech.