SaaStr AI Live: The Top 5 Issues Managing Multiple AI Agents In Production
SaaStr runs 20-30 AI agents in production and hit five major problems: context-switching fatigue, blackout periods when onboarding new agents, succession planning failures, agents that constantly criticize operators, and multiplying compliance overhead. They also struggle with orchestration, ROI measurement, and knowledge transfer when a single person owns each agent.
Chapters
Shoot.
This meeting is being recorded by Update AI.
Great. We've already been thwarted. By the Zooms. Okay, we are live. Hello, everybody. Welcome back to workshop Wednesday. Sastra AI Live. Excited to be here with all of you and your agents here today. We thought we would do a fun one since we have 20, actually almost 30, I think when I counted it this morning. Agents and Vibe coded tools and apps in productions. We wanted to pick our. We narrowed it down to five plus one bonus. We wanted to talk about our top five issues. Once you start to manage these multiple agents in production, what does that really mean? What are maybe the nuances folks haven't thought of if you've only deployed like one or two agents? Kind of like what breaks when you have multiple agents at a high volume and high scale. So we're going to hit that today. And then side note, today's an exciting day because Jason's going to be on the Salesforce earnings call later today, so you can watch it at 2pm Pacific. You can also watch the replay if you miss it. Should be exciting times. So it's a. It's a big day. It's Aster in Salesforce. All right, fun times. Let me keep admitting, folks. And go. Okay, as always, I always like to have this as our first slide because folks go back to it and reference it. So for any of the agents and tools we'll reference today, you can go to Sasser AI Agents. That's where we put our agent directory, which I have a few more we need to add to it. But this is our depository of all the agents and some community agents that we use across the board. So a lot of the things we'll talk about today are linked there if you're looking for the links. So as always, keep that in mind. Okay, top five issues, I'll summarize them here and then I'll go into them in depth. I think there's a lot we've learned in, like the now 9/4, 10 months of managing multiple AI agents and production is being recorded by update AI between Jason and myself. Um, so I kind of narrowed it down to the top five things and then I have a bonus. And then Jason, obviously you can feel free to add anything I might have missed in these top five, but I do feel like these are truly the top five impacting our day to day now that we have so many agents and apps in production out in the world that are AI powered. Um, so yeah, I'll go just briefly through them and then I'll go through each of the five in detail. So I would say say issue number one, and this is maybe force ranked is context switching becomes extremely difficult when you have 20 plus agents. They don't all function the same way. If you guys saw the article that Jason did over the weekend about like how we use Salesforce and Agent Force, it's kind of like the backbone and the plumbing for a lot of these agents. You know, there's a reason we do that and that's because a lot of these agents function somewhat independently. Some of them push back to Salesforce, some of them don't, some of them talk to Claude, some of them don't. And so it's a bit of a hodgepodge today. Like that's the reality of managing all these AI agents and productions. They all speak slightly different languages, they all ingest context very similarly but still different ways. They all have slightly different personalities, I will say these agents and they all kind of want different things from you. And so I think context switching, just like in as a human brain keeping up with the agents becomes kind of difficult on a day to day basis. That. So again, I'm just going to go through this quickly then we'll dive into one of each of one of them. Number two, I think the, the new age of blackout period for again, for those of you who have maybe added a couple of agents but now you're, you're getting into the high volume of multiple agents for us at least even with the help we get from our vendors, which we'll talk about a bit. Even with the help we get. Like I feel like every new agent costs us at least two weeks of what I call either a blackout period and somewhat chaotic of like I kind of have to ignore the other agents anytime I bring on a new agent which as you might imagine since they need daily review, it's kind of rough on the entire stack. It's just like this cascading waterfall of effects that happen every time we add a new agent, of which I famously said on LinkedIn I was not going to add any more. And then I added two more in the last two weeks, so. So there goes that. And I can share some reasons why if you didn't watch the one from last week, okay, the other one, I would say number three, which is a huge issue actually, maybe it's number one, but the AI, what we call the AI Agent Succession Planning crisis. I actually asked our agents today what they would do if I had to pass them over and the answers were actually a little bit surprising. You'll See why when I dig into that one, the fourth one, I would say the agent as the truth tell one of my agents, more famously than the other, the 10k roasts me all the time, every day, because I talk to it every day. Like, that's the first one I talk to each morning. It will literally roast me all the time. Which is funny because when I push it on that for this webinar, it said it wasn't roasting me. So that's. That's an interesting learning too, where it said it was being helpful and I thought it was roasting me. And then last but not least, before we get to the bonus one, I think there is a lot of, you know, compliance and security, maybe not issues, but just nuances and maintenance that people don't talk about. That is a real problem. Right. I think that's why most high, you know, highly secure. Like, I'm not going to vibe code a Salesforce for a lot of reasons, but part of the reasons is because Salesforce is secure. Like, that data is there. We've got 10 years of data there. It's the plumbing for a lot of our other agents. But also it's, you know, they've thought about all these things like SOC2 and ISOs endlessly so that I don't have to. So that alone is like kind of worth it for us to use it and keep using that. But I think there's other issues when you start to vibe code your own apps and agents that most folks probably haven't thought about because you, you're so used to these other tools like a Salesforce doing it for you, that even myself, I didn't naturally think about doing that myself when I started pushing apps into production. Anything at a high level you want to add, Jason?
No, I think this is, this is enough for today, I think. I think you'll get to the next one. It would be useful just as an overview. When you log in each day, who do you talk to? What does that take? How much time does it take that. Because that, that feeds into the first point, doesn't it? There's context, switching decks. There's also just this. And part of that is all these different interfaces, all these different exceptions, all the different things. When you log in each day to Artisan or Qualified or Agent Force, there's a lot of time in different interfaces and different conflicts. That'd be the main one. And then maybe just a quick reminder to folks, maybe you have it in here how we segment our base for these different agents, because it's related to the first point, right?
Yeah, yeah, yeah. I would say I'll come back to this because I feel like this is kind of a good recap. But yeah, to your point on the context switching text, right. It's, it's, it's not even that I think about them as 20 agents anymore. Like I think the better comparison to make to folks on this call and watching live is you have to almost think about it now. And I think about it now as managing 20 different people which like before we had 20 agents. I don't even know what we had. Maximum headcount here, let's say 12 at the very, at the very peak. Now we have 20 plus almost 30 different agents plus, you know, three humans and a dog that we manage. So I think that's a better way to frame it to folks is to think about each agent almost as its own entity, as your own employee that, you know, speaks a different language, has a different personality, needs different things from you. Like to Jason's point, like I'm not immune from logging into each of these tools every day so seeing what's going on. Right. So like this is a good example of my, my kind of like morning even just this morning. Like I actually didn't even have time to go through my whole checklist because we are on this call attend. So I was like I haven't actually even made it through all of my agent check ins for the day and it's already 10 now. It's going to be like 11 by the time this is over. And I have other calls today. So like it's basically going to take me the whole day just, just to check in with all of our different agents. So I don't really know if this is my morning routine but my daily routine. But so yeah, kind of a quick example of the ones I check the most. Right. So I would say I actually log into 10k kind of first because this is our main internal AI VPM. We've done a previous episode about it where we did a deep dive so you can go back and check that one out. But just as a high level, this is one that is running on internal data. It has some API data. It's literally telling me what I, what I slash we should be doing every day for you know, tickets to Sastry, paid tickets to Sastry annual, our VIP summits that we have, our sponsorships that we have, our sponsors, media contacts. Like there's a bunch of high level, it's high level, you know, goals that I'm trying to hit with 10K. And so I check that one every day just to see where we're at and like, am I falling behind? And that's why this one roasts me all the time. It's like, Emilio, you didn't get, you know, these five things that I laid out for you done yesterday? I'm like, I had to go to sleep, dude. Thanks for roasting me. I understand why we're behind. Can you just help me figure out how to get caught up in a way that I can actually do with the time that I have today? And so then it will kind of reevaluate its to do list for me for the day. But 10k literally tells me what to do. So that's why I log into that one first. Because actually 10K2 will tell me what to do with our other agents. That's also why I log into that one first and foremost. That one is a mix too of Claude and Replit. So I'm kind of like bouncing between those two entities, which, you know, a lot of Replit runs, I'm pretty sure on Claude. And so for that one, context switching is not too, too hard because they kind of speak the same language, but they have different nuances in how they interact with you. Right. Like, 10k as Claude is obviously more like text based, whereas 10k as the Replit agent has a lot more dashboards, has a lot more numbers in it. So it's kind of a combination of both that I'm talking to at the same time. There's. Or then I'll go into, you know, what are our outward facing agents. I'll go into all of our sales agents and ticket agents, and that's artisan qualified agent force and now Monaco. So that's four different agents I have to log into. Look at who needs a human response. Look at who it's reached out to over the last, you know, day between the last time I checked it yesterday, let's say morning, and see what it's doing. Right. Like a lot of times I'll need to refresh what the agents are doing, who they're reaching out to, the copy they're reaching out to. For instance, I have it in the next screenshot here. Like I. You can see where it's roasting me already. Like, I had to context switch for this week when I was doing this on Monday because I was like, we have a distinct promotion going out this week for Sasser annual tickets in particular because the ticket prices go up on March 1st. And I literally had to put that context into five different agents. Like literally. You can see some of the screenshots here. I was like I have to go in and tell Artisan that I have to go in and tell qualified that I have to go in and tell Salesforce that I have to like 10k already knows that cause he's the one who came up with it. But then he's telling me why aren't you launching LinkedIn ads immediately for this new promotion? Do it right now. I was like I will do it as soon as I'm done talking to the other agents. And so context switching becomes extremely like. I don't. It's just hard to keep up with I think sometimes in your brain. And um. And a lot of the times it's hard too for the agents to remember everything you're doing. Right. So I think there's kind of like a double edged sword there.
And so the, the at least for us for today, if you're literally logging in and spending anywhere from 10 minutes to an hour with four to five of our core GTM agents. Right. I would say every, every single day. Right. And different user interfaces. You have to remind each others of the changes the campaigns because they don't talk to each other. I know we haven't found anything so it's slightly rhetorical question but people talk about orchestration agents and master agents. We haven't found anyone that can integrate agent force artisan qualified Monaco momentum attention attended. Like we don't. There's nothing out there today even with 10k which we built ourselves that at some magical API or other level can integrate everything for you that does product does not exist, right?
No, it doesn't exist. I will say the, the. The benef Salesforce buying qualified momentum is like eventually buy probably Dreamforce. Right. Those two things will be integrated into one. So at least I have like two less dashboards and I'll probably have one centralized one by October. But only because you know they've. They've acquired those tools. For most tools it's, it's completely separate.
Yep, yep.
So it's.
You're going to have a one on one with your agent every day instead of a weekly one on one instead of a check in on Slack. If you want to accomplish what we've done or better, you have to do a truly and honestly a one on one with your agent every day. Even if you don't want to do the work. You got to do the work to see one on one with every agent every day.
Yeah. And I think it's an Interesting learning too. I didn't put it here. But like one thing I do with my agents is I ask them every day, like what should I be mindful of, what should I be looking at? And, and then sometimes it'll say, hey, like I can give you a recommendation but you need to give me some data back or you need to tell me what you're doing with your other agents or you need to give me X, Y, Z inputs in order for me to output that. And so that is a very good way. I think more so to look at it is just think of this as 20 different people that you have to manage every day. Right. Sometimes you can get away with doing a one on one with a human once a week if you're, you know, lucky. This is, you can't, you can't wait a whole week. Like that's the thing. It's like if you wait a whole week with any of your agents, just it'll be so out of date by the time the week's over.
The production, the output is so high.
Yeah, yeah, exactly. You can't, you just can't afford to wait a whole week. Or like you're, or you're probably just wasting, honestly you're probably wasting your money if you don't spend the time to do it daily because a lot of these are waiting for you to give it inputs. Right. Like it's such a high volume, like artisan qualified agent for us. Like I'm constantly giving it more people to reach out to, better messaging, different campaigns, different things where like if I don't do that, most of those don't do it themselves. So they're just going to sit there. Like your agents are just going to idle if you don't check in with them every day. Which I also think is just like a waste of time and money because what you want is to have that high volume output. So you're maximizing what the agent can do. Right. So it's an interesting nuance. Okay. Number two, I would say biggest learning is we learned this kind of quickly, but I think it's just more so now, getting harder now that we have 20 plus almost 30 agents. But you know, in the beginning it used to take us more than two weeks to implement some of these agents. I would say now we've pretty much gotten it down to about two weeks for a lot of reasons. One reason, like a lot. Again, even though context switching is hard, you can share a lot of context between agents. So kind of once you have one, you can do another One, it gets easier. It's not easy, but it gets easier. But I would say we've kind of gotten it down to like a two week implementation pipeline for any of our agents. It's true for Monica, that we just did. It's true for Happy Fox, that we just did. Like, each of those just took two weeks. And that was not spending the entirety of the two weeks on it, but it was spending the majority of two weeks on it. And so this just gets harder with every new agent that you add, because each new agent means you're not spending, you know, that daily time I just mentioned. You're probably not doing that if while you're onboarding a new agent. Like, I know I didn't spend the time I needed to with each of our agents in the way that I, I, I usually do when I was onboarding these new agents, because I was like, I want to get these off the ground. I want to get them up and running. And so I'm just gonna have to do, you know, I'm gonna have to do the trade off and let the other ones slightly degrade or slash sit idle while I get these new agents up, because there's just no way I can do it all. And so I think that's a huge trade off. When you're looking at bringing in, you know, multiple agents is instantly things go stale with your agents, right? While they're idling, they go stale really fast. Not because they can't do things on their own, but because they're again waiting for you to tell them what to do. So if they've run through, like, let's just say one of these outbound agents has run through a whole contact list, but I'm busy onboarding another agent. It's just sitting there. It's literally idling. It's sitting there. It's not doing anything because I haven't had the time to give it new contacts. Like that is, I think, just a huge nuance folks don't really talk about is anytime, you know, we're all trying to push, like, okay, we, we also push like, we have a lot of agents and I think there's a lot more agentic things people can be doing, but just realize like, anytime you bring on a new one, it's gonna take time, it's gonna cost money for these agents. It's gonna cost some of your, you know, mental overhead and mental bandwidth and mental time. Like, these agents do not deploy themselves. And so even with all the help you'll get in the world, which you should only pick vendors you get help from. But even with that, like, again, two weeks is pretty fast. I think most agents, especially in the early days, took us like a month, maybe six weeks to get up and running. Now we've gotten it down to two weeks because we've gotten pretty good at it. But I'd say in that math, you can really only add 1/1 and a half agents per month max. Like, otherwise you're running in place because you can't really keep up with your current agents to add the new agent. So it doesn't actually, maybe it doesn't make sense to add that new agent if you can't keep up with it or know that you can, that you'll need to do kind of a blackout period to do a new agent. And so I think this is super nuanced, not something I really realized until we had multiple agents of production, that there is a trade off. Like it's. You're going to get a lift from it for sure. Right. If it works the way you think it will. But there's a trade off. Like, it's not free. It's not free. Scalability instantly. Okay. No. Oh, these are. Yeah, these are screenshots I added. So I added some of these screenshots of Monaco. This was like one of our newer agents that we just did. Again, we got help from the team to put us into the product. I think it took, you know, probably two weeks conservatively, maybe a little bit less actually because we, we worked fairly quickly with them. But again, it was one of those things where I blocked out doing other things. And actually the Monaco team works over the weekend. So I did a lot of this over the weekend, which was nice. But we got it up and running in basically a week and a half. And you can see here, like in its first week on, you know, it reached out to 64 people. It booked six meetings instantly. Some of those are like tier one accounts for us, which is pretty dang good. So again, is it worth it? Yes. From that perspective, it was worth it to let our other agents kind of like sit idle slash do a little bit less while we were getting this new agent on board. Because we believed it would be worth the trade offs. Right. But just know that you're going to have to probably weigh trade offs when you come into something like adding a new agent and maybe just plan for a blackout period. I think that's my kind of meta point is if you plan on it, it'll probably work more to your benefit versus just going into it like, oh, I can just add this in a day. That's not really going to work for you or your agents. So, okay, number three. And this may not apply to all of you, but I think from what I've seen, and this is where I want to get your take too, Jason. I see a lot of folks where it's either a single or, like, maybe one. Like, for us it's two people, but, like, it's kind of a single point of failure for our agents. And it's funny because I put some screenshots on the next one of like, I asked my agents what, what it would do if I stopped talking to them, and the responses were interesting. But I think this is where folks get themselves into trouble because they think they can, you know, recruit somebody to just manage all the agents. That doesn't really work. They think they can just, you know, roll it out to the entire sales team or the entire CS team. That doesn't really work. There's reasons that doesn't really work. Like, this is, I would say, the biggest double edged sword of, like, I do think having a single point of truth with who is managing the agents, right? Like, who, from our perspective, which contacts go into Qualified versus Artisan versus Monaco versus Agent Force. Like, that is just all in my brain right now. And I'm sure Claude could write it down if I told it to and give it to other agents if it was really pushed. But like, but then if, like, let's just say even if I got the agents to give me an MD file of everything it knows with me, I'm not sure the next person can really pick it up in the same way. They might say, okay, you know, Emilia was segmenting a lot of her ticket Outbound and Artisan and then a lot of her sponsor Outbound and Agent Force and then New Cold Outbound in Monaco and then, you know what, whatever else we're doing, retargeting in and Inbound and Qualified, but maybe this new person doesn't agree with that. They may say, hey, agent, like, oh, you're outbound. Cool. I'm just gonna keep one of you. Like, one of. Like, we only need one of you to stay to do, you know, Outbound. If it's truly, at the end of the day, those are all doing outbound functions. Somebody else might say, I only need one of those agents to do those things. Which might be true. But also, like, we have found, like, we have all these tools because they're super nuanced. They're like, hyper effective in certain Verticals. And that's why we've chosen to do multiple agents versus just one agent. And so I think that's an interesting nuance. You would lose like again, double edged sword of like, I think having one person know what's going on with all your agents is super important. But then what happens if you know you're in a bigger company, you have maybe multiple people working on agents or you're at a bigger company and that person leaves? Like how, like how do you scale past this? N equals 1. And I don't think there's a good answer for this today. There is no like again, crazy good agent that can manage all the other agents on its own today. As of February, there's. That doesn't exist. Right. Like I wish there was. I don't know if I think there will be, but there's not one today. And so I think even with all the help we get, it's, this is just a huge issue that I think the market has not realized yet.
Yeah, it's good. I want to keep going, but yeah, I mean, I mean obviously we're extreme and tiny. I mean if you left for some reason, we would, we would have to cease using our agents. There's no, there's no, there's no plan B. So we can keep going. It is a. You know, we're just all learning that you need some sort of chief agent officer. Right. Whether it's, whether it's whatever you want to call them, someone that can manage all of your agents that I think needs to be a bit of a nerd, a tech nerd, ideally a bit of a marketing nerd. Because a lot of these products are. If you can manage a complex marketing automation tool, you can probably manage most of the products that we use. You can hack the rest. But you know, thinking through it, I mean, this is, this is captain obvious. But I think if you actually find the person that can deploy these agents for real, that actually can be success. Just like a lot of these functions. But immediately they should recruit. You need to recruit somebody else on their team and divide and conquer and make sure. You have to. Yeah, you got to have two. Right. I mean, one's hard enough. There's a lot of. In the early days of agents, when we talk to folks, there's very few people at a lot of organizations that can do this. It's not that hard, but there's very few people. But you. Yeah. If you don't have to, you're at existential risk.
Yeah. Like literally when Philippe is a Zero at Persona was in London. He, you know, he famously set up all their agents. But then he was like, I, I started using, he was qualified or something like with the sales team. And then he was like, I rolled it out to like a few reps to be able to like, because like qualified, you can round robin, like the inbound, right? You can say, okay, like I'm gonna, I'll be the master. He's like the master controller of it of like doing the training and the programming. But qualified is actually an easier one to get the rest of your team on. Can just have them respond to folks when the agent can't. You can set up certain escalations and how, however you want it. Right? So for him, he was like, okay, I rolled out to like five of the top reps on the sales team. And then the very top rep, whose name is also Amelia, ended up being the most like, affluent at learning how to work with the agent hand in hand as a copilot. And so then he decided from that like kind of pilot test with his humans that Emelia on their team would be the next person he trains on how to use the agent. So like he did kind of, you know, like a little bit of a beta with their team and then said, okay, I know now who wants to actually manage these agents the way that I do. And so now I'm going to train that person. So that's another way to do it too, across your team is to do it that way. But yeah, this again, double edged sword though, because now it's like, now he has to tell all the agents everything, plus he has to tell Amelia everything. So like.
And he's the CRO, arguably.
And he's the CRO, arguably. Yeah, exactly.
Right.
Yeah. So it's funny too. I asked our agents what they, what they recommended we do if for some reason I got hit by. I said, if I get hit by a bus, what, what should you tell other folks about, about yourself so that they could like, if Jason were to take these agents over because I got hit by a bus, what would you, what would you tell him? And, and the 10k version of Claude said it would. Well, these docs are on my computer because I use Claude on, on, on machine. It would need to give him these, you know, documents, which I'm like, I don't know, maybe you could ask my laptop password. I don't know, maybe you could get them. But like, first of all, that's already an issue because I'm like, these docs are literally on my Computer and probably nowhere else. Then it's literally saying the next campaigns he has to run for March and April, which I don't think you would want to do. And then I think it's interesting it called out what I consider the vibe for Saster annual, which I hadn't really thought about. It's just, it's a little funny that the agent was like, make sure Jason or whoever takes us over if you get hit by a bus knows what the vibe is like. So it's fun. I was like, I do actually call it a moment in time. That's really funny. I use that in like a lot of copy and I use that in like a lot of things. So it's a little funny that the agent picked up on that. It wanted you to know the vibe, Jason, just in case I get hit by a bus. I think the other interesting thing was I asked our Saster sponsors, which is an app we talked a lot about last week, how many lines of code it has, which was shocking because I think, Jason, you said it's something like 3,000 is like, you know, average or basic or simple. It said 12,000 and it said it was hefty. But then I said, okay, since this is a hefty 5 coded app that I made for sponsors. Yeah, how would you bring somebody new up to speed? And this is where it gets tough, right? Because I'm like, I think what it says, it's so complicated that somebody else would give up. It's explaining, it's a sponsor portal, fine, that's easy. But then says how the authorization works. Every sponsor company is a clerk. Org. I'm like, that's already complicated because the agent doesn't have my clerk login. So you're already kind of fucked here. Two, it goes over the tier system that I created, then it goes over the sponsor data and then it says, you know, a lot of the sponsor data is hard coded and that's because I just give it to the agent and then it has like master tables that it puts it into. It's also nuanced in like how I create that sponsor data is I create it with Claude a lot of the time and then I give it to Replit. So again, already running into a lot of issues here. If I get hit by a bus, key pages, the back end. I don't even know what a fuck freaking postgres SQL really means.
Well, it's our database, but it's our database. It's too hard for someone to take this over.
Yeah, like, okay, file up let's go to Replit Object Storage submission sync to Google via zapier Again, you're just running into a lot of issues here. Like the agent doesn't know my clerk login. It doesn't know my Google sheets login. It doesn't know my Zapier login. It's a, like it's, it would be a mess to hand it off. And then it was funny because then my agent said, don't get hit by a bus. That was, that was its recommendation. I said, thanks. I'm really trying not to. All right, this is number four for me. You've already seen it a little bit in these slides. These agents, as I, they're interesting to work with on a daily basis versus humans because, you know, some sometimes humans have their own ambitions, their own goals. Like, I feel like Claude is famously goal seeking, but in a very different way than a human being is. Right? In a very different way. So I think there are times where I also feel like these agents don't really know the date and time and like they don't realize, they don't realize on their own that like when you start chatting with them at six in the morning, you're still chatting with them at midnight, that you should probably go to sleep at this point. Like you can't keep working with your agent. So like, it's just a little funny that as I, as I considered it. But you'll see my agent's response in the next slide. I consider my 10k is like roasting me all the frickin time. Like you can see it here. It said you're behind on Summit outreach. I said, I know I am. Hold on. I lost my slide. You needed to send 200 emails by February 15th. You said 87. You're 56% behind target. Now, maybe you don't think this is roasting me. I thought it was though, because it also told me to block three hours. And I was like, you know, I don't have three hours, let's do this and catch up. Like, thanks, but also now you're just stressing me out and roasting me versus being helpful. So I thought that was a little bit funny because it was. It, you know, what does the agent care? The agent's just gonna tell me the truth. The agent has all the data more than I probably look at it, right? Like, I look at it a lot, but it's got all, like, it knows where I'm behind, it knows my calendar, it knows all these things that it's still said you're dropping the ball here. Catch up. It's constantly asking me, what's preventing you from doing this right now? And sometimes I'm like, it's literally 11pm And I'm tired, so I can't really focus on launching this XYZ thing that you want me to do right at this very moment because I need to sleep first and then do it. So it's just interesting, right? Of like, okay, what then? What do you decide is the human leader of the agents is helpful versus what crosses the line into maybe slightly demoralizing of. Because your agent knows everything. It's not that it's wrong when it's roasting me, right? That is maybe the uncomfortable truth. Oftentimes it roasts me, and I'm like, yeah, well, I deserve that roast. You were right. Like, I didn't do this thing that I'm now behind on, but also, like, because so much, like, so, like, 10k roast me the most. So many other agents roast me slightly. But, like, because you're getting it from so many different angles and so many agents because you can't keep up with them, sometimes I feel like it does cross a little bit of line where I'm like, okay, dude, like, today just, like, sugarcoat it to me like you would a person. Like, today, I don't need the heart. Like, I can't deal with hard truths every day. I don't think anyone can. Like, I can to some degree, but I think every day, all the time from your agent is a lot. So it shows. I have some screenshots here of how it's been roasting me, but it's funny because it said, you know, literally it said to me on Sunday, what's. When it was super late? What's blocking you from the LinkedIn lads from going live? And I. I literally said it's because it was late. And then I said, hey, you've kind of roasted me a lot lately. Can you. Can you bring up some examples for this webinar I'm doing? And it said, looking through the transcript, I haven't really roasted you. It said, I've been a tough accountability partner. And then it listed ways. This is only 2 out of 5 ways. Then it listed ways it should have roasted me. And I said, thanks. This is. I don't know if you're. I don't know if your agents roast you as much, Jason, but I think this is just a. Like, a fun, interesting one of, like, you know, just something maybe you don't expect from your agents is that they will always tell you the truth. And they have all the data. So I don't know. It's an interesting one for sure. Okay, let's get into the last one and then I'll do the bonus one. And we've, we've got quite a few questions that I want to try and get to. So. Compliance and security issues. Anytime we run an audit or ask an agent to run a security audit, it takes time to fix these. Like, we ran a huge one the other day on Sasha AI. We haven't even fixed, I would say, even 10% of the issues that came up in the audit because it became super fragile once we started, like, futzing with the code. And like, then, you know, sometimes when you do a security audit, it will go too far. Like, it'll start to lock things down to the point where you're like, I actually can't even use my app anymore because it took us too far. So then you kind of have to peel back one by one. It's something you have to walk the agent through. It can't really do it that great on its own. And so this takes a lot of time. Not only does this takes a lot of time, the maintenance becomes a lot harder each time you do a secured audit and implement whatever it recommended with you together. So then when you start to multiply that across 20 agents, it's almost unfathomable, like how to keep your apps and all your data secure. But you said you've been running the security more than I have. Like, you're the one who actually told me that I should write it on.
There's a lot here, I think, I think we can spend as much time or a little time here. I, I think it is, it is a reminder that in general, I mean, you can see this in the press, Agents can do more autonomously. That's why they're agents. Right. What's the definition of an agent? I'm actually not sure, but I think it is a piece of software powered by AI that can complete tasks autonomously. And all of these agents, if that we're talking about, go to market. Agents and others have access to your data. And there's an inherent level of security in that. Salesforce is our hub. Right. As to tie this to the beginning. That, that is important. I think, I do think it is one of the, if, if no other reason to use something like Salesforce, your hub, is that it is secure, but these agents then take data out. And the honest truth is no agents, no third party agents are more secure. Than sales source. They're all less secure is the reality of it. They're less secure because they're startups, but they're also less secure because the agents can do crazy stuff with them like publish them to the wild. Right. Or do other things. It is just a reality. And then just. The final point is once you vibe code yourself, which we have done a lot of, they are inherently less secure than third party apps that you buy today. I don't. That may not last because a lot, all of the, the, the products from cloud code to replica level below that have added more and more security, but they're all custom. They all are less secure than a sales source or something. So all of the, the apps like us you're going to run are going to have customer data through them. They're all of them. Right. You're not Stripe or PayPal. Like it's not that dramatic in many cases. But bear in mind you're taking some measured risk. So at least if nothing else, the ones that you create yourself before you launch and then frequently, at least every month, just go to the agent and say do a deep security audit on my app and just have it do that. Don't assume the apps do it yourself. That's the best actionable thing I can take. And then just be thoughtful that there are, there are just inherent trade offs to this that we're all going to have to learn. Right. And it may make sense as you get going in the agentic revolution to maybe use slightly less sensitive data to start. If you're a conservative enterprise, it just may make sense just like it always has been for enterprise software. You always start in a, in a little group or little function. That's safer. When you buy a startup, it's just this on steroids because you cannot fully predict what the agent will do with your data. It's just a reality.
Yep.
It's just a reality.
Yep. Yeah, I put a few screenshots here
of like run another audit.
Yeah, run another one. Thanks dude. Like there was a question in the chat too. How are we running these security audits? Some of them you can do natively with the agent, right? Like lovable repl. You can just ask its agent to run an audit for you. Other times again, you may not need it if it's a full blown third party tool, but you should ask that tool, like I asked transfer from Artisan all the time. I'm like, hey, what is your. How like what's your compliance right now? Like what do you. Because you have so Much of my data, like, let's just make sure it's not going anywhere it's not supposed to. So I think that's another thing too is like when you use third party tools like we do, obviously we use Salesforce for a lot and that's ultra, like fairly secure, right? Knock on wood. But for the other ones we use, I just ask them. I'm like, hey, what, what are you guys up, up to date on? What are you doing to make sure our data is secure? Okay, last one and then I'll do questions. This is an interesting one. I added this because I got a little frustrated yesterday. But I think this I added as number six because this may not apply to everyone and may not be a bridge that you ever cross. But I think if you get to the point where your agents do work 247 and you have almost 30 agents, um, and again, your agents know all the data when they answer a question. They have your APIs, they have your sales. Like they have all these things they can look at and are brutally honest slash roast you when you can't keep up with them. Um, I think makes it harder sometimes. I know, at least for me when I deal with actual humans, that sometimes I lose patience with them a lot quicker now because I'm like, what do you mean you don't know the answer? Like, my fucking agents know the answer instantly. Like, what do you mean you don't know the answer to this very basic question? What do you mean you haven't delivered on XYZ thing that I gave you three weeks to do? Or what do you mean you forgot something that I've told you literally 10 times now? It does make you on Sometimes I often start to wonder. I'm like, do I need them or can't I build an agent to do this? Because if I'm losing patient with, then I'll probably lose patience with somebody else in the same boat. And if an agent can just do it and the agent won't lose patience, maybe I should just build an agent to deal with them and they don't have to deal with me. So I think it's just an interesting nuance. I think something else I've seen just to be wary of. This is almost somewhat unrelated but related in that I've. I've really find it now in the age of AI in, you know, the early phases of 2026, when folks tell us that they're gonna help Saster for, you know, let's just say XYZ thing for Saster annual, like I'll give you a concrete example. A couple months ago I was working with a few parties on just sastry annual third party production things we normally contract out, things I thought an agent couldn't do. And I went out to a few different agencies and production teams to RFP for it to get a quote for it. Right Normal. Okay, fine. A few folks told me this would be your deliverable. It was one sentence and this would be the price and it was something exorbitant like 40 or 50k a month. And I was like in the age of AI that's what you're promising me? Something that like is one sentence, one price point and nothing else. Like you couldn't even ask your own internal agent or frickin ask Your Claude or ChatGPT how to make a better proposal. Like that's terrible. In the age of AI I was like this is just unacceptable. I just didn't respond to those people. And it's sad because multiple people did it. And I think maybe that's just a symptom of agencies versus software tools and maybe marketing agencies won't exist in a year because of this. But I literally was like how in the age of AI can you say you have a one sentence deliverable and a fixed price point and you can't even use the basic AI better than our team can? Like what? I was exasperated. I was like this is so crazy to me that so much of the world is still operating this way. Like I think you know, AI is probably going to come for them. But I was like I don't think anyone in the age of AI should be giving you a fuzzy deliverable and a fuzzy timeline. That's just not acceptable anymore. I don't think that was ever acceptable. I think it's just more unacceptable now. The other thing too is again I kind of mentioned earlier but like I know sometimes people will roast Claude on social media for like forgetting things of like your conversation got too long, it has to get backed it or forgot something in the MD file or accidentally deleted something. I'm like yeah, but the, the things that humans forget is honestly sometimes worse. Like the amount of times we've had to resend somebody the same thing like over and over again is a lot more than the times you have to remind Claude of something that it maybe forgot because it couldn't. Like it didn't have enough memory or storage. Like I do think it's a little bit different. Again, I do think person personal goals and goal seeking is a lot different than the way that Claude is goal seeking like Claude and all the different agents in the LLMs are goal seeking to try and help you hit this goal. Right? That's why 10k rows me all the time. It's trying to hit this goal and it doesn't understand why I can't keep up with it fast enough to hit the goal. That's a very different goal than maybe let's say a human on the marketing team being like hey, I actually just want to do. I only want to work on ads. I don't want to work on anything else in marketing. Right? That's very different goal seeking with people than it is with agents and LLMs. Also this is an interesting nuance, but I do feel like I have now managed more agents ever than than humans. And so I'm probably worse at managing people now than I than am like agents I get, I can you know, talk to them first thing in the morning, last thing at night. Like they're not going to be impatient with me if I don't respond to them right away. They might be idle, but they're not going to be like, you know, the same as the same vibe as somebody in Slack being like hey, I have a question for you. Can you answer this right now? And sometimes I can't. Like so I do feel like now that I've flipped the switch to managing more agents, I think I've probably become slightly worse than managing the people that are, you know, that work with Saster, especially leading up to SAS Annual. So it's something that I am hyper aware of now because I'm like, I have to remember that there are not agents I need to be more. I don't know. At some point I'm like, I just don't know what's realistic anymore. I'm like if the agents work 247 and feasibly, any human can use an agent, why can't they keep up a little bit more? So I don't know. It's like I don't even know what to do with this. I just think it's an interesting. That's why I called it my bonus point of once you reach this point, what does that really do right in your, in your nucleus of how you operate with the team. The team is agents. Like they are still part of the team though, right? So it does kind of change not only a lot of your day to day and the maintenance that you have to do. But I think in some ways it's kind of made me worse at working with people. All right, anything else you want to add Jason before we go to questions?
No, I think it's great. Let's, let's. Let's hit the questions. And I think it's just a reminder. I do want to, but it's a reminder to me that no matter how much people talk about on social media about an orchestration layer, we haven't found one yet. It's. It's on our checklist. But when I look at a lot of the GTM and other vendors, they're just building point solutions. Right. No matter what anybody says. So as soon as we master the orchestration layer ourselves, we will share it with you. It is, it's definitely a challenge for 2026, but it's one we haven't even realistically been able to tackle yet. But let's get the questions.
Yeah, it's funny, there are a few questions on why we haven't tried to build our own orchestration layer.
Well, how would. I mean, do all these agents have enough of an API or open system that we can manage. Can they all be managed through an API? We'd have to extract all the data through into cloud or wherever. Our own Vibe coded app and then we'd have to mat and we could get them all on some sort of unified system. But they'd all have to be 100% manageable through their API.
Yeah. Which they're not all that.
I. Yeah, I don't think it's a priority for any of them. I don't think it matters whether it's M. C.P. or anything there. If they're not exposing their entire. I mean, literally just going in every morning and seeing the exceptions and issues that come up from campaigns the night before, if that can't be fully replicated inside an orchestration layer with some management, it's useless. Like if it's not as good, it's useless. Right. So everything would have to be exposed. It's a good question. And it's not. I'm not saying someone smarter than us couldn't figure it out, but we haven't even begun to figure that out. There's no obvious off the shelf, ish, even Vibe solution today. And platforms are a lot of these agentic platforms are not as open as they look or as you might think, not as. That's not fair. As much as you might think, there's siloed solutions today.
Yeah.
Right. The only thing that is open is Salesforce. It's where they all meet. And if Salesforce could be our or truly our orchestration layer, that would be the actually the simplest path. Right. But it's our management layer, but it's not really a truly an agentic orchestration layer yet.
Right? Yeah, not yet. Let me go back through the older question. Someone asked. Clarifying questions. When you've been talking about your agents and apps, are you talking about cloud code? Cowork? Open. We don't use Open Claw, but Open Claw or agents inside of SAS vendors. I feel like we've touched this every week now. People keep asking why we don't use Open. Like we don't need it right now. But yeah, you can go to. If you missed out the topical, you go to Saster AI slash agents. You can see all of our agents there. We did a deep dive last week on our build versus buy role, which is 9,000, 10,010 to buy, sort of 90. 90 to buy, 10% to build. And we explained why we build things versus sometimes buy them off the shelf. But most of this is third party slash off the shelf stuff that you can also use slash replicate some of the internal stuff. You can likely replicate too with your favorite vibe coding app. But yeah, that's. That's our 9010 rule that we wrote down last time.
Look, just on the open clothing, I mean, we could laugh about it, right? I mean, I tried it early. The. The reason we don't need Open like the challenge we need solved is our. We don't need our. Our agents to be more autonomous. We don't need help running them more often. Like the. At the end of the day, what Open Claw is clever at is helping you run Claude and other things around the clock when it doesn't naturally do. So. It's reasonably clever for that. We don't. We already have our agents who are producing more output than we can keep up with as they're configured to run autonomously by orchestration. We really need them to be unified. We need. We don't need. I'm not even sure we need an AI orchestrating R20 agents. We need a single interface where the humans meet with the AIs. That's what we really need. Right. And maybe that needs some automation. That would be nice, but they're already running on their own. These are not isolated agents that, that we need Open Claw to. To have a heartbeat file to get them going again. They're off to the races. It's just logging into 20 apps every day and dealing with the issues is a headache. Right. So we need to simplify the human side and maybe even. Let's keep going. Maybe even orchestration is the wrong term we need. Unification is sort of what we need.
Yeah. Yep. Maybe we'll build one after annual. We'll see. It's only 90 days away. Maybe we'll see, but not again. I keep telling myself I'm not gonna add another agent or do this thing, and then I do it. But likely not before then, since Sastry Annual is right around the corner. Another question in the chat from Alex. Any other thoughts on scaling past one person to manage all of your agents?
Again?
Yeah, we kind of touched on it earlier, but any additional thoughts on how you scale past 1? 1/2, 2 people managing all the agents.
How do we scale
past one or two people. Yeah. Managing all the agents?
I don't know. You would know better than me. I. I don't think it's that complicated. I think that. I think that you. You. I mean, listen, there's obviously conflicts in some ways. A lot of the start of this conversation was about conflicts, potential conflicts between agents and making sure they don't conflict. But if you have two folks on your team that work well together, two humans, they'll just divide and conquer.
Yeah.
I mean, we are our agents. Our go to. Our sales agents are roughly as Amelia alluded to and we've talked about far are. Are actually fairly clearly segmented. There's. There's raw outbound. Right. There's. There's. There's inbound. There's re. Energizing lapse leads. Right. There's lapse leads, and I might be missing the fourth one. I've just have different people manage these different campaigns and have them coordinate every day, just like the agents coordinate every day. That would be fine. If we could find a mini Amelia or a maxi Amelia, we would hire him or her tomorrow as a human, like, no problem. And they would just divide and conquer. I don't think that is an issue with agents.
No.
It actually might let us do more. Right. We probably could do a little bit more.
Oh, for sure.
Yeah.
Yeah, yeah. I think the issue I've run into is like, I. Well, I was like, I'm not going to try and solve this problem before annual. But two, I. I think the problem I run into is like, I can't find folks that know more about the agents than I do at this very moment in time. Right.
Well, that's. That's. That's. That's a big. I think what you need is someone that. Not that for real, wants to learn and is a good nerd about tools.
Yeah.
You need someone that has already built. Listen, everyone should be Screening hires better. You should have someone, someone should come into the interview and have built an agent and replit or Claude code or does something. That should be the test. Yeah, that should be. In fact, what they do at replit itself now is they give you a massive amount of credits. I think they give you like a thousand dollars worth of credits in the interview and they say build anything you want with a thousand bucks, come back to us and then we'll do the interview. Yep, it's the best test in the world you should do. If we could. If they don't need to be better than you, but they need to pass that test. Right? Here's whatever you need. Just, just show me something you've built that automates GTM or agents that is better than we do. And you know, if you're not too crazy, we probably hire you tomorrow. Even if you could be pretty crazy, we'd still hire you, right? It'd be fine.
Yeah. Yeah, I think that's a good test. And someone else asked about our stack, which we answered. Another question is how do you calculate your agent roi? We've covered this on previous chats before, but just at a glance since most of these are go to market agents, we, we calculate ROI directly in, in meetings booked, but actually meetings but doesn't even really matter that much. I, I count it more so as close one revenue. That is literally our, our very top line agent ROI across the board, across all these agents is roi. Like true ROI and revenue.
I'd say there's just two things. It is very easy to attribute revenue to each agent. It's very simple.
Yeah, it's super easy.
In fact, there's rarely even a multi touch issue. At the agent level there may be multi touch. At a market meta marketing level it's very easy. Which agent interacted with which lead and did that, did that lead close like. And then we attribute revenue to them. That's the main way we measure roi. The reality is, having said that, it's not why we started. We started because we had people that didn't want to do these jobs and we said, can we replace a six figure hire with a five figure agent? So the truth is even if these agents performed a little bit worse than they did, they would still be ROI positive on that, on that goal. Right. Our goal was basically to achieve the same amount of revenue with half the humans and, and the agents. That was, that was the way we initially measured roi. And honestly I, you, you know, you, you need to deliver the one thing I'll say to folks in general, if they're scratching their heads and why is it so hard? I can tell you some of the products that we use, most of the ones we use, they have infinite demand. Like Monaco, we just rolled it out for outbound that we talked about. They're booked for two months, including weekends for demos. Okay. There is one called Basis, which is an age product for accounting. Yesterday, I don't know the team, but they just raised it a billion yesterday. And they said in their, in their, in their header, one of the challenges is like their demand is simply overwhelming. Like they can't serve the demand. Now some of that is because you have to train these agents and you have to onboard them and you can't dump it on the customer. So there's a reason for it. But that's how we measure roi. But if you're a vendor, if you're working a startup, your ROI needs to be massive in this world or you're going to be slaughtered by folks that deliver. Like a six figure meeting on day one. Like Monaco did, right? Or take over all of like two people did for like each of Artisan and Monica and qualified. They replaced like two, two people each, right? That's high roi. Mediocre ROI is dead. It's just dead. Products that just give you productivity bounces. No one's going to buy that stuff today. So that's why I challenge folks out there. If you're stalled out, if your business is struggling, if people aren't lining up out the door to buy your agent, your agent is not good enough. Anyone that has this massive roi, they cannot service the demand. They literally cannot service the demand. At least not all the demand. And, and in fact, what A lot of the vendors that we highlight here, if nothing else, they ruthlessly screen out prospects that are not a good ICP fit because they don't even want to waste their time, anybody's time. They don't want them to churn, they don't want them to bounce. If you don't have enough data, if you're too small, if you're the wrong org, some of the folks we talked about just, just, they just, it may, it frustrates people. We get emails all the time. Hey, can you get me a meeting with this vendor? I mean, we can, we will, but, but sometimes they're making the right decision. They're so overwhelmed with demand, they've got to focus on their core icp. So that should be you. I know it's tough to hear, but it should be you. And if it is if you have this agent where the ROI is so insane you can generate new business for them the first day or the first week or you can replace multiple humans with an agent reliably. In today's world right now, this may not last. In today's world, you will have demand out the door. Out the door. And if you're not, don't delude yourself that you just have that your AI is good enough. It is not.
Yep. Okay, I'll try and hit one or two last questions. Another question from the chat was what's preventing you guys from letting the agents do more of the work? I. E. Emailing on your behalf, updating LinkedIn, letting it do the LinkedIn ads, etc. Since it's roasting you on that, I'll give you my quick tape is it can't do it. I would let it do it if it could. These agents can't do that. I have not seen an agent successfully do email marketing at scale. The moment I find one, I'm using it that actually works. I've not found one that actually works. Like not just writing all of these, just write email copy. They don't actually send it to the right contacts at the right con at the right time. They just don't do it.
I would let it do it'll come. Listen, some folks are going to challenge us and say hey my startup does it. Listen, we look at everything that's out there. The reality is, you know, marketing is behind sales. It's just a reality. Honestly, if you squint at the apps we use our stack, half of them really are marketing automation. But for sales, right? Go back to the old days salesloft outreach. Companies like this, they were, they are marketing tools just designed for the sales team instead of the marketer. Right? That's these are just those tools on steroids with AI. They're just ahead. It is embarrassing that we do not have a fully automated HubSpot slash marketo today. There's no excuse. It's free friggin 2026 like and marketing actually is some ways easier problems to solve than sales, right? Instead we're living, we're living in the past and even I, I get folks reach out to me and what they're doing in marketing is very narrow. Like I can automate a little piece of your LinkedIn ad and maybe we'll add that. Right? We haven't historically done that. But I don't need a, I don't need a landing page, right? Or like a little tight optimize my Instagram. I need a. That's why we built our own VP of marketing. I wish we hadn't. So we are all over this. I hope that in the back half of this year when we do these AI lives, it's actually all about marketing. That's what I'm optimistic about. But we don't need any. Like, we need the kind of ROI and marketing that we see in sales. Otherwise, it's just. It's not worth it. They're not better enough. Right? But we would love. We would love to this. And there's no reason it can't be automated with AI. There's no reason. There's no reason that you cannot ship better emails than a human can create. There's no reason AI can't take your past campaigns and update them with new visuals, new, new video, new content and send them out. There's no reason AI can't segment your base better than a human can say your segment your base. There's just no excuse. There's no excuse to not run programmatic advertising for B2B, not for B2C without you having to do anything. There's no. Like that all should be doable today. And people are going to say, we do it, we do it. We'll keep looking, friends, but if you can do all of this, then, like, do what? These leaders have set it all up for us on their own and show us that it works and we'll. We'll be on your homepage. But it's got to do all of it. I don't need a landing page or an infographic. It's not enough.
It's not enough. One last question that I'll hit and then we'll wrap is because I think it's a good one. Question from James in the chat, you guys have talked a lot about your data either pushing or pulling from Salesforce. Do you have one unified data model that you maintain and that all the agents access in Salesforce or do you have multiple data models supporting different agents depending on the roles that Jason outlined? So I'll give you my answer and then we can get your take on this, Jason, is we do have one data model that we push back or pull from Salesforce most of the time. Again, these agents collect too much data. Like, once you start to have multiple agents as well, I think what you'll start to find is it's too much data. It's too much data for humans to act on. It's too much data for agents to act on. Like, sometimes too much is too Much like we have purposefully told our Salesforce and our agents to only ingest certain things so that it's not like, because, like it literally knows when you're on the website with qualified. Like it knows what pages you looked at. Knows what pages you looked at on salesforce.com like it can pull that into a conversation that we have with you either for tickets or sponsorships or whatever it may be. Like it knows all that. And to some degree that is useful context. But some other things I don't really. Like it doesn't need to know. Like it doesn't need to know that Bobby used to work at your company and he came to Saster five years ago, but now Bobby's left. Like, does that really matter? It's a new sale basically at that point. So that's too much context. Like there is such a thing as, I think just too much slash irrelevant context that you can get into trouble with once you have all these agents producing so much output. Right. There's so much they could in theory tell each other. But I think you have to make the decision of what do they actually need to serve your outcome, whether that's closing the deal, buying it, whatever it is, you know, retention as a customer. Like they may not need to know all that. Like some of that might be too much for them as a human to process on the other end of it. Oh, you're muted, Jason.
Yeah, for sure. I mean, certainly cell sources are source of truth, right? For, for, for these apps. Yeah. You will quickly discover it's true with everything in AI is you need a certain amount of data for it to be great. Right. And then, but then any more than that is too much. It's also like memory. Like you think you need to. Your memory to have everything in ChatGPT or Cloud. It turns out it doesn't. Right. We probably need more memory than both of them have on the consumer apps. But you only need so much for your campaigns, your support to be great. Right. So you'll learn, you'll quickly have too much, too much data. The one thing I would just add, it's just interesting, it's minor is, you know, our, our source of truth used to be Marketo. Marketo is a very dated marketing application owned by Adobe. We shouldn't be on it. Even from the old days. We should have been on HubSpot or another solution. But we had someone that briefly worked on us that knew Marketo and brought it in and we're kind of stuck.
We.
We won't be stuck on it forever. But we've been stuck on it because it's highly segmented, has massive data, because that's not really an agentic product and because our agents don't really hook into it. I mean, Emilio, you're the boss. It is, it is dying as our source of truth and it is attributed to a very low end basic marketing automation tool that we could probably replace with anything off the shelf. Right. So because it used to have all our data, because it sent all the campaigns, it was better than Salesforce. But it is very interesting that the amount of data we have in Salesforce has probably gone up two orders of magnitude and our marketing automation solution has died because of it. For us.
Yep. Yeah. It's literally to the point where like I think our renewal for Marketo in particular is like right after disaster. And I was like, I probably don't need it. Like, honestly, like it's. To your point, it does nothing. And to our 9010 rule last week I'm like, it's, it's terrible for what it is. Like it's. Yeah, I agree with you. I stayed on it for so long only because I had so much of our data for the past 10 years. But now I'm like, actually any of the good tools can just ingest that in like a day. Like and then to my point, it doesn't need all that. Like it only needs a few things that you've probably recently done. It doesn't need all historics for 10 years. Like for the founders who are part of Sasser. Like those people haven't moved on but a lot of the GTM folks have moved companies probably five times by now in the last eight years. And like we have all that history in Marketo. Do I need that? No, I just probably I just need their most recent thing that they've done with us to give that context back to them when we want to pitch them for something it's asked or like I just actually don't even need all that data anymore so it's become less useful to us. Like I don't.
And I guess as we would leave we, we will probably when we have, if we have the time after SAS annual in May, we'll probably find a marketing an agentic next generation market anonymous tool that integrates just well with Salesforce, just the data in Salesforce and takes our data from Salesforce agentically and creates campaigns. Right. And if we can find someone do that. Forget about Marketo. I don't think we'd want HubSpot either. Unless HubSpot does it. We don't need these dated marketing automation platforms because Salesforce has been re energized as our. I don't, I mean you, you can find your own source of truth. It could be in Snowflake or databricks or on your C drive now with openclaw or whatever you want, but it will become our super hub because it is our source. It is our, it is our. It is our data lake and source of truth. Right. It could be your others, but we don't need three. We don't need market. We don't need a Mark, a Marketo and a HubSpot source the truth. And granted, HubSpot does integrate sales and marketing, but we wouldn't. For years we wanted to move our marketing automation from Marketo to HubSpot because it was more modern for years. But we would never do that today because it's not enough.
Right.
But it won't be our source of truth for marketing. Like we don't, we don't need that to be a source of truth. We need something that can agentically send emails and maybe a few texts from our Salesforce data. So that'll be a fun journey to be on the back half of the year. We'll do it all together.
Yeah, we'll do it together. Okay. I think that's. I know there's other questions in the chat. We'll do this. We're trying to do these every other week so you can send it to me in the meantime and we'll answer it next time. In the meantime we are, I would, I don't know, something like 70ish days away from SAS, Randall, so. Well, hopefully see you guys there. I'd be remiss if I didn't tell you that ticket prices go up on Saturday because Saturday is the last day of the month. So get your ticks now before they jump up because why not do that and take advantage of that. We will talk a lot more about our agents there. We've got some of the best of breed AI native apps coming. Their CEOs are coming this week. So it'll be a lot we're doing.
They'll have everyone there to teach you how to do this stuff too.
Yes. For real.
I love the CEOs of Replit and Lovable and the CEO of Vercel and all these great people and you know, CTO of databricks. It's all great. But we'll have people hands on showing you how to do these agents answering your questions. You can, you can pepper them until they fall, fall down exhausted because that, in fact, our whole first day is deploy. And it's, I mean, it'll be all the. But the whole point of the first day is to help you deploy these agents yourself if you haven't, or to fix your issues. That's the whole point. So it'll be great. See you guys in.
We'll go deeper there. And then. Yeah, we'll see you on here next time. And thanks, everybody, for joining.
