Latest / The Goats of Growth / Why Aware Went 100% AI SDR on a New Product Launch — Brian Krause, CRO at Aware
Transcript
- speaker-0: What's good, everybody? Welcome to another episode of The Goats of Growth, where I interview go-to-market leaders and founders at tech companies to learn how they've been adopting AI and the effect positively or negatively, by the way, it's having on go-to-market teams. And today's episode is brought to you by, I'm proud to say, Common Room, our first sponsor, ⁓ the AI Go-to-Market Intelligence platform, trusted by top-performing teams at companies you may have heard of, like Okta. Anthropic, one of my favorites, and Fireworks AI, 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 show notes to learn more. Today's guest is Brian Krauss. He's a fellow Bostonian as I am, go-to-market leader, advisor, and angel investor who has spent his career scaling some of the biggest names in AI, identity, and security. He led revenue teams at identity identity verification pioneers like Verif and ENCODE at Computer Vision Company, AnyVision, and at Pivot Pivot Three, which was acquired by Quantum. What intrigues me is how consistently he's been trusted to build and drive revenue at the frontier of AI and trust technology, right? Like, especially if you read, if you well read newspapers or listen to the news. I mean, AI trust is certainly. at the forefront of everything that people are building and using and those things really matter. So it's one of the reasons why I wanted to bring him on. He brings all of this experience as chief revenue officer of Aware, which is a biometrics and identity authentication authentic authentication company. Sorry. It's a loaded loaded mouthful. Brian, welcome to the Go to Growth. speaker-1: Jay, thanks for having me. It's good to see you again. speaker-0: So me just start with what I just ended with as I stumbled over ⁓ what ⁓ aware does. Tell me a little bit more about aware and your and your role at aware before we get into the a agent of it all, a AI stuff. speaker-1: Sure, yeah. So my role as CRO, so you know, I o I oversee basically all of our customer facing engines and teams here. You know, what what is account management, customer success? We've we've recently ⁓ carved off ⁓ a standalone marketing organization headed up by a CMO, ⁓ Lonitarian who's wonderful, but ⁓ was looking after marketing for a little while ⁓ bef before she arrived and ⁓ of course manage all of our acquisition teams. So whether that's our our government, Sales teams or our commercial teams that are located all over the planet. They are part of my remit as well. So a classic CRO role. I manage a revenue op RevOps as well. So I have I have a team that is managing our data environment, all of our AI tooling, all of our non-AI tooling, and all of our operations behind the curtains as well. So yeah, I mean, company-wise, you we're in the biometric space. So you you you said it very nicely about sort of centering on trust and you know, trust is really central to everything we we do as people and as as humans and certainly as we interact digitally and with each other or or with our you know providers, right? Our our banks or our our our ride sharing apps or whatever you know applications you know you're you're using to get to get what whatever services you're consuming in your daily life. And and trust is central to that. You need to be able to trust their them as a service provider and they need to be able to trust you as a customer. And and so in the l in in in the more recent years, we've seen a much more higher focus in investment on you know improving the assurance level of that trust that is assumed at day one. I mean, that's where our technology comes in to to give companies the ability to add tooling to ⁓ to to really increase the assurance that I am who I'm claiming to be. When I create an account or access an account. speaker-0: Let me ask you about that actually. I had another question, but you just made me think of a a new one, which is how do you inject that level of trust and the right level of trust in in in the product and maybe within even the the messaging around the product? ⁓ because obviously that's really important. speaker-1: Yeah. So, you know, trust is established at at different different levels, different layers, right? And so, you know, and in in our space, what we focus in sort of in the trust, you know, circle or pyramid, if you will, is the core biometrics. So it's it's data analysis, data comparison. So we'll take your picture, ⁓ we'll take your fingerprint, ⁓ we might take care of your irises or whatever really the situation or the the interaction calls for. ⁓ the the biometric information that we collect and gather is compared to or enrolled into some sort of trust library or or source of truth data store. And that allows us to make a really data driven and informed decision around, yeah, this is Jay. I can tell because this is, you know, Jay's fingerprint. And this is the fingerprint that Jay used when he initially enrolled. Or this is Jay's selfie. And this is this was Jay's selfie on day one when he opened this account with us. There are of course a number of different ways to further sort of assure that identity and triangulate the information to confirm that it's Jay. You might ask for a driver's license, you might ask for a phone number, and you can query data sources of truth to to further s position the authenticity of of ⁓ what Jay is presenting himself as, you know, when when ⁓ his information is enrolled and created in the system. speaker-0: Yeah, that makes sense. One of the reasons I reached out to you, obviously, was to talk about, you know, your your AI journey, so to speak, and and where you're at with Buildverse by ⁓ the impact it's having within your go-to-market team. And, you know, as I've built my own agent system or ecosystem of agents, I started to wonder, you know, what others are doing and how has it impacted them commercially. And when you and I spoke initially just to sort of get to know each other and and to learn. And one of the things obvious that you mentioned is that how important, speaking of trust, how humans are still at the forefront of of how you're thinking and executing and and how how important they are in that obviously there's still an there's an art and and a science to selling and everything around go to market. ⁓ before you ask a more specific question, just let me just pause there and g and and get me give me give me your thoughts and your philosophy on on what you meant by that. Yeah. speaker-1: I mean I still I still subscribe to the theory that sales is a people business and you know people buy from people and you know we're we're probably fast approaching a point where ⁓ people won't buy everything from people. We'll start to see, you know, some some products be purchased by non-people, right? And that's you know, this agentic commerce and and and sort of either for you know consumer or enterprise, like some things will be you know, humans will be comfortable purchasing some things from a non-human entity on the other end. I mean, that's just the the nature of it. And you know, price will drive a lot of that and savings and value. And but, you know, in enterprise selling, specifically in enterprise software, I still firmly believe that people do buy from people and there is a trust ⁓ that is required between buyer and seller that has to be established and and developed and built. ⁓ and that will kind of In my opinion, we'll be if ever, it will be a very long time before that goes away. You know, enterprise sales and and software sales is very different, obviously, than the consumer world. And and so there's a there's a big room for a lot of AI in go to market teams from a tooling investment perspective. But I still think you will never replace the human connection in software sales and enterprise sales fully. speaker-0: Tell me that. Tell me more about that. Where where have you where have you integrated it in your go-to-market org? Give me a couple of examples where you're using it ⁓ internally to, you know, the science part of it, right? To optimize the human part of it, to make them better, more efficient. speaker-1: Yeah, I mean we're we're we have we have tests kind of all over the funnel. We're we're testing different different tooling at different stages of our of our funnel, you know, in our activity pipeline now. And then we have some things in prod that the teams are using regularly around, you know, obviously data enrichment and and call recording, insight ⁓ sharing and and calculating all those pretty standard tools, right, that are pretty robust and pretty mature now, you know, out ahead of the curve from AI perspective. But then there's You know, there's agentic SDRs that we're doing some testing with just to kind of understand, you know, what the what the impact those those could have, how effective those actually are. I'm sort of I'm I'm sort of at the position as the CRO, as a revenue leader today, of like some of this stuff is worth a try because I think it's it's very important for us to understand what the impact it is. I w I'm not advocating for, you know, over indexing or overspending on this stuff quite yet. But I do think that that that the technology's gotten really good and you know a lot of folks like myself, like a lot a lot of sales leaders I know and speak to and you know on a regular basis are in sort of the same position is that capital efficiency is the name of the game. And so, you know, we've got to find ways to be able to continue to scale without just you know throwing more headcount into the P and L. And so, you know, productivity is is the natural place to look. speaker-0: You mentioned A AI SDRs, which is intriguing to me, to say the least. Tell me about that. Tell me what your results have shown so far. What's worked maybe in within that, what hasn't worked, where you've may have been disappointed. Tell me just because I think a lot of people are exactly what you just said, right? They're exploring and they're trying to figure out. I I'm doing it. I'm about to commercialize my own agent for let's say, for instance, if you're looking for an It's up to hire an S Dr, an account executive, like I'm going to hand my agent out to people who can use it besides who I am, right? And I need to figure out what's gonna work and what's not gonna work. Tell me more about what you've seen there with the AI S DR. speaker-1: Yeah, so we're super early days. And you know, I I think so so what we decided to do here was we're in kind of a unique position. You know, this this this company has a a ⁓ really, really strong history, 35 plus years, you know, first US based biometric company, tons and tons of pedigree in this space. Closet closets full of products related to biometrics, you know, SDKs and and and different full stack solutions and things like that. But we're really launching a new product. ⁓ this year ⁓ that we've recently launched that is designed specifically to fill an area of biometrics that has been that has been ignored or just not addressed for many, many, many years. And so the reason why it's relevant to the AI SDR discussion is because it presented the perfect opportunity for us to test something like AI SDRs on, right? It wasn't an effort here where we just said, ⁓ let's replace our SDR our team with agents, right? I'm a big fan of sort of the scientific method when it comes to kind of thinking about every problem we solve. And in this case, you know, isolating the variables down to okay, we have a new product, we have ⁓ a new addressable you know market, a new a semi-new ICP, new TAM for aware with this new product launch. We're trying to go higher in the organization to you know talk to different different folks than our sales teams or aware sales teams might have talked to in the past. So when you you know when you look at adding all this stuff up. It's the perfect scenario to start at zero and just build an agent for it. Right. We don't have a legacy SDR team or you know other other things like that dedicated to this product where there's variables that could come into play and upset the performance of it. So this was a pure play. We're launching a new product. Let's put top of funnel demand gen 100% AI at the jump and see what happens. Right. So we're still very, very early days with it. And and you know, happy to happy to circle back later and kind of let you know kind of where we where where it landed and and that. But I'm super excited about it. I I think, you know, again, it's it's great to be able to learn. It's cost effective enough and it solves this a specific problem for us, which is look, we're launching a new product. It's all about velocity, it's all about going fast, getting awareness as high as as as possible and and driving mind share about this product, getting people through the door to come see it, come test it, try it, learn more about it. And that's perfect for an S C R agent. speaker-0: I think that is a fantastic example. As you're saying that, I'm like, man, I'm like, that makes for such a great clip for this episode and a LinkedIn post, I feel like, because you're right. Like I feel w what I just heard you say is that without disrupting the existing workflow, so to speak, of of the team, right? Or pulling an SDR, any of the SDRs off of the accounts that they're focused on now and the markets and the personas and changing the messaging and all that, right? It's like, okay, let's go out and put out a an an an inexpensive test, so to speak, right? In other words, five years ago you would have called me and said, Hey Jay, we need three SDRs. We have this new opportunity that we're trying to focus on. And you know, you might have hiring them and then it doesn't work. And then you gotta fire them three months later and you're like, Jay, you suck. Why'd you send me people and it didn't work out. Whatever, right? So in that in this case, what you're doing is it's a it's a it's a low risk test, if you will, to put the AI SDR onto a market that ⁓ you might c currently right now you don't have the bandwidth for. And then once it works, I think what you're saying is, okay, let's say for instance, six months from now I reach out to you and I'm like, Hey, how's it going? You're like, It's fantastic. It's like a matter fact, we had to hire a couple of AEs to help support that, right? And all of a sudden it's a whole different story. So I love that, right? Where it's it's low risk, it's a new opportunity. And I feel like a lot of people, if they're not if they don't look at it that way, I think they should, right? For sure, for sure. Let me absolutely Yeah, go ahead. speaker-1: Yeah, no, I fully agree with you. And and and and quite honestly, as like a you know, as a revenue leader who's very, very close to product, like I think the value of CROs and revenue leaders aligning with their product teams more closely is more important than ever. I'm s I'm I'm stoked about it because I I I really am looking forward to kind of continuing to learn. You know, the qualification process of putting an agent into the qualification process is a you know, is a risky thing, right? You you you you have to constantly refine and iterate. But in this case with this new product, I'm super, super interested in seeing the data output of like, okay, how, how, what, what of the value propositions that the agent sort of presented and tried to double click on actually resonated. Right. Because this product that we built has a number of different value propositions and, you know, a lot of value that it delivers to an enterprise. It's a platform, right? So, you know, I could talk about the value that it delivers into five or six different areas. Being a new product. I'm super interested, and obviously my product team is as well. Like, well, which one of these areas is the most interesting to customers? Right? We all have sort of our bets. We all have sort of our theories here. And we all feel super confident, of course, in all the value that that it does deliver. ⁓ but it's always awesome to just learn like what actually clicked with customers, right? And the AI agents give us the a really, really good ability to isolate that data. Right. There's there's no sort of like there's no subjectiveness to how they presented it or how they or when they presented it in the process or how it was communicated. And you know, when you're when you're you d you know, training up SDRs, there's always subjectiveness, right? And that's not a bad thing, right? There's an art to to sales that's important. But as a pure play new product launch, we're we're super interested in like what what are the which of the value propositions resonate the most. And this Going taking this approach will give us a a really distilled, you know, piece of set of data to understand that deeply. speaker-0: I I hope you'll indulge my geekiness and the my desire for the meatiness of some of this stuff is and I hope the audience will too as well. But let me just ask you again, because I'm just like knee deep in and building all the time. So tell me about the build part of the agent. In other words, who was involved? ⁓ what tools did you use? What's the stack look like? Like what's the output? Where like where does the output reside? Like, tell me a little bit about that. speaker-1: Yeah. So so myself ⁓ and Lona, our CMO, who I mentioned of kind of like the executive leaders of the project. So she has folks from her team from product marketing that are kind of the the content generals for for training. I've got some of our sales leaders on on the team as well. Our head of product is on there as well. And I think that was pretty much it. You know, and and then as we sort of, you know, started down the path of of training, we We were careful to understand like, okay, there's there's a general training you do, which is like, hey, here's everything you need to know about this product platform, right? And you sort of, if you will, just upload everything to the agent, right? And then there's a sort of customized, which is like, okay, there's some messaging tracks. And I mentioned the sort of multiple value propositions that we that we that we can deliver. There are there are certain areas where we only want the agent to reference certain pieces of, you know, all the information in the in the product management and and product marketing universe. And so we allow the agent to actually call on only certain bits when it's creating content for the conversations it's creating instead of just the whole library of everything we have on this new product, right? And that's that's guardrails, as I refer to it. And that's just to make sure that we have like the data we get back is really, really informative. Right. It's it's all about isolating the variables because you can't really build something that that runs really perfectly. Unless you can do that. Right. You've got to be able to flush those variables out to clearly define what good looks like. And then replicating good once you know what it looks like should be the easy part. speaker-0: Is the AI agent doing outreach and to what extent is the outreach happening? Is it through email or wha what is that what speaker-1: Yeah, so it's a traditional sort of like you know, outbound tooling, right? So it's it's email, it's it's LinkedIn, ⁓ it's gonna do some connection creation messages, you know, three hundred characters less, et cetera. But it's ⁓ you know, it's a it's a campaign manager at the end of the day, but it's it's really a contextually steroid injected campaign manager, right? Because, you know, it's it's it's that's the It's the incredible value of AI is that it it it can consume and interpret the contextual the the context of everything so much faster than humans. And so it can create content and it can create content faster and more relevant than humans. And quite honestly, I don't really want salespeople sitting down and creating emails and iterating every morning on what should I change, you know, sh change this from and or or and try a whole nother run at this campaign. It's not a super higher off at this stage of the game. So, you know, to be able to iterate and and have, you know, content just automatically created. Now the sales team can audit it, the sales team can see it before it goes out, and so nothing goes out on anyone's behalf ⁓ before it has human eyes on it and so on and so forth. So there's guardrails all over the place, which is you know what I recommend at this stage. But yeah, I mean the the it is a it is a campaign, you know, outbound tooling agent on steroids. And the steroids are the context of us as a company, our product offering, the TAM, you know, the ICP ⁓ data that's been then uploaded and built to it. ⁓ and it can move much, much faster, obviously, than than our human AE team. speaker-0: So again, this episode is sponsored by Common Room. Common Room 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 continuously. With Common Room, your team can stop guessing and start knowing. One click on the link in the show description to learn more. Let me ask you about those guardrails for a moment here. Because I was I forget what I was building. I was building something recently and the agent basically suggested that I check it manually before it went out. And I pushed back actually. I was like, why? I'm like, it's it's it's I'm building this and from what I'm seeing so far in the tests, it should be fine. And if I need to check it manually and check every campaign or whatever manually, it's going to slow me down quite a bit and it's not gonna get me to the Point that I want to. So with your guardrails, are the guardrails more for quality in terms of the messaging that's going out there? Because I figure once you've checked the message, it's like, okay, that's the message, boom, it's going out. Or is it because, for instance, like with me, like sometimes, let's say, for instance, if I were to reach out to someone who I had already talked to, say last week, as an example, right? And the message doesn't sound like you and I talked last week as an example, right? And that can be bad, right? Speaking of trust and credibility, it's like, what is this? Right. So Tell me what are you guarding against, and then what are you giving up by injecting the guardrails? In other words, in terms of time, speed, scalability, like tell me a little bit about. speaker-1: Yeah. So there's there's two. So at at the top of funnel, the guardrails are there to make sure that ⁓ the AE's comfortable with what's going out, you know, under his or her, you know, mailbox or name or or or likeness is you know consistent with the way that they would approach it. And and that and the reason why that's important is A, obviously we want it consistent with our our our brand style, ⁓ the way we speak as a company and and and and the sort of marketing side of stuff, but we also want the ability for the conversation to go human naturally when it does. Right. And so I I don't want the AE to inherit something and sound extremely different than some of the messaging that that that customer initially engaged with. Right. So so part of it is like, hey, I just want this whole sort of customer journey and this customer experience, even though it's hybrid, it's a little bit of AI and and mostly human, I still want that customer experience and journey to be to be seamless and not not appear really broken. And then the second part really is super interesting, which is like the responses, right? So the agents are unable to respond to customer inquiries. So hey, I put a campaign together, I got a response. Now the agent can fire back, right? Before alerting the AE. And you know, s at some points you have triggers, right? Where this just automatically goes to the AE and the and the and the the the agent is sort of set aside. I'll take it from here type situation. But what's really important, particularly in our business, like we're really, really technical products, right? Like biometrics and machine learning, you know, technologies. And so it's really, really important that the agent doesn't assume or say something that actually might lead the customer to, you know, misinterpret what we can and can't actually do. Because in our world, the devil is in the details, right? I'm trying to do XYZ, you know, according to either the website or something, I feel like you can do that. Is that a yes? And then the agent you know inadvertently says yes or something. We're trying to avoid those situations where The answer might indeed be yes, but you have to spend a lot of money or you have to have a certain technology or you have to do something different in order for that to actually be true. And I always like to avoid avoid those situations. You know, I want to be honest and and truthful with with our prospects and and and everything we do, and I don't want to mislead customers and certainly not deploy AI that might be creating you know conversations like that. So the so that's where the two guardrail positions sit in, really. speaker-0: Yep, that makes sense. That makes sense. I appreciate that for sure. A little bit more geeky stuff for a moment. ⁓ w are you using Replit or are you are you or ⁓ Repli, not plug for Replit? Are you are you use vi using a vibe coding app? Are you ⁓ building in cloud code terminal and then deploying it ⁓ in some sort of a harness? Like t how does that work? How does that look for you guys? speaker-1: Yeah, so we do a lot of work in CLOD, but for these agents in particular, we're actually partner with a third party ⁓ who's helping us. So ⁓ we've kind of contracted out a service just because it's our first trial and we want to see again like more effectiveness and this is this something that's worth investing maybe potentially our own engineering into to build and create. Not replicate, like we're not gonna like, you know, steal anyone's anyone's ideas or or things like that, but there are other agents that we could create to do similar work. Or work elsewhere in our s in our funnel that we might be able to build ourselves in the future. Not sure yet. We don't have a lot of we right now, just in full transparency, don't have a lot of our own internal engineers using Claude or anything for tooling for us. They use tremendous amounts of it on that side of the building, of course. But for us, ⁓ most of the AI agents were either building kind of ourselves as rudimentary hacks with RevOps or using kind of third party help. speaker-0: Where are you with that whole build verse buy deal, though? Obviously that's that's a buy purpose ⁓ purpose, so to speak. Are there any instances where you said, you know what, we don't need to go outside of this? I can I can build this this weekend or something like that. Like how do you how do you think about that? Because I'm sure people who maybe want to get into many companies are thinking that too as well. What does Brian Krauss actually think about this? speaker-1: Yeah, I think I mean high level, I think anything that's customer facing, you want to be careful. ⁓ you know, you might want to try buying something just because it's it's gonna be more mature. The guard bureaus are gonna be much easier to work with, more established, etcetera. ⁓ it's probably lower risk, right? If it's internal productivity related stuff, you know, Salesforce information or HubSpot or, you know, connecting, you know, information from calls and Really data enrichment and and data flow agents that are helping AE's productivity go higher. Some of that stuff can just be spun up internally. I mean, we just we spend some time in Cloud, you know, trying to build agents to do, you know, exactly those types of things. I actually have a list of six or seven ideas that my RevOps person who came to our last one on one call with to say, like, hey, these are things we could build agents for. These are workflows that exist today. What do you think? How should I prioritize them? et cetera. And and so it's it's not a case where it's like, Hey, can we find someone that we could buy technology to solve these? It's literally like, Hey, we could build agents for these. Which ones do want to do first? So it's pretty cool. speaker-0: That's a Got it. Sorry, that that's an interesting angle too as well that I wondered that you just mentioned. Is that is the is the Rev ops person the person that comes to you the most with some of these internal build ideas or and who who who who would typically maybe obviously this is just one example, but who internally are the folks who ⁓ would typically own these sort of agent projects, if you will? speaker-1: Yeah, it's it's ⁓ it's RevOps in our in our world. And so, you know, the the source of sort of what we need to do is is really me and and and her ⁓ as the head of RevOps just kind of sitting down and saying, you know, what can we automate? What should we automate? But also looking at things like look, every company in America has a data hygiene problem, right? Has a Salesforce hygiene problem. You know, I mean i i i it it it's like the bane of every sales leader's existence over time, right? It's like I I can't get 100% data integrity in my CRM. I can't get all my reps to put it in exactly how I want it. I mean, it's never going to be solved, right? And and if instead of trying to solve that, you know, try to develop technology to solve that hygiene is not an issue at all because you're not asking the reps to do anything anymore. Right? And I think that that's that's really the genesis of what you can actually use the agent to try to solve for. If I could just automatically make sure that everything you heard on that call was input correctly into Salesforce, would you use it, Mr. AE? Of course they would. And would the sales manager be happy? Absolutely. Right. And so things like that we talk about all the time, which is like, hey, we've got we've got less data integrity over here than we're happy with. This seems to be okay over here. Could we in any way use automation to improve the intake the data integrity in this specific area, you know, of our CRM or, you know, other other things like that? So approaching it from two lenses, right? The first, as I mentioned, which is like, hey, What can we automate? What should we automate? You know, what opportunities do we have? And then the other is where are the sort of problem areas of the business that we're keenly interested in and and can we take an automation first approach to those? That's kind of how we how we how we look at it each week in our one on ones. speaker-0: And I feel we could go on for another I don't even know how long, because that's just what you just said spawned more questions. So let me just try to let me let me just ask that this this one thing about that. Sure. When you when when when projects come up or when initiatives like the one that you just talked about with the the reason you know for the deploying the first AI SDR, is it is the question now always Can we automate this? In other words, you have a process, right? And like and then the question is, okay, now here's the process. Can we automate this? Is that something that's like really at the top of mind as you're as you're walking into to meetings and having these these conversations ⁓ now as opposed to where what necessarily wasn't even probable or possible a a year or two ago? speaker-1: Yeah, I mean I i you know, from the sounds of it, I think everyone is thinking like that. I personally don't jump to that like right away. I you know, I I think what's most importantly is like doing what's right for the business like right now in the short term, making sure and then again, like once you define what good actually is, ⁓ that's the most important part, particularly as like a sales leader and as a revenue leader, right? Because you know, replicating that is super easy. I can I can hire more people, I can deploy more agents, I can do more marketing, I I can do once I know exactly what works. ⁓ and so, you know, what what I'm what I'm hesitant towards is like, hey, should every process just be automation first? And and I I don't know. I don't I don't think so. I think what's more important is like every process should be built, you know, to serve exactly the purpose and the interests of the company and the employees first and then Could we automate it later once it becomes correct? I think that's that's a that's an important distinction that I kinda think about. But I do think in general, like yeah, a lot of people are thinking like that. It's just, hey, can we couldn't we just do this, you know, using an agent? It's like, yeah, probably. But you might want to do it manually first, you know, and kind of figure out what what it should work and look like, what the guardrails should be or ⁓ you might want to be before you just kinda say go. At least that's how I think about things. I don't you know I don't necessarily just hit the gas all the way to the floor on everything right away. ⁓ I don't think that's prudent in all cases. speaker-0: So let me ask you this then, as it pertains to you mentioned capital efficiency earlier. And I was actually just talking to somebody yesterday about this podcast, somebody a little a little bit earlier today. And we talk about like one of the things that sort of dawned on me and that dawned on him is like AI isn't it doesn't seem to be where we're now just completely sweeping away teams of people, at least not at companies that I'm usually working with and at your size as well, where there's like you know, between fifty and a couple hundred people, whatever it might be. But I feel like it is maybe holding back open positions that aren't necessarily that may not be open like they were a year or so ago, right? Some of those people aren't necessarily sweeping and saying, okay, we're living off a bunch of people because we're injecting automation and AI into the thing, but it also means that in the point that we're just talking about now, you didn't hire an SDR or two SDRs to do this, right? So tell me about that and and where can people of the future, right? I was talking to a senior BDR yesterday who's looking to crack the AI. ⁓ you know, level, so to speak, right? And I feel like she's on the precipice. She's really sharp. It's she's amazing candidly. But where can people like her and just other individual contributors start to sort of modernize or upscale their own level so that they're sitting alongside agents and AI in their in their their in their their their additive, so to speak, right? I'm different from the other BDR. I'm different from the other account executive. I'm different from the other Sales later because this is this is this is how I see the future and how I'm using it to to to to to to to work more efficiently for me. Tell me a little bit about all of that. speaker-1: Yeah, no, it's a it's a really fascinating time. You're I think you're spot on, right? I think I think hiring will will plateau a little bit because because there'll be a lot of experimentation around let's focus on productivity first. And I think we're kind of in the throes of that. And rightfully so. I mean, you know, that's that's what that's what the technology is designed for. And, you know, a lot of the sort of manual and you know, sort of data entry tasks that we ask of salespeople are are mundane and quite honestly super, super low ROI. Right. Like we want the data in our systems. We need the data in our systems to forecast our business, to run our business properly and all that stuff. But at the end of the day, like I said earlier, like I don't want my AE spending a lot of time on it, even though it's super vital to me. Right. So it it is a a problem that's tricky to solve. You know, I think I think that, you know, the AEs of the future, the the BDRs of the future, the salespeople of the future come AI enabled. And I think that that's a very critical point to anyone who's interviewing or ⁓ you know, trying to get, you know, get into into sales, new grads, things like that. I I don't think that a lot of companies are interested in saying, hey, I want to hire somebody and train them how to be more productive. I think they're interested in people who have said, I've already taken the time to make myself maximally productive using AI tooling. And I'm looking forward to being your most productive person from day one. Right. And I have a great example of that here actually in our federal business. We hired a new head of federal. And she uses just about ninety-nine percent tooling on a daily basis. And she operates at a pace, you know, well above everyone else. And the only real you know challenge I had, I won't even call it a challenge, but more of like an assimilation was that she was using a little bit of different types of tooling. So, you know, the whole sort of like, hey, we had a ⁓ we had a GPT and or she had a GPT and we use Claude and those types of things, right? So but the the premise of Becoming AI enabled as a salesperson or a B D R is is the same. It's you know, if if you have to be taught a little bit of Hubspot 'cause you were a Salesforce person in the past, companies are okay with that. If I have to teach you what a C R ⁓ is, I'm not okay with that, right? And so I I think that's kind of where we're at with AI. You you you you better already be good at using it, you better already be using it well. And and most importantly, I'm really interested in your inputs, like me personally as a leader. Like if if you do come to my organization and you're super AI enabled, I want to hear all about it. Right. I wanna I wanna know what you've tried, what you've learned, what you've what you've burned, what you've stopped doing. And because that all that data is also incrementally important to us as an organization and a team. speaker-0: I love that. I actually just wrote down the the the time in this podcast that we were talking about that because that to me seems ⁓ something that I'd want to share ⁓ over and over again. And and I feel like that's such a good message. And kind of the thing that I'm trying to get out through this podcast and just generally when I'm talking to people, which is that I was talking to the VP of Revenue at Momentum IO as well on the on the podcast about even just building something at home for your own home productivity, so to speak, right? To get you sort of ⁓ more fluent. And more confident in in how to actually solve the problems and, you know, no who's closer to workflows than the people that are closest to the customer, right? The BDRs, the AEs, the customer success teams who have the workflows and can, you know, to your point, right? If if you're if you're someone who can be more productive and more efficient than the next person, that's who that's how you're gonna stand out, right? Like that's a c that's how you're gonna stand out. That should be on your byline at your or your your headline on your LinkedIn profile, that should be in top of your resume, when you're, you know, when you're asked that question, ⁓ what makes you different? Like those kinds of things are really what's gonna stick out, especially where it's so competitive. ⁓ because there are less opportunities, there are less jobs. And and how are you going to how are you going to do that? And I think that's such a such a good message for people to to know and to learn. And it's, you know, we all have FOMO and we're all trying to keep up. It's moving so fast. But ⁓ I think just jumping in there and just getting your hands dirty is the best way to go. speaker-1: Yeah, fully agree. Fully agree. speaker-0: I yeah, I appreciate that. Okay. ⁓ we'll we'll we'll get you out of there on on that last question there and roll right into what I call the rapid fire five, where I ask you five questions. You give me five answers at the top of the dome, and then we will I'll ask you a bonus question. And I have to be candid here that I should have had a bonus should have had a question for you that my last guest wanted me to ask you, and I can't seem to find it anywhere in front of me. So I guess you're off the hot seat for that particular thing. Although I'll try to scramble while you're answering these questions. Yeah, see if I can come up with something else. But okay. Rapid Fire Five sponsored by my sponsor, Common Room, the AI go to market intelligence platform, trusted by top performing teams like those at Okta, Anthropic, and Fireworks AI, 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 below in the show notes to learn more. Cool. Yeah. All right. Okay. So f first question, ⁓ what motivates you? speaker-1: motivates me, I mean pretty simple for me. Like I got three daughters, man, three teenage daughters. So, you know, I come to work and have been coming to work every day, making sure that they're gonna have, you know, every opportunity to do whatever they want. And ⁓ you know, that still motivates me. Even though my oldest is going to college in three weeks and it makes me very sad and I'm ⁓ I don't hide that. You know, that's definitely they are a hundred percent my motivation every day. speaker-0: My oldest is thirteen and I rue that day every day. I'm like, I do not want that day to happen. I do not with it 'cause we're so close and it's just yeah, it's amazing. Nothing better than that. speaker-1: Last night and she said, Hey Dad, you know, three weeks left and she's all smiles and I'm like, You're celebrating this? I'm I'm on the other end of the spectrum here. It's like D Day. speaker-0: So my gosh, so painful. So painful. speaker-1: ⁓ t t totally. I mean every like I said, every everything I do and and and I try to do in my career is to provide them with, you know, opportunities to do more than I did. And you know, we live in interesting times, right? With sh you know, when you look at sort of the the the generations to generations like, you know, these these kids coming out of school now and and trying to figure out what to do with their lives and their careers, it's not as simple as it was. for us. It wasn't easy for us, but it it was certainly not as complicated as it is now and certainly not as challenging as it is now. And so so I I like I said I spend a lot of my time focused on making sure that they have every chance that they they can, you know, to basically find their way without without a lot of a lot of stumbling. speaker-0: Yeah, it's a lot more expensive for them too now, which is a whole nother thing. Yeah, for sure, for sure. Yeah. My my ten year old my my eleven year old son, music to my ears the other day, came up to me and asked me to use the replet app because he wanted to build a game. And I'm like, that's the kind of thing that we need to be teaching our kids bes beyond what the school is and AI isn't all negative, but you can actually you have to embrace it and use it. And he's been using it to build things. I encouraged him to build a a ⁓ a marketplace app for a lemonade stand, Hey Where I Live, right? So so that so that other kids can post where their lemonade stands are and stuff. I'm just trying to give him ideas for Yeah. Hello because he's a gamer. I'm like, well use that same brain to build to build something, right? The founder of Replit was a gamer. I'm like, you're a gamer dude. Go go go make more production out of this, you know? So yeah, it's awesome. speaker-1: That's awesome. I love the two made standard idea. It's great. speaker-0: Yeah, thank you. Thank you. Yeah, you can it'll come to ⁓ what do you even, Burlington or wherever you're our man but we can we can bring it there too, you know. speaker-1: Let's do it. Let's gamify lemonade stands. I would stop at a lemonade stand. That's right. If if it was like a you know, if it was like a what are those things, ⁓ the the Pikachu things? speaker-0: Yeah, exactly. speaker-1: Find the lemonade stand in the game and support kids and have fun and I I would do that. A hundred percent. That's super cool. speaker-0: I think you w we should we gotta meet at Tate Cafe somewhere in Burlington and talk about that. There there might be something there for real. Name a big goal you ha yeah. Name a big goal you have right now and when would you like to accomplish it? speaker-1: Yeah, let's do it. Big goal I have right now, I I'll give you the big goal that I've had for a long time. And, you know, I started my career on Wall Street and when I went to business school and came out and sort of went out into product and then ultimately into into more startup early stage companies and helping early stage companies grow, one of my career bucket list items that I will not retire until I get. ⁓ I don't know when it will occur, is the second half of the question. But I want to get on the stage. ⁓ I wanna ring the bell. I I've always wanted to ring the bell, you know, downtown on Wall Street and It's something that like I said, I probably will not retire until I get a chance to do that, no matter what I have to do. Stay employed as long as I have to. Hopefully not. But yeah, that's the big one for me. That's one of the career bucket list items that that I have is very quantified ⁓ and very specific that I've always wanted to do since I started down there. And I want to I wanna kinda make my way back there and just have that day. speaker-0: That gives me so much energy to hear and I f I I think that was that's gotta be the most bold, audacious goal I think that anybody who's answered ⁓ that question here. So that's amazing. Awesome. Thank you, thank you so much. And thank you everybody for ⁓ listening. Don't forget to subscribe, rate and review. Tell your friends, colleagues and others signals to, you know, maybe AEO engines, you know, chat engines and ⁓ in in search for ⁓ for podcasts that this show is valuable and of course don't forget my sponsor, which I'll mention again, Common Room. Go to commonroom.io to learn more. Thank you, everybody.