KnowTechTalk

The episode offers almost nothing a B2B operator wouldn't already know about workflow automation; it stays firmly at the level of 'automation saves time and reduces errors' with no tactical depth, no architectural detail, and no meaningful framework a listener could act on. The bulk of the runtime is origin-story chat, consumer analogies, and the host's own anecdotes.

“it runs without needing humor interaction. That means it's always going to be error free”

“when you onboard and you offboard, you forget. like for a small business, adding them to payroll, adding them to benefits, you know, giving them insurance, giving them a desk”

Every conceptual frame used - bank tellers vs. ATMs, self-checkout, the industrial revolution - is a worn-out analogy for automation that has been recycled thousands of times. There is no contrarian argument, no first-principles reasoning, and no perspective that challenges conventional wisdom about MSP automation.

“I'll go back a step further, even the idea of the industrial revolution. And prior to that, people hand making things one by one and all of a sudden factories pop up”

“bank tellers went to bank machines. You still have a bank teller there”

George Smith is the Community Engagement Manager at Rewst - a community and marketing role, not a technical practitioner, operator, or founder who has built or scaled the thing being discussed. His background is explicitly sales and outdoor instruction, and his most substantive contribution is relaying a second-hand CRO analogy about orchestras.

“My name is George Smith. I am the Community Engagement Manager at Roost”

“I went to school for sports science and coaching. I spent a lot of my early 20s doing a variety of sales jobs, working bars, selling phones, being an outdoor instructor”

The sole concrete data point is an unnamed partner saving '$200,000 in six months,' which cannot be verified or contextualised. All other examples - onboarding, offboarding, password resets - are described in generic terms with no named companies, stack specifics, pricing, timelines, or measurable outcomes.

“just came through to us this week and just mentioned in the past six months they've saved at two hundred thousand dollars”

“we have a Discord community that's almost a thousand MSPs in there”

The host frequently redirects conversation to personal anecdotes (her own door-to-door flyer, grocery self-checkout preferences) rather than probing guest claims, and her questions are soft and leading with no pushback whatsoever. The closing question - asking for the most important career lesson - yields an unchallenged platitude with no follow-up.

“Is that making sense? Am I getting a good grip of it here?”

“Any success stories about Roost automation you can share with us?”