about
Full-Stack Web Application Developer & Software Founder

I build the operational software businesses run on: CRM and case-management systems, education and learning platforms, multi-branch retail and point of sale, payments, and the automation that removes the manual steps between them.
The work I take on tends to have three things in common. It holds real money or real people's data, so correctness matters more than novelty. It is used every working day, so it has to be deployed without downtime and maintained for years. And it is rarely a blank page — most of it means understanding a business that already works, in spreadsheets and inboxes, and building the system that finally fits it.
I work end to end: data model, backend, interface, deployment and the ongoing changes afterwards. On most of the projects in my portfolio I am the only developer, which means the architecture has to be something a single person can still reason about a year later.
Before touching a system I read it: the data model, the deployment, what the last person was solving. Most bad changes come from confident assumptions about code nobody re-read.
A screen that looks right over a model that is wrong is a liability. I get the entities, the states and the money definitions right first; the interface follows from them.
A green local build is not evidence. I check the deployed thing — the page served, the row written, the email received — before saying a change is shipped.
The architecture has to still make sense after a year of changes made in a hurry. Invariants that matter get enforced by the database or by a test that fails the build, not by discipline.
Most of my projects are named in the case studies: an education operations platform handling student applications, agents and commission; a multi-branch retail platform with a storefront, point of sale and warehouse working from one catalogue; a CPD learning platform with secure lesson delivery and verifiable certificates; a property and investment CRM with its authorisation enforced in the database; and a case-management system for a regulated advisory practice, described without naming the client because of what it holds.
Two of those are sanitised on this site. That is deliberate: if a system holds sensitive data, the case study describes the engineering and leaves the client unnamed. I would rather lose the logo than be careless with it.
Before the application work there were marketing and brochure sites — they are listed in the archive at the bottom of the work page. They are where I learned to ship, and they are not what I do now.
Everything on this list is something I have shipped with and would be comfortable being questioned about in a call.
I founded AM IT Solution to build custom software for businesses whose operations have outgrown spreadsheets, disconnected tools and manual processes. It is UK-registered and bills in pounds, and it works with clients internationally.
This site is mine: my work, my writing, how I think about building systems. The company site is where the company sells. Keeping them separate is the point.
I am part of the Programming Hero developer community — alumni meetups and the HeroUnion gatherings, where a few hundred developers compare what they are building.



