RevOpsAF The Podcast

A handful of actionable concepts emerge (agent graveyard, hub-and-spoke governance, intentional friction in build requests, building agents where reps actually work) but they are surrounded by significant conversational padding, mutual self-congratulation, and restatements of the obvious. The density of novel ideas per minute is low.

“this concept I'm kind of calling the agent graveyard, where they go build a bunch of agents, throw it out to the field, but then no one owns them and manages them”

“strategically adding friction to a process can actually be very beneficial”

The 'agent graveyard' framing and the hub-and-spoke AI governance model with an embedded product manager are genuinely useful mental models, but most of the episode rehashes standard AI-adoption discourse (centralize vs decentralize, build vs buy, AI fluency concerns) without first-principles reasoning or contrarian takes.

“this concept I'm kind of calling the agent graveyard”

“someone that will sit on our kind of go to market or commercial operations team that will start to funnel requests and then they can build or they can throw to the central team to build, but they, like, are the gatekeepers”

Brandon Bussey is a legitimate practitioner - actual VP of RevOps at a 17-company PE roll-up with prior stints at Amazon, Qualtrics, and Lucid - who speaks from hands-on operator experience rather than thought-leadership posturing. However, the seniority ceiling and scale of impact are solidly mid-market, not exceptional.

“I was at Qualtrics Lucid Software and then did some consulting for a little bit”

“we're a private equity roll up. So we are right now the amalgamation of. We just did an acquisition. So I think we're at Ah, 17 companies”

The episode names concrete tools (Glyphic/Airspeed, Letter AI, Salesforce, Claude), references a third-party event with a named speaker (Kyle Norton, Owner's CRO, $2M - $100M growth), and gives a rough 70% figure for requests eliminated by friction. But the AI SDR failure story is conspicuously vague and most financial claims are illustrative rather than evidenced.

“Kyle Norton, the CRO over at Owner. And his whole session was around like how he approaches build versus Buy. And Owner has done something crazy like over a year, two years, has gone from like 2 million to $100 million”

“I don't know, 70% of the things I was going to ask for, like, we didn't build”

The host asks a few sharp structural questions (job title and reporting line, the centralized-vs-workflow contrast, surfacing failures) but consistently pivots to sharing his own lengthy opinions rather than pressing the guest, and never challenges an unchallenged claim or asks for harder evidence on weak assertions like the AI SDR story.

“What's the job title for that role and will they roll up to revenue operations into your team or somewhere else?”

“it's interesting because there's kind of a contrast between what we were talking about before...But then what we're talking about here, with how you implement it...is implemented in the tools or the systems or the places where people are already working”