RevAmp by DealHub.io

The episode surfaces a couple of genuinely useful framings - RevOps as a 'story problem not a tech problem' and AI's indifference to silos potentially forcing cross-functional unity - but spends most of its runtime on broadly familiar territory (RevOps wants to be strategic but gets stuck as a cleanup crew) without going deep on any single idea. Too much conversational meandering dilutes the useful content.

“The problem with RevOps is they not really have a tech problem. It's a story problem.”

“AI doesn't understand silos. It's not built that way and it's not political because it's not a person. It's an interface, it's a system. That learns. So now suddenly humans kind of almost have to unite to create processes that AI will understand.”

There is one genuinely contrarian take - that the GTM engineer framing adds complexity rather than solving anything and is a symptom of RevOps never being allowed to own its role - but the broader thesis (RevOps should be strategic, AI is an opportunity) is a well-worn conversation in this space. The 'naming, framing and claiming' point is borrowed category-design language rather than a fresh argument.

“go to market is not an engineer's role... the very framing of the fact that you need a go to market engineer in my opinion adds another level of complexity to an already complex problem”

“RevOps is not directly connected to a core metric that the business owns. Marketing is sales is CS is. Right. But RevOps isn't.”

Karthi Ratnam is a legitimate community builder and movement-marketing practitioner with real operational experience at RevGenius, but she is not a RevOps practitioner who has architected a revenue engine at scale - she is commenting on RevOps from the outside as a community founder and marketer, which limits the depth of first-hand insight available.

“I started off as like a tech writer because I'm fascinated, I've always been fascinated to bridge the gap between what's technical and marketing”

“I started working at GT Partners. I was heading there, go to market and that's where I met Jared and we both had passion for similar things.”

Concrete evidence is almost entirely absent: no named companies beyond a glancing mention of 'Gains' (Gainsight), no metrics, no timelines, no dollar figures, and the most promising specific material - confessions from an actual RevOps survey - is explicitly withheld. The episode is almost purely conceptual.

“I think one group that did it really well is customer success... that kind of movement was driven a little bit by a SaaS company, like Gains”

“Well, no, um, because it's. I can't. But if you joined us next week at a roundtable, you can hear all about it.”

The host shows some craft - he surfaces the GTM engineer controversy as a productive disagreement prompt and presses on the confessions with a direct follow-up - but he frequently validates rather than challenges ('That's a really good question'), lets conceptual claims pass unchallenged, and the episode closes on a product plug (the movement kit) without any real scrutiny.

“Are you able to give us any examples of some of those confessions?”

“I would argue that Chief Revenue Officer has suffered from this as well because it really in essence often becomes just the executive name for head of sales”