← Discovery hub

One operational layer. ~55 capabilities in nine families.

This is the system as it is actually built — your PMS on the left, the orchestrator in the middle, the nine families of engines it runs, and the two people it ever talks to. Watch a real event travel through it.

Enquiry→Book→Confirm→Attend→Follow-up→Recall→Reactivate — OakStone fills every gap in this loop
Flow 1 of 3 · step 1
Live · money core — the engines a pilot proves
Live — built & running
Built — compounding as data and the network grow
event going out
result coming back

It sits on top of your PMS. It does not replace it.

Dentally, SOE Exact and Open Dental stay the record of truth. OakStone watches what happens in them, acts on the gaps, and writes the result back — so your team keeps working the way they already do.

Every action is queued, idempotent and retried, and logged line by line against your own records. Nothing happens that you cannot go back and check.

Nine families, one layer — not nine tools.

Each family is a cluster of engines sharing the same orchestrator, the same patient inbox and the same audit trail. That is why the whole loop closes: a cancellation and a recall are the same kind of event to the system, just with different rules.

A pilot leads on B · Fill the diary — the money engines. The rest are built and compound as the data and the network grow.

Status (22 Sep 2026): every family is built and validated on synthetic data; the pilot turns that into real-patient proof. Honest rule — we never claim live proof we don't have.