I've spent 20 years building software and watching where it breaks.
These days, I help companies avoid the same mistakes,or at least make new ones that are cheaper and faster to recover from.
Most technical problems aren't technical. They just pretend to be.
I've worked across startups, scale-ups, and enterprise environments,retail, construction, FTSE 100,building teams from scratch, migrating legacy systems to modern architectures, delivering enterprise client solutions, and getting companies through ISO 27001 certification and acquisition due diligence.
That includes delivery issues, unclear ownership, stakeholder chaos, fragile systems, rushed architecture, and the slow creep of technical debt that everyone knows is there but nobody quite wants to touch.
Ten years as a developer. Ten years as team lead, architect, and CTO. That split matters,I understand the technical reality and the business pressure, and I've spent long enough in both to know which one is usually causing the problem.
What I care about
Clear thinking, honest trade-offs, and building systems that actually hold up under real use.
What I don't do
Buzzword-heavy strategy, performative transformation, or pretending everything is fine when it clearly isn't.
How I work
Direct, pragmatic, and focused on outcomes. I'll tell you what I think, and I'll help you fix it.
I've spent the last few years deep in AI-assisted and agentic development workflows,not just experimenting, but figuring out how these tools actually fit into real delivery environments.
The gap between what AI can do in a demo and what it can do reliably in production is still wide. Bridging that gap is where most of the interesting work is right now.
I was running early TensorFlow image classification experiments before most teams had decided whether machine learning was worth taking seriously. Since then I've delivered an industry-first AI tool and run webinars helping other teams navigate adoption. I know what real progress looks like,and what's just demo confidence.
AI won't fix a broken delivery process. It will just help you break things faster.
If any of this sounds familiar, we should talk.
No pitch decks required. Just a conversation about what's actually going on.