Effective Discovery
Overview
Effective discovery is critical to thoroughly understanding customer needs and establishes the foundation for being able to effectively articulate GitLab’s value and differentiation in a compelling, customer-centric way. Effective discovery will help you attach to your customers’ biggest problems, gain access to higher-level business stakeholders, and serve as a trusted advisor to your customers. This, in turn, will help you build and maintain a healthy and predictable pipeline, to meet and exceed your sales goals while helping your customers achieve their business objectives. After reviewing the below information, GitLab field team members are encouraged to take the interactive Effective Discovery course in GitLab Learn.
Qualification
The first phase of any discovery process is to determine whether or not you should spend time on a particular opportunity pursuit. A good guide for this phase is codified in the Criteria for Sales Accepted Opportunity (SAO) and includes confirmation of Authority, Initiative, Fit, and Timing.
Ideally, effective qualification also includes identification of the prospect’s:
- Cloud strategy
- Preferred cloud partner(s)
- Future growth potential (Landed Addressable Market (LAM)), and
- Preference for SaaS or Self-Managed
Understand Value Points
The second phase of discovery uses an iterative insight/question loop, often across multiple meetings or conversations, to uncover the prospect’s underlying challenges and motivations, with the ultimate goal of constructing a highly relevant and differentiated value message that ties the GitLab solution to the prospect’s business needs.
Preparation
Ensure you are ready for each discussion. The level of preparation for each discovery conversation will vary, so use your best judgment for how deep you go and be sure to leverage the information that has already been collected during Prospecting and Qualification. The key point is to be prepared and to not just wing it. Consider the below recommendations.
Research the Prospect
Researching your prospect may include but is not limited to:
- Annual reports and/or financial statements
- Account activity/engagement history in Salesforce
- Recent news or press releases
- Research your contact(s) on LinkedIn, Twitter, and/or other social media platforms
- Insights gleaned from partners that already have relationships with the account
Understand the Persona
Different roles within the prospect’s organization will inherently care about and be motivated by different things. Leverage the below resources to understand the challenges and motivations of the persona you are engaging.
Develop a Pre-Call Plan
As outlined in the Pre-Call Plan job aid, be sure to consider the below questions.
- What is your desired outcome for this conversation or meeting? What do you think the prospect’s desired outcome is?
- What information do you need to gather to achieve your objective(s)? What discovery questions will you ask, how, and in what sequence? As outlined above, this iterative insight/question loop will often span across multiple meetings or conversations.
- Start with Customer Strategy-based discovery questions to seek to understand your prospect’s goals, objectives, and initiatives
- Next, ask open-ended Customer Needs-based discovery questions in pursuit of understanding your prospect’s desired outcomes, current situation and environment and level of satisfaction, and motivations (including personal needs)
- As you develop and prioritize your discovery questions, what types of questions will you ask that reinforce GitLab’s differentiators?
- For a deeper dive, re-review the Defensible Differentiators content and sample questions in the GitLab Value Framework doc (see top asset highlighted in the Resources: Core Content (internal only) section of the Command of the Message Internal Handbook page)
- What agenda will provide the structure needed to help you achieve your meeting or call objectives? Assuming you achieve your objective(s), what are possible next steps you may recommend? How will you close the call or meeting to progress the opportunity further?
- What are some potentially relevant success stories (e.g. same industry, geo, anticipated pain points, etc.) and other proof points (e.g. favorable analyst report) that you may want to reference or highlight to build interest and credibility?
- What questions or objections do you anticipate the prospect may have? If those indeed come up, are you ready to respond?
Seek to Understand
Approach With Curiosity
Approach discovery conversations with a curiosity-led mindset and a desire to better understand the customer’s challenges as well as the implications of those challenges.
- How big is the problem?
- How does this impact higher-level goals and objectives?
- How does this challenge impact the person(s) with whom you are talking?
- Who else in the organization does this challenge impact and how?
TED
Leverage the TED questioning model (see below) to get the prospect to open up and provide more context and detail about their challenges.
- T: Tell me more about…
- E: Can you please explain the impact of…?
- D: Will you please describe how others are affected by…?
Five Whys
Use the Five Whys technique to identify the root cause(s) and understand the “So what?” Check out the short video below and read the Why Salespeople Should Ask The Same Question 5 Times In A Row blog to learn more.
Active Listening
Commit to active and effective listening. Watch the video, listen to the podcasts, and check out the Why Your Active Listening Skills Are Crucial to Hitting Your Number blog.
Master Command of the Message
Command of the Message is a proven, value-based sales messaging methodology from Force Management that allows GitLab sales team members to effectively uncover customer needs and articulate value and differentiation. Leverage the below resources to ensure you are confident in the methodology and the GitLab-tailored sales resources created to help you be successful and delight your customers.
- Command of the Message Handbook page
- Command of the Message e-learning module (90 minutes) (GitLab internal with protected IP from Force Management)
Identify the Buying Process
The final phase of discovery identifies the roadmap, along with potential roadblocks, for getting a deal closed as well as key stakeholders who must be involved. Discovery will continue throughout the sales process as you and your account team continue to gain a deeper understanding of all elements of MEDDPPICC to increase the likelihood of earning the customer’s business.
- Leverage Customer Decision-based discovery questions to gain a better understanding of the Decision Process, Decision Criteria, Paper Process, and more
- Check out the full MEDDPPICC Handbook page
- Complete the MEDDPPICC e-learning module (60 minutes, GitLab internal)
Avoid These Discovery Pitfalls
Lack of Preparation
See the above section for tips to avoid what may be the most common discovery pitfall.
Happy Ears
Resist the urge to prematurely talk about or begin to position GitLab until you have a thorough understanding of the customer’s challenges, the implications of those challenges, how big the problem is, the urgency of the problem, who cares about the problem and why, and more (see below).
Not Attaching to the Biggest Problem
You must have a solid understanding of the prospect’s key business drivers, strategic business initiatives, and associated objectives and goals to be able to serve as a trusted advisor. These will almost assuredly relate to one or more Customer Value Drivers. Use Customer Strategy-based discovery questions followed by Customer Needs-based discovery questions to identify how GitLab can have a positive impact on your buyer’s business issues.
Failing to Identify the Negative Consequences of Doing Nothing
Watch the short videos below to learn more about the importance of seeking to understand, and helping your prospect understand, the negative implications of their current state. As a salesperson, you must understand the difference between the prospect’s current state and the future state that GitLab can help deliver and effectively articulate that difference in a way that compels them to take action.
Lack of Multi-Threading
Sales multi-threading refers to the concept of engaging and developing relationships with multiple stakeholders who are involved in your customer’s decision-making process. According to CEB Global, the average B2B deal has 5.8 decision-makers, and that number typically increases along with the size and complexity of the contract. Even if your primary contact has significant authority in the organization, that may be insufficient if the rest of the buying group is not on board with the decision. Therefore, the more connections you have from the buying side, the better your chances of getting a deal closed. To learn more, check out the below articles/blogs and podcast.
- What is Multi-threading Sales and Why Do You Need to Start Doing It?
- The Tactical Guide to Multi-Threading Sales
Supplemental Resources
Overall Discovery
- Executing Great Discovery podcast (31 minutes)
- Discovery is a Process featuring Matt Petrovick (GitLab Strategic Account Executive) (2.5 minutes)
- Matt Petrovick’s Favorite Discovery Call (3 minutes)
- Matt Petrovick’s Most Memorable Discovery Call (2 minutes)
Preparation
- Be Match Ready! featuring Peter Davies (GitLab Strategic Account Executive) (2 minutes)
Active Listening
- Improve Your Active Listening Skills podcast (15 minutes)
- Why Are You Talking? podcast (9 minutes)
- Use the Customer’s Words and Stop Talking featuring Peter Davies (GitLab Strategic Account Executive) (0.5 minutes)
Attaching to the Biggest Problem
- How to Enable Reps to Sell Higher podcast (27 minutes)
Identifying the Negative Consequences of Doing Nothing
- Standing in the Moment of Pain (1 minute)
Multi-Threading
- Navigating the Decision Process with Multiple Buyers podcast (11.5 minutes)
- Multi-threading with Application Security featuring Matt Petrovick (GitLab Strategic Account Executive) (1 minute)
424f73d2
)