SERVICES · DENTAL GROUPS AND DSOs
We interview your leadership, ingest what you already have, and build the structured knowledge layer that tells an AI how your group actually operates — then keep it true as the group changes.
Not a set of Markdown files — Markdown is only the storage format. You are buying three layers that stack, and only work together.
“Spring Lake has 8 operatories. Dr. Smith’s comp is 30% of adjusted production. Hygiene target is $1,800 a day.” The way the group actually runs, written down.
Accounting, practice management, payroll and banking, connected and reconciled against the same definitions the context layer uses.
“Why did Spring Lake EBITDA decline last month?” The model is no longer reading numbers — it knows how Spring Lake is supposed to operate.
A structured organizational knowledge system, written in the group’s own language and owned by the group.
That chain is the difference between a folder of documents and a system a model can reason across. It is also the part no export from your PMS or accounting stack can produce for you.
One implementation, then ongoing maintenance. Maggie and any software licensing sits separately on top.
$12,500 one time
Defensible range for a typical 5–10 location group: $10,000–$15,000.
$1,000 per month
Typical range $750–$1,500/month depending on locations and entities.
$0 self-serve
The seven-file starter, guided question by question, exported as a folder.
A group that changes providers, comp plans, budgets and locations every quarter has a context layer that decays. Maintenance is the difference between a foundation and a snapshot.
Most of the work is getting four people to agree on what a number means. The writing is the easy part.
Sessions with ownership, operations, finance and clinical leadership. We capture definitions, thresholds and who owns which number.
SOPs, comp agreements, budgets, chart of accounts, provider rosters, scheduling templates — folded into the structure rather than left in a drive.
The full file set is written and, more importantly, linked: every location resolves to providers, production, compensation and the statements they land in.
Leadership reads it back and corrects it. You own the folder. Maggie connects it to live operational and financial data.
Is this just documentation?
No. Documentation describes. This is structured so a model can traverse it — a location resolves to its providers, their compensation, the production that drives it and the line it lands on in the statements. That traversal is the product.
Why not have our team write it?
They can, and a guided interview walks them through the files. Most groups stall because the knowledge lives in four people’s heads and nobody owns reconciling their answers. That reconciliation is most of the engagement.
Do we need Maggie to get value?
No. The folder works next to any model. Maggie is what connects it to live accounting, practice-management, payroll and banking data so the answers reflect this month rather than the day it was written.
What if we have more than ten locations?
Pricing scales with the number of locations, entities and payroll models. Larger groups and multi-entity structures are quoted after a short scoping call.
See the difference before you buy anything.
The worked example on this site runs the same question twice against the same dental group data — once with context, once without.
Read the worked example