B (3:04)

Yeah, well, and for those a little less familiar, can you tell us what does Trey AI do and you know, what specific problems you solve and who are typical customers?

A (3:14)

Sure, yeah. So our customer base spans from ops teams and you know, ops within marketing, ops within sales, ops within it. We sell a lot into it. It's a big target demographic for us. But Trey as a whole is a workflow orchestration and an AI orchestration platform. So whether or not you're doing traditional pushing and pulling of data through the workflow side of the house, or with our AI offering being able to build agents that sits on top of your existing tech stack. So think a one stop shop to build AI agents versus trying to like manage the sprawl that you would have if you'd used all the in app agents or point solutions that are out there.

B (3:58)

Yeah, yeah, definitely. Yeah. That's becoming a, it's becoming an issue. Right. So. Yeah, well, so yeah, let's, let's start here with the strategic aspect of this maybe. And a lot of leaders are very focused on acquiring the best AI tools kind of to your, to your earlier point. But you know, one of the real bottlenecks to adoption is legacy infrastructure that they're built on. You know, from your perspective, how does this integration blind spot manifest in large organizations? And what are the typical symptoms of a company that might be hitting this wall?

A (4:38)

Sure, yeah. So I mean, a lot of these old legacy systems who are kind of pivoting to try to adopt the AI infrastructure, the issue isn't their first use case. It's typically the point solutions do a really good job about that first initial use case that the entire platform is kind of baked around. The problem really comes with the second, the third, the fourth use case. A neighboring department sees that you're doing something and then they want to do it, but their tech stack is just a little bit different. And before you know it, the one solution that it did really well suddenly can't do, you know, everything that everyone else wants to do. So it's almost like the point solutions kind of get promoted into incompetency. It's like, it's like it did. It started so good and then it kind of became a problem. So I think that's where Trey fits really nicely within the market is we are platform agnostic. We don't care whether or not you have a salesforce first approach for your CRM or if you work with Eloqua. Right. So under the hood, everything is APIs, and we are the orchestration layer that sits on top of that. So you can build and deploy at scale. So whether or not one department uses one tool set versus another department, they can have completely different ecosystems and still build on the trade platform.

B (5:57)

Yeah. So what does this look like in, you know, in practice? So an integration first mindset, as you've called it before. You know, what does that practically mean for. And we'll focus primarily on the marketing and the CX part of the house here. But how does this approach change how they should evaluate, select, and even budget for new technologies?

A (6:25)

Sure. So, I mean, if you listen to other podcasts or AI influencers that are out there, they always say garbage in, garbage out. Right. So if you not only have bad data, or even if you have really good data, but the data is not connected and your agents don't have access to that data, then they're only as good as the data that they have and the connectedness that they have within the platform. So that's why having an integration first approach, where making sure your tech stack just at a fundamental layer is connected before you even think about building, you know, agents or automation that sits on top of that. So, yeah, it's. And I think that's why Trey is so poised within the market when it comes to AI, is because our roots is an iPass. It's connecting other systems together. So super impactful. Otherwise you. You start deploying agents and then realizing that you have to connect the data and clean the data, and then you're kind of back to square one. So, yeah, very important.

B (7:24)

Yeah, I mean, it's, it's just kind of a different. It's, it's silos, but just in a different way, I think, than most people are thinking about. Right. Because the point of agents is to connect things. So you're connecting things, but you're still running into limitations with some of those, those very focused tools. Is that safe to say?

A (7:45)

Yeah, yeah. I mean, especially if you use a point solution, it's like that point solution is really good about keeping you locked in their ecosystem where the data lives. But then it's like, okay, maybe you migrate your CRM or you adopt a new tool and then suddenly that data is inaccessible to you because maybe that new platform doesn't have a native integration with, you know, your CRM, your market automation platform, your email marketing platform. So, yeah, having that integration first approach is key not only to keeping the sanity within your team, but also when you start thinking about deploying agents at scale.

B (8:22)

Yeah, yeah. And so I believe one of your customers is yext and reading through the case study, they managed to build over a hundred integrations in a handful in just three months. Knowing what it takes in Fortune, you know, very large companies, let's just say to do one integration, that's a pretty, you know, phenomenal rate of, of speed and, and integration. Can you walk us through what was required to move from building integrations? I mean, if we're talking 100 integrations in three months, we're talking not weeks, we're talking days or hours. Right?

A (9:03)

Yeah. I mean every use case is a little bit different, but with, with yext, their big thing was their IT team was just completely bogged down, which just some of those common issues, password resets, access control. They're so busy doing that work and they couldn't actually start working on more impactful work like thinking about where is the business moving, working on infrastructure. So what they did was they built a series of agents that, that sat in front and, and in front of the IT team to do the case deflection. So answering those common questions. So they loaded it with knowledge and gave it a set of tools where the agent could even take actions so the IT team could focus on more impactful parts of the business. So yeah, I mean they're, they're, they're definitely a big customer. But you know, some customers start small, which is a couple of agents or a single agent use case scene and realizing the ROI from that and then moving up. Or you can be like yext or your enterprise business where you just have to move fast, where, you know, our front end interface makes it very friendly to build at scale, which I think was key for them to, you know, build hundreds of integrations. You can't do that with just code. You have to have a scalable infrastructure, which Trey definitely has.

B (10:16)

Yeah, well, and I think definitely to your point, to do that many things at scale and do it well, you also need that mindset of, you know, here's how we want to approach and good use cases. So, you know, I would imagine to your point, there's, there's a lot of organizations that may start off with a few pilots use cases or something like that. Right. And, and then kind of build from there.

A (10:39)

Yeah, yeah, it, it, you know, it's interesting some departments, the way that I've kind of approached it was, you know, meet with your team, document those repetitive tasks that are just kind of bogging everybody down or kind of draining them from their energy day to day, and then you can Get a lot of buy in when you start to like, be like, hey, when we can remove that from your plate, like that thing that's bogging you down, like we can just build an agent on it. That's a very approachable and easy way to get everyone bought in on it. And then depending on the use case, you can directly tie it to revenue. So whether or not it's a sales ops, marketing ops use case, or it's from open to closed case deflection, you can start to get those real ROI numbers and bring that up to your executive team and then identify the next use case after you've kind of shaved off that first bit.

B (11:30)

Yeah, and speaking of that, I know the case study for EX, they saw a 60% reduction in integration costs, so pretty phenomenal savings there. Speaking of ROI and things like that, some organizations may not again do that extensive amount of things, but still are looking for roi. And what are some of the metrics that can be used to, to start telling the story? Because I would imagine this is also, it's a change and any change, you know, it requires humans to be okay with that also. So you kind of need to win, you know, hearts and minds, however you want to say it to do that. So what are some of the other metrics used to kind of sell this in?

A (12:15)

Yeah, it depends on the team and the use case, but I'll kind of just give you a few examples. So it of course, like open, like how long a ticket is open to when it can be resolved is like a key, a key metric or the number of, you know, tickets that are resolved. So that's kind of a good IT example. On the marketing side, it could be from, you know, when you lead capture to getting it into the sales pipeline. Right. So you go to an event and you get that CSV and then you have to manually clean it and then send it off to the salesforce team to do import check to see if there's a lead existing and then update that. You know, all of that could be automated. So like another customer I worked with, from getting a lead into the system to getting it in the hands of sales, like took over a week when you could just automate that and have that done, enrichment, routing, all that done just within minutes. So there's, you know, tons of different metrics out there for like the value of getting to that lead record as quickly as possible and that impacts whether or not they pick up the phone and ultimately become a customer. So like that's a marketing use case and then from like an HR use case, like employee onboarding, like getting them onboarded as quickly and efficiently as possible so you can start getting value from that employee and having them start to do the work that you hired them to do. So different use cases across the board. But I mean those are just a few examples.

B (13:39)

Still jumping between tools just to update your website Framer unifies Design, CMS and Publishing on One Canvas no handoff, no hassle, everything you need to design and publish in one place. Framer already built the fastest way to publish beautiful production ready websites and it's now redefining how we design for the web with the recent launch of Design Pages, a free canvas based design tool. Framer is more than a site builder, it's a true all in one design platform. From social assets to campaign visuals to vectors and icons all the way to a live site, Framer is where ideas go live start to finish. Framer is a free full feature design tool. Think unlimited projects, unlimited pages, unlimited collaborators, and all the essentials ready to design, iterate and publish all in one tool. Start creating for free@framer.com design and use code Agile for a free month of framer pro. That's framer.com design and use promo code agile framer.com design promo code agile rules and restrictions may apply if you listen to the Agile brand. You're here because you want to lead. You want insights to help you build smarter experiences, stronger brands and customers who keep coming back. That's why you are going to love Simply CX, a brand new podcast from Microsoft hosted by Nicole McKinley, Microsoft's global customer experience lead. SimplyCX takes you inside the conversations that are shaping the future of customer experience and engagement. Each episode features industry experts and business leaders from companies like CarMax, TD bank and T Mobile exploring the innovations transforming CX. We're talking omnichannel journeys that actually connect AI that enhances human connection and how culture, collaboration and technology can work together to deliver trust, personalization and scalable growth. If you lead cx, influence CX or simply want to understand how the most admired brands stay ahead, Simply CX belongs in your rotation. Hear real stories, practical lessons, and the innovative strategies that will define the next era of customer centric success. Elevate the way your organization connects with the customers who matter most. Start listening to Simply CX every other Tuesday wherever you get your podcasts, and follow host Nicole McKinley on LinkedIn to keep the conversation going. So I also want to talk about the let's call it future ready aspect of this as well, because, you know, there's several. Obviously change is the only constant. Right. So not only are new things popping up, but an organization may shift platform, you know, they may be on, you know, Salesforce one day and something else, the, you know, maybe not the next day. But you know what I mean, these, they're going to change.

A (16:26)

I don't know. You say that, but I mean, it seems to happen that way.

B (16:30)

Yeah, fair enough. Yeah. And so this idea of being, you know, this, this integration first kind of mindset, it, it also keeps you ready for again, not only those things that we don't even know what's coming three years down the, down the road, but also those, those platform switches which are costly and, and time consuming and everything like that. I guess maybe talk about the mindset part of it first because it, it does require, I talk about agility a lot on the show, obviously, but it requires thinking very agile and flexible and knowing that, okay, we're using X tool today, we're probably going to be using Y tool in three years.

A (17:15)

Sure.

B (17:16)

What does that kind of thinking require?

A (17:19)

Yeah, so I mean, within our platform we have something called a callable workflow. And that's just a really fancy way of saying it's a narrowly scoped piece of automation or you know, it could be an agent to complete a task. And that callable workflow can be plugged into any process that you might have. So a good example of this might be something like lead enrichment. Whenever you want to enrich a lead, you pass this callable workflow and email address. It enriches the lead and it passes you back the enrichment data. So regardless of the use case spanning from like marketing sales Rev Ops, any of those teams can use this callable workflow. It'll enrich the data and get it back to them and be used in, let's say, 50 different automation processes. The scalable piece is, this is just one workflow. So let's say you change your enrichment provider from something like Clearbit to Zoom Info instead of having to go into those 50 different automations and update it from Clearbit to ZoomInfo 50 different times and handling all these different auths and it can just become a mess. So because Trey's infrastructure supports callable workflows, we have that composable architecture where you're only changing that, that process one time in one workflow. Marketing Sales, Rev ops, all those teams can continue to use that same callable workflow. They don't even realize under the hood that you've actually changed something so their, their processes aren't broken. There's a lot of continuity and you can kind of grow your business in that way. Same, you know, the same thing is like I mentioned earlier, Trey is a platform agnostic. We don't care if you're plugging, you know, an agent or a workflow directly into Salesforce or Eloqua or Sugar or you know, fill in the blank CRM. You can flip those out very easily within the platform. So from a scalability perspective, I think we have that in spades. And then from an agent perspective, you have like OpenAI coming out like every month with a new model. So like our agents can run on top of, of Gemini, OpenAI AWS bedrock. We don't care where, we're agnostic in that manner. And you can deploy the newest model or change models just on the fly.

B (19:23)

Yeah, and so you mentioned, and I'm certainly seeing this as well, is every platform out there has the agentic. It was Genai two years ago or maybe even a year ago for the later adopters, but now almost every platform has some kind of agentic component to it. How does one of those platforms live in a world with an organization that's adopted Trey? You know, how can they coexist or like what's the, what's the optimal solution there?

A (19:56)

Yeah, so we see this sometimes with Glean. There's kind of a better together story there where Glean does some search capabilities. We do search capabilities, but let's say a company has already adopted Glean. Like that could be baked into our processes. So as long, long as whatever tool you're using has an API and it can be invoked via like a rest, you know, interface, then yeah, we definitely have seen customers integrate with some other AI tools that do things really, really well. But we're finding that you still need some sort of constant orchestration layer where you have a lot of observability, you have access control for an example. A lot of these kind of pop up AI solutions like they're not HIPAA compliant, they're not GDPR compliant, they don't do regional host hosting. So it's like you got to be careful that of what data you pass these especially when we live in such like a compliant first environment. So I think that's where even if you have those, you still need those access controls that an orchestration platform like Trey offers. Still in the mix.

B (21:02)

Yeah, yeah, makes sense. So for those execs out there, marketing execs listening to this and they're, you know, they're Hearing some of the symptoms of, hey, I should probably be looking into something like this. What's the, you know, where, where do these conversations kind of start internally? Like somebody's identified an issue, but like, where's the best place to start for them?

A (21:26)

Yeah. So I think the first area is to just identify the use cases amongst your team. If you're a marketing executive, I would challenge you to go to your team and just ask them how long it takes for, let's say, an events lead record to get into sales arms. And if you know it's in days, you've probably got a problem and you definitely need, need to fix that. But you know, if you pull the, the, the, the marketing team or the marketing ops team, they likely know where the problems are. So it's just giving them the latitude to kind of dig a little bit deeper and then build out maybe a mvp, like a minimal viable product of what a use case could be and then bring that to some, someone like me here at Trey. Challenge us here, here at Trey and be like, hey, here's our use case, here's our pain point. Let's get into like a proof of concepts, start to build that out, see the value, and then adopt a platform like the Trey platform to help solve it. Not only just that, that first initial use case, but then once that's taken care of, move on to the next use case and the next use case. And then before you know it, you know, you have a fully kind of orchestrated layer to handle your automation and your agents within your business.

B (22:38)

Yeah, yeah, makes sense. Well, as we wrap up here, a couple last questions for you. If we were to have this interview one year from today, what's one thing that we would definitely be talking about.

A (22:51)

One year from today? Probably about that the content on the Internet with AI and stuff out there, it's becoming, it used to be very clearly, you know, AI and then it kind of shifted into like, okay, there's not six fingers anymore, but it's a little blurry and a little confusing. But it's getting so good and it's going to be, we're going to be living in a world in a couple of years, I think, where you're not going to be able to tell the difference. Even, you know, folks like me who are like in AI every day and there's something there, there's some controls that I think that we need to be putting in place. So when I talk about, we live in a world of a compliant first standpoint, so GDPR, you know, making sure that you're like SOC2 certified. I think there's going to be something else there that businesses are going to need to adhere to when it comes to AI or at least letting users know that they're interfacing with AI. So I think that's coming and I'm very curious to see what that looks like. But that's probably going to be the next phase in the evolution.

B (23:54)

Yeah, yeah, that's. I'm waiting for that too. So. Yeah, that makes sense. Well, Stephen, thanks so much for joining today. Last question for you. What do you do to stay agile in your role and how do you find a way to do it consistently?

A (24:09)

Yeah, I drink lots and lots of coffee. Um, no, it's I, you know, I say yes when I want to say no. Like I found that that's probably the best thing that like helped me out. It's like things are very scary. There's a lot of asks out there that I'm just like, I don't know, like I've never done that before. Have any of us done this before? Like, this is all new, new stuff. So lots of coffee and say yes instead of no.

B (24:33)

Nice. Love it. Well, again, I'd like to thank Steven Stouffer, Director of Automation Solutions at Trey AI for joining the show. You can learn more about Stephen and Trey AI by following the links in the show notes. Thanks again for listening to the Agile brand brought to you by Tech Systems. If you enjoyed the show, please take a minute to subscribe and leave us a rating so that others can find the show as well. You can access more episodes of the show@theagilebrand.com that's theagile brand.com and contact me. If you're interested in consulting or advisory services or are looking for a speaker for your next event, go to www.gregkilstrom.com that's G R E G K-I H L S T R O M.com the Agile brand is produced by Missing Link, a Latina owned, strategy driven, creatively fueled production co op. From ideation to creation, they craft human connections through intelligent, engaging and informative content. Until next time, stay curious and stay agile. Before we continue, I wanted to share a key strategic resource that a majority of the Fortune 500 are already aware of. Finding the best technology, business and talent solutions is not easy. With business demands and competitive pressures mounting, you need to be able to design, deploy and optimize your technology to provide leading customer experiences while driving business growth. Those of you that have been listening to this show for a while. Know that this podcast is brought to you by Tech Systems, a global provider of technology, business and talent solutions for more than 80% of the Fortune 500. Tech Systems accelerates business transformation for their customers. Whether you're looking to maximize your technology roi, drive business growth, or elevate customer experiences, Tech Systems enables enterprises to capitalize on change. Learn more@techsystems.com that's T E K systems.com now let's get back to the show.