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

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

Justin designs and deploys automation inside live, 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 actually flows.

Justin approaches operations the way product teams approach software.

Instead of treating workflows as static infrastructure, he treats them as versioned systems. V1 is not the final state. It is a hypothesis. You design it, ship it, measure it, and then deliberately evolve 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 itself, clarified ownership, reduced hidden handoffs, and versioned the process. The result was a measurable improvement in throughput and reliability without adding complexity.

Coming from a product and design background, Justin now applies product iteration principles directly to internal systems. The core idea is simple but powerful. Operations are not back-office admin. They are products. And if you do not version and evolve them intentionally, they will decay.

This conversation 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 lives. That gap is where expensive platforms go to die.

In his podcast episode, Justin shares what actually happens during discovery work. The duplicated steps. The manual approvals are no questions. The reporting rituals exist only because no one redesigned them. Before you layer AI on top, you need to understand how work truly moves across teams.

The provocative take is this. AI does not fix broken systems. It accelerates them. If your process is fragmented, AI will simply make the fragmentation faster and more expensive.

This conversation cuts through hype and positions Justin as a pragmatic operator who starts with workflow design, not flashy tooling. It offers podcast audiences a refreshing perspective amid the noise, and it opens up real conversations about how to unlock performance without chasing trends.