Start Grow Manage

There are genuine, usable insights scattered through the episode - particularly the pivot from technical to business-focused alignment meetings, the robotic-cell solution for manufacturer labor retention, and the production-downtime cost framing - but they're buried under extended origin storytelling, audio-issue tangents, and the host re-summarising what guests just said.

“we went and did alignment meetings, technical alignment meetings, which if anybody's ever done done them, nobody enjoys them... we got an education when we started to take that more of a business approach”

“every shift that one of my production lines is down cost me $26,000 and they run two shifts across 36 lines”

The idea of an MSP proactively introducing robotic automation cells to solve a manufacturer's labour-retention problem is genuinely fresh and goes beyond the standard QBR-pivot narrative; the rest - culture, niching, asking why - is familiar MSP consulting doctrine recycled in conversational form.

“we realized that by getting some education on some of our vendors, robotic vendors that deal with the manufacturers, we can solve some labor problems”

“There's rarely a right and wrong choice. Usually the better bad choice”

Stu and Mike are genuine long-tenure operators (22+ years, survived the 2008 crash) with real client stories and hard-won business lessons, making them credible practitioners rather than thought-leader tourists; however they operate at modest scale and one guest's audio issues meaningfully reduce his contribution to the episode.

“when the economy shifted in late 2008, we had, I think we lost $300,000 worth of projects that were scheduled for the last quarter. They just went away”

“I left there and went into consulting, which gave me better options to grow and develop. And I left consulting and opened my own company because I was uncomfortable with what my employers were asking me to do”

The episode contains several concrete, named data points (the $26k-per-shift-per-line downtime figure, the $300k Q4 2008 revenue loss, the 36-line/2-shift/3-site plant, the $200k project unlocking $800k revenue) that give real weight to the arguments; however much of the culture and hiring discussion stays abstract and unsubstantiated.

“do you know that every shift that one of my production lines is down cost me $26,000 and they run two shifts across 36 lines”

“I think we lost $300,000 worth of projects that were scheduled for the last quarter”

The host asks reasonable contextual follow-ups (e.g., 'So what did you, how would you express that change?') and surfaces useful transitions, but rarely challenges an assertion, frequently re-states the guest's point back to them as a question, and loses material interview time to audio troubleshooting and jokey asides.

“So what did you, how would you express that change?”

“It's almost like it, it really is a calling. It's like you had an injury that Caused you to go to this. And then. And the, the way that you retrained your brain was through technology. That's crazy.”