Small Business Big AI

The episode delivers practical, actionable insights about AI deployment focused on workflow automation rather than generic tool adoption. The law firm example with specific numbers ($300-350K savings on $10-12K investment) is concrete. However, the conversation includes significant filler (extended introductions, self-promotion, obvious platitudes like "don't be scared") that dilutes the density. The core insight - identify staff pain points and automate them rather than buying tools - is sound but not particularly novel for operators already thinking operationally.

“what is the next evolution of using AI in your business to really think about optimizing or automating a business process or a workflow”

“they were probably spending collectively as a paralegal team 25 to 50 hours a week inside this system doing manual stuff”

The framework (identify repetitive work → automate it → free staff for higher-value work) is logical but well-trodden in AI/automation discourse. The emphasis on asking "what does your team hate" instead of "what can AI do" is a useful reframing, but the underlying logic is standard workflow optimization theory. The guest's methodological approach (crawl, walk, run) lacks fresh thinking. No contrarian or first-principles arguments emerge; this is by-the-book execution thinking.

“If AI can write the email, then why is your team still doing the same repetitive job every single week by hand?”

“the gap is really knowing what to point it at”

Brandon Herder brings legitimate practitioner credibility: 30 years in B2B tech, CMO of an edtech startup where he deployed AI at scale, founder of Pivot180AI with real clients. He speaks from lived experience of building workflows, not theory. However, his company is only 6-7 months old (as of the episode), so track record is limited. He's relevant and senior enough, but still relatively early in this particular venture, which slightly limits caliber.

“I've been in business since January 5, 2026. So I'm only six to seven months into this”

“most recently as the chief marketing officer of an edtech startup where he watched AI move from an idea and a slide deck to something deployed at real scale”

The law firm case study provides strong specifics: 8 paralegals, 25-50 hours/week spent manually, $100/hour billing rates, $10-12K development cost, $300-350K annual savings, specific workflows (client onboarding communications, proof-of-validation document review). The landscaping example is descriptive but less quantified. The framework questions are named but not deeply exemplified across verticals. More vertical examples with numbers would strengthen this further.

“they were probably spending collectively as a paralegal team 25 to 50 hours a week inside this system doing manual stuff”

“my first client was a local law firm here in Raleigh, North Carolina”

The hosts ask reasonable setup questions (e.g., "what was broken, what did you do, what changed, give me a number") that prompt Brandon to deliver the law firm case study. However, follow-ups are largely soft and affirming rather than probing. The hosts rarely challenge assumptions, ask about failure modes, or push back on claims. When Brandon mentions buying tools without understanding workflows, the hosts nod rather than press on why this happens or dig into real obstacles. The conversation reads more as guided storytelling than sharp interrogation.

“I want you to be honest with them. I want you to think about one client that you had or have. What was the thing that was broken and what did you actually do?”

“So you ask, what is one thing that your staff hates to do?”