Latest / The Goats of Growth / Can They Explain the Prompt? Hiring SDRs for AI Fluency — Brian Liebel, SDR Leader at Glean
Transcript
- Jay Webb: What's good, everybody? Welcome to another episode of the Goats of Growth, where I interview go-to-market leaders and founders of tech companies to learn how they've been adopting AI in their go-to-market, both positively and negatively, as far as how it's impacting their operations. Today's episode is brought to you by Common Room, the AI go-to-market intelligence platform trusted by top-performing teams like those at Okta, Anthropic, and Fireworks, to name a few. Common Room's agentic flows. Help your team know who's in market, act on those signals automatically, and run go-to-market motions at scale. Click on the link in the notes to learn more. Today's guest is Brian Liebel, Director of Global Sales Development at For the Americas at Glean, the AI platform enterprises buy to make sense of their own scattered int internal knowledge. Before Glean, he built SDR teams at eight by eight and sold Human Capital Management Software ran a territory of more than ten wireless ro locations as well before that. Brian, welcome to the Goats of Growth. Brian Liebel: Hey, what's going on, Jay? Pumped to be here. Thanks for having me. Jay Webb: Absolutely. Thanks for thanks for joining me. So tell me a little bit about with what I just ended there with about Glean. Talk to me about about Glean and your role there. Brian Liebel: Yeah. So Glean, right, is an enterprise AI platform, right? So we help companies turn internal knowledge into action. so I lead our sales development function here, in the Americas. and we are you're obviously responsible for going to market, right? And, you know, uncovering, right, a a a super large gap in the enterprises of today's world, right? Leveraging AI to actually get value. so companies like Uber, right, companies like Disney, GM, right, leverage Glean to power their workforce. you know, it's a it's a super exciting company because we we're growing at a tremendous rate, right? We're we're a tech unicorn and and we get to have AI conversations in the the gold rush era, right? We're we're slinging pickaxes during the gold rush, which is is super exciting. you know, so our our customers, right, are are not only looking for AI. Right. But they're looking for people that know how to deploy it at scale, right? They know how to get value out of it. and you know, the crazy part about the today's world is no one's ever done it before. Right. So I was actually at a a conference a couple of days ago and they asked, What's your what's your differentiators, right? What's glean's moat? Right. And I would I would actually call it our sales process, right? we're we're not just coming in there and and value propping people to death, right? We're taking really deep dives into uncovering a deep understanding of their business, right? How to leverage AI at scale. we're a horizontal tool, right? So we can sell glean to anybody. IT, engineering, manufacturing industry, retail industry. It doesn't matter where you are or what you do. there there's a use case for Glean. and that's the exciting part about you know the space we're in. So I've been here six months, right, and we've scaled our team pretty significantly, right? We have over a hundred SDRs globally. and man, it's been a a wild ride based here in Nashville, Tennessee. but we are HQ'd out of S F. so we are you know super fortunate, right, to to not only be centered in just the Bay, you know, we have a presence in New York, we have an office in Nashville, and we're we're growing in all three places. So super pumped to be here and you know talk about how we're helping people. Jay Webb: One thing that you said that sticks out that I wanna follow up on, you said deploy at scale, which in my mind I think, okay, so there are deployments and then there's deployments at scale. And people in in in companies obviously have heard some heartburn deploying at scale and being able to do that. Tell me about that. When you say deploy at scale, what what have they struggled with? And then what is Glean helping them do? What does it look like when there's a successful deployment at scale? Brian Liebel: Yeah, if you if you go back in time, you know, two years, right, year and a half, two years, every every company in the world, right, had a mandate, right, from their their C-suite or the board or their founders to use AI. Because nobody wanted to be, you know, the person that didn't use the smartphone when the smartphone came out. Nobody wanted to be the person that didn't move to the cloud when the cloud came out, right? so so companies wanted to get ahead. and what happened was, right, they'd buy one of the large language models OpenAI, Claude, et cetera, and just give it to every employee, right? Say, use the crap out of it, right? Let's let's blow through as many tokens as we can and just leverage this to get efficiency, right? And to to get scale and to make people do more with less. and what they found was that wasn't happening, right? they were spending a lot of money right on these licenses. spending a lot of money on tokens and they weren't seeing right an efficiency gain, right? and the big reason was there's a a huge gap when when you use AI if it doesn't have the context of the tools that you work with it. So your CRM, your SCP, your ERP, right? Nay insert any tool. AI is only as good as the context that you give it. I'm sure everybody's, you know, created a presentation or drafted an email and that first pass stunk. You know Glean's has a really unique ability to connect horizontally across all of your tools, not only index the data, but under st it understands the data. you know, so what that allows companies to do is, you know, we have a you know, our our amount of daily active users and monthly active users is double the the trend in SaaS, right? Typical SaaS deployments, you see 10 to 20 percent daily active, monthly active users. Glean's in the forties. Jay Webb: Mm. Brian Liebel: which tells us when when we deploy, when we attach to every tool in your tech stack and we're embedded in your infrastructure, your frontline employees right actually get value out of it, right? Because they're getting work done, right? They're they're actually getting work done with AI versus prompting it and using it as a an answer machine. people use Glean as a thought part. Jay Webb: Yeah, that makes sense. And one of the things you mentioned is, you know, boards are looking for or executive teams and so forth are looking for outcomes, looking to find a way to attribute these deployments, the AI agents, to some sort of an outcome, whether it's generating more income, lowering costs, improving efficiency, all of that stuff. Talk to me about that and some of the pressure that the teams are failing to inject and implement AI and AI agents into their flow of work. And is part of that conversation that you're having on the sales side that exact thing where that's FOMO where they're where they're they're feeling like they need to do something, but they don't know what they need to do, they don't know how to do it. And and you and your team obviously are sort of pulling that out of them in conversation. Talk to me about that. Brian Liebel: Yeah, I think your your depiction there is right. Right. And if you're, specifically on a go to market team, you've you've probably had that thought, right? Am I missing out? What am I not doing that someone else is? Right. I see all these thought leaders on LinkedIn talking about this, that, and the third with Claude, or I and you're sitting there wondering to yourself, what am I doing wrong? Because I'm I don't feel a big gain, right? And a lot of your a lot of the ancillary tech. Right. Ever every tool in your stack is some component of AI that's been built into it. Right. And you probably noticed, right, your tech stack two years ago, everyone attached AI into their into their actual name of their company and quite simply for that reason. but using AI within a, you know, kind of a standalone tool, right, versus using an AI native tool that is not standalone is quite different. you know, I think when when our SDRs are having conversations with these executives, right? We're reaching out to not just sales leaders, we're reaching out to IT, engineering, we're reaching out to customer support. you know, the the the common thing we're hearing is we're already doing something. Right. Everyone's everyone's got, right? You know, Claude or Chat GPT or Gemini, insert one of the LLMs. but where we are able to really, you know, kind of challenge the status quo is asking those questions, right? Unraveling, not in a negative way, but in a in a curious way around like what is it doing for you? Right. How how is your business difference from when you guys deployed that versus now? What is it not doing for you? I think if you ask any leader in any space right now, there's something that they want AI to do for them that it's not, right? And and often right the the reason it isn't is 'cause it it doesn't have that context. But I don't want this to be a glean sales pitch. It you it's a it's a common problem in the market. that I think you're you know, you're not alone if you have that feeling. Jay Webb: Yeah. Brian Liebel: but that that's what we're hearing now is we're doing something, but we don't really know if it's working or not. We don't have Jay Webb: Yeah. Brian Liebel: a way to track it, right? None of those tools show you efficiency gain. They don't show you, you know, implicit or explicit ROI. So it's hard to it's hard to measure too. It's really hard to measure. Jay Webb: So let me ask you this, as it pertains to your own team and and how you're operating with your you know, your your sales development folks, how are you sorry everybody, if you hear the barking, that's my my dog there in the background unexpectedly. How are you using workflows and building agents to to find efficiency gains with with with your team? And and then I guess Part B of that question is that as you as you're evaluating talent on your own team, what skills are you looking for as it pertains to their use of a usage of AI? How are you able to to screen for that? So talk to me about that. What you how how you actually integrated into your own go to market team. Brian Liebel: Yeah. I I love this qu I love this two part question, right? To the first part. you know, to me, true agentic workflow is that agent working autonomously for you. It's not prompting, right? It's not you plugging in a bunch of inputs to get a get an output, right? It's do you have, you know, agentic workflows in place where when your SDRs or your salespeople are doing, you know, high value activity. So talking to customers, right? Is that agent working for them in the background? Right. So to give a specific example, every morning, right, when when my SDRs come in, right, we we have agents working in the background that are servicing them top accounts, signals, et cetera. it's actually able to pull these pro find prospects within these accounts, put them into their workflows in our SCPs, craft first messaging. So when the SDR sits down, They already have the the work the legwork done, right? So the prospecting, the research, you know, using your your data tool, bringing someone into a sequence, et cetera, et cetera. And then they're able to use their brain, right? And really structure a point of view on an account. so that leads into the second question, right? We're what we look for, right, and what a lot of I think businesses are looking for now in their interviewing processes is AI fluency. Jay Webb: Mm-hmm. Brian Liebel: so We care less about if you got some certification in Chat GPT or you have some coding license in Claude, right? Are are you AI fluent? Right. So what that means is do you not only know how to use right AI in a way to make your life better, but do you know how to use it in a way where it does not create a knowledge gap? so there's a really interesting study done in China last year where they they allowed 30,000 students to grades K through twelve or seven through twelve. to use AI in their, regular coursework of the semester. And they saw speed to complete homework go up. They saw or I'm sorry, speed to complete homework go down. So they were getting their homework done quicker. They saw scores go up. And initially you go, wow, right? AI is making us faster and we're getting the answers right more. Right? It's gotta be working. And then they took it away for the final exam and they saw exam scores plummet. Right. So there's this knowledge gap that AI is creating and and when you're in sales, right, you you can't have that. Right. Because when the AI is not in the room, when it's just me and you, right, you have to know what you're talking about. Right. You have to have business acumen. You have to be able to, you know, empathize with a prospect. You have to know what questions to ask, ensure there's AI riding copilot on some of these calls. but if you don't have AI fluency and you can't speak through the prompts and the agents you're building and you don't understand what it's doing for you, that's the problem that will happen. and that's something that we intentionally try to avoid when hiring and then in the day to day. Jay Webb: Can you measure AI and actually define AI fluence and fluency for me? And then is there a way to because obviously it's hard to measure when you're in a a a conversation? Well, no, is it let me ask you define it for me and is it hard to measure and under and get a grasp for a particular candidate's fluency during the conversation? Brian Liebel: Yeah, I think put yourself in an interview process, right? And specifically a go to market role. It's really easy, right, for anybody to plug a a a pretty strong prompt, right, into Claude or GPT, right, to prep you for an interview. It's gonna tell you the buzzwords. It's gonna tell you what that interviewer wants to hear. you know, it it's gonna be able to give you a you know, if it's a practical interview, right? So a cold calling exercise or an emailing exercise or, you know, all of these, you know, different scenarios that, you know, happen in sales or go to market related interview processes. We give you pretty good pretty good results, right? it's it's probably the easiest, that discipline's probably the easiest for AI to make you look good initially and say the right things. can you peel back layers, right? Can you walk us through why you prompted that? We know you're gonna use AI, right? We want you to, right? You have to embrace it. But can you actually explain your reasoning, right? So can you explain why you put those prompts in, right? Can you talk through the results? do you have the acumen to know if the answer is right or wrong? Right. I mean, Sam Altman, OpenAI's CEO, said it himself, right? Y you shouldn't trust AI, right? Because the results aren't always accurate. I'm paraphrasing that, but you can find the the direct quote. so you know, we look for are you able to use AI as a thought partner, right? And not an answer machine. Right, because if you use it as an answer machine, it will hallucinate, it will be wrong, and you won't actually learn anything. Whereas if you're using it as a thought partner, you you can learn from what AI is doing for you. So that's a little bit of like the detail behind fluency. there are some deeper things that we do, but in general it's it's simple, right? Can you walk me through how you got to that result? Right. Jay Webb: It's like my kids who are now thirteen and eleven, eighth grade and sixth grade respectively. And when they first started doing long division, and I can't remember when that was, but they would do the long division, they'd get the answer, and then the next follow-up question would be, Can you show me your work? Right. And Brian Liebel: Yes. Jay Webb: right, and it's the same thing, right? There's a parallel between prom writing a strong prompt, producing an answer, but then the next level question is is that, well, Talk to me a little bit more about that. why did you why that prompt? And you know, I think one of the things too that it sort of illuminates is patience, persistence, critical thinking. Like I feel like there's so many different things when you are prompt engineering, if you will, to produce a particular result. it's illuminating, I think, how many things and I'm not sure if you and I had talked about this offline or not, because I've been having a number of these conversations, but at the end of the day. There is a skills gap that is to your point, right? That is that is starting to to widen, right? So there are people who are going to be AI affluent in in inf AI fluent, and then there are people who aren't. And so when opportunities come up, whether it's at your company or elsewhere, if you have two people and one person is proving that they are more AI native and more AI fluent, they're going to be a stronger candidate. And ev everybody is concerned about that AI is gonna take more SDR jobs, AI is gonna take AE jobs and so forth and so on. But I feel like if you're able to sit with the co AI, like co be a co pilot or have it be a copilot and exponentially improve your own productivity, you're gonna be that much more valuable and you're gonna stand out that much more as a candidate than the next person that walks in who is is a little bit behind there. W would you agree? Brian Liebel: Yeah, spot on. Right. I think In sales or STR roles, yes. I think in ops and support roles exponentially more. Right. If if you're a if you're an old school sales ops manager or revenue and like if you don't know how to, you know, orchestrate AI at scale for your sales team or your STR team, you've already been replaced, right? You see the, you know, go to market engineers out there, which to me is just the fancy title of the new sales ops manager that knows how to use AI, right? That's all that is. you're done. Right. that and that's that's not to sound harsh, but that's the reality because there is not a enterprise in the world that's looking for, someone that knows how to do CM CRM reports in Salesforce. Anyone can do that, right? We are looking for people that can run complex infrastructure, complex AI orchestration. so yeah, that I think the ops related roles see see an impact and already have. and I think the sales related roles in a transactional sale, yes. there are things AI can automate out for you, right? In a complex enterprise sale, maybe not, right? If you look at all the the big players in AI right now, they're all hiring SDRs, right? And there's a reason for that. Jay Webb: Yeah. And I think that, you know, the the the companies that are that are hiring those enterprise account executives, I we just picked up a couple here, it's in one of the things they said is, you know, we're gonna give preference to people who are, you know, fluent, more AI fluent th than not, because you know, if you could produce, you know, X amount in a certain period of hours on, you know, one person, let's just say, what can that next person produce? Right, even in that same seat because they need to fill the seat. It's not like they're not filling the seat, right? Because to your point, AI can only do so much, right? They're not filling the seat, but you know, can you look at your position in a way that's bigger than you are right now? and in and and get that much more out of it. So it's it's it's very interesting. What about, and this is a question that I'm just now curious about as I'm hearing you say this. Let's take a team of account executives or a team of of of SDRs, and now you have a sales enablement team, right? or RevOps team, somebody, or even just director of sales, right? Director. Where does is there room for additional enablement or training? In other words, AI enablement. In other words, okay, we we want to be more, we wanted to hire more native AI folks, right? We want these we want our team to be more to be stronger in this area, but they're not, right? There is a knowledge gap that we see and understand. And maybe RevOps comes in and and really helps under close that gap a little bit, right? Let's get on and let's start building something in Claude. Let's pull up a a vibe coding app and I want to create an agent. what do you think about that in terms of companies who are AI native, who have the the bandwidth, so to speak, and the knowledge to be like, all right, you what, we're going to specifically encourage and train our team to get better at building workflows and building apps and working with Claude. Talk to me about what what your thoughts are on that. Brian Liebel: Yeah, it's interesting. I think it's so different based on the size of your business. Right. If you're a a startup or, series A, Series B company, right? there's a there's immense value, right, that that can bring. Right. I think enab a big gap I've seen in the past is enablement, enablement and sales need to be super tight. Right. If if the sales leadership isn't helping enablement guide it's it what it wants enablement to do and quite literally is to make people better. you often see those those trainings fall flat. I don't think there's anyone in the world that doesn't want enablement to come in and say, Hey, here's a really amazing new workflow you can use to to make your life better, right? To make your your job, you know, more effective. but what happens is is you know, you start seeing, you know, if you just enable everyone and say, Go start building with AI without any strategy, you get a ton of wasted you know, AI slop, right? You get a ton of AI tech debt where you're building all the your vibe code and the a little tool or you're building a workflow that half the team's using, the other half isn't, right? If there's no strategy behind it, Jay Webb: Mm. Brian Liebel: I I see that everywhere, right? That so so what what's happening is I call it the AI tribal knowledge silo, right? because you know a lot of companies don't have that infrastructure. Right. And to your point, I think enablement or RevOps is a really great team deleted in a sales org. Be because they have purview into every team involved and and probably have a better lens of some of these workflows. I know our team here does an amazing job of of enabling us, but you the the key thing here is what are you enabling, right? And what is the problem you're looking to solve? Just vibe code and divide code d doesn't really add business value. Jay Webb: Yeah. Brian Liebel: It may make that one person's life better, but if it's not scalable, you're not gonna see a true efficiency gain for the business. Jay Webb: Yeah, that makes sense. I didn't even think about it that way. It's funny. I was talking to somebody recently who I think they're coming up on the the the podcast who they have a a budget for their reps to build stuff, basically. Right. and you're there there's certain certainly silos because they're all building different things at their desk for their own use cases, so to speak, right? But if it's not if it's not pulled together in an in an organized way. I can see how that can, you mentioned tech tech, how that can certainly get out of hand. So I'd be curious to to hear how that how that goes for sure. What up this brings up another question, which is well actually I'm gonna go back to a thought that I had and then I'll come back to to this one. which is the build verse buy, right? Like you have an ability to build certain things within your own Flow, go to market, so to speak. And you might come up against this in the sales process, and then you have the ability to or the choice to buy. How do you think about that? In other words, so actually I'll combine the question. The the the the workflows that you have now as far as your team getting prepared to get on a meeting and in and and pull in the right information, all that. Is that a third-party tool that you're using that is you know, has AI built into it? Is it something that you guys have built for? flows, workflows internally to start pulling information to prepare your reps. Like talk to me about that and and and the decision to build your own versus buying and then how do you sell against that, right? When somebody wants to build their own as opposed to you know buy your own your solution. Brian Liebel: Yeah, it's a good question. I again I yeah, I know this I've said this before, but it's extremely variable, right, based on what you're trying to build, right? Jay Webb: Yeah. Brian Liebel: if if you're trying to build, you know, something to compete with a sales engagement software, right? Or a parallel dialer or a you know, signal engine, right? There there's variance there. If you're trying to build you know something like man, you know, it We hear that often, right? 'Cause everyone thinks they can build, right? but but you can't. You know what I mean? Like v very rarely can you, right, when it comes to large scale products. Now if you're looking to build something right, simple, in you know, f for simplicity's sake, like you know, and some of our our vendors are are gonna hate us like I can build a really, really great, right, account research agent in Glean, right? That's gonna tell me everything I need to know about an account, right? It's gonna log into Salesforce and tell me all of the historical context. It's gonna pull every signal that we have in Salesforce and anything outside of Salesforce that we don't have, right? Jay Webb: Mm-hmm. Brian Liebel: like that's that to me, right, if if it's database, like it's relatively easy to get. Int using internal AI, right? Building it yourself. Now, is it scalable, right? It depends on what you're looking for it to do. you know, so I think like if you're trying to build use some complex, right, you're trying to build an HRIS system, right? You're probably not gonna get AI to do that because when you think about security and governance, that's a whole other world, right? In and a l and where I'm going with this is if it is a commoditized task. Right, or something where the data and information is readily available and it's internal facing, you can use the I to build it. If it's something Jay Webb: Mm-hmm. Brian Liebel: that's gonna be external facing or encompass customer data, right, then then then you're talking about a whole different world. and that's another big reason why people like using Glean, right? Because of you know, the way we help you safely and securely govern your data. you you probably shouldn't try to build it yourself. you probably should pay a trusted vendor that's servicing large companies that are similar to yours because you don't want to take on that risk, right? That risk is not worth it. So build, you know, simple internal facing, right, you know, repetitive tasks. I would buy anything that's touching your own sensitive data. it's a massive risk, right? So I know that's a broad answer to your question, but that that kind of encompasses every industry, not just sales. Jay Webb: Yeah, that makes a lot of sense. I have a follow-up question to that, but first let me just read the the the next ad from Common Room, sponsoring this next question. Common Room is the AI intelligence platform that pulls your CRM, your product data, and real-world signals like web activity and other buyer intent signals into one cohesive view. One of their products, Person 360, unifies account profiles across companies and keeps everything updated. check out the link in the show notes to learn more about that. Let me ask you this from your own perspective. Have you had that? Have you faced that yet in terms of the decision to build verse buy? or maybe you were presented with something that could solve a problem and you said, geez, you know what, this is you know, nothing that is it's it's more of a a point of problem perspective. In other words, it's like a sp single problem that I know we could solve. Could we build this ourselves? Have you have you come up against that? Brian Liebel: So one thing one thing that we do internally, right, is obviously being an AI native company, we won't we want to empower our our workforce to be extremely creative and hey, y the especially our frontline employees, right? You're closest to the the the problems, right? You're closest to you know the pain. so I I can't off the top of my head think of a specific build verse buy scenario, but one thing that we have done that's really I think unique in the space is we've ran a S Dr hackathon, right? So you've probably heard of an engineering or IT team do a hackathon. You probably haven't heard of an SDR team do one, but you know, quite quite literally, right, we gave our you know our our West S Dr team they took half the day, right? And they locked themselves in a room and they listed out every part of their job that took time, that was painful, that they thought this shouldn't be this hard. and then they actually built within Glean, right? Glean's a low code, no code platform, right? So it's it's super easy to to build in in Glean using common language. they built some really cool stuff. they built some really cool stuff. And I think like some of those, you know, some of the agents they built or, you know, some of the HTML artifacts they built, we we leverage today now. So not a specific scenario like when you're talking about Buying tech, right, and displacing budget with internal AI build. But I think it's a really good starting point to get you enough information to know how to do that, right? you you have to channel the frontline, the people that are using the tool. Right. Remember, if you're using a an SCP, you know, ninety-nine percent of your users are gonna be your frontline contributors, right? They're not gonna be the sales ops person or the f the SDR manager, right? So you might want to channel. Right, that team to give you a really good picture. 'cause if you make their life easier and better, guess what? Revenue comes at the end of the day. So that's one thing we did at a hackathon and we built it obviously ourselves in there, but we also uncovered, some pain that we are looking at, other vendors to help us do that we we didn't build. Jay Webb: That is fantastic. I love that for sure. couple things. What was the artifact? In other words, what what what was the outcome? Name I'm sure there are a bunch, right? It was a hackathon. So, like what was the one name one artifact that came out of that that it was a a big difference maker? Brian Liebel: Yeah, th there there was a million. the one I'm thinking of is, you know, I mentioned this in the top of the show. it was that account research agent where, you know, one plug in the account you want to go after and it is going to download everything that you need to know. Internal context, external context, find you every single right persona that's necessary, find their data through our data provider, pull them into our SCP, and get you set up, ready to go. the next day with all of that work done for you. And as one of our SDRs built that. to me that's one of the most powerful because again, it's autonomously working for you, doing three, four different layers of work that came out of that hackathon. there are many others though. Jay Webb: Going back to what we were saying earlier, that's a fantastic resume builder for that S Dr, right? Because that's literally you you're literally writing that on his resume as you're saying that, right? that that's the thing. Brian Liebel: Yeah. Jay Webb: And the and the fact that you enabled them to do that, right, I think is is huge. So it begs the question, because it sounds to me like it was a it a one off, right? is this going to it it seems to me like something that should happen quarterly. Okay, every SDRs, we're gonna do another hackathon. We'll let's see what else we can come up with. We have this artifact that's fantastic now, it's helping us. Let's find the next one, right? Like, have you tell me about that? Like, have you th thought of doing another one or or make it a regular occurrence? Yeah. Brian Liebel: Yeah, we've done it is gonna be an occurrence, right? We we haven't figured out or we definitely wanna do it across the globe versus one office. you know, we've actually done that with our management team too, right? So it's like you you yes. The the crazy thing too, Jay, is like the capabilities are changing so fast that you you you kind of have to have a cadence to reevaluate what you're using AI for. I mean Quite literally a glean daily. I gotta I gotta stay up to date on what our platform can do because quite literally daily it's changing and getting better. And if if you're not constantly, in the AI world looking at what you're doing with it, you you're gonna be left behind. or you're gonna be missing out, right? So like, yeah, you ha the the the moral of the story there is have a cadence, right, of reevaluating how you're leveraging AI. Jay Webb: Man, there's just so many things there. let me ask you this. With that particular hackathon, right? Cause now I'm thinking about, okay, a sales leader just heard that on the podcast on the episode, and then like, okay, where do I begin? Like, what does that look like? That's a great idea, but what are what are the steps? So w I mentioned how that other company essentially gave their folks a budget, right? Here's whatever. Here's usage tokens, his fifty dollars, whatever it was that they did for that. Hackathon. what were the guardrails, guidelines? walk me through the the the mechanics, I guess, of that. Was everybody in a room? What wha what give it to me. What did it what did it look like? Brian Liebel: Yeah, so picture right downtown San Francisco, right? Big conference room, team of SDRs, ton of food, ton of coffee. We c you gotta cater that, right? If you're gonna lock salespeople Jay Webb: Course. Brian Liebel: in a room, you better give them coffee and food. and they started with like really two guidelines, right? Because I think the more you create guidelines for something that should be creative, right? At the end of the day, it's a hackathon from from our lens is a creative exercise. It's less about an engineering hackathon where they're chopping away at code, right? This was an I an idea hackathon, right? Jay Webb: Mm-hmm, mm-hmm. Brian Liebel: you know, they had to one, present right, whatever they were building with a business case, right? So that was the the first guideline. So at the end of the hackathon, each SDR presented their agent or agents or whatever they built with AI in a in a business case format. Right. So what problem was it solving? what value is it going to add to the business? and then the the other guideline was we wanted them to quite literally start there, right? Think about the pains and problems that exist today, right? That take time away from you doing what you do best, talking to people, right? Talking to customers. Those are the Jay Webb: Mm-hmm. Mm-hmm. Brian Liebel: only guidelines we gave them. It had you had to genuinely think about, you know, from business perspective, what does this solve? And then two. Is this something that's gonna allow you to do more human time, right? For lack of a better term. but we Jay Webb: Yeah. Yeah. Brian Liebel: doubt those were the only limits, right? And I think because we didn't limit them too much, we got some really big ideas, right? And then we got some smaller ideas, but they all accomplished the the goal we set out to do. Jay Webb: I think I heard you say I love that. It's that's fantastic. I think I heard you say that it didn't just stop there though. You I think the the leadership team or some some members of the of of the the leadership team did it as well. Tell me about that. What did that was that essentially the same mechanics and what w w what was the outcome there? Pul poking out pricking artifact or something that was built as a result of that? Brian Liebel: Yeah, I think when you you and again, every environment's different, every business is different, but when you enable your workforce, right, to to leverage AI, you you also wanna, like I said earlier, you wanna understand what's working, right? So what I what I ask my managers to do is, hey, I've heard a lot about a lot of these really great agents people have built one off in silos, or you know, there's a lot of buzz going on around, you know, Zach's agent that he built, right? Because it's it's a better version of what We deployed for the team, right? Because, we're we're we're giving them a space to be creative and use it, right? and that's the coolest part is g guess what, right? our you know two month in ramp SDR built a better agent than what we built three weeks ago, right? So that that just goes back to like as the capabilities change, you have to constantly evaluate. So what I asked my managers to do is just make sure that we have the pulse, right? And we're constantly updating what our top agents are to do. insert the many jobs a salesperson has to do. So that I think that's where management hand comes in. You should build, right? You should be creative as well. But make sure you know what your people are doing, right, that's working. Right. And man, I'd say once once every couple of weeks we're on a team call and they go, Hey, you're not gonna believe what so and so built. Right. And then we get to go into the lab, right, and cre you know, just you know, think, okay, how can this change our business? So that's what they do. Jay Webb: Yeah, for sure. I think I that's the culture that you're building there, right? Like what you just described versus, let's say, for instance, another company, call it same size in the same space, but they're not necessarily thinking in that way, right? And they don't have that culture. They don't have the culture of the hackathon that you just talked about. You don't you're not building things, breaking things and coming to idea coming together to figure out ideas and okay, what what what worked literally three weeks ago. Is not working now because by the way, do you hear this new thing about Jev? What's Jev? Jeb does things, Brian Liebel: Yeah. Jay Webb: there's so many different things that people that you have to stay on top of in order to get it. So I think it's it's interesting. This whole AI thing, it's like it's definitely it's it's exponentially making things faster. But one of the things it's definitely doing is the FOMO piece that we talked about before, right? Because there's so much to keep up with. It's it's It's it's it's crazy. Just I'm gonna try to squeeze in one other question here before we get to the rapid fire five, just because I'm curious, which is because I've I've I've built a lot of agents that I use for my own company and I feel like as time goes on, and I'm laughing because like time like a week goes by and I think, I better go reevaluate what I just built a week ago to your point, because capabilities change. I feel like also the context that the agent has may may may may be wrong. In other words, it may not have picked up on the newest context, the newest inputs that you just put in it, even though you're thinking it should as a human, because that's if I if I was sitting alongside a human and I go, Hey Brian, could you start thinking this way and forget about what we said three weeks ago? And sometimes the agent picks up on the stuff that was three weeks ago that's now stale, right? And so to continuously look at what you're what you've built and what you're using is a job I guess in and of itself. and I guess this will be the last question before we get into the rapid five, 'cause I feel like I could keep going, but I know we're gonna run out of time, which is that artifact that you just th that that was built in terms of the pulling all of the information that the team needs, you know, to prepare themselves for calls and all that. How often do you feel it's necessary to go back and look at that and evaluate and be like, all right, is is is it still working? Right. Or is it is it is it Has it lost context or is it stale? Or maybe we're because they were using glean and I'm thinking because I'm using, my own stuff that is less than glean, Brian Liebel: Okay. Jay Webb: that that maybe that maybe it's it's not you don't have to worry about that. It's it's it's gonna be fine, right? I don't know. You you tell me like how much do you need to go back and and revisit it to make sure that it has the right context and it's not hallucinating and doing the right things. Brian Liebel: Yeah, fortunately with Glean we don't. because Glean's connected to Salesforce, right? We can have, you know, we set auto like certain artifacts or certain agents refresh or run on their own time. And you know, Jay Webb: Mm-hmm. Brian Liebel: say it's you know, an SDR working company XYZ and that agent ran for them, you know, a month ago and added some prospects, uncovered some closed loss notes, you know, and say that SDR booked another opportunity and that op closed out. A month from now, two weeks from now, the day after, Glean has all of that context, right? So if a new SDR inherits that account, they're gonna have that context, right? They're gonna know the most up-to-date information on an account, just due to you know our platform. for other things, you know, I I I do think like anytime you're connecting data to your AI stack, right, or connecting another tool to your AI stack, you also have to understand w what's changing in that tool, right? So like I I find that often, right? People people connect, right? And it's maybe not necessarily what you built in Claude, but it's, Claude's MCP into something else that got all funked up. so I think us we're we're the benefactor of not having to really do that. We we have guidelines and you know certain parameters that we set based on the agent where we are checking that, but in terms of your question of context. that is the biggest problem enterprises face is what you said, AI hallucination, because it doesn't have the full story. Jay Webb: Yeah. Brian Liebel: and when it does, that's when you I think you really get game changing results. Jay Webb: Yeah, yep, for sure, for sure. Yeah. That's been a personal pain point of mine, candidly, as is you know, just building my agents, building my recruiting agents, just going back and I feel like I'm constantly trying to improve it and tell it no, that's not what we talked about. this is this is what you really Brian Liebel: Yeah. Jay Webb: this is what you have to be thinking about going forward. Like this is I don't know, it's just it's crazy, but I appreciate that, for sure. Okay. You ready for the easy part, which is the rapid fire five, I ask you five questions, you give me five rapid answers and then I get you out of here with the bonus questions. Brian Liebel: Yeah, th this might be the hard part 'cause these these questions, while simple, man, I I overthink. So these are these are fun ones, but I'm I'm ready to rock. Jay Webb: All right. Sounds good. Well, I'll give you a couple more seconds. I'm gonna read one more ad from Common Room really quickly here. So Common Room presents the Rapid Fire Five. Common Room defragmi defragmatizes your first party data and combines it with real world buyer signals. Context three sixty in particular enriches, resolves, and keeps it always fresh. So again, go to the link in the show notes to learn more or reach out to me and I'll make a personal introduction to you, to the folks at Common Room. All right, here we go. First question, the rapid fire five. number one, what motivates you? Brian Liebel: Yeah. So what motivates me is I hate to lose, right? so there's nothing in life that to me stinks more than losing, right? and I've used that mindset to, you know, kind of channel right what happens on the opposite end of losing, which is winning, right? So you know, being able to have this fear of failure, which I think is a good thing, allows me to approach everything that I do in that facet, right? I want to win. and it sounds very simple. but throughout all of that let's call it childhood trauma of maybe, you know, losing in sports or not being the the tall athletic person or not being great, I've found that when you're able to stay motivated and you know focus towards a common goal of winning, and you have a fear of failure, right, you're actually much more prone to learning, right? You're much more open to you know, learning from your losses, right? I always say, show show me someone that's okay with losing and I'll show you a loser. and I know that's aggressive, but man, I I I really think the the the end cap of all that is you know positivity, right? You know, I I correlate winning to being positive, right? And and to me, I'm able to be in a much more positive mind state when I'm doing good things, working really hard, avoiding failure. But fear fear of failure, right, and hate to lose is actually what motivates me. Jay Webb: I was talking to my daughter last night who's a basketball player and I said to her, I said there's I her name's Jada. I said, Jada, there's winning and then there's everything else. That's just what I said. So yeah, I'm I'm right there with you. number two, name a big goal you have right now and when would you like to accomplish it? Brian Liebel: Yep, run a half marathon and by February. so I got into running pretty big a few years ago. busted my knee, fell off. I need to get back into it. It's ninety eight in Nashville. and I hate running on a treadmill, so I gotta hit the road. But starting tomorrow it'll be fifties and sixties. So I'll be I'll be out on the road and I wanna get back up to to running a half marathon. So that's that's my goal and I'll be I'll be doing it by February. Jay Webb: I have to ask this follow up question. Do you have a a goal in mind as far as the time? Brian Liebel: I wanna keep it under a nine minute mile, right? So anywhere Jay Webb: Okay. Brian Liebel: in the eights would make me happy. Jay Webb: Okay, there you go. All right. I'm gonna have to follow up. When is when's the race? February. All right, cool. I'm gonna be f Brian Liebel: February. We got some work. Yeah, we got some work to do. Jay Webb: I'm gonna be f I'm gonna be following up with you on that. Good luck. That's awesome. what's your most preferred way to learn new information to stay sharp? Brian Liebel: Man, I'm a I'm an audio, right? I'm an audio person. I I love listening. I love podcasts. I love audio books. I am not a physical book guy. I'm an audio book guy, one hundred percent. to me, right, the car is the the greatest place to learn. you know, capitalizing on your commute to work, is what I found is the is the best way to learn because I have all that time. just me, the car and and whatever I'm choosing to listen to. So audio book, podcast in the car. A hundred percent my favorite way to learn. Jay Webb: Love it. Who's your favorite character of all time? Brian Liebel: Man, I've been thinking about this question for too long and I I don't think I can choose one. But if I had to pick, it's Will McAvoy from the show The Newsroom, played by Jeff Daniels. I think the newsroom is one of the the greatest shows that has ever been made for television. it is just absolutely fascinating. he won an Emmy for that role. the year of Breaking Bad, right? The year of Mad Men with Brian Cranston and John Hamm. so that that to me is is the best you know, fictional character of all time because it's a fictional show about a newsroom that covers nonfictional topics of history. So check it out if you haven't, but Will McAvoy played by Jeff Daniels. Jay Webb: wrote that down. I'm gonna s I want to look at it now. last question. What's your favorite thing to do when you aren't working? Brian Liebel: Man, two things. One, coach basketball. So I I, work for a travel basketball program based out of New York. I've coached for a long time. since moving to Nashville, I coach much l much less, but get to meet them on the road and support. so you know, being involved with with youth sports is my passion. and then secondly, you know, honestly being a homebody with the wife and and our three dogs. not nothing beats that. so in a gym coaching basketball or at home on the couch with with the family. those are my two favorite things. Jay Webb: Sounds we got a lot to talk about offline. Lot lot Brian Liebel: Yeah. Jay Webb: lots of similar lots of similar passions. That's fantastic. Okay. You ready for the bonus question? Brian Liebel: Let's do it. Jay Webb: All right. Bonus question comes from Evan Leek, who's the senior director of integrated marketing at curio. All right, here it is. If you hadn't gone down this particular career path that you're on now, what's the alternative altern alternate version? of you doing of what you're doing right now? what would it be? What's the alternate version of what you're doing? Brian Liebel: Yeah, if I didn't go down the the the road of sales, which I've been in my entire life, I would be a chef. I would have gone to culinary school and I'd be I'd probably be working somewhere on the line in a kitchen. food's another recent passion. And unfortunately, they don't pay as good as B2B Tech does, so I I won't be making that that that leap into that world. But if I had to start over, I I bet you that that's the road I would have. Jay Webb: Well, if you get your own show, your own chef show or something, Brian Liebel: Yeah. Jay Webb: then maybe, you know, I mean, come on, think bigger, Brian. I thought this was about winning. my goodness. You know what's interesting by the way? I was looking at Evan's answer, and it his answer was chemistry, but as I'm remembering that conversation, he loves to cook. Like, and I said to him, I remember saying to him, I go, Wow, that's amazing. Because that was by the way, that was his answer to number five, right? In other words, what do you like to do? I think it was when you're not Working and he said cooking. And I like, wow, it's interesting because that's a chemistry exercise in and of itself, right? Because he's putting together or baking where he's putting together different, ingredients and and coming up with something. So I thought that was just an interesting answer. So interesting. Okay. I thought you were gonna say coaching. okay. Or Brian Liebel: Well yeah, that's Jay Webb: you know. Yeah, for sure. Okay. Brian Liebel: Another another profession that doesn't pay you well for long. Jay Webb: Yeah, exactly, exactly. Okay, so let me ask you a question that you would like for me to ask the next guest. Brian Liebel: So I'm gonna hit him with a simple one. and I ask this question quite often. So I'm from Buffalo, New York, right? Where the chicken wing was invented. there's only one right answer to this, but do you prefer to dip your wings in blue cheese or ranch and why? That's it. And the right answer is I'll give you a dot dot dot. Jay Webb: Do you prefer to dip your wings in blue cheese or ranch and why? And there's only one answer. I just feel like I need to attempt to answer that question. Yeah, and Brian Liebel: Yeah, yeah. You have to answer it, Jay. Jay Webb: and and how can you here's here's the honest thought as I'm thinking about that, right? I honestly don't even freaking know the difference when they bring out the the dressing. I don't. I I just say when they say blue cheese or ranch. To me, it's a freaking toss up, but I'm gonna say it's blue cheese. Brian Liebel: You're right. That's the right answer. You in Buffalo, New York, they don't even serve ranch, right? So th there there's one right answer. And if you want to get a room polarized, ask that question. 'Cause for some weird reason people get real passionate insert me about that topic. But that I'm I'm excited to hear what the next guest has to say. Jay Webb: That is fantastic. Wow. That is amazing. Wow. What a fun question. the easiest one actually. How can folks reach out to you to say thank you, perhaps learn more about Glean, maybe become a member of of the team? What's the best way to for them to do that? Brian Liebel: Yeah, add me on LinkedIn. I'm sure Jay will drop it in the show notes, but Brian Liebl, the I think there's only one of me on LinkedIn, not a common name. But find me on LinkedIn or firstname dot last name at glean dot com. Right. We are always growing, right? We're always looking, you know, for for amazing talent to join our team. so if you're passionate, you know, about becoming a seller, if you're passionate about getting into this world, you know, we'd love to connect or if you just wanna talk, Yeah, I'm happy to help. So LinkedIn or email but LinkedIn. So happy to connect. Jay Webb: the hackathons alone are a reason for one to apply candidly if if you are in the market and listening to this. So I mean, just I think you need to be with people who are forward thinking. I think companies need to hire people who are forward thinking. so for sure. And of course if you reach out to Brian, don't forget, use the goats of growth in the subject line somewhere or the first line of the the message if you're sending through LinkedIn, because obviously that'll get his attention. and that's obviously it'll be in the show notes, but that's Libel L I E B E L Brian. Brian, thank you so much for for doing this. This was fun. I knew I was gonna have fun and be excited to interview you and publish this because of all the things that you're doing over there at gleaning just your own perspective. So thank you very much. goodbye, everybody. Don't forget to subscribe, rate, and review. Tell your friends, colleagues, co-workers, all that stuff. and until then, I'll see you on the next episode. And that's it. Goodbye, everybody.