Questions people ask

Because you deal with the person doing the work. No account managers, no messages lost between people, no juniors learning on your project. I take on a small number of clients at once, so your operation gets proper attention.

I don't publish prices because every operation is different. Each build is quoted on its scope: the Diagnostic sets out in writing what the work involves and what it costs, before you commit to anything.

I look at how your operation actually runs: the tools, the hand-offs and the manual steps. You get a written assessment of where it loses time and money, what each problem costs you each year, and a costed plan for fixing it. If you go ahead with the build, the Diagnostic fee is credited against it.

Yes, on a buyout: the code, accounts, IP and documentation are all yours, and support is optional. There is also a licence option with a lower upfront cost, where I keep the code and look after it for a monthly fee that includes support.

Nothing lives only in my head. Every system comes with documentation and a proper handover, so another engineer could pick it up. If something goes wrong, I fix it as quickly as I can, and a support plan keeps it looked after day to day.

Yes. Usually that's the point. Most operations need less software than they own, so I start by making what you already pay for work together before adding anything new.

No. Most of what I build is ordinary, reliable software and automation. I use AI only where it clearly helps, like answering routine questions or sorting incoming enquiries, and you decide what it can and can't do. Nothing goes into an AI tool without your agreement.

It depends on the project. The Diagnostic sets the timeline in writing before anything starts. You see progress on a staging link from week one.

Anywhere. I'm based in London and work remotely with companies around the world.