AI Pathfinder for Private Equity Podcast

The episode contains several substantive ideas around AI's operational role (agentic workflows, churn models, pricing optimization) and genuine PE-relevant insights about exit prep as AI readiness. However, there is meaningful padding - generic discussion of culture, innovation incentives, and the 5-10% early adopter framework that circulates widely. The guest repeats points and avoids depth on harder questions (e.g., outcome-based pricing is acknowledged as unsolved but not explored rigorously).

“I think there are certain incentives that you can bring about across an organization that enable businesses to move faster. And I think it is all about culture because I think you do need everyone to come along the journey.”

“I think most leaders I see either have a good understanding of the opportunities within their organization so the opportunities in sales or the opportunity is in churn or the opportunities in pricing or they have a good understanding of the sources of insight that AI enables them to get hold of now.”

The framing of exit prep as AI readiness is useful and relatively fresh for PE. The specific insight about revenue stability driving valuation multiples (avoiding usage-based pricing models that hurt exit value) is solid and contrarian to typical SaaS orthodoxy. However, much of the episode retreads familiar ground: agentic vs. chatbot distinction, churn modeling, pricing optimization. The manufacturing example with component forecasting is concrete but not particularly novel.

“We're working with an organization at the moment who has a decent usage based pricing model. But that means that their revenue changes every month, every quarter, uh, and that means that their valuation multiple is going to be hampered because of the way their pricing and packaging is structured.”

“Dashboards are dead. Long live the dashboard.”

David Whitcomb is a legitimate practitioner with relevant experience: IBM data science background, consulting experience (implied at OCNC in PE diligence context), and founder of a service firm actively working with PE-backed businesses on data and AI. He speaks from actual project work, not theory. However, he is a service provider selling into PE, not a PE operator or portfolio company executive, which limits his caliber relative to someone who has actually scaled a PE-backed business through these workflows.

“I started very much as a data scientist data engineer with IBM. I then spent four or five years with ocnc, spending a lot of time around the private equity ecosystem, learning around diligence.”

“At DVS we kind of think of governance on two scales. For our own internal reporting everything is fully agentic.”

The episode includes concrete examples: a manufacturing company reducing order delays from 20% to 8%, a software business growing GRR by 6 percentage points, and specific tool integrations (HubSpot + Claude, Zapier workflows, Productive ERP). However, many claims lack specifics: which companies, which industries, what exact revenue impact, timelines are vague. The guest often speaks in generalities about 'organizations we work with' without naming them or providing dollar figures, margins, or detailed metrics.

“So this manufacturer used to have, I think it was kind of 20% of orders kind of delayed through the process due to you know, bottlenecks in production line downtime, etc. um, but through the pilots that we were working with them on we were able to get that down to 8%”

“We're working with an organization at the moment who has a decent usage based pricing model. But that means that their revenue changes every month, every quarter”

The host (Steve) asks reasonable setup questions and shows familiarity with the guest from prior conversations, creating good rapport. However, the questioning rarely pushes back or demands rigor. When the guest admits DVS hasn't solved outcome-based pricing, Steve doesn't press on why or what the blockers really are. Follow-ups are mostly 'tell me more about X' rather than 'that contradicts what you said earlier' or 'what happens if you're wrong.' The conversation reads more like a friendly conversation between collaborators than a critical interview.

“Is there an area that's um, being underestimated in terms of what the potential is right now do you think?”

“Um, and what has that ultimately led that manufacturer to achieve?”