About
Built around the chart and the ledger, not the booking calendar
Medical spas are run on booking software with a clinical record bolted on the side. That is why the compliance problem and the margin problem are both invisible until after the fact.
What we decided at the start
One patient record. One set of books. Every treatment given draws down a real lot at a real cost, and every dollar taken posts to an append-only ledger that has to balance.
Compliance is not a report you run at the end of the quarter. It is a set of rules, stored as data, that stop a clinician signing a note the practice would not want to defend. A medical director can waive one, in writing, with their name on it.
Nothing about a patient leaves the record. No identifier reaches an address bar, a log line, an error message, or a language model. That is a design constraint we enforce in code, not a policy in a document.
- Who it is for
- Owners, medical directors, injectors on a tablet, and the front desk.
- Where it runs
- In the browser on a laptop, tablet or phone. Nothing to install.
- Multi-location
- Each location has its own timezone, rooms, hours and stock; the books stay together.
- Roles, not logins shared
- Every read and write re-checks the person's role against their membership.
We are happy to show you the whole thing
A walkthrough runs on a demo organisation with synthetic records—never real patient data.