What we build, and what it has to survive.

01 — Healthcare

Clinical operations

In production

Software for the operational work around care rather than the medical record itself: referral and dispatch, procedure documentation, clinician credentialing and competency, facility reporting, and the reconciliation between what was performed and what was invoiced.

The requirements here are not cosmetic. Access is enforced per role at the database, so a permission cannot be lost by rendering the wrong screen. Every read and write of patient data is recorded. Exports are checked against their source before they leave the system, and an export that cannot be reconciled says so on its face instead of presenting a total that quietly disagrees with the invoice beside it.

Our healthcare platform runs in production today, including an external portal through which facilities pull their own records under their own logins.

02 — Business

Operations platforms

Available to scope

The systems a company genuinely runs on, which tend to be the ones no vendor sells well: intake and dispatch, contractor payroll, renewals and expiry tracking, document retention, and the monthly reconciliation between what was delivered and what was billed.

These usually exist already — as a spreadsheet, a shared inbox and one person who knows how it works. We build against that real process rather than asking you to adopt someone else's, and we integrate with the accounting system you already keep the books in instead of replacing it.

03 — Personal

Smaller tools, same standard

Available to scope

Focused software for a single job — tracking, records, reporting — where the off-the-shelf option would mean giving up the part that made the thing worth doing in the first place.

A small scope is not a reason for a weak data model, an unversioned schema or no backup. The engineering is the same; there is simply less of it.