DSO
The same hierarchy, run at your scale.
Organisation, then clinics, then operatories — the structure a dental service organisation already runs on, and the one Leady is built on too. Licensing, booking and reporting all sit at the location and the chair, not at a single practice-wide setting that a group of this size would outgrow immediately.
What follows is what the software does today, at any number of locations — not a claim about who has already bought it at this scale.
What is true at DSO scale
- Licensing is per location, so a phased rollout — five sites this quarter, the rest next — never touches the sites already live, and never waits on the ones that are not.
- One hierarchy across the whole organisation: clinics, then operatories, with booking written at chair grain — the location and the operatory number — at every site.
- One admin view across every location: licences, phone numbers, call volume and billing, reported the same way at every clinic, not a login per address.
- Standardisation is a choice, not a limit: the approval dial — hold for front-desk approval, or book directly — is set per location, so a newly acquired practice can keep its own settings through a transition while the rest of the organisation runs one way.
- Double booking is refused by the database, per chair, per location, at every site in the organisation — an EXCLUDE constraint, not application logic that a busy day across dozens of chairs can race past.
- A Business Associate Agreement per entity, under one master agreement: no call for a location is answered before that location’s BAA is signed.
- Patient data belongs to the practice at each location. On request, we send a copy of that location’s data and delete ours.
What a DSO asks
- Can we roll this out in phases?
- Yes. Licensing is per location, so a phased rollout — five sites, then the rest — never touches the sites already running.
- One agreement, or one per clinic?
- One agreement covers the organisation. Each location still signs its own Business Associate Agreement, because that is what the patient data at that address requires — no call there is answered before it is signed.
- Does every site have to run the same way?
- Only if you want it to. The approval dial is per location, so you can standardise it across the organisation, or let a newly acquired practice keep its own settings while it transitions.
- What reporting do we get across the organisation?
- One admin view: licences, phone numbers, call volume and billing, across every location — not a spreadsheet somebody assembles from a login per clinic.
- Who owns the data, at every location?
- The practice at that location. On request, we send a copy and delete ours — the same answer at one site or at fifty.
See where every location’s system stands →
Tell us how many locations, and we will call you. Pricing at this scale is a conversation, not a page.
Talk to us
Tell us the organisation and how many locations, and we will call you. This opens an email to sales@meetleady.com with what you type already in it.
Contact sales