Projects, with the numbers attached
Three engagements we're allowed to talk about, described the way we'd describe them to another engineer — including what was actually hard.
A twelve-year-old dispatch system, replaced without stopping the trucks
The problem. Every quote went through a desktop application that only ran on Windows 7 machines in one building. Nobody dared change it. Growth was capped by the number of people who could sit at those desks.
What we did. A strangler-fig migration: we put an API in front of the legacy database, moved one workflow at a time to a new web platform, and ran both systems side by side until the old one had nothing left to do. Fourteen months, no cutover weekend.
Meridian Logistics · Outcomes
A patient app that stopped crashing and started retaining
The problem. A React Native app with a 2.8-star rating, a 9% crash rate and a release process that took three days of manual regression testing before anyone would press the button.
What we did. We rebuilt the data layer around offline-first sync, moved the two most fragile screens to native Swift and Kotlin, and built an Appium suite covering the twelve journeys that mattered. Releases went from three days to forty minutes.
Kestrel Health · Outcomes
40,000 automated tests, and a Friday deploy that nobody dreads
The problem. A regulated lending platform with 200 engineers, a four-hour test suite that failed randomly, and a release calendar that had shrunk to once a month because nobody trusted the pipeline.
What we did. We triaged the flaky tests ruthlessly, deleted the ones testing nothing, parallelised the rest across ephemeral environments, and added contract testing between the twelve services that kept breaking each other.
Northfold Financial · Outcomes
Your project could be the fourth one on this page
Tell us what you're building and we'll tell you honestly whether we're the right people for it.