Growth Elevated Leadership Podcast

There is a genuinely useful core story about using Claude Code to automate enterprise SaaS implementation configuration, and the observation about agentic coding being uniquely verifiable is non-obvious. However, the episode is padded with lengthy tangents (Italian vacation, Scottish polling-place anecdote, snow-hill college story) that dilute the substantive content across 37 minutes.

“the thing that I love, I believe that when it's all said and done, agentic coding is probably going to be one of the very few killer apps that is left. And the reason for that is there's a forcing function where the LLM generates a bunch of stuff and you have no idea if it's true or not, if it works or not, but you can execute it with code”

“I was actually had the opportunity to to meet up on a customer one of the very first customers that went through this process and it's a far cry from we've all done a sass implementation we've all seen the spreadsheets of doom”

The argument that code execution acts as a unique grounding mechanism for LLM outputs - making agentic coding distinctly more trustworthy than prose generation - is a genuinely fresh framing. Beyond that, the advice largely recycles standard startup wisdom (experiment, start small, get your hands dirty) without contrarian or first-principles depth.

“I can't go out and check if the summary of Tolstoy is accurate or captures the sentiment exactly, but I can with code, right? And it either works or it doesn't”

“you and I have been in tech companies for a long time. We've spent tens of millions of dollars paying people to write code that we've never read. But we go out there and we execute it and we do the demo”

Peebles is a legitimate technical practitioner - a CS-trained founder who personally built the automation he describes rather than delegating or theorising about it - which lends real credibility. He is not a celebrity or career podcast guest, though his company and profile are relatively modest in scale.

“it was about half an hour, 45 minutes. It almost one-shotted it”

“myself and the product manager, we're still the owners of this. That's pretty cool. You know, he spends probably a couple hours a week on it. And I spend 15, 30 minutes a week on it”

The episode offers useful specifics - named tools (Claude Code, Gong, Notion, YAML, Anthropic API), a concrete timeline ('less than 40 hours'), and a named customer use-case (Roche blood-analyzer training) - but stops short of quantified before/after metrics, cost savings, or deal-level revenue data that would elevate it further.

“we built a little script that sucked out all the calls from Gong, all the transcripts, boiled them down, and then basically went through and shoved them into a handover document framework”

“they've bought this piece of the platform and it's contract page four, line 32”

The host steers the narrative competently and occasionally lands a useful reframe (e.g. the Lego-set analogy for configurability), but he never challenges a claim, never asks for hard numbers on time or cost saved, and consistently affirms rather than probes - making this a friendly guided tour rather than a rigorous interview.

“Sounds like a perfect example to try to try to automate or do something with ai because time consuming a little complex annual yeah important repetitive and and growing”

“It seems like whenever you're involved in Scotland somewhat, the weather is beautiful outside. So when you visit, it's beautiful. Today is a beautiful day. I thought it was just always beautiful. Is that the case?”