In this short dialogue, Speaker A explains how AI‑driven Sales Development Representatives (SDRs) can reduce human bias in selecting event speakers and allocating slots, because the AI evaluates sessions purely on predefined criteria without personal relationships. The conversation then shifts to the practical architecture of a SaaS go‑to‑market engine, where multiple “sub‑agents” (AI tools) are employed. Speaker A cautions against proliferating too many core agents—suggesting that 20+ is excessive—but notes that SaaS communities often need several because they integrate with partner apps and sponsors. He illustrates a real‑world workflow that uses two AI SDR platforms: AgentForce for leads already in Salesforce (leveraging existing data) and Artisan/AISPR for warm follow‑ups on leads outside Salesforce. The discussion highlights trade‑offs such as platform cost, data movement, and the ability to split leads across agents, ultimately presenting a pragmatic, bias‑free, and cost‑aware approach to outbound funnel management.
Chapters
the AI is maybe— I don't want to say it's better at it. It's about as good as like the human agency was because I'm like, we put in the same context, right? We're like, hey, here's all the good sessions from SaaS. Here's all the bad ones. Here's what to look for. Here's what we don't want. And also we're limited on how many slots we have. And so because the AI is like less biased, sometimes it is like the grades it gives is like a little bit more fair than sometimes, you know, humans would be like, oh, This was my client or this was my friend. Like, can I get them on stage? Like, the AI agent does not care.
I love it. So these, the right side, I'm curious, like when you think about, do you think in the terms of jobs to be done or, 'cause like some of these could have some overlap. So how do you—
They do overlap.
Yeah. How, how do you think, like, do you narrow 'em down to silos or they overlap in certain ways that's strategic for SaaS or how do you make sure all these work together in, in like a function?
So I'll preface, like, I don't know that people truly need 20 subagents. I know, you know, I know, like, like, like, like, I know there's like the U.coms of the world where like you can build like a lot of subagents for like a lot of different things. And some people do. And like, they'll have agents for like things that I would consider more so of a Zap. Like, that's fine. And they call it an agent. So like, depending on how you define it too. But I still don't recommend 20 like core agents, like really doing your go-to-market it's, it's too many. But SaaS is unique in that, you know, we are a community. We, we, we do events, we have sponsors like Momentum, and we have other sponsors like Salesforce where like we do try and use the apps that our, you know, our partners have and that our sponsors have. And that's why we have so many. Like some of them do have direct overlap. But honestly, even though some of them have direct overlap, right, like AgentForce is an AI SDR. Artisans and AISPR. So we use both of them, but actually it's, it's fine from my perspective, like other than the cost of paying for two platforms, which most people don't want to do, right? Costs aside, I would say because my brain can like split how I'm putting leads to each of those different agents, to me, I don't— it like makes sense to say, okay, I'm going to use AgentForce for people I want to follow up with that are already in Salesforce because duh, they're already in Salesforce. And then like Artisan, I'm going to use more so for like warm follow-ups. I can show you my chart of like how I kind of think about this too. Yeah, let's see where that guy is. But yeah, I use it for like warm follow-ups. Yeah, let me go to this guy. So like this is my— this is like across my agents. This is like my outbound AISR funnel and this is just for outbound. This is not including inbound. But I like to show this to people because I'm like, some of these people are in Salesforce. Yes, some aren't. So like if they are in Salesforce, I'll use AgentForce for it because it's just easier. Like that data is already there. I don't have to move it.
