Why TunTech exists.

The story

I've spent 30+ years inside cloud and technology consulting firms — and I've seen the work from every angle. I started as a developer, writing code and watching projects from the inside. From there I moved into project management — earning my PMP along the way — then program management, and eventually spent about a decade as a process and portfolio consultant — helping consulting firms diagnose what was breaking in how they delivered work. Later in my career I held PMO leadership and VP of Delivery Operations roles, where I built delivery organizations and ran them at scale.

That arc matters because TunTech isn't built on a single role or a textbook framework. It's built on having lived the work at every level — from the consultant who's frustrated by a broken handoff, to the PM trying to recover a slipping project, to the VP staring at the utilization report wondering where the margin went. The patterns that repeat across cloud and technology consulting firms aren't theory to me. I've watched them play out, lived through them, and helped firms fix them.

TunTech exists because most consulting firms don't know what's wrong with their delivery operation until a client walks — or a project blows up. The Operational Performance Diagnostic, the ADAPT framework, and the TOP platform are all built from three decades of those patterns — formalized into a diagnostic that surfaces what's breaking, quantifies what it's costing, and produces a roadmap leadership can actually act on.

If you run a cloud or technology consulting firm and you're feeling delivery friction, margin pressure, or scaling pain— this is what TunTech was built for.