SaaS Stories

There are a handful of useful observations buried in roughly 47 minutes - the junior-hire-and-train strategy, the university coding camps, and AI-agent reducing customer service load - but the majority of the episode is filler, meandering anecdotes, and obvious observations about technology disruption that offer nothing a B2B operator hasn't already heard.

“I think with the with the custom build, often if you do it right, you can you can make the users the stakeholders because they're building it”

“I think they told us it was like an 83% improvement on on or what they were able to do”

The episode recycles well-worn takes - 'every business will need technology,' 'AI isn't ready for serious development,' 'human connection still matters' - without any genuinely contrarian or first-principles argument. The one mildly original moment is the pre-App Store preparation tactic, but it's brief and not developed into a broader framework.

“Before the iPhone, uh before the app store even opened, I said, build a couple apps. I want to submit them because I know I'm gonna get a phone call”

“technology will always be there, and everybody will need to use technology and it will accelerate at an even greater pace”

Froehlich is a genuine practitioner - 20+ years running a custom software firm with international offices and a long client roster - which gives his observations credibility. However, he doesn't speak with authority about scale metrics (no revenue, no headcount), and a portion of the episode is consumed by the host sharing their own parallel experiences rather than drawing out the guest's depth.

“we have offices in in um one, two, three, four offices overseas in in different countries”

“most of our people um have been here 10 plus years, or at least most of the people”

The episode has pockets of concrete specificity - named client Sports Thread, the 83% customer-service improvement metric, 5% camp acceptance rate with 25 candidates and 1-2 hires, Newport Beach and Tampa offices - but lacks the revenue figures, deal sizes, or timeline data that would make these examples truly instructive for an operator benchmarking their own situation.

“It's it's sports thread, it's a youth, a youth sports um uh SaaS product”

“we'd only like five percent of them we would allow, and then we'd have about 25 people, and the senior people would run these camps”

The host asks structurally decent questions (pivot story, hardest client problem, hiring philosophy) but consistently responds with agreement and personal anecdotes rather than following up or pushing on interesting threads; the result is two people validating each other rather than a probing interview that extracts depth from the guest.

“I love that you said that because uh we do exactly the same thing, but we didn't always do it that way”

“What was the moment you realized technology, not concrete, was where you needed to be?”