Next in Commerce by Netguru

The episode surfaces some genuinely useful process-automation sequencing logic (data structuration first, then decision-support, then execution automation) and the 'organizational immune system' framing for change resistance is handy shorthand, but large swaths of runtime are consumed by pleasantries, hedging, and meta-conversation with no informational payload. The promised 'measurable business outcomes' of the title never materialise as actual measurements.

“the pattern that we follow is always there are different processes that we can automate. I like to think about what is the outcome that is going to deliver. Uh, for the business, first processes that we automate, that we automate are the ones that are about preparing information”

“In every company there's kind of an organizational immune system as I like to call it. And this is about resistance to change”

The frameworks on offer - lean startup MVP validation, bottom-up change management, 'find your lighthouse project' - are well-worn consulting and innovation-management staples. The Einstein problem-definition quote and the generic 'curiosity and continuous learning' leadership advice are pervasive in business content. The 'sparring agent' use case is mildly interesting but handled superficially.

“Albert Einstein used to say that 50% of a problem resolution is defining a good problem”

“I believe Eric Ruiz was here, uh, so this is I think a good quote for him. But uh, this is needed more than ever. First of all, question, is this really a problem for your customer?”

Rodrigo is a genuine in-house practitioner at a large industrial company actually deploying automation, which is more credible than a consultant or vendor. However, he is a mid-level programme manager, not a C-suite executive or recognised domain authority, and his anecdotes stay at a fairly abstract level that limits the value of his seniority signal.

“I work on improving end to end processes, uh especially the ones that are across supply chain management”

“My background is not technical at all. But I needed to learn all these skills to convince, uh, a large organization that it's worth the investment”

Despite a title promising 'measurable business outcomes,' the episode contains zero metrics, no timelines, no named tools beyond generic acronyms (BPA, BPAs), and no quantified results. Use cases are described only in categorical terms ('customer emails,' 'PDF conversion,' 'sales approval agent') with no data anchoring how much time, money, or error rate changed as a result.

“One specific example, you can convert PDFs to something that is much more readable than a structured or for a robot”

“our customers are sending us emails every day, are sending us reports, uh, from where are we performing well and what are not performing are getting us surveys”

The host asks reasonable thematic questions and makes one good pivot toward concrete examples ('Let's get concrete now'), but consistently accepts vague or restated answers without pressing for numbers, named tools, or outcomes. Apologetic interjections ('I think I sort of broke your train of thought') and unchallenged platitudes dominate the second half; the quick-fire close adds no new substance.

“Let's get concrete now. So time for actual um, optimizations that you yourself have witnessed or driven. Uh, basically, uh, give us some processes”

“Sort of a roasting agent.”