Technology advice and delivery, for businesses and their investors.
Senior technology judgement when you need a decision, and a builder when you need the thing built. You can hire one without the other.
Free, 30 minutes, no obligation.

It usually starts with a question nobody inside can answer.
Whether the drag is a technology problem or a process one. What the process everyone complains about is actually costing. Whether the technology in a business you're about to buy is an asset or a liability. Each has a different first step, and the first conversation is about which one is yours.
IF YOU'RE THE OWNER OR MD
You can see the drag. You can't see whether it's a technology problem or a process one, and there's no CTO to ask.
IF YOU'RE THE COO OR OPERATIONS DIRECTOR
You already know which process is costing you. You need the number before you need the tool.
IF YOU'RE AN INVESTOR OR PORTFOLIO OPERATOR
You need someone to read the whole estate rather than sample it, and tell you what it costs to fix.
IF YOU'RE THE IT DIRECTOR OR HEAD OF IT
You know what needs doing. You need a second senior opinion on a big decision, or a build your team can't fit in.
Advice on the technology.
The build, if it's worth building.
Fractional and interim CTO
A seat on your leadership team for as long as the decision needs one. The judgement about what to change, and the standing to make it stick.
Technology due diligence
For investors and portfolio operators. I automate the analysis, so the review covers more of what you're buying. I don't automate the judgement.
Internal apps and platforms
The system your business needs and can't buy. Your rules, your data, your workflow, running on infrastructure you host.
AI automations and integrations
The information already exists somewhere in your business. I stop your people being the thing that moves it.
The design, first
A small, fixed-price piece of work: your process in your own words, the riskiest assumption tested, and a priced plan for the build. Stop there if you want.
The industry sells AI models. The model was never the expensive part.
The hard part of operational AI is everything around the model: assembling the data, understanding the process, knowing where each value came from and who checks it. Once you understand a process and stage the data, doing the thing is the easy part.
So I put the work where projects actually fail, and treat the model as what it is: a component.
I spent my 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. The job was the same every time: walk into an underperforming technology function and turn it into an asset.
That's the part an automation agency can't sell you. Deciding what to build — and what to refuse to build — is worth more than knowing how to build it.
An automation firm will build exactly what you ask for. That's the problem.
Software does the routine delivery work, so the build is quicker and costs less. A person makes every decision that matters: no agent can sign a contract, take on a client or close a project.
Eight stages. Each ends when a named artefact exists — or it hasn't ended.
There's no separate progress status to maintain. The artefact either exists or it doesn't.
0 Bootstrap
An empty project, ready to work in.
1 Discover
Your process in your own words, its rules written down, and how it performs today.
2 Prove
A small test of the riskiest assumption, and what it found.
3 Specify
Everything to be built, each with what "done" means.
4 Propose
A fixed price and a written scope.
5 Build
The working system, on infrastructure you host.
6 Handover
Runbooks, every decision written down, and training.
7 Measure
What changed, measured the same way as at the start.
I won't hold your system hostage.
Or leave you one you can't look after.
Some firms keep you dependent and charge rent. Others hand over everything and leave, with code nobody in the building understands. You own what's built outright, and the handover includes what your team needs to run it: runbooks, the decisions written down, and training.
You may run, host, modify, fork, transfer, or engage any third party to maintain or develop what you receive — without permission and without further payment. That's a warranted term, not a promise in a slide.
Before handover, automated checks confirm your system doesn't depend on any tool of mine. If a check finds something, the handover waits until it's fixed.
I don't make extravagant claims.
I work with facts.
If I can't show you the evidence, I won't claim it. That goes for this page too.
It's time to experiment.
Not to bet the business.
Nobody can promise what AI will do for your business before trying it, me included. So don't make the big bet first. Pick one process, write down what you expect to change, and test it in a small, cheap proof of concept. If it works, you have the numbers to build on. If it doesn't, you've lost weeks, not a year.
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.