A Slice of SaaS

A handful of genuinely useful operational ideas surface (the dedicated change-enablement role kept deliberately out of technical conversations, internal complexity leaking to customer experience) but they are buried under significant conversational filler, repetition, and generic management advice. The episode runs long relative to the net new ideas delivered.

“I intentionally keep that person, um, from those original technical conversations so that when that information is handed over to that person, they're looking at it from an outsider perspective”

“everything that you do internally in terms of complexity is felt by the customer”

The 'Intent Based RevOps' framework is essentially OKR thinking rebranded with a new label; the supporting ideas (five whys, Crucial Conversations, Lencioni's buy-in concept, Amazon's one-door/two-door) are all well-circulated frameworks that the guest acknowledges borrowing. Very little here challenges existing RevOps orthodoxy.

“I use the phrase write it in crayon all the time”

“there's a book that I love called Crucial Conversations”

Darren Fay is a working Senior Director of RevOps leading a 28-person team at an actual company, which gives his operational commentary credibility; he is a genuine practitioner rather than a career podcast guest. However, he is not a widely recognised figure and the episode does not surface the kind of hard-won insight that signals truly elite experience.

“I have a dedicated change management person that I've, um, put together. I'm calling it change enablement”

“in revenue operations, you know, you tend to get stuck in this rut of pleasing people and you want to like, please your stakeholders”

Almost no concrete numbers, metrics, timelines, or named case studies appear in the transcript; the guest names a few tools (One Source, Confluence, Sonar) and two books but offers no data on outcomes, no before/after figures, and no company-level examples beyond vague references to 'a previous company'. The episode is almost entirely conceptual.

“Right now we're using something called One Source. I've used something called Confluence in the past”

“I think Sonar has a, a product where you know, they look at uh, you know you can see the downstream implications of a change in salesforce”

The host is engaged and occasionally surfaces relevant sub-topics (discovery, diplomacy, cost of change) but rarely pushes back on vague claims, frequently agrees and adds his own anecdotes instead of pressing for depth, and closes with 'is there anything we missed?' - a hallmark of an underprepared exit. Questions tend to be leading or multi-part rather than sharp.

“is it the carrot? Is it a stick? Is it a combination?”

“I actually downloaded it today because I listened to another one of your podcasts”