The Tech Marketing Podcast

There are a handful of genuinely useful practitioner ideas (email-to-deal-reg, meeting assist, embedding AI at every PRM touchpoint, converting time-saved to dollar values for ROI), but they are buried under substantial filler, mutual affirmation, and high-level statements that most channel ops professionals would already know. The ratio of novel ideas to padding is mediocre.

“we also thinking about email to deal Reg. Like just imagine the partner doesn't even have to come into the portal. Simply send an email, agent creates it.”

“I really focus on KPI's metrics first. I won't start anything until I have the proper KPI metrics. Because once you build something you still have to report out metrics on it.”

The core arguments - partners are overwhelmed, AI should be embedded throughout PRM, data quality is prerequisite for AI, deal reg is broken - are widely circulated complaints in channel circles. The email-to-deal-reg framing is a modest fresh angle, but the overall thinking stays within conventional wisdom and does not challenge any dominant assumptions.

“we try and build a lot of capabilities for our, for our partners and we, um, m overly stimulate them”

“you have got to have AI in this PRM tool. Like, every single element of this has to have an AI touch point.”

Divya is a genuine 15-year channel practitioner who has actually built a PRM from scratch at ServiceNow and dog-fooded Now Assist for partner use - real operator credibility. However she is a Senior Director rather than a C-suite leader, and the conversation stays closer to process storytelling than hard-won strategic insight.

“I have been able to build our own PRM from ground up”

“I've done operations, I've done programs, I've done, um, everything around, uh, analytics and insights, and then was really asked to lead this digital transformation kind of organization”

There are some named tools (Now Assist, Partner Finder, Perplexity), a rough automation estimate ('60 to 80% of the work'), and a credible methodology for converting hours-saved to dollar figures, but the episode lacks hard metrics, actual adoption numbers, revenue impact data, or real before/after comparisons - the numbers cited are estimates and proxies, not reported outcomes.

“AI is able to take that 80, 60%, so 60 to 80% of the work that they're doing and automate through an agent”

“let's say we're going to save them an hour a day. You take that hour a day and, and take the, the amount of money they would make that hour a day and you're able to actually rationalize into dollars saved”

The hosts know the domain and occasionally land decent follow-ups (pressing on KPI methodology, asking what 'AI embedded everywhere' concretely means), but the conversation is dominated by validation, affirmation, and leading questions that telegraph the expected answer - there is no pushback or productive tension anywhere in the episode.

“you've hit all the nails on the head there”

“I knew that was going to be your answer. I kind of, I, I set you up there.”