IoT & AI Leaders

The episode contains a handful of genuinely useful framings - 'foundation-first vs. tool-first,' the 'trust layer,' and the power-plant equipment AI hub - but these are interspersed with significant padding, repetition, and high-level generalities that a mid-level B2B operator would already know. The density of truly non-obvious claims per minute is low.

“The hard part is the trust. Hard part is asking really good questions like, can I trust the data? Can I trust who is accessing it? Can I trust the output? Can I explain how a decision was made?”

“most companies today are building unstable foundations and lot of assumptions... They are layering AI on top of fragmented data, legacy processes, disconnected systems, and really with unclear governance”

The core thesis - slow down, fix governance before you deploy AI - is sound but far from novel; it recycles standard enterprise consulting advice that has circulated for years. The observation that AI can audit its own code for bugs is one mildly counterintuitive moment; otherwise the episode stays firmly in well-trodden territory.

“The question is, it's not about how do I deploy AI. The first question should be how do I prepare my environment to support AI?”

“AI is really good at finding bugs. So it's kind of, it's very ironic that it, that it, um, in its mission to accomplish the work, it takes a lot of shortcuts. But then when you turn that lens around and tell it to go examine its own work, it can find all the mistakes”

Both guests are genuine practitioners - a 20-year-old services firm CEO and a senior director with real client engagements in energy, healthcare, and manufacturing - not pure thought leaders. However, they are mid-market consultants rather than operators who have scaled AI inside a large enterprise themselves, limiting the ceiling of their authority.

“we help a number of power plants, whether they are renewable, fossil, hydro gas, natural gas in the US here”

“I've been with proarch um, over nine years now, uh, mostly in consulting capacities. My current role really is around helping clients modernize their environments”

There are a handful of concrete vignettes - the power-plant equipment AI hub, the hospital patient-tracking Bluetooth sensor deployment, the oil-platform '8 million measurements' figure - but client names are withheld, the savings claim ('six figures easily') is vague, and most assertions are left un-quantified and un-attributed.

“detecting these anomalies early on could save like six figures easily or more easily”

“he said that something like 8 million things get measured on an oil platform at sea”

The host is clearly knowledgeable - he draws useful analogies (MRP/ERP, Cisco services) and occasionally circles back to earlier points - but he talks excessively about his own experience, asks heavily leading questions, and rarely presses guests to quantify or substantiate claims, resulting in a collegial but under-challenged conversation.

“I wanted to pick up on that. Um, I made a note to come back to that. You said that Santosh earlier a few minutes ago, the trust layer, the truth layer, um, uh, you've described it in various forms. Is that a sort of process governance policy that a company needs to implement or is it also enabled by technology?”

“I can imagine that you guys, uh, this is my assumption on your business. I have a services background. I run a large part of Cisco Services business globally.”