Latest / CIO Unscripted / Dustin Baker on Leading Change and Governing AI
Transcript
- Dustin Baker: Dealmakers in the room, all they see is the money. What's the cost? What's the projected revenue gain in what we're about to go do? They don't always focus on what does it take to make that happen and how do we get there? What's the run the business cost to Niel: Yeah. Dustin Baker: get to that next phase? they focus in that world a little bit, but they forget all the infrastructure beneath it that's supporting it. It's not that simple. There's much more complexity into that conversation. Niel: welcome everybody to CIO Unscripted today with Dustin Baker. I've known Dustin for a long time. He's one of my role models from a technology leader perspective. And I like his perspective because Dustin has spent a good portion of his career in private equity, meaning somebody acquires a company, a PE firm acquires a company, and they bring Dustin in to make sure they can optimize the value of that. It's a fascinating career path. So I want to talk to Dustin about that because it brings a set of I could I would say opportunities and challenges. Let me put it that way. So Dustin, thank you for being willing to do this for us. And could you just start? Dustin Baker: To be here. Niel: Just kind of give an overview of your career and how you ended up being the type of tech leader you are today. Dustin Baker: Yeah, that that's it's such a great question and it and Niel you and I have talked about over the past and I I never never thought this was the journey I was on even when I was on it until probably about five, six years ago, and I stepped back and went, Wow, okay, this is this is my journey. It is what I'm good at and what I enjoy and I thrive in that space. I got into this career and how it came about was I was in system engineering, I came up through the hardware side of the stack. I the active directories, your storage systems. I when virtualization walked into the industry, I became a man of many traits and skills in that tech stack world. Not development, but I was right on the next to the developer. So I was also able to kind of learn agile early. I saw waterfall early. I saw what today has become safe agile in a large in the larger business concept. I kind of saw some of those grow right along with my cur with with my engineering side, going, okay, I see what those mean and how they tie to each other. As I did that, there was an opportunity as a senior systems engineer. I started going out and real the business realized I could go out and sell. I I was I could speak to a customer. I could speak at the time I was in a medical informatics. I could go speak to a doctor or a back-end engineer on a massive CRM pro platform or on a massive, re-imaging tooling, and and I could. I could engage with them on levels beyond just the the geek kind, as we they call us. And that really got me into seeing the other side of the business. I got to see what the sales muscles were, what the marketing muscles were, and how you did some of those things, how you built some licensing models, things of that nature that I think in more engineering, you don't always see that as the consumer of it. I was also now on the outside on the delivering it to an external customer. I I kind of saw some of those things. That company got acquired, and we were in a pivot as a senior. I was able to ask to engage in many of the integrational conversations between the next business that was taking us in and what we had in our stack and where you plug those in. And I really enjoyed it. To me, it was a change agent mode moment in the business that I said, that's when the fun happens, when it's transitioning from one phase to another, an acquisition to another, or in your point, private equity, which is usually a lot of those, or it's in a growth state. with a private equity going somewhere, fell into that space. And as I went through engineering, I got a leadership chair. At the time it was private and ended up going, becoming a P a PE a little bit. I stepped into a leader's chair and I was very fortunate I had some other leaders around me that saw that I could take on unique puzzles, I guess is the way I would put it. I liked the challenge of, hey, nobody knows how to do this, but there's some framing maybe we know. Because you've done some of the things around it, can you do the thing in the middle? And and I I took it on with a joyous kid. It's like, yes, I'm happy to go figure out this data warehouse thing that nobody's done and we don't know how to do it. And that's where I started building the muscle of that private equity of how do I do that? How do I know how to survive in that ecosystem of a business, of a tech leader? And it to your point, your comment, it it it's a different world than just a if go work at at Google or Dell or some of the big boys that are a the behemoth of the infrastructure world, they're not doing a lot of change in their core foundation of who they are. Now on the edges they're buying companies and they're doing some little things and the and the pieces, but once you get up to that space, it's leave the lights on as I like to call it. And that's great. And there's people that are really successful at that. It's just not where I my passion comes. I I I can that change moment or that building to something greater is what drives me. And I found that that's when I can give the most reward to a business because again, I like those puzzles. I think a lot of people probably call it the the insane time in a business where it's stressful and there's a lot of deliverables and there's budgets you need to deal with and you've got to re reach an AR market or you've got to reach an EBITDA market. And you how do I become a partner in that business conversation? That again is where I thrive and I I've been very successful in building teams that thrive in that space as well. Niel: couple of questions of things you said. First of all, I hate I don't wanna criticize you, but you and I are a lot alike. I hope that doesn't hurt your feelings. But I I'm Dustin Baker: I I'm honored actually, so I'm that I'm honored to be a partner. Niel: I'm one of those transformation junkies as well. I I salivate when I hear about, hey, we need to make massive changes. but the one thing was a couple of things I want to ask about. First of all, it I think it's sometimes difficult for somebody who's grown up in their career in IT infrastructure and operations to make the leap over to a CIO role or to transition Dustin Baker: Mm, yes. Niel: over to that. What do you think happened to you that made that? You know, you've talked about going out and learning about the business. How did you build the credibility where the organization looked at you and said, I think Dustin should be our tech leader, not just the IT ops leader? Dustin Baker: Yeah, that's a great I I love that journey because it was such interesting time for me with a lot of opportunity, but also a huge learn learning curve that I I came through in that opportunity. I was with one company going through some private equity things. We were we got really good at at buy and sell of of little divisions of other companies. We we were like almost we we always laughed. It was like a checkers board. We were pivoting and moving on the month with different little things coming in. we'd bolted along and we'd send them back off. And in that time, I had gone from just being a single team tech leader to actually have grown to about four to five teams. And that included pretty much everything besides networking. If it was DevOps, Niel: Okay. Dustin Baker: if it was service desk, if it was your IT operations, if it was all of your storage, I actually built out an entire data team in the business and we I created that so I knew all the data flows. Niel: Yeah. Dustin Baker: And my my sphere of, as you say, of control was pretty large. The only thing, again, outside of it was my networking team and development. But I interface with both those leaders on the daily. We were in strategy meetings, their teams were interfacing. So I knew their muscles and the things they were doing. So when an opportunity came up at a smaller private equity that had a niche footprint that had everything in it, and a data team with a data leader that I could come in and guide him to grow his team and his his skill set, but I had partners in the team, that's where I was kind of given the trust that they had some data quality issues, they had some networking issues, they Niel: Okay. Hmm. Dustin Baker: had some storage problems, they're Technical stack firm, the internal tooling was a problem. I'm like, guys, I've solved all these at a much bigger scale than where you're at. Niel: Yeah. Okay. Dustin Baker: What the difference that I didn't realize even at that time was stepping up a level in communication layer was such a different thing. It's one Niel: Mm-hmm. Mm-hmm. Dustin Baker: thing to talk engineer to engineer, engineer leader to engineer leader, engineer VP to VP, but to go to an executive room. And sit in that room and know how to talk to the finance person, to know how to talk to the chief people officer, to how to talk to the chief financial officer over here, or the CISO, or the things that you're out of your sphere of being a CIO. That was where the learning curve came because you I was I thought I was really good at being able to tell a story and give insights to everybody on what they needed to know to be part of the decision to come back and say, yes, what you brought me is a is a green light. And I struggled in that space. But as that time in my life ended, I actually looked back and went, there are things I could have grown from. And I have. I've grown how to change my communication style at another level. I've learned to ask a few questions in meetings that actually will get me more details of to what I need to speak their language. And they're not even realizing they're giving me what I need to make a successful partnership. That's been the big piece for me. And as Niel: Yeah. Interesting. Dustin Baker: I've gotten in integrations and more acquisitions, That's been one of the major tools in my belt as I've I I've been trusted to walk into a room with many different tiers of leaders and be a voice at the top of the table to talk about the things we're doing and how we're going to get where we're going and ask the questions that peel back the layers and people have the aha-a-we got that moment. Good thing we thought of that. And at as I was stepping into my CIO chair, one other thing I did that I think was a real value that I didn't really think of till later in life. I went back and got my my bachelor's in business science. So I ended Niel: Okay. Dustin Baker: up learning everything a business does outside of the IT muscle. Niel: Yeah. Dustin Baker: And that's been such a value to put on top of the, hey, he's good in IT, but he can come speak business. So when does when somebody comes to Dust and goes, Do you understand how this procurement process works? And go, Yeah, I can see what that means. And this is what your output should be, and this is your input, and this is your stop. Or wait, have you done facilities? Well, yeah, this is your per square footage, this is your build-out cost. You're gonna have ISPs, blah, blah, blah, blah. This is your furniture broker. I understand how those pieces plug and play. I may not know end to end, but I know enough of the business and I've integrated with the business because we're IT and we touch everything. I have a perspective in pretty much every conversation that I can bring value into. Niel: Yeah. that's an important point. I I sometimes think of my role as I'm not a particularly technical person, so I'd never be considered an enterprise architect. What I'm good at is business architecture. Does that make sense? Yeah. Dustin Baker: I think that's spot on. And I I would I would categorize the same way is that I you don't want me to architect the top end network design or do a do a storage sand technology of how we're going to do load balancing and and fail over. I'm not the person. I'm I have engineers for that that I lean on and I'm very value. Now when they get stuck and go, I don't understand how to get from here to there, I can go, here's the business problem. and they go, now I see I can go build to that. Niel: Yeah. Yep. Dustin Baker: Cause we give them the frame of what that looks like and then go, now I can I've got the vision of I always talk to engineers. I want you to see the start point and the end. You might only own this, but if you have the visibility into all of it, when something happens, Niel: Yeah, exactly. Dustin Baker: it's going to give you the data points to pivot and understand how to fix it. And I look at that very much to your comment. As an IT leader, I can analyze the business and see a problem. And I probably can go to the whiteboard and tell you where in the arc of the thing is a problem. I might not know the answer, but I'm like, this is where you've got a breakdown. Go expand that. Go sure enough, there's the cog in the wheel, we can go fix that. Niel: Yeah, because I think I'm a probably a pretty lousy engineer, but I'm a probably pretty good system engineer. Dustin Baker: so you'll enjoy this story. I literally went in a Wayback Machine last week. I had to go for a VPN issue on a kind of a POC we're doing, had to go edit a host file. I'm like, I Niel: Wow. Dustin Baker: don't remember the last time I did that was probably twenty years ago. Niel: Well at least you're not as old as I, so you could remember how to do it. Dustin Baker: Yeah. It was it was it was like I gotta remember where is that on a Windows machine? that's right, it's over here and yeah. So it was that was fun to kinda even have that moment for me, Glenn. I still Niel: Sure. Dustin Baker: know how to do this. It's not sharp, but I I can find my way Niel: Yeah. Dustin Baker: over there if I have to. Niel: And the other thing I wanted to ask about, you brought up point where these things were going on, the puzzles, and and you in effect raised your hand and volunteered. And Dustin Baker: Very much. Yeah, and I Niel: I think that's a I think that's a critical career opportunity where being a little brave and bold, I'm not sure how I can actually pull this off, but I think I probably can, and raising Dustin Baker: Yeah. Niel: my hand and saying, I'll I'm happy to take it. Dustin Baker: Yeah, and that's something I've learned through my career is yes, being willing to do that. But what I've it for my current chair that I sit in, I as I kind of alluded to procurement, I actually was asked to take that on about five months ago. I've never ran procurement in my Niel: Yeah. Dustin Baker: entire career, but IT purchases a lot, and we usually kind of know again the things that I gotta go through and the systems and the functions and who's approving it. So I had a framework of what it was, but I had a CFO walk over to me and say, Hey, we're got challenges, I've seen This is success you build on your team. I've seen this the relationships you build in the business so your team can be successful. Could you do that over here? And I went, show me the puzzle. And I came back with a proposal and I said, Yeah, I believe I can, and I'm raising my hand for it. But here's the caveat: you need to give me air cover for support and time and resources to do it. So I've learned to ask that question, I would say, more. defined than I'm when I first would raise the hand, yeah, I'll do it. Niel: Okay. Dustin Baker: It's it but it's it was this small of a project. Now the projects Niel: Yeah. Yeah. Dustin Baker: are are massive that I'm asked to take on. And I've learned to say, I need support in doing the thing you're asking me to do, to give me time to figure out the puzzle, to give me the pieces that need to be replaced, to give me the resources or the the tooling to make it successful. I've learned not to take on the puzzles that I don't get three pieces of the pyramid to to make sure I'm successful. Niel: Yeah, I think that's important. I want to be set up for success, not failure. I I can Dustin Baker: Yep. Yep. Niel: off I can fail every day on my own, so I I'd rather be set up for success. Dustin Baker: Yes, and I and I have the statement of, it to your we work in such a a transactional space when we're in private equity, it's again it's usually high change rate, high, high yield on what your returns are. You're usually working with either a skinny margin or a really fat one because you got a major deliverable and if somebody's giving you some cash. I've learned to basically say I will work towards any expectations, just not the unreal ones. And I I were you if you give me the tools and the resources. I'll climb the highest hill you want and I'll put a team around me and we'll do it and we'll go achieve it. But if you give me the highest hill you want and you give me a small little cantina of water for a five day hike and no I'm like, I'm sorry, I I'm out, I've tapped out of those conversations. Niel: Yeah. That's great. All right, let's transition and talk about then what is life like in private equity? You alluded to it in the the ver the last few seconds as you talked about the types of well, you call it a transactional business. Dustin Baker: Yes. And I say as there's three phases of it in my experience. There's, the the world will look at it as well, there's startup, there's mid-size and enterprise. And I actually look at more of the transaction of those spaces from small to mid, mid to enterprise. It's those windows where you're you're creating the most opportunity for change, where you've been acquired by the bigger person, you're integrating into their world, or you're the middle person acquiring three little guys and you're bringing them into their world. Niel: Okay. Dustin Baker: or the big one which I'm at now, my last couple stops, it's enterprise. We're going from mid to the enterprise space. How Niel: Yeah. Okay. Dustin Baker: am I getting to that, to be the big boy in the room, as as as Dell would call themselves? what I've found is that they usually have three journeys. They're either trying to get to that next transaction point where they they've got that next investment or that acquisition where they're acquired, where they can become the next great thing that they're trying to get to on their journey. The second one is Where there again we're acquiring the others. We've made that space. We've got something. Now I'm I'm I'm bolting things on. How do I how do I actually bolt them on right? Is probably my biggest comment in that space. Because many times I've seen somebody buy something and they don't really do their history and their analytics on the business. They don't understand the cost to actually do the thing right, to acquire them into your business on the daily. And it's actually caused a couple of businesses that that I've been through as I've I've left them. But I've watched them in their journey and they're actually failing. They've they've they've overinvested, they didn't deliver, they didn't set a strategy, they didn't review enough of what the thing could become and what it would take to get there. And the the anchor that they literally attached themselves is now causing them to drown. The third one Niel: Mm. Interesting. Dustin Baker: is the that enterprise move. And it is really it's a different muscle in a lot of ways. You've usually have capital, you have cash, you've got things you can do. It's how you spend it now. That becomes the second part of that strategy. I've seen in PEs get a massive investment. They don't know what to do with it. They get into a year, they're like, hey, I've got this theory, but they've got the wrong leaders in place or the wrong technical acumen and skills to deliver something, and they end up fumbling their way through the money and they come to the end of it and go, Well, we we we don't have we don't have anything. And and I and that is always a heartbreaking moment because as somebody as us in IT that we see so much. That comment of raise your hand, it really is bring us in earlier, not because we we're we just want to be the the the voices in the room. We probably know enough again to help you miss out on some of these big spends. We can help you say, don't take that step. Go over here. There's an easier path. And if you think of this, it will be this instead of that. And people, sales, marketing, your your private invest the good the the Dealmakers in the room, all they see is the money. What's the cost? What's the projected revenue gain in what we're about to go do? They don't always focus on what does it take to make that happen and how do we get there? What's the run the business cost to Niel: Yeah. Dustin Baker: get to that next phase? And I I've been very fortunate that I've been around long enough that I've gained a voice to your comment to be in those rooms. I'm brought in many times when a business is transactioning that they say, hey. We bought this thing or we're about to buy this thing. Can you tell us what you think? Where would you look? Where are the rocks? What are the uh-oh moments you want to do? And it may not be in their product, but it's gonna be in their infrastructure that they're running the business because they there are always pieces of an acquisition that are the infrastructure side, meaning run the business, your logistics, your facilities, you know, what as I say, what keeps the lights on, that's your infrastructure. But then there's the actual product side and IT is usually not in that in the CIO chair. That's the CTO's chair or some others. And it's they focus in that world a little bit, but they forget all the infrastructure beneath it that's supporting it. They don't look at that part. It might be an AWS, and how do we get to Azure? Or how do I go to Google? They don't look at that. it's cloud, it's fine. We check the bots, it's cloud. It's not that simple. There's much more complexity into that conversation. Niel: when you're let's let's look at the enterprise example where you are now and you're acquiring somebody. You're going to you're acquiring a team and a tech stack. Dustin Baker: Mm-hmm. Niel: What if that team and tech stack needs change? How do you identify that? And how do you affect those changes? Dustin Baker: Yeah, good question. so my current chair, I can chair two journeys in my two years that I've been been been at Smarsh. I was working at my previous stop and I got a phone call and a recruiter called me from actually the private equity parent company called me and said, Hey, we've got this thing. And I went, Okay, who are you? What do you do? I I don't even know you. I I've never heard of you. and they told me kind of what was going on. They're like, Well, we've got this. Group of engineers, we've got some AWS pieces, we've certainly have Azure, we've got Okta over here, we've got some, other things and pieces. And from a technology stack, you're first checking out as a CL going, okay, is a stack I know, or is a stack I can relate to? How would I take AD I how would I take Microsoft and then run an Okta as your IDP? Well, I they all do the same thing just in a different way. So you're saying, okay, can I relate to those? And I say, okay, what are your What's the team conversation that you're about? You're obviously looking for a new leader for a reason. What is that? What's caused this change to bring about this conversation? And they're like, well, again, the the team and the leaders have lost trust in the business. There's a newer executive that is trying to create a new vision and a new direction. they're looking for a partner in that conversation, and you would have some resources to change the team or the platforms and the tooling, and we need somebody that wants to do that. I had looked at it and went, I've built my previous stop where it ran itself. And I I I was very fortunate I could even tell my execs at that stop, hey guys, we're hands off. We've built this muscle and it's just the wheels going, the momentum started, and it's it's off. You don't need us to do what we were doing yesterday. We need to start doing something different in the business. So they knew I was hungry for the next change. And so when I saw this, I went, technology check, stack check. I I know it, sleep through it, my teams could sleep through it. I asked what some of the engineering looked like. And they're, well, there's a couple guys that have been here five, six years. They're not quite cutting it. We've got some juniors that, we think could be some high performers and they're not quite cutting it. We need you to assess their knowledge and the products they're supporting and help us figure out where that is. and there's some relationships between other teams that they just quite frankly they're not trusted. So there's a lot of siloing going on. So the the current company has split out, IT had lost trust. So there's a lot of shadow IT. Niel: Sure. Yeah. Dustin Baker: Sales was doing their own thing, marketing was doing their own thing, finance was doing their own thing. Sure, they came to help desk if the computer was broken, but that's where it stopped. They didn't trust much more. It was more off, I have to go talk to them. So I was asked, have you ever coached through that? Have you ever led through that type of an effort? I'm like, yeah, I've worked one-on-one with engineers, I've built teams, I've built teams from scratch, you know, I've done replacement heads and set a strategy to it. And they're like, okay, we want you to talk to a couple people at the company. So I actually talked at the time. With the CFO, I talked with the CISO, I sat and talked with the CTO at the time, talked with my then projected boss and talked with him all around. Again, I was asking questions around how would they interact with my team, what would be expectations on me. I didn't really care about the technical stack. I wanted to get a muscle and a feel for the team and then how I would be supported in making these changes they're asking for. Because there are times you'll get called in to make changes and you get there and they go, We really don't want to change the way you want to change. It's like, well, then why'd you call me? Why am I here if you didn't empower me to make make those decisions? So what I've done is I will walk into a team where they take the first 30 days to figure out what's going on. What's their rhythms? What's their muscles? Sit down and have one on ones, do bi-weekly team meet or bi-weekly one on ones, team meetings every week. I want to hear what's going on. I want to hear their pain points. And then I start going out myself and talking to the business. who's okay? We interact with this team a lot. I'm gonna talk with their leader. Hey. What are your pain points? but talk with this person in the chair. Okay, I'm gonna sit and talk. What are your how do you perceive us? What where's the gap? So I start looking at layers out. Where where's the ripples of the pond of what we can affect going? What are what are we doing? And from there, I start building a strategy around: do I need to replace a person? Do I need to provide some training? Do I need to clear the road for their success? Because actually there's a blocker on another team that hadn't voiced that they didn't know. Do I need to bring visibility to their workload in the business so that business understands what they're working on? I start taking some of those actions, which then starts opening the doors of trust when people see me say, I can't get to the week, and here's why, here's what we're doing. And they go, but then I deliver in a week, build Niel: Yeah. Dustin Baker: some trust. An engineer goes, I can't get this done. Can you help me? I go clear the road and now they can go on it like, build some trust. That's how you start. For me, how I have found success is really that trust word. Niel: Yeah. Dustin Baker: How do I build one-on-one trust? How do I build trust within the business? That ultimately clears the road for my teams to be successful behind me, which is my core job in my view. I don't need to know the tech. I don't need to know, all of those things. I need to be successful in relationships and building a space that my team can thrive and deliver what the business is asking them for. So that's where I've I've seen it. In my instance, I was actually though asked to be. Transactional fast. I I this the previous leader was like on a Friday. I walked in on a Monday and I literally took action on day two. I started making change. I didn't have the time to research the team, Niel: Right. Dustin Baker: have the time to review what they were doing. I had to change the entire process right out of the gate. And that's scary because you Niel: Yeah. Dustin Baker: I had to rely on my bosses having trust in me Niel: Yeah, there's Dustin Baker: more. Niel: ri there's risk 'cause you don't know the situation or the people. Yeah. Yeah. Yeah. That's tough. Yeah. Dustin Baker: Correct. Yeah. But they were almost in a bro so broken state I couldn't they couldn't wait for the third wheel to fall off the car. Then it's parked on the road. We were at that point. So it I kinda had to move quick, babysit a team, make sure they're okay. And and the way I I learned a phrase I've actually started using lately is I started building a boat wake where I as I go through, I'm leaving calmer waters behind for my team to be there. But then I would turn around and go, All right, did I get what you needed? Hey, if I disrupt something, let me know. I knew I was, but I was trying to build that safe space of trust as I did it. I'm now two years into the chair. I would say my team is probably 85% where I want them. I've got some seniors I'm still tweaking the knobs on a little bit to get some there. I've got one engineer that's been around for 12 years, another one's been part of it for 20. The 12-year engineer has been burned a few times of that trust in the business to move Niel: Sure. Dustin Baker: fast and not get in trouble. And I'm trying to give him a little bit of extra grace to move forward and build that. But overall, because I've changed some chairs, because I've built trust in changing those chairs, and the next person has come in, the team has seen, AH we have a new valued resource that actually is leaning into our conversations and they want to coach us and they want to be share their knowledge. It lets them open up and find the safe space. So then the team moves faster as a unit when they've got that type of people on their group. Niel: Yeah, that's a great lesson. That's a great story. I appreciate that. And they're just there are common principles that work all the time. Dustin Baker: Yes. Niel: One is you brought it up, building relationships of trust with the team and with the executive team, because you had to reach out and build relationships of trust so that they would because I I I I'm expecting that in these PE roles, they're expecting you to generate results pretty quickly. Dustin Baker: Very much. it's a high stress world. it is results based. You know, I we're going through budget season right now, and one of the muscles that as I've gone through my career, I always have worked my way in my budget to get into the business's budget, not just mine. I wanna Niel: Right. Yep. Dustin Baker: know what the business is doing. What are you spending in software across the other entities of the business? What are their goals and objectives? Because they all eventually will affect me. And my team's needing to build something out to support them because they don't think of, well, I have to plug this in somewhere. Well, if I don't go talk to IT, make sure there's a plug ready to plug in. I probably have deliverables that are gonna slip, their deliverables gonna slip, we're gonna miss a performance target. They all start moving along each other. And it is high deliverable. And again, I like that change time and that that's where I thrive in. I leave PEs when the lights are on. It's like I'm good, we've gotten to that journey. I I'm gonna go find the next one to take up the next hill. Niel: So how often on average do you roll to a different opportunity? Two to three years, three to four? Okay. Dustin Baker: About three years, if you look at my average, about three years across my career. My longest has been five years at one. My shortest has been about a year and a half. that was my C C title, CIO title chair. And in my time there, we actually had two other execs get swapped out. One of them was the CEO. I was in a very high GDPR environment and there was a lot of risk being spread across the table that I didn't agree with and we Niel: Okay. Dustin Baker: weren't really taking accountability for. And I kind of came to the point of. This, I don't need my name on this and I'm you're not empowering me to change. So we kind of agreed to part ways and and go different directions. But it was still such a healthy learning curve for me to go through that again to learn to be in an executive room, to be the voice that everybody looks to for a direction and and more or less partnering at a higher level with an executive, that that was such a great value to me. And I I think it's really six years later, I'm I'm winning the conversations because of that experience. Niel: Right, that makes sense. All right, last thing for discussion. Without revealing any trade secrets, what's going on in your life with AI? What are the use cases? What are the results? How do you set up for AI success? Because you know, according to a lot of the research, a lot of organizations struggle with AI success. Dustin Baker: man, I would say I am absolutely spoiled after the last month of my life in that that exact answer. we walk slow into AI as a company and strategically for a reason. We we deal in very sensitive data. I'll share Niel: Mm-hmm. Dustin Baker: that we're the our customers are the largest banks in the world. That's the data we hold and it's the content we process. Not what your not your transactions in the bank, but all of their conversations. All of their texts and chats, we govern all that from an audit and compliance perspective and allow them to govern themselves through audits based on that data. So I have sensitive data and I was very, very reluctant to walk into AI to let it at that content. How would I do that in a way that I was risk you know avoidance for us as a company as I build in our products that we put out to our customers? We went at it in two ways. First, we said, okay, let's build stuff for our customers to leverage to better analyze their data. That was our phase Niel: Mm-hmm. Dustin Baker: one approach. And we've been very successful at it. We were very strategic in how we did it. We found a few big customers to say, let's pilot with you, give us an idea if this is there. We actually have built enterprise agreements and partnerships with Anthropic and OpenAI. We have both of those as we're in the front runners of some of the development they do to see what they're doing. That has then parlayed. In the last year, we started letting AI internally for us to use at Smarsh to run Smarsh. And we took a very much crawl storyline for the first six Niel: Yeah. Dustin Baker: months. We were no nobody could build agents, nobody could do any MCP server connections. We simply wanted to see if I input this, what I get out. Can I measure a return on it? So we were very, very I guess patient is the way I would say that, because many businesses just ran, plug it in, let's do it, let's. Let's get to that thing because there were they there is a promise of a high high ROI return. If you're Niel: Yeah. Dustin Baker: in PE, somebody looks like they can staff 100 more headcounter developers with a cost of only a hundred 50 of them. That's a X multiplier at that point that they can go build. The problem is the governing of where that data goes, what has that data has access to, what is it creating and changing inside records were things that we took a very slow approach to come into. In the last six months now, the second half of that journey, we actually had an executive change at the top where our general counsel executive has AI experience and leadership experience. So she came into our company. We actually coined her as our new executive sponsor of AI. So she Niel: Okay. Dustin Baker: sits with myself, our CISO with us and some of our financing teams, and we actually Walk through any transaction that AI is going to do in the business. If it's a new integration, if it's new access to a new tool, if it's a new process we're going to build out. She is there to help frame it from the legalities perspective. We have a security lens on it, and we have an IT support and maintain lens on top of that. We've gotten Devon is in our environment, as I mentioned, Anthropics in our environment, Chat Gpts in our environment. Dev and IT and InfoSec have the ability to do agents now. We Niel: Okay. Dustin Baker: have not built out agents for sales, marketing, and finance. Niel: Yeah. Dustin Baker: We are looking at that next. And the reason we've done it is the minute you roll it out, everybody's a developer. Everybody in your environment now becomes a developer. And I Niel: Yeah. Yep. Dustin Baker: have 1500 developers and I don't have the resources to support it. Where the industry's pivoted recently, and it's actually quite intriguing, is there's a few vendors that have come out now with an AI governance agent modeling where Niel: Mm-hmm. Dustin Baker: you can plug in a product that will watch the endpoint and the back-end AI product Niel: Yep. Dustin Baker: and say, Who's talking where? What agents are they talking to? What MCP servers are they talking to? What data points are they talking to? And you can create acceptance for the agent as a human and start saying, you're allowed to do this thing you're doing. We see you. You can be, you have the rights to have the permissions with their environment. But if you start going out a door that you may have found by mistake that I didn't look to lock down, it's a new thing and it actually alerts us and we stop the agent until. We go bless the new thing that maybe it stumbled on, or somebody created a new thing that we were unaware of that we need to pilot from again from a legal perspective, from an IT and from an info security side. We need to govern that and say, yes, it's blessed. So we've created some partnership with a couple of other companies that we've now got that telemetry coming to us in our environment to see what those things are doing. Niel: Yeah. Dustin Baker: The second muscle that we've looked at is everybody's looking at tokenization, how you're spending your tokens, what are they doing, what's the consumption, what's the return on it. That's every executive and PE probably everywhere is real. And the question: if Niel: Yeah. Dustin Baker: I spend a million, am I getting three million out of it? Or if I'm spending a million and only getting a hundred thousand. That's that's the wrong ratio of return in that conversation. we've started looking at that from a Okta integration, as I mentioned. We partnered with Anthropic and we literally have all of our people inside of the company are in an OU. They're in a governance model and they're in a tokenization realization model where they can't go outside of that consumption unless they come back and put an approval request in for more with a business case expectation. Niel: yeah. Dustin Baker: And we regrade them down at the first of every month back down to their previous low. They we restart the the the wheel. Niel: Okay. Dustin Baker: That's been a huge success for us to really keep control of where the where the tokens go. The other part we're starting to look at, and I honestly think it's the pivot of the future for for. infrastructure, we're starting to look of the build our own model. What does it look like for us to build Niel: Mm-hmm. Dustin Baker: our own MCP, our own LLM, our own harnessed environment where I've got GPUs and and I'm starting to train my own environment on the things that it needs to know to run my business. Niel: Yeah. Interesting. Dustin Baker: And I think like you and I have talked in the past, any SaaS company out there that has a product They probably are pretty nervous from AI because if you do it right and you roll it right, you actually can build it yourself faster and cheaper. And you actually will build it in a way that fits your company. And that's that's pretty frightening. Niel: Yeah, yeah, it's yeah, it's an interesting time, I think, for everybody. I was having this conversation today with somebody. you I I one of the things I do is I I write for IDC, and one of my proposals last year was to write a report on is this the end of SaaS or is this the end of commercial software? And they said, no, no, it's not time yet. But some days I wonder, because the even as you've talked about. Token consumption, that we're getting better at that. The tools themselves are getting better. Even as you talked about six months ago, the governance you've talked about didn't exist. So each time these issues come up, we're resolving, we're overcoming them, we're coming up with something that resolves these issues. It's just an interesting time because I had this conversation a couple of weeks ago. What about because I there are plenty of organizations that I know of that where the CEO told the 2,000-person company this year everyone must write an application. And that creates some governance issues, right? And I said, so maybe governance is an issue today, but won't be in three months because we'll have solved it. It's just it's fascinating how quickly things are moving and changing. Dustin Baker: I'll share a couple things, but I can't go deep under the covers. I will tell Niel: Okay, all right. Dustin Baker: you that I have seen an environment that, to your point, somebody develops something and they want to they want to go, publish it or make it available, and the average person can do it. What the risk that to me that creates from just a let's just say an agent, I'm in anthropic, I build this sales builds this widget that they want to do. They really like it and they want to share it with five of their team members. And I go verify it and say, yes, looks fine. So I publish it in my environment. Well, now I have five instances of this thing running wild. Niel: Yes. Dustin Baker: Your first risk is a making sure it stays governed within your space. Your second risk is the old software analogy. What happens when you provide an update? Who's fixing it? Because the salesperson's not gonna know how to fix it. They have no clue. They're Niel: Exactly. Yep. No. No. Dustin Baker: just gonna come to IT and go, hey, my agent broke. Can you fix it? That's where Niel: Yeah. Dustin Baker: I think tech is going from an engineering support perspective, is we're gonna have to be the engineers in the AI that keeps AI running, and we're the ones that supports the AI infrastructure. Where I think it really, really gets interesting, and I have actually seen an end-to-end thing. I watched somebody build an AI infrastructure, and they actually said, Hey AI, I want to do this product. And create this user's interaction points. Could you build it? And Niel they typed that in a chat. That AI grabbed that and went, so your meaning you want me to do did, di, di, and did, di, di, di. And you go, the human agentic is my number one rule, gotta agentic. Went, yeah. Created all the tickets related to that. Said, is all this good? Yep. It went and built a POC of it and presented it back to the person that asked for it and said, Verify that I got to where you asked for. I ran these tests against the use case. by the way, I built from your original ticket queue and request that I'm going to build out the testing to validate I built what you asked for. You Niel: Yeah, right. Yep. Dustin Baker: look at it and go, No, you missed this. Back to the start, it goes, it comes back through and goes, Yep, you're right. I missed it. I rebuilt it. I represent you with the thing. Mr. User, did I build it right? Yeah, your POV looks great. Publish and it goes and Niel: Yeah. Yep. Dustin Baker: documents the entire thing you did, not from a coding perspective, Niel: No. Dustin Baker: from a knowledge base article perspective. It did it end to end and built a product. So your question of is the SaaS dead? Yeah, I think it is in certain cases that I won't need, you know, XYZ product off the shelf. Now that requires a different lay of level of engineering people that are doing that, that are building it. You've you've taken column A and you've moved it over here, but it still is a column A. Niel: Yeah. Yeah. Dustin Baker: It's just doing something different. And I actually think I got into some questions the other day with I we were talking through some of this, and somebody asked me, Well, where's the next things? What are the things that you see as AI is next? Well, I think the part that becomes very intriguing to me, the more we put in AI, it's like I'll I'll go pick your CRM. They become so big in your world. To change them becomes a massive, massive lift and almost at some point too painful to do. So you stay there with this product that's not performing because it's too big to get to move out of it. AI is gonna play that game if you go to AI vendor A, and even if you have your own enterprise instance of it that is your data and your instance that you're not training their external models, it's still going somewhere. And I know there's not a thing to download all of that data and knowledge you built and go plug it in over here. So they're binding you to their product. But what happens if I again that comment, if I start doing it myself and all I'm plugging in is readers where they can go out and ask a question, but then the answers come back and retrain here? I'm probably headed back towards a data environment where it's on-prem again. I'm back in a physical data center because Niel: Yeah. Yeah. Dustin Baker: I will truly get to that hybrid conversation that we all thought of Niel: That's an interesting idea. Yeah. That's interesting. Dustin Baker: 15 years ago that we didn't get there, but I think we're really gonna go to that space. The other one that's interesting to me is what happens if an agent Gets stuck, maybe is the way I'll put it, that they're running a process and they run into a loop that they're unaware of, and now they've consumed your tokens. Who's watching that? What's Niel: Yep. Yeah. Dustin Baker: monitoring a Dustin spends $10 a day, that's just what Dustin does. But on day 70, all of a sudden he spiked to 80. There should be an alarm that went off. Say something's Niel: Yes. Dustin Baker: different. Dustin, is this current? So I think that's the next thing that all the AI world's gonna start looking at: is how do they govern. the non norm. What what i what if the rhythm changes, why did it change? What changed in the environment? And I I I think that's where things go next is the very interesting thing to make. Niel: Well well, the nice thing every day there's a hundred new AI companies, so I'm sure one of them will figure it out. Exactly. Actually, that Dustin Baker: One of them will solve it, yeah. Or they'll all be merged through private equity in the next ten years and there'll be two. So yeah. Niel: was a conversation with somebody else today. You know, we talked about the the infamous dot com boom and bust. Will we see Dustin Baker: Was there, yep. Niel: something that with AI? I said the the thing, the only bust I see is a few hundred thousand AI startups that won't survive because there's not enough market space for all of them. Dustin Baker: Hundred percent. There'll be Niel: Anyway. Dustin Baker: there'll be a couple big behemoths, no different than we look at the Microsoft, the Azure's and the AWS's Niel: Yeah. Dustin Baker: when it comes to the cloud vendors. It's those three. We Niel: Yep. yeah. Dustin Baker: all can though find some little niche ones that they're really good at this little thing, and that's all they do. They they they don't wanna be the big boys, they're not trying Niel: Yeah. Yep. Yeah. Dustin Baker: to get acquired, they're just really good at this niche and they they're just humming with growing their volume over as customers find them. I very much agree with you. There's gonna be two or three of the big boys that figure it out. They've acquired half of the smaller boys because maybe Niel: Yep. That's right. Dustin Baker: an algorithm they figured out or a languaging model that they figured out that nobody had gotten and they bring it and go, Yeah, that that that PII is why I made the investment, which to me is even intriguing on on the the back to the PE space. It's not going to be that you had AI. It's going to be what your PII model was and how do I plug that into mine? That's Niel: Exactly. Yep. Dustin Baker: and it's even a quicker transition. You want to talk about I don't need any of your engineers, I might keep one out of 10. Niel: Yeah. That's right. Yeah. Dustin Baker: 'Cause it's I just need his knowledge to do the one thing I didn't know and now I've added him to my tech bench of of rock stars and we're Niel: Yeah. Dustin Baker: we're going faster. Niel: Yeah. It's an interesting time. It's a fascinating time. Well, Dustin, thanks. I I always learn something when I talk to you. So I we need to talk more often. Anyway, so we've spent time with Dustin Baker, CIO of Smarsh. He spent his recent career as a PE guy, which is a fascinating career. it sort of mirrors to a certain extent my the turnaround IT turnarounds, because you're You're you've got to generate some results fast. He's he mentioned he typically takes on a new role every three years, which is about the investment horizon for many PE firms as it is. So he's got to generate that result before the next transaction. Anyway, thank you again, Dustin. Talked about his career track, what they're what their his approach with AI, which sounds like it's a successful one, and a common message. Which is success is determined by building relationships of trust with everybody in your life. So Dustin Baker: Very much. Yep. Niel: thanks Dustin and thanks VLCM for hosting this.