Case Studies
Selected engagements.
Work where the outcome was the point. The problem, the approach, and what measurably changed.
- Build
A clinical SaaS provider in ophthalmic surgery
- Problem
- The calculation engine ran only on local machines, and had never been built to be deployed as a web application. Surgeons could see individual cases, but not the averaged outcomes across all of their own. A vendor deadline twelve weeks out committed the company to delivering exactly that, on the web.
- Approach
- Took over the existing codebase, made it fit to deploy as a web application, and built the outcome analysis on top of it.
- Outcome
- Shipped inside the twelve-week deadline. Outcomes across a surgeon’s whole case history could be analysed and optimised for the first time in the industry, and the system has since analysed hundreds of thousands of procedures.
- Respond
A B2B SaaS provider
- Problem
- An attacker had compromised the shared hosting estate behind more than a hundred customer-facing sites, including the systems the business ran on. Uptime and revenue were both taking damage for as long as it continued.
- Approach
- Contained the compromise, rebuilt and restored the business-critical systems, then hardened the estate against the route that had been used.
- Outcome
- Business-critical systems were back inside three days, and the hardening has held — no recurrence since.
Tell us what you are building, or what you are worried about.
One email gets you a scoping call with the person who will do the work. No discovery questionnaire, no account executive.