Brief · 2026 · Product, research and engineering

Clarity

A bespoke finance ledger for a dental clinic, replacing a 16-month Excel workflow. 897 records came across from the spreadsheet, and it is now being rebuilt around a second user who must never see a rupee figure.

Problem: Sixteen months of clinic finances in a cash receipt log with no patient in it, so it structurally could not answer who still owed money.
User: A dentist I know, running one small clinic, entering transactions between patients. The rebuild adds his attendant, who must never see a figure.
Decision: The model narrates and typed code computes. A numeral it cannot trace back to a source does not reach the screen.
Number: 100 of 100 eval cases pass, and the build fails if they stop. The first run scored 86 and caught a real defect. The tone judge is deliberately left non-blocking.
Refused: The tone scorer never gates a release, the payment QR automation stays unbuilt, and the keyboard shortcuts he told me he does not use are coming back out.

100-caseeval suite, fails the build
86/100first run, caught a real defect

Open Clarity

The full case study is about 10 minutes on how it was decided, measured, and where it can still fool me.