AI tools

“If you have an elite mid-market and enterprise seller, they will have so much more leverage with all of these tools that the competitive dynamic will say, but it was only that seller was worth 350 K to me before, but now look at what they're going to produce. …”

“I think I see this mistake where you have RevOps people investigating tools and then applying them, but then there's no thought of, okay, how does this get to a rep? How do they follow up? How does the manager then look at what's going on?”

“We have a mindset that's like, there are probably great tools in the world. We should start with those tools and implement them in our own workflows, as opposed to try to build them ourselves right now.”

“Honestly, you could pick a slightly worse tool, but if you invest the time and effort, it's going to be dramatically better than what you have today. Right. The key is investing in the orchestration and the QA.”

“What we haven't seen working well is really to go out and ask everyone on your team. To tell everyone to go out and test new things, it really creates a lot of unnecessary deprecation of efforts and also chaos, you know, as well.”

“Like, I think in trying to save money, you're actually spending a lot more time than you normally would just deploying these and getting the outputs of AI by doing these 10 different betas. I was like, just pick one, and if you feel like the cost It's prohibit…”

“And I think a lot of folks I talked to, too, more common, you probably do too, Jason, just say they're not going to add headcount so that they can empower their teams, either Q four, 25 or Q one, 26 with these tools. Like they're just, again, reallocating budg…”

“Some of these tools are, like, you know, 40 to a hundred K a year-ish, but we replace headcount.”

“None of the AI tools we use today, which are all great, but none of them can really use AI to auto segment in a way that can deliver these results.”

“If you build a 60% solution. No, one's going to pay for it.”