How I work
three steps to independence
Most consultants sell you a dependency. I sell you the opposite — I find the root cause, fix it with your team, and leave. Here's the process.
I take on two engagements at a time. Not five. Not ten. Two. This means I'm expensive. It also means I actually finish.
The Process
The First Look
A free sample of certainty
You tell me what's not working. I tell you whether I think it's a symptom or a root cause — and if I can see the likely culprit, I'll name it on the call. After 30 minutes, you know more than after months of internal meetings. No pitch. No obligation.
- →You describe the pain — what's broken, what you've tried
- →I tell you if it's a symptom or the root cause
- →If I can see the likely culprit, I name it on the spot
- →No pitch, no obligation, no follow-up spam
The Diagnosis
The root cause, documented. Yours to keep.
I embed with your team, map the system, and find the root cause. You get a documented diagnosis: what's actually broken, why it's been breaking, and the exact plan to fix it. Knowing what's wrong IS the value. Some clients take this plan to their own team and never hire me for step three. That's fine — I sold certainty, not code.
- →Deep-dive into your architecture, processes, and team
- →Root cause identified and documented
- →Concrete fix plan with clear scope and timeline
- →You own the diagnosis — take it to your team or hire me for The Handover
The Handover
Break the cycle. Then leave.
I fix the root cause WITH your team. Not FOR them — WITH them. They learn why it broke, how it was fixed, and how to never make the same mistake again. When they own the UNDERSTANDING — not just the solution — I leave.
- →Root cause fixed at the source — permanently
- →Your team trained on the solution, not just handed it
- →AI-amplified engineering workflow transferred to your team
- →Documentation, tests, and operational metrics that prove it works
- →I leave when your team stops making the same mistakes
Every consultant you've hired before was incentivized to stay. I'm incentivized to leave. That's the difference.
The Fire-Me Promise
I don't sell retainers. I don't build dependency. If I haven't found your root cause and put you on a clear path to fixing it within 90 days, we have a problem. That's never happened.
My goal isn't to become your IT department. My goal is to make your team — or your lack of one — work so well that I become unnecessary. Then I move on.
This isn't a marketing line. It's what happened at HORNBACH. It's what happened at Rolls-Royce. It's the design.
What does The Handover look like?
It depends on your situation. Here are three common scenarios:
Your systems keep breaking
The same bug comes back every few months. You patch it, it quiets down, then it returns — because nobody found the root cause.
Root cause
The architecture makes the bug inevitable. Each patch is a bandage on a structural problem.
The Handover
I find the structural flaw, rebuild the broken component with your team, and leave them with a system where that class of bug can no longer occur.
You need technical leadership — but not permanently
You need a CTO or senior architect, but you don't need one forever. You need someone to set the direction, upskill the team, and leave.
Root cause
The team has capability but lacks direction. They need a framework, not a permanent boss.
The Handover
I embed as technical leader, set the architecture and operating model, train your team to own it, and transition out when they're ready.
You need a team that runs without you
You built some IT, it grew organically, and now it's a mess. You need someone to bring structure — then leave before they become a dependency.
Root cause
The system accreted through quick fixes. Each workaround made the next one harder.
The Handover
I map what exists, identify the structural debt, rebuild the foundation with your team, and teach them agentic AI workflows so they move 10x faster without me.