The transformation is always the same: from founder-dependent to institution-run.
Every engagement, regardless of industry, ends with the same thing true of the business that wasn't true going in — it runs on systems, not on one person holding it together in their head.

Three commitments that don't change by industry.
Built personally, three times
Three departments, three industries, from zero. The case studies below show the actual departments running, in detail.
See it built: national partner networkThe documentation is the deliverable
SOPs, Business Process Frameworks, and Segregation of Duties documentation get filed with the business — and stay there after I leave.
See it documented: franchise investment architectureBuilt to run without me watching it
I build the tooling most infrastructure consultants stop short of, and I've run a department, which most AI consultants haven't. That combination is what makes the systems rigorous enough to trust and automated enough that nobody has to chase them.
See it running: the KPI and AI layerOne capability, compounding across four stages.
Understanding people
8 years — Hospitality
I spent eight years in hospitality, where I learned that service businesses run on how people behave under pressure — guest experience, staff performance, consistency at scale. That's where I first understood what makes people reliable when things get busy.
Understanding scale
6 years — Telecom
Telecom is where the same instinct had to become a system. Managing large teams across a state meant I couldn't rely on instinct alone — I built performance governance, daily review rhythms, and accountability structures instead. I also helped transform traditional service centres into next-generation ones, and built the partner ecosystem around them — proof the same thinking worked a second time, in a second industry.
Building infrastructure
4 years — Building Materials
At AIS Windows, I joined a department that didn't exist yet. There was nothing to optimise — only to build. Every SOP, every governance document, every review forum came from zero. That's infrastructure built to outlast whoever's running it, including me.
Extending into AI systems
Ongoing
Once that department could run on its own, I pointed the same instinct at software. The result reads the same governed numbers I already trust and drafts a short brief before a review starts — it interprets, it doesn't decide, and I check it before anyone acts on it. This is a direction I'm extending into, not yet the main occupation.
If the business still depends on you being in the room, that's usually the conversation worth having.
Currently accepting a limited number of advisory engagements.
Start a conversation