Most AI tools help individuals work faster, but very few solve the coordination problems that slow organisations down. Justin explains the critical difference between single-player AI (email, notes, scheduling) and multi-player AI that operates inside multi-department workflows.

He shows why injecting AI into real operational processes like intake, approvals, onboarding, hand-offs, and cross-team workflows is harder than most vendors admit, and how leaders should think about applying AI inside existing systems.

Justin designs and deploys automation inside multi-team operational environments, giving him a first-hand view of what works and what breaks when AI meets real business processes.

Behind most scaling companies are dozens of fragile spreadsheets quietly running core operations. Justin breaks down why spreadsheets persist even in modern tech stacks, and why replacing them with single tools or custom software usually fails.

He shares a practical, step-by-step approach for migrating spreadsheet-driven workflows into orchestrated systems that connect existing tools and teams without large rebuilds or massive change programmes.

Justin’s work focuses specifically on replacing spreadsheet-driven operations across Ops, RevOps, and customer teams using connected, tool-agnostic workflow design.

Most companies treat operations like a series of urgent fixes. Something breaks, they patch it. Growth creates friction; they add another tool or another person. Six months later, the system is bloated, brittle, and no one really understands how work flows.

Justin approaches operations the way product teams approach software. Rather than treating workflows as static infrastructure, he treats them as versioned systems. V1 is not the final state. It is a hypothesis. He designs, ships, and measures it, then evolves it into V2 and V3 as the business grows.

In this episode, Justin shares a real client example of a fast-growing B2B team whose onboarding process looked “fine” on paper but was quietly collapsing under manual coordination and Slack chaos.

Rather than rip and replace their tools, Justin redesigned the workflow, clarified ownership, reduced hidden handoffs, and versioned the process. The result was a measurable improvement in throughput and reliability without adding complexity.

Justin applies his background in product and design to iteration principles for internal systems. The core idea is simple but powerful: Operations are not back-office admin; they are systems to be versioned and evolved intentionally, or they will decay.

He reframes operations from maintenance work to a strategic design discipline that compounds over time.

Every leadership team right now is being sold AI as the answer. The assumption is that productivity gaps are technology gaps. Justin argues that most companies do not have an AI problem. They have a process problem.

Leadership believes they understand how work flows through the organisation. The people doing the work know where the real friction lies. That gap is where expensive platforms go to die.

Justin shares what really happens during discovery work: the duplicated steps, the manual approvals with no questions, and the reporting rituals that exist only because no one redesigned them.

Before you layer AI on top, you need to understand how work truly moves across teams. His provocative take: AI does not fix broken systems; it accelerates them. If your process is fragmented, AI will simply make the fragmentation faster and more expensive.

Justin is a pragmatic operator who starts with workflow design, not flashy tooling. He offers podcast audiences a refreshing perspective amid the noise and opens up real conversations about how to unlock performance without chasing trends.