Case Studies
Go directly to the system, the operating constraint, and what the available evidence can support.
Every record starts with a question.
Each one below opens with the question the client actually had, then shows the system we built around it and the point where a person still decides.
A dental practice wanted recurring payments on lower-cost ACH without adding a second reconciliation job at the front desk. We built a posting path around the existing ledger instead of a migration project. The cloud service carries opaque payment information and nothing else. Patient matching, posting, and exception detail stay on the clinic workstation. An ambiguous match or a reversal stops and waits for staff. A posting completes only after Dentrix read-back confirms the expected ledger state. The system is deployed and running in production at the clinic.
What happens when an input is missing?An orthodontic clinic builds the same patient presentation for every case, from an intake PDF, clinical photos, and a template that keeps changing. We built a local-first pipeline that reads the active template, maps extracted values and photo views into explicit slots, and returns a deterministic deck with an error report and an audit. Missing inputs surface as warnings instead of invented clinical content. The operator confirms patient identity, reads the warnings, and decides whether the deck is ready. Working files are wiped after delivery. This record makes no outcome claim.
How do teams use AI without giving up the decision?A semi-private airline asked how its teams could use AI inside work they already owned. We paired useful tools with guidance, guardrails, and human verification, so the people doing the work kept responsibility for reviewing it and making the final decision. The engagement is confidential. The client stays anonymous and the operational details stay withheld, so this record carries the principle rather than the implementation: AI should support responsibility rather than blur it.
We publish what the record supports.
These pages are implementation records. Each one names what was built, which controls hold, where a person decides, and how far the evidence reaches. Deployment status is stated plainly: the dental system is deployed and running in production, and the presentation system is published as a build record with no adoption claim. None of the three quantifies hours or dollars saved. A savings number with no measurement behind it is marketing, so we leave it out and say why.
Show us where the work gets stuck.
Start with the process, cost, delay, or failure state. We will tell you what kind of system the evidence supports.