Capabilities
Four domains that reinforce each other.
Deliberately narrow. Each of these exists because the others need it — automation needs infrastructure, AI needs a product around it, and none of it matters without something someone can actually use.
Software Development
Building the actual product — interfaces people use without being taught how, on top of code that stays readable six months later.
Automation
Finding the repetitive step inside a real workflow and removing it — usually the highest-value thing software can do for a business.
Artificial Intelligence
Applying models where they genuinely beat conventional code, and being honest about where they do not.
Technology Infrastructure
The foundation underneath the product: how it ships, where it runs, and what happens when something breaks.
Method
Technology is only valuable when it removes a real problem.
Most software fails long before the code does — it fails at the point where someone decided what to build. So the work starts in the workflow, not in the editor.
01
Understand the problem
Sit with the process as it actually runs, not as it is described in a document.
02
Analyse the workflow
Find where the time goes, where errors enter, and which constraints are non-negotiable.
03
Design the right solution
Choose the smallest thing that removes the problem — including deciding not to build.
04
Build and test
Ship something real quickly, then put it in front of the people who have to live with it.
05
Improve on results
Watch how it is actually used and refine. The first version is a hypothesis.
Have a problem worth solving?
Tell me what the process looks like today and where it breaks. If technology is the right answer, I will tell you what I would build — and if it is not, I will tell you that too.