Speaker 1. Welcome to the Revenue Builders hosted by John Kaplan and John McMahon. In this clip, Daniel Simon from Glean breaks down what strong, multi-threading looks like in an enterprise AI deal. He walks through how he moved beyond the CTO and built use cases across product, engineering, finance, legal, and the AI program team. The point is simple. AI deals do not stick because one executive likes the idea. They stick when multiple people can connect the solution to their own workflow, their own path, and a measurable business case. For revenue leaders, this is a practical look at how to turn interest in AI into real internal demand. Let's dive in.
Speaker 2You said there's a difference between being in, Johnny said, like a domain expertise in an application versus the ability to connect hundreds of applications. And get that 360 view. And that is, I think that's extremely interesting for customers right now.
Speaker 3I do for sure. Where have we sold deals like this before, right? Like what are some roadblocks that I could face? Like maybe that's not in Slack and there's even like, you're pulling stuff from the public domain too. Like, Hey, help me do some research on this company. What are the different business units that I'm going to sell to? What are the different outcomes that these individual personas would then focus on? And I can craft my very tailored messaging to each of those people. That's not just going to live in Slack. So you really do need something that's much broader. And of course there are great, like there's legal tools out there. There's call center tools out there and they're going to do things that Glean cannot do. But you're always, like the first thing that everybody does in a company, and I'm sure we've all had an experience with like Google Drive or SharePoint. Like their search quality is terrible. And what a lot of the MCP, MCP is the connectors that a lot of our competitors use. And MCP is enhanced. They're inheriting that terrible search quality. So if you don't rebuild the context engine, you're going to have a really tough time finding the most accurate answer.
Speaker 2- Which again, is going to go to how the user uses, you know, at the executive level. So talk to me a little bit about like, I think selling in your environment is not just selling at the executive level. It's like, if I was selling your product, I would be selling to Dan almost as much as I would be selling to the CEO or CEO. Or CFO of a company. Because at the end of the day, how they are going to look at a success of any AI strategy is, if I turn it off, will Dan screen? Will Dan have a problem? That's my, right now, that's my ultimate, my ultimate measure right now. If you take away any of these tools, will the rep, will the user, will the end user screen?
Speaker 3- For sure. And I think that goes back to multi-threading. 'Cause I want multiple people to screen when that turns off. I'll talk about a recent deal. I sold at a really large e-commerce company. So the way I landed at the CTO, he then passed me down to a couple of different personas. There's somebody who leads the AI program for the organization. She has a plug into the product managers, the engineers, the finance team. And then also legal was another domain. We build a use case for all of them, right? And there is something that we can solve for each of those personas. So I like to sit down with each of them. They're one of the biggest differentiators that I learned. I learned early at EMC too, with a very crowded competitive space is get in person. In person is going to differentiate you very quickly. And with all the noise out there in AI, I think there's also something to be said of like, go build a real relationship. You're gonna get a lot of like outreach that looks very similar. You go build a relationship. You do that better in person. So my engineer and I flew up to this customer and we met with each of these people for about an hour. Identified what their current state is. What are some of the different metrics that we had on some of these use cases? So maybe it's like I'm drafting a PRD, product review documentation. An HR use case around onboarding new employees, like drafting open recs, for example. There was like a variance analysis agent that we had to build for the finance team. We quantify each of those use cases. How long would it take you to do that today? In some cases, like it took maybe 10 hours, 14 hours. And part of that would be like, oh, well now I have to go wait on an update from this person that sits over in EMEA, right? We're on a different time zone. So I'm waiting and waiting. Like that's stalling business. It's stalling revenue. So we have all of these little quotes as well embedded into this with the metrics, which I think really amplified the business case when we went back up to the CTO who had already brought in ChatGPT, mind you. So we showed him a business case of like, yeah, you have ChatGPT, but you're spending 10 hours on this task, seven hours on this test. This is how many different people that this is affecting in the business. It was like a seven to $10 million loss. For them to not buy Glean. We were a fraction of that, of course, but our ROI was something ridiculous, like 50, a hundred X, right? Because we've been able to multi-thread. If I only landed with like a single team, I wouldn't have had as compelling of a story.
Speaker 4- Now, do you think if they hadn't taken in ChatGPT and you showed up that you could have gotten the deal because they might've said, well, let's use ChatGPT first because we hear that that could do it. So is it almost better that, for salespeople that are selling a real good AI tool that they've already used one of the large LLM models to try to achieve what they, their business outcome and you come in afterwards because they're more educated?
Speaker 3- Yeah, I mean, I'm confident in my abilities that we could have got a deal done there, but I think you're right.
Speaker 4- I love that.
Speaker 3- There's no pain, there's no deal. Like there probably wasn't a lot of pain yet. And that's what I've heard in my first year of selling is like, oh, Copilot's our strategy. Oh, ChatGPT's our strategy. I'm kind of feeling today like it was back at my EMC days. Like nobody gets fired for buying Cisco, buying EMC. Like people are like, oh, we're not gonna get fired for buying Copilot or ChatGPT. Like everybody knows about it. They're the biggest company out there right now. And I'm starting to feel that a little bit with Anthropic too, but they all have the same challenges is token consumption, accuracy. Like they're just not there. And now that they have the pain, my message has become much more compelling. And it's also helped us sell into a lot of Fortune 500 accounts now, who have tried to build this themselves. They have two or three different products that are still not working. And it makes our story that much more compelling.
Speaker 4- They're not worried about security. That doesn't come up where you're taking all your internal data and it's getting consumed by these models and even customer data, personal data. They're not concerned that much about security and compliance.
Speaker 3- I mean, I'm sure they've got some good sales reps telling the story. And then on the other side, like they're six to 12 months into that implementation. Like, hey, this isn't, this isn't really what we were expecting yet. So yeah, I think what's cool about Glean too, is we actually do have a security product embedded into our platform. It's called Glean Protect. So it actually will scan for sensitive content. So say you have credit card information or any type of PII that you don't want in there. There's a bunch of rules embedded into that, or you can create your own rules to remove that from your index. So it also, like some of my strongest champions have become CISOs. They're like, I was looking at some data security protection tools and like, I'm a little scared of ChatGPT than making sure that they get this right. And you're telling me Glean, not only could help me alleviate the need to buy a separate product, but they feel much more comfortable rolling out Glean with the way it's not, it is permissions as part of that. We obviously inherit the permissions of that source application, but also making sure that their users can't search for something that's overexposed in SharePoint. Like there was a instance in a pilot that we were running, which frankly helped us sell the deal. They had the salary information of all of the executives and it was publicly accessible. So somebody like me, a seller, I could, if I knew where to look for that in SharePoint, and it was probably hidden in a bunch of folders, but if you're in a ChatGPT and a co-pilot, like I'm not so sure that they would have been able to catch that. And that's something that Glean can find.
Speaker 4- And who have you found in these deals? Where's the power base? I mean, you have the technical buyers, like the CIOs, you talked about a CTO, you get the chief digital officers, and you have the business buyers. You got sales, you got ops, you got CS. Where do you like to go first, second, and why?
Speaker 3- First, I'm always calling in the tech organization, because I do believe that they are the ones that are gonna roll this out. And a lot of them have tried to build their own platforms. There's also a lot of opportunities I've had around the data teams. So people that are working with some of the warehouses out there, the data bricks, like a Snowflake, they tell a very compelling message too. They actually both use our product for their own internal use, because what they do really well for structured data, Glean does really well for the unstructured data. So they're a customer and a partner of ours. We can integrate with their platforms to tell a much better together story, but instead of having data scientists have to kind of create their own Glean, we can actually automate a lot of that for them. So I'd say tech organization is a great fit for us, like engineering. Data teams and then go to market is also a great one. If we can drive revenue faster, help with better conversion rates, help win rates against your competitors. What I'm, I mean, it's QBR season right now. So I'm actually using Glean to build my QBR deck and they're urging us to do that. And it's not even a deck anymore. We actually have interactive HTML pages where I can say, "Hey, what's my forecast? What are the white spaces in my accounts?" And it can, it's like a presentation, but in a website format. I can just type that all out into Glean and it'll create an HTML website.
Speaker 5for me which is really awesome wow thanks for listening to today's episode if you enjoy the content please subscribe rate and review the show to help us reach more people this show is brought to you by force management where we help companies improve sales performance executing the growth strategy at the point of sale check out forcemanagement.com for more information Thank you.
PodcastTranscript AI