MyDentalForce Book a Walkthrough
Back to resources

Field notes

DSO software: what the category actually contains

Six jobs, not one product: the category map for a 2 to 20 office group, the order the jobs break in, and the questions that keep vendors honest.

The MyDentalForce team7 minute read

DSO software is not one category. It is six separate jobs that every dental group has to cover: the practice management system that holds the chart and the ledger, revenue cycle management, analytics and dashboards, patient outreach and schedule recovery, HR and credentialing, and document and compliance operations. No single product does all six well, and a group that shops for DSO software as a single purchase usually ends up with the weakest available version of each job. The useful question is not which platform to buy. It is which of the six jobs currently runs on memory and spreadsheets in your group, and what to buy for that one job.

This map is written for groups of 2 to 20 offices, the range where the word DSO starts getting used while the budget is still finite. Most of it applies just as well to a single office planning a second, because all six jobs already exist at one office. They are simply held by fewer people, and several of them by the owner personally.

What does DSO software actually mean?

A DSO, a dental support organization, centralizes the business side of dental offices, billing, HR, purchasing, compliance, marketing, while dentistry stays with licensed clinicians. DSO software, the way vendors use the phrase, means anything sold to that central team. That is why the search results for it look incoherent: a practice management system, a claims clearinghouse, a dashboard product and a staffing tool all call themselves DSO software, and all four are telling the truth. They just do different jobs.

The fix is to stop shopping by the label and start shopping by the job. Six jobs cover what a 2 to 20 office group actually runs on, and the map below is the whole category. A product that claims more than two rows deserves extra questions, not extra credit.

The six jobs, in one table

Job What it covers Who is in it daily The question it must answer
Practice management system (PMS) Charts, schedule, ledger, claims out the door. The system of record. Everyone, in every office. Is every office on one system that supported add-ons can connect to?
Revenue cycle management (RCM) Claim follow-up, denials, payer A/R after submission. The billing team. Who owns this claim today, and what happens to it next?
Analytics and dashboards Production, collections, goals: per office and rolled up. Managers and owners. Which office needs a conversation today?
Patient outreach and schedule recovery Recall, unscheduled treatment, lapsed patients and patient balances, worked as call lists. Front desk and outreach callers. Was the list worked, and what came of each call?
HR, payroll and credentialing Hiring, hours, pay, licenses, provider credentialing. Office managers and central admin. Is every office staffed and every provider current?
Document and compliance operations SOPs, policies, OSHA and HIPAA artifacts, training records. Office managers. Can a new hire find the current version in one place?

Two things about the map are worth saying plainly. The PMS is the only row that is never optional and never shared: every other row reads from it, and a group split across different practice management systems is doing the other five jobs the hard way, office by office, export by export. Consolidating the PMS is unglamorous and it comes first, before anything that sits on top of it.

The outreach row is the one most groups discover last, because nothing breaks loudly when it is missing. A denied claim announces itself on an aging report. The hygiene patient who quietly went eighteen months without a visit announces nothing, and neither does the crown that was diagnosed, accepted and never scheduled. Groups that staff the billing row and skip the outreach row are collecting yesterday's production carefully while leaking next month's. The honest list of outreach software by job breaks that row into its own sub-categories if it is the one you are buying for.

What should a DSO dashboard show?

A DSO dashboard should show a short list of numbers per office and rolled up, defined the same way in every office, each with an owner attached. Production against goal, collections against production, and the leading indicators that move before production does; the dental KPI short list gives each one a formula, a source report and an owner.

Two tests separate a dashboard that runs a group from one that decorates it. The per-office test: a roll-up that cannot be opened into offices hides which location created the change, and the whole point of the number is to start a specific conversation in a specific office. The definition test: if two office managers can compute production two different ways, the dashboard is a debate, not an instrument. What a dental production dashboard should help you decide covers the line between display metrics and decisions; the short form is that a tile either triggers a decision or gets deleted.

What breaks first at two offices, five, and twelve?

The jobs never change with office count. What changes is when each one outgrows the people holding it in their heads, and the breakage has an order.

At one office, and usually still at two, the owner can hold analytics and outreach personally: look at the schedule, know who is overdue, ask the front desk what happened to the Tuesday cancellations. The first thing that breaks at two offices is not software at all. It is agreement, and the fix is deciding what both offices do the same way before buying anything new. Two offices on one PMS with shared definitions outrun two offices with a dashboard and neither.

Around three to five offices, visibility breaks. The owner is no longer physically in every office, and "how did yesterday go" becomes a phone-tag question answered by whoever picks up. This is where the analytics row earns its line in the budget: per-office numbers a manager reads instead of requests.

Then execution breaks, and this is the step groups misdiagnose. Knowing that office three's recall effectiveness slipped is not the same as someone in office three calling the overdue list today. That is the outreach row: a ranked list per office, worked daily, outcomes logged where a manager can see them. A group that buys dashboards without buying execution becomes extremely well informed about problems nobody is working. The daily standard is the operating habit this row exists to hold up.

RCM centralization usually follows, when billing moves from each front desk to a shared team and claims need one queue instead of five inboxes. HR and compliance tooling tends to come last, when the binder and the spreadsheet stop surviving audits and turnover. None of these thresholds is a law of nature. They are the order in which memory fails, and your group may hit them in a different sequence; the map still tells you what you are buying when it does.

A group does not need more software than a single office needs. It needs the same six jobs, each with a name on it, visible from one place.

Five questions that keep vendors honest

Whichever row you are buying for, the same five questions sort vendors quickly, and they work in a demo:

  • System of record: does it read from the PMS and write results back, or does it ask your team to retype into a second database that drifts?
  • Per-office visibility: can a manager see each office's activity and results without asking anyone to run a report?
  • Access: is it scoped per role and per office, or does every login see every office's patients and numbers?
  • Implementation: is a new office live in days, weeks, or a quarter? Ask for the steps, not the adjective.
  • The exit: can you export your lists, outcomes and history and leave without a negotiation?

Where MyDentalForce sits on this map

Honest placement: MyDentalForce covers the analytics row and the outreach row for offices on OpenDental, plus a defined slice of the billing row, and nothing else on the map. It is not a PMS; OpenDental stays the system of record. On the outreach row, Patient Outreach builds one ranked daily call list per office from that office's own OpenDental data, due and overdue hygiene recall, unscheduled treatment and lapsed patients, rebuilt every morning, and every call outcome is logged and written back to the practice management system. Balance outreach runs as a separate weekly list with the same accountability.

On the analytics row, Production Command shows production, collections, goals and tiered bonuses per office and rolled up, so the per-office test above is the design rather than a feature request, and managers see each office's activity and results without asking. On the billing row there is a cross-office worklist for a billing team, and it is deliberately not full revenue cycle management; a group that needs end-to-end denials management should buy that as its own job. Access is scoped per role and per office, a new office is typically live within days of getting access, and the same engine runs a single office exactly as it runs the 19-office Houston group whose daily operations run on it.

If you run one office, you already run all six jobs; writing them down with a name next to each is free and worth an afternoon. If you run several, the map is the budget conversation: find the job that is living on spreadsheets and memory this quarter, and buy for that one, before the label on someone's pricing page talks you into buying all six at once.

See it on your numbers

Rather see it than read about it?

Book a 30-minute walkthrough and we will run it on your own offices.

or email us at info@mydentalforce.com