The challenge
The clinical knowledge was real and valuable, but it was spread across Word documents, Excel workbooks and a Microsoft Access database, plus folders of photographs. Keeping it consistent meant editing the same fact in several places, and none of it could be handed to another clinician as a finished product.
What we built
Desktop app
A Windows app with its own database, per-device license keys and signed installers.
Website
The same interface as a read-only web demo, for showing prospective clients.
Printed book
A clinician's reference generated from the website's data, in three print-ready versions.
How it fits together
Nothing downstream is edited by hand. A change goes into the source data once, and each product is regenerated from it.
- SourceClinical data tables
- BuildsApp database
- ExportsWebsite data
- GeneratesPrint book
How we built it
Most of the code was written with Claude and Codex, with us directing and reviewing every change. That's how one small team delivered an app, a website and a book together. The part that took experience was everything around the code: sorting out which of the practitioner's notes were right, designing one source for all three products, and checking each output against the original references.
The result
- 162
- muscles, each with a consistent ID across app, site and book
- 3
- products generated from one source
- 1
- place to make a correction