Sales Play: Upsell Premium to Ultimate

This page has all the information for the GTM-CICD sales play.

Note: Think of a sales play as a recipe. If you follow the recipe, we can achieve more predictable, consistent results. And if we find an asset or approach that works best (or flops), then we can tweak the recipe to continuously improve. **If you have improvements to suggest, please contribute comments to this MR to suggest your edits and upvote on others.

Overview

Objective - Convert landed accounts that are already using CI/CD to expand from GitLab Premium to GitLab Ultimate.

Who is this sales play for?

  • Primary: SAEs and AEs who call on one or more existing GitLab Premium customers
  • Secondary: SAs and CSMs who support one or more existing GitLab Premium customers

Note: This play is FYI only for SDRs because it is upselling tiers, not necessarily expanding seats.

Who to meet

Ideal Customer Profile - Existing GitLab Premium customers already using CI/CD

  • Bonus points for:
    • Organizations at lower maturity level undergoing or planning to undergoing tranformation
    • Siloed teams with disparate tools, especially security, lacking visibility at the individual level and executive level
    • Organizations with stringent regulatory security or compliance requirements

Target Buyer Personas

Persona role Possible titles
Economic buyers CISO or Security Manager, VP of Security, Director of Security, VP of IT or CTO, App/Dev Director
Technical influencers Chief Architect, App Dev Manager
Other Personas to consider Infrastructure Engineering Director, Release and Change Management Director

Target Account Lists

Getting Started

Consider the following questions:

  • What has prevented the customer from moving to (or considering moving to) GitLab Ultimate?
  • Does the customer have any strategic initiative or priority to which upgrading to Ultimate would align nicely?
  • Are you engaged with the right personas/teams (see Target Buyer Personas above)?
  • Do you have access to power/authority (a business decision maker)?
  • Who are your champions within the account?
  • Are the capabilities and PBOs that are enabled by GitLab Ultimate important to the customer? Why or why not? How do you know?

Value Discovery

Common Pains

GitLab Premium customers may be experiencing one or more of the below challenges:

Challenges (“Before Scenarios”) So What? (“Negative Consequences”)
Difficulty writing secure code without becoming security experts Increased risk
Vulnerabilities found late in the SDLC Costly remediation, blocks production at last minute
Costly triaging and tracking of vulnerabilities Inefficient use of scarce security resources, lengthy remediation process
Managing complex tool chains, plugins, and fragile automation scripts Added cost, maintenance, and admin overhead
How to ensure scans are executed consistently and policies applied teams may skip scans or use exceptions to push ahead, difficult to see across tools when this happens
Security costs are unpredictable or concerning as DevOps scales must find more money as number of apps grows

An in-depth view of security pain points and probing questions around them can be found on the DevSecOps resource page

Common Benefits

By upgrading from GitLab Premium to GitLab Ultimate, customers may experience one or more of the below benefits:

Desired Future State (“After Scenarios”) So What? (“Positive Business Outcomes”)
Greater efficiencies for both security and dev less risk and greater velocity of DevOps
Consistent compliance to policy less risk of vulnerabilities in production and easier audits
Reduced security exposure, more scanning finds more vulnerabilities reduced risk to finance and reputation
Predictable security costs that scale with DevOps able to confidently forecast and budget as DevOps and App Sec both scale

Required Capabilities

To achieve the positive business outcomes highlighted above, what required capabilities does the customer need to solve for and how will success be measured?

Required capability Customer Metrics
Comprehensive app sec scanning methods percent of apps scanned with multiple scan types
Scan results delivered to the developer in their CI pipeline vulnerabilities found pre-prod
Security governance time spent on audits, fewer compliance issues
Option to use 3rd party scanners metric?
Vulnerability management mean time to resolution

Engaging the Customer

Note: maybe we use this link as mvc1 and then change the resource pages to the suggested format?

Questions to Better Understand the Customer’s needs Discovery questions
current state 1. Are you wanting to shift security left? How is that going?
2. What security tools are you using today?
3. How are you currently securing containers and Kubernetes?
future state 1. What if you could simplify your shift-left efforts?
2. What challenges do you have with your existing tools and can you predict their cost 2 yrs out?
3. Would you like to better protect containers and K8s?
Required capabilities 1. Could security integrated into CI help you get there?
2. What if you had one, known cost that enabled ALL your security scans, with results to the developer in their CI pipeline, along with vulnerability management for the security pro? What if you could either eliminate some existing security tools or reduce their use/cost?
3. What if you could scan containers and monitor their host and their traffic within K8s clusters?

Note: if they say they do NOT want to shift left and empower developers to find and fix security flaws, you are probably speaking with a security analyst. Talk to his/her boss, DevOps, or application dev/engineering team.

Positioning Value

Elevator pitch

With GitLab Ultimate, organizations are able to truly shift security left (and right!) while keeping up with DevOps velocity. Empower developers to find and fix vulnerabilities earlier and security teams to manage risk from detection through remediation. With GitLab, the integration is done for them. No need to fit your security tools into the CI pipeline - it’s already built-in! And for ONE predictable cost, even as you scale!

GitLab Ultimate enables IT transformation by optimizing and accelerating delivery while managing priorities, security, risk, and compliance.

Note: Everything you get in Premium plus all security scanners, vulnerability management, security and compliance dashboards, free guest users, 50,000 compute minutes, a named CSM, and moreā€¦

How GitLab Does It

How GitLab meets the market requirements for security (link includes benefits, videos, and more.)

How GitLab Does It Better

With GitLab Ultimate, organizations are able to truly shift security left (and right!) to find and fix vulnerabilities earlier while keeping up with DevOps velocity and new attack surfaces of cloud native apps. With GitLab, the integration is done for them. No need to fit your security tools into the CI pipeline - it’s done! And for ONE predictable cost, even as you scale!

For one cost, you can:

  • Scan every code commit on every app (no more choosing because scans are too expensive)
  • Use multiple scan types to find threats individual scanners might miss
  • Manage all vulnerabilities found in one place with united collaboration between dev and sec
  • Easily assess remediation progress
  • Automate policies and focus on the exceptions not individual inspections.

Advantages of a single application for DevOps and Security together include unparalleled visibility and insights/traceability with consistent compliance to policies and regulatory requirements for cleaner, easier audits.

Key GitLab differentiators include:

  1. Detailed and Actionable Scan Results Displayed in MRs created from Feature Branch
    • Microsoft does this for SAST and Dependencies. Other scan types require integration and bring-your-own licenses.
    • Veracode, Fortify, Synopsis struggle to scan quickly within the CI pipeline and require DIY integration.
  2. Block MRs based on Security Policy
    • Microsoft does this for SAST and Dependencies. Third party scans likely require customizing CI pipeline.
  3. Compliance Management
    • GitLab just launched Compliance Pipeline Configurations where customers can enforce even more separation of duties by setting up a single pipeline definition for a specific compliance framework (PCI, HIPAA, or even a custom one). All projects using that framework will include the predefined pipeline automatically.
    • GitLab Compliance Management secures more than just the code but the software factory itself, a big concern after the Solarwinds breach.
    • GitLab makes compliance easy
  4. Fuzz testing, including API testing
    • No one else integrates Fuzzing nor API testing into the CI pipeline.
    • Fuzzing can help find flaws not identified by a security CVE (signature of a known vulnerability)
    • Fuzzing is taking on new importance with cloud native apps and Infrastructure as Code
  5. Offline environments
    • Especially important to regulated industries like government and Financial Services
    • Most scanners require punching out of the secured network for the latest security rules/updates. We can containerize these for running in a disconnected environment.
  6. Vulnerability management (vs point solutions)
    • Traditional app sec vendors (Veracode, Fortify, Synopsis) sell a Security Center to manage vulnerabilities found from each of their scanners (all sold separately!). GitLab not only comes with vulnerability management, but it’s in the same tool that the developers use so nothing is lost in translation. In addition, you can easily pull in third party scan results into the CI pipeline (MR) to compare findings, somewhat similar to ThreadFix. Is your customer paying for this or other tools to do this?

see provided link for additional details including value and videos

Proof points

Proof points

Objection handling

Most common objections

Objection Response
How does your scanning capability compare to leading scanners? How accurate are they? accuracy slide, G2 SAST
Can you integrate with my incumbent scanner? We can work with other scanners or replace them
Ultimate is 5x. Why Ultimate

Other objections and responses can be found in the FAQ deck with more detail on Potential objections here.

Services

General PS deck

GitLab (or a GitLab partner) offers the below services to help accelerate time to value and mitigate risk:

Sales Play Tactics

These are Sales prescriptive actions to initiate engagement with target audience for Premium to Ultimate upgrade of existing GitLab CI users. Strategy and actions differ by market segment with SMB relying on marketing to drive inbound contacts initiated by the customer and ENT/MM primarily using the play to guide conversations initiated by sales.

Enterprise and Mid-market Accounts

Strategy

For Enterprise and MM, sales will do active outreach to customers to engage them in conversation using the recommended email templates and conversation flow below, modifying as needed. These accounts will not be included in the automated email campaign. This allows the SAEs greater control over who is contacted in their accounts, and the contacts can be more personal.

ENT and MM Sales Actions

  1. Review the target list and prioritize contacts.
  2. Familiarize yourself with context for this play (above), especially differentiators and objections
  3. Familiarize yourself with the recommended email sequence and next steps (below).
  4. Use the three email templates below to reach out to leads.
    • We have provided a recommended sequence, but choose the best email to start based upon your current conversations.
    • Copy and paste the emails as-is into Gmail.
    • Personalize it, but do not edit the hyperlinks in the email templates. Each one is linked to a Pathfactory track with recommended content for optimal user experience.
  5. Check your own email inbox for alerts showing which contacts have responded (Example email alerts: Contact request, Email offer engagement)
  6. Conduct the meeting suggested below (1, 2, or 3) for the corresponding email to which they responded.
  7. Update sales stage in SFDC.
  8. Determine the cadence for progressing to the next step based upon the initial meeting. We recommend sending the next email in the sequence after 7-10 days, even if they didn’t respond to the last one sent. The flow is intended to move their thinking along even if they don’t call you to discuss each one.
  9. Repeat with next recommended email until you finish the meeting sequence, get to a POV, or to a sale. If you reach the end of the recommended emails and meetings and don’t see progress, please leave feedback in this issue or in slack at #gtm-ci-cd. Where are you stuck? How can we help?

Small Business Accounts

Strategy

For SMB customers, we will rely on inbound responses to the marketing-generated ‘contact sales’ emails in the recommended email sequence. Marketing is the key driver for this segment to get to an initial meeting, then sales will use actions below for follow up with interested prospect.

SMB Sales Actions

  1. Review the list of target accounts/contacts
  2. By Friday, 2021-04-23, identify individual contacts that need to be excluded from the marketing generated emails by filling out columns A & B on this target list. The default approach should be to include as many accounts and customers as possible, excluding only where such communication would be disruptive to existing deals. The first automated email will go out starting Tuesday, April 27th and subsequent emails will follow every 7 days.
  3. Familiarize yourself with context for this play (above), especially differentiators and objections
  4. Familiarize yourself with the email sequence and next steps (below).
  5. Check your own email inbox for alerts showing which contacts have responded (Example email alerts: Contact request, Email offer engagement)
  6. Conduct the meeting suggested below (1, 2, or 3) for the corresponding email to which they responded.
  7. Update sales stage in SFDC.
  8. Determine the cadence for progressing to the next step based upon the initial meeting. We recommend sending the next email in the sequence after 7-10 days, even if they didn’t respond to the last one sent. The flow is intended to move their thinking along even if they don’t call you to discuss each one.
  9. Once they click ‘contact sales’ on an automated email You must send subsequent emails manually using the templates provided. This allows you to determine the cadence and next step based upon the initial meeting. Please use the templates as they provide tracking links so we can alert you on their responses (and marketing can see what is most useful). You can modify the templates in Gmail to fit your unique conversations as needed.
  10. Repeat with next recommended email until you get to a POV or sale. If you reach the end of the recommended emails and meetings and don’t see progress, please leave feedback in this issue or in slack at #gtm-ci-cd. Where are you stuck? How can we help?

This sequence of recommended emails is intended to move the prospect from interest to POV. Note:

  • Marketing will be sending these emails to SMB targets generate leads.
  • MM and ENT Sales will choose the best email to start with based upon current conversations. Then use the template to send it to the contacts provided and any additional, to generate leads.

  1. Email template 1

    Subject: Interested in speed and security?

    Offer 1: From DevOps to DevSecOps: Automate your security tests with CI

  2. Email template 2

    Subject: Learn how to deploy to production 6x faster

    Offer 2: How Chorus uses GitLab to power its development

  3. Email template 3

    Subject: No more afterthought security

    Offer 3: Tired of afterthought security? Take a fresh look at GitLab Ultimate

Next Steps

Meetings to get to value alignment

If your customer engages with emails (sent either from marketing or from yourself), the lead will come to you via email and will it show what asset they clicked on and if they clicked the ‘contact us’ button. Based upon this insight, and any conversations you may have had, you will want to choose where in this progression is most appropriate to begin.

The following sequence is recommended to progress the customer from awareness and interest in GitLab security capabilities to consideration, agreement of solutions alignment to expected value, and ultimate purchase (pun intended)

Meeting 1 - assess business objectives

Use Value Discovery above along with these recommended assets to determine their business priorities, existing security tools, chief pain points:

Ask 4 questions:

  1. Wanting to shift left? (If no, talk to the Dev or DevOps team instead of security)
  2. What tool currently in use and/or consideration? (for each: SAST, DAST, Dependencies, License Compliance, Container scanning). Is this a Microsoft shop? Enter into SFDC (please, it’s super helpful).
  3. Using containers and/or Kubernetes? If yes, are you scanning containers? Helm charts? Testing APIs?
  4. Which desired outcomes do they most relate to: efficiency, consistency, risk, predictable costs?

Milestones: Identify key value driver, champion, and economic buyer, agree to second meeting

Metric: Opportunity stage 0 - pending acceptance or stage 1 - Sales Accepted Opp or no opportunity

Meeting 2 - assess security priorities

Based on their business objectives, assess interest in learning more on theses topics then schedule deep dive with your SA. (@cblake and the #s_secure slack channel can help with any questions you may have.) Identify key value driver, champion, and economic buyer.

Milestones: Identify key value driver, champion, and economic buyer, agree to meeting with economic buyer

Metric: Opportunity Stage 1 - Discovery

Meeting 3 - help them see the value

Use the provided ROI framework slide to help the customer identify all of his obvious costs, now and most importantly, into the future. Show how GitLab can provide predictable costs as they scale. Make sure it’s clear that our greatest value is our all-in-one approach that provides all types of security scans integrated into a united UI for both dev and sec. Be sure to include the value of this benefit along with tool costs.

  • Security CISO deck (includes value framework slide)
  • IF a more detailed ROI is if needed, consider one from Darwin Sanoy. Please provide feedback to help us tune these models in this issue.
  • Determine if additional steps are needed for solutions alignment (e.g., additional demonstrations, hands-on workshop, POV)
  • Do NOT push for a POV. Explore more efficient activities with the customer. If the customer requests a POV, move to POV agreement steps.

Milestones: agree to next meeting

Metric: Opporunity Stage 2 - Scoping or Stage 3 - Technical Evaluation

POV agreement (If POV is requested and necessary)

  1. Define POV requirements like this (link to David Astor’s SKO preso or Cherry Han’s package)
  2. Execute POV. Move requirements met to complete on issue board. Orchestrate collaboration with PMs for any unmet needs. Use #s_secure slack channel or capabiities page to identify the right PM to engage on the POV issues. Get customer to engage with PMs on the issues.
  3. Measure success of POV
  4. Propose solution/Ask for order and for reference

Additional Resources to use

Will have specific resources under actions above. This is for additional resources.

Measuring progress

Consider these milestones and adjust stages in SDLC as you progress.

Milestones

  • Gameplan with GitLab champion (MEDDPPICC)
  • Meeting with Security team or other economic buyer
  • Agreement to do POV
  • POV requirements defined
  • Successful POV
  • Proposal

Metrics:

  • Avg days per stage to progress
  • Longest step (common blockage?)
  • Economic buyer titles - common factor?
  • Retro on sales play

Note: progress of the GTM Motion will be measured at the campaign level with clicks/opens/page visits, SAO.

Marketing is running a related demand gen campaign.

  • Initial launch will include the email campaign outlined above for SMB to drive leads using the Message house.
  • An ‘air cover’ campaign will raise awareness of GitLab’s Ultimate capabilities. It will likely include Security (first) and Planning capabilities (next).
Last modified October 30, 2024: Fix broken links (39532aab)
View page source - Edit this page - please contribute. Creative Commons License