Our work
These are real pieces of work, described only as far as the public record allows. Client projects, earlier employment and independent products are marked so you can tell them apart. We have not invented results.
Client project SaaS · AI
A SaaS platform for finding and comparing managed service providers, with the search, data model and later AI-assisted matching built as the backend.
The problem Information from several sources had to become one model that could be searched and ranked, including a sentence turned into parameters the existing search already understood.
Read the case study
Client project Business software · Field work
A fire-door inspection system for engineers in the field, extended and turned into a progressive web app that still works when the building has no signal.
The problem Inspections happen where the signal often fails. The Laravel system already in use had to record a visit offline and synchronise later, without being replaced.
Read the case study
Client project Website
A WordPress website for a Bowen therapy practice, with the theme adjusted for the practice and the hosting looked after directly.
The problem A practice site needed to explain the work, look considered, and stay online without turning into a project of its own.
Read the case study
Earlier role Marketplace · Integrations
Seller product-import tooling for a UK online marketplace, built as part of the early engineering team in 2013 and 2014.
The problem Seller catalogues arrived in many shapes and had to become listings a customer could buy, inside a marketplace that was already live.
Read the case study
Earlier role SaaS · Modernisation
A collaboration platform used by companies internationally, rebuilt from an older PHP codebase onto Laravel, with a web front end and a mobile app.
The problem A monolithic CodeIgniter product had to keep serving customers while it moved onto Laravel, with a mobile client added and releases made repeatable.
Read the case study
Independent product Architecture · Real-time systems
An independent cross-platform game with a split backend, an API, background jobs and a real-time service. Included because of the architecture, and labelled as an independent product.
The problem Player actions, stored records, slow work and live updates needed separate processes that could stay in step: an API, a queue and a real-time service.
Read the case study