I built the delivery side because advice that stops at the recommendation is half a job.
A career of walking into underperforming technology functions, written down and made repeatable.
Free, 30 minutes, no obligation.


I spent a career on the other side of the table.
VP inside a bank. Executive Partner at an industry research firm, advising CIOs. Interim CTO on the operations board of a group, and interim and fractional CTO engagements since.
The job was the same every time: walk into an underperforming technology function and turn it into an asset. Often enough that the sequence stopped being intuition and started being something I could write down.
The recommendation was never the hard part.
Advisory work has a structural problem. You diagnose the thing, you write the recommendation, and then you hand it to whoever has to build it — and from that moment the quality of the outcome has nothing to do with you.
So I built the delivery side. The method is how a recommendation becomes a working system without losing anything in the handoff. The automation is how one person carries that without a delivery team behind them.
Four things I won't do.
Who decides usually depends on the role I'm in.
Built with the method: Sourcier
A data-quality and automation product for recruitment agencies running Bullhorn — the method's own proving ground, run as a client of itself. Pre-launch, currently invite-only.
Start with the design. Stop after it if you want.
The first engagement is a small, fixed-price piece of work whose output is the design itself: your process in your own language, the riskiest assumption tested, and a priced, generated proposal for the build. You own everything it produces.
Thirty minutes first, no slides. If it's advice you need, we talk about the decision in front of you. If it's a build, by the end you'll have the name of the process worth measuring first.
Free, 30 minutes, no obligation.