Consulting & mentoring
I help technology leaders and their teams to put AI to work across the engineering process, make their operations agentic, and ship quality software, backed by proven engineering practices.
Engineers trained in disciplined, test-first AI-assisted development
Years coaching engineering teams on TDD, BDD, and continuous delivery
Books published on testing and AI-assisted development
Published papers, including peer-reviewed research on agentic refactoring
Ways to work together
Pick whichever matches where your team is right now.
01
For CXOs, founders, and heads of engineering
Where AI actually fits in your business, what to build and what to buy, and which workflows are worth making agentic first. I still build and ship AI products myself, so the advice comes from inside the work rather than from a deck.
02
For teams shipping to production
Working with your team on how they build — TDD, BDD, clean code, continuous delivery — and fixing the problem rather than the symptom. These practices matter more now as AI is writing most of the code, not less.
03
For engineering leaders and senior engineers
Regular sessions to unblock your teams and think through the calls you’re not sure about. Bring whatever is actually bothering you — an agent that keeps going sideways, a roadmap you want a second opinion on, a team that has quietly stopped reviewing what the model writes.
04
For product and engineering teams
A few days with your engineers, working in your own codebase instead of a demo project. They leave knowing how to test and review AI-written code — the way I wrote it up in Test-First Copilot, taught to real teams since.
Who this is for
If you recognise yourself in more than one of these, we should talk.
You are trying to work out where AI actually belongs in your business, and what is worth building versus buying
Your team ships to production every week, and you want AI in that process without quality quietly slipping
You are the one making the AI calls for your teams, and you would rather talk them through with someone who has made them before
You are rolling out Copilot, Claude Code, or Cursor and want it to stick beyond the first month
You have a large legacy codebase and a nervous feeling about pointing AI at it
How we would work
A few people using AI well is not the same as your company getting better at it. Here is how we close that gap.
01
A free fitment call where we map your AI goals, your current stack, how your teams work today, and what you are actually worried about. If I am not the right person, I will tell you.
02
We pick one team and one real piece of work — small enough to move quickly, real enough that the result means something. We agree upfront what better looks like and how we will know.
03
What worked in the pilot becomes training, working agreements, patterns, and guardrails for the wider organisation, including the engineering practices that make the AI part safe.
04
We look at what actually changed in your delivery and your code quality, correct what drifted, and hand the practice to your own people so it does not depend on me being in the room.
Track record
The AI part is recent. The engineering part is not.
Book a free fitment call. We’ll go through where you are with AI, what your engineering practices look like underneath it, and whether I’m the right person to help you.
Book a free fitment call