Client names are withheld
Nearly every engagement sits under a confidentiality agreement, so we describe the client by sector and scale instead. References can be arranged directly, with that client's agreement.
Selected work
What we have built, in the detail that matters.
Six systems, anonymised at the client's request. Each page covers the problem as it arrived, the architecture we shipped, and how the result was measured once it was running.
Case studies
Systems that went into production and stayed there.
Filter by the capability that did the work, or by the sector it landed in.
Showing 6 of 6 case studies
The portfolio in four numbers
6
Systems written up here
One page each, covering the architecture as it was built
4
Sectors represented
Retail, manufacturing, healthcare and logistics
40+
Retail sites counted daily
Footfall read from cameras those stores already owned
100%
Clients anonymised
Names and logos withheld under the agreements we signed
Honest reporting
How we report results.
A case study is a sales document. These ones are written so that an engineer on the client side would recognise the system described.
Mechanism, not uplift
The figures describe what each system does now: what it counts, how quickly it decides, and what it will not do without a person. We do not publish revenue impact or return multiples.
Numbers come from the system
Volumes, intervals, thresholds and gates are read from the running system or the project record. Where something was never measured, it is not on the page.
Tell us the work you want taken off the desk.
Bring the process, the constraints and the mess. We will say plainly whether a system is worth building, and what the first measurable version would cost.