Selected work
Six systems, and the numbers they moved
Every figure here was measured against a baseline established before the work started. Where a project failed to hit its target, the case study says so.
- Case studies
- 6
- Sectors
- 6
- Still in production
- All of them
- Earliest
- 2024
What clients say
The quotes we are proudest of are the uncomfortable ones
The evaluation harness was the part we did not know we needed. It turned an argument about whether the model was good enough into a number we check every week.
They talked us out of the redesign we asked for and into the rebuild we needed. The invoice was the same either way, which is how I knew the advice was honest.
We spent two years arguing about whose number was right. It took six weeks to discover we were both right and neither of us had written the rule down.
Two vendors before them told us the audit trail could come later. That answer is why they were previous vendors.
In week one they told us our deadline was not real. Nobody had said that out loud in four months of internal planning, and the project succeeded because someone finally did.
The handover was the most thorough I have seen. My team had shipped three changes on their own before the engagement formally ended.
Next step
Tell us what you are building.
A system you want built, a model that has to survive real traffic, or a process that should have been automated a year ago. The first conversation costs nothing, and occasionally ends with us telling you not to build it.
Reply within one working day
A person, not an autoresponder.
A 30-minute call, no deck
We ask about constraints, not budget.
A written view within a week
Including the case for not proceeding.