Twenty years of web applications, integrations and infrastructure. I do not build websites. I build the software that runs in the background, talks to the rest of your systems and keeps things moving.
By day I run ZiiX, which makes workshop software for the European market. Alongside that I take on freelance work where twenty years of systems experience actually makes a difference.
It is rarely the code that is the problem. Usually nobody has worked out what actually needed solving. I spent the last ten years as head of development and CTO sitting between the business and the engineering, and the rest of my career building the thing myself.
So I can have the conversation about what a problem costs you every month, and then write the code that removes it. There is no link in the middle getting it translated wrong along the way.
I am sharpest in a fairly narrow field. Both lists are here so you can tell quickly whether we are a fit.
The work looks different every time, but the pattern is the same. There is something the business depends on, and it needs to be built, connected or automated by someone who has done it before.
The systems that replace spreadsheets, mail threads and manual lists. Built for the way you actually work, rather than a standard process you have to be squeezed into.
The biggest gain usually comes from making the systems you already have talk to each other. I have been connecting ERP, finance, identity and industry services for over ten years.
Numbers you can actually decide on. I take it from the data foundation and modelling all the way out to the screens management really looks at.
If a task gets done by hand every week, it is usually worth automating. I find them, do the maths on them and build them away.
Code that cannot be deployed is not finished. I set up environments, pipelines and monitoring, and I am happy to take on operations if you would rather not.
Sometimes the job is not to build, but to work out what should be built. I have led development teams for ten years and am comfortable sitting on your side of the table.
We start with the problem, not the solution. What is it costing you today, and what specifically has to be different afterwards?
You get a written proposal with scope, architecture and price. Then you know what you are getting, and what sits outside it.
Small deliveries you can see and use along the way. The code sits in your own repository from day one.
Handover with documentation so you can carry on yourselves. Or an agreement that I stay and look after it.
Workshop software for the European market
Plant identification with an honest, botanical answer
BI platform, internal systems and integrations in a nationwide workshop chain
Write a few lines about what you are dealing with. I will come back with what I think, including if the answer is that someone else would do it better.