Services
When the verdict is build, or when you already know what you need, I design the system and write the software myself. The person who sat in your operation is the person who builds for it.
Most software is built at a distance. An agency translates you to a project manager, who translates you to developers, who never meet you. Every translation loses something, and what arrives at the end fits the documents rather than the business.
I work without the layers. You deal with me. I spent ten years building systems for banks, lenders and retailers, the kind of software that makes lending decisions and cannot be allowed to fail quietly. Ten years of that teaches you something unfashionable: writing the code is the easy part. The hard part is building the right thing at the right size, then staying until it earns its keep.
It also keeps the price honest. A team of five has to build something big enough to justify a team of five. One senior person, building exactly what the assessment scoped, has no such incentive — and nothing gets lost between the person who understood your business and the person writing the software, because they are the same person.
The first working version arrives early — weeks, not months — and it is small on purpose. It does one thing your business needs, end to end, and real people use it while the rest is still being built. Every build after that point is guided by what those people say and do, not by what a planning document guessed months earlier.
When the system is complete, it is not finished — it is watched. I stay through the first ordinary weeks of use: the busy Friday, the staff member who was never in the demos, the awkward question no one predicted. When the system has survived your ordinary life rather than my careful tests, the engagement ends, and you keep everything: the software, the source code, and documentation your next engineer can pick up cold.
The technical history is public, and it is written for engineers. If you are one, or you employ one, they are welcome to inspect it: the case studies and the writing. You will never need any of it to work with me.
Every build is scoped and priced as a fixed piece of work before it begins, sized by what the feasibility assessment found. Builds usually start with the assessment, from €9,500, because it is the cheapest mistake-prevention either of us can buy. If you already know precisely what you need, we can begin with a conversation about scope instead.
Yes. Some clients need a fractional artificial intelligence architect: a senior technical mind a few days a month, steering the work of an existing team, reviewing designs and keeping a build honest. That arrangement is priced and scoped the same way as a build — fixed and agreed in advance.
Every build is priced as a fixed piece of work before it begins, sized by what the feasibility assessment found. There is no day rate ticking over and no meter running; you know the full cost before you commit.
Most systems I build are running in a client's ordinary week within a few months. I have taken a working assistant from first line of code to daily use by hundreds of people in three weeks; a larger platform takes longer. The honest schedule is part of the scope we agree up front.
You do. The system, the source code and the documentation are yours, and I stay long enough to hand them over cleanly — to your own people if you have them, or running quietly on services you control if you do not.
Write to me about what you run and what needs building.
Start a conversation