How we got here
Garman Technology was started by Ben Garman, an engineer who still writes code every week. The early work was for product companies: the software inside and around physical products, and the systems that sold and supported them. That is where the habit of taking responsibility for the whole estate comes from: when the device, the app and the back office all have to work together, one team has to understand all of it.
Over time the business software became the centre of the work, and most of the companies we work with today trust us with their platforms, portals, integrations and the running of them.
We have stayed deliberately small: a senior team, UK-based, with the people you meet in the first conversation still on the project years later.
We run on software we built
Everything that runs Garman Technology, from customers and projects to time, files, credentials and billing, is a system we designed and built for ourselves, deployed the same way we deploy for clients. We live with the consequences of our own decisions every day.
- Customers, projects and the people on them, with access that follows project membership
- Time recorded against projects and priced into monthly timesheets and invoices
- Tasks, files and a shared drive that mounts in Windows Explorer
- A self-hosted credential vault whose access mirrors the project team
- Billing through QuickBooks, so what we invoice is what we recorded
- Built with .NET and Angular, deployed to AWS from a CloudFormation stack that builds itself from nothing




