The Zero100 Podcast

The episode delivers substantive, non-obvious ideas about AI ROI measurement that challenge conventional wisdom - avoiding premature headcount cuts, moving beyond FTE reduction templates, redesigning workflows end-to-end rather than bolting on solutions, and distinguishing between quick wins and strategic momentum. Most claims are grounded in field research and client work rather than generic platitudes, though some sections drift into confirmatory elaboration rather than introducing fresh tensions.

“if you take a broken workflow, weak data, and muddy decision rights, and then drop AI on top, you're not going to get any meaningful transformation. You're to get a more expensive version of the same dysfunction”

“The real winners, they're not just automating a task, they're redesigning that workflow around the task”

The framing of AI as general-purpose technology (vs. standard IT project) and the emphasis on end-to-end workflow redesign rather than isolated use cases represent genuinely contrarian takes in a sea of 'AI pilot' content. However, the distinction between labor savings and throughput/quality gains, while useful, is increasingly circulating in practitioner communities. The scorecard evolution framework feels somewhat derivative of broader supply chain maturity models.

“are we making a fundamental mistake by treating AI like a standard IT project that has to pay for itself immediately, rather than a general purpose technology like the steam engine or like electricity?”

“stop forcing every AI use case into an FTE reduction template”

Both speakers are legitimate supply chain research/advisory leaders with field credibility - Garant John holds a VP Research title and references prior software vendor experience, while Justin Gilbeau is positioned as Senior Director and speaks from direct client engagements. However, neither is a sitting operator who has personally executed at scale (e.g., a CPO or supply chain SVP running these transformations). They're analysts synthesizing best practices rather than practitioners proving concepts in production.

“I've led planning teams in the past”

“one of our industrial manufacturing members has saved over $300 million in nine months”

The episode anchors claims in named examples: Uber's token budget burn, Klarna/IBM/Forge premature layoffs, food & beverage company's 5% and 3% savings, Walmart's 3% tail spend savings, industrial manufacturer's $300M in 9 months, specific metrics (300,000 hours annually, 45 minutes per day saved, 80% speedup, 90% effort reduction). Metrics are concrete (decision latency, % low-value work automated, % administrative vs. value-added time). Some sections lack specifics (e.g., 'mature operators managing like utilities' lacks company names), but the ratio of concrete to abstract is high.

“one leading food and beverage company says its AI initiative has generated over 100 million euros in cost savings, around 10 million euros in free cash flow”

“one of our industrial manufacturing members has saved over $300 million in nine months by using AI to mine commodity cost supplier, ah, forecasted demand data”

The host (Cody Stack) asks sharp, probing questions and listens for nuance - e.g., drilling into the difference between faith-based and real ROI, pushing on the tail spend distraction risk, asking about the flip side (where AI fails). However, few genuine follow-ups challenge or complicate guest answers; the host mostly validates and transitions smoothly. There's minimal productive tension or disagreement. The conversation flows logically but remains largely confirmatory rather than exploratory or adversarial.

“But is there a danger that obsessing over tailspend and intake traps companies in minor savings while bigger structural opportunities go untucked?”

“Let's talk about the flip side. Where are you both seeing companies fall into the hype trap right now?”