Detailed case studies are in development. We're being deliberate about what we publish — anonymizing where required, getting client approval, and writing in enough depth that they're genuinely useful, not promotional.
Most consulting firms' case studies read like sales brochures. We're aiming for something different — case studies that are useful to practitioners, not just impressive to procurement.
Each one will cover: the actual technical problem, the architecture decisions we made and why, what we'd do differently in hindsight, and measurable outcomes. Wherever possible, with client permission, named. Where confidentiality requires it, thoroughly anonymized.
We'd rather publish three detailed, useful studies per year than twelve generic ones. The first will go live as soon as we have approval to share it properly.
A preview of the case studies in development. Subjects, not specifics — names and details will appear when published.
How a regional specialty care provider replaced fragmented patient flow tracking with a unified analytics platform. Covers integration across EHR systems, the metrics that mattered most to clinical operations, and how leadership now spots capacity bottlenecks weeks earlier than before.
A common starting point made into a documented journey. How we replaced an ecosystem of fragile Excel reports with a Power BI semantic model that operations teams can self-serve from. Includes data lineage decisions and DAX patterns that scaled.
An honest study of a project where we recommended against the AI solution the client originally wanted — and built a simpler, cheaper, more maintainable alternative instead. The case for restraint in AI consulting.
They're written for marketing, not learning. Generic wins, vague metrics, vendor logos. They tell you nothing about how the work actually got done.
We're trying to write case studies the way good engineering teams write post-mortems — with specificity about what we built, why we built it that way, what worked, what didn't, and what we learned. Useful to read whether or not you ever hire us.
That takes time and care. But it's the only kind of content worth publishing.
We often find the most interesting projects start with a conversation about a specific operational pain. Tell us yours.
Start a conversation