Back to all posts
dental support organizationsMay 16, 20268 min read

Why Your DSO Isn't As Efficient As You Think (And What AI Changes)

Earlier this year, Databricks CEO Ali Ghodsi shared a story about how his company reduced the connector development cycle from nine months to just one quarter.

A
Ash Ghaemi
Why Your DSO Isn't As Efficient As You Think (And What AI Changes)

Earlier this year, Databricks CEO Ali Ghodsi shared a story about a connector development process that had taken three quarters. After rethinking how the team worked, it could deliver seven connectors in one quarter.

The breakthrough involved redesigning the workflow. They compressed requirements gathering from a quarter to a week, brought in specialists to handle difficult system setup, moved testing earlier, and changed how engineers worked across connectors. AI accelerated the coding, but the surrounding process had to change to realize the benefit. 

A similar rethink is coming to dental support organizations, and it will happen on two levels.

At the DSO operating level, much of the reporting and analysis process can become a conversation. At the practice level, individual operators can investigate performance without waiting for a regional manager to interpret every report.

AI supports both changes. But the larger opportunity comes from redesigning the work around it.

Here is the gap many DSO CEOs need to examine.

Where DSOs Actually Lose Efficiency

Many established DSOs have custom dashboards, monthly operations reviews, regional managers, and a reporting schedule.

That looks like operational maturity. Yet underneath it, six efficiency leaks can slow practice growth and leave problems unresolved.

The First Leak Is Interpretation Lag

Data from the dental practice management system becomes a report. The report is reviewed in a meeting. The meeting produces action items for regional managers, who then arrange conversations or practice visits.

The time between recognizing a problem and addressing it can stretch into weeks.

If the issue involves missed appointments, weak follow-up, or delayed collections, the consequences continue while the organization works through the reporting process.

Across a portfolio of practices, that delay adds up.

The Second Leak Is the Prioritization Bottleneck

A regional manager overseeing ten practices cannot address every issue every week.

The loudest problems demand attention. Smaller but persistent issues can go untouched because nobody has time to investigate their cumulative impact.

Leadership needs a way to distinguish what is urgent from what is financially or operationally significant.

A long list of metrics does not make that decision easier by itself.

The Third Leak Is the Knowledge Gap

An experienced regional manager knows which dental metrics matter, which changes deserve investigation, and what questions to ask next.

A new manager may have access to the same dashboard without having that experience.

When operating knowledge stays with individuals, training takes longer and turnover becomes more disruptive. The organization loses context about what worked, what failed, and why.

The reports remain. The reasoning behind them can disappear.

The Fourth Leak Is the Standardization Problem

An effective process developed in one location may never reach the rest of the group.

The Dallas office improves its follow-up workflow, but other offices continue working the old way because nobody has time to document, test, and introduce the change.

The organization has already learned something useful. It simply lacks a dependable way to apply that lesson elsewhere.

The Fifth Leak Is Acquisition Drag

A newly acquired practice brings unfamiliar systems, people, and workflows.

Leadership needs time to establish a reliable performance picture before deciding what to improve. When access, reporting, and operational review move slowly, the group delays opportunities to support the practice.

Acquisition integration involves more than analytics, but getting visibility earlier gives the regional team a better starting point.

The Sixth Leak Is the Marketing-Operations Disconnect

Marketing tracks lead volume, acquisition cost, and campaign performance. Operations tracks appointments, attendance, dental case acceptance, production, and collections.

When those views remain separate, both teams can meet their own targets while missing a breakdown between them.

Marketing may generate inquiries that do not become attended appointments. Operations may struggle with follow-up while leadership assumes the problem is lead quality.

Without a connected view, the organization can keep spending before understanding where the patient journey is breaking down.

These six leaks are what dashboards and operations reviews should help address. But visibility alone leaves substantial work between the data and the decision.

What AI Changes About How a DSO Runs

This is the rethink, and it follows the same principle as the Databricks example.

The technology becomes more valuable when the workflow around it changes.

In dental analytics, that means reducing the manual work required to investigate performance, establish priorities, and get an issue to the person who can address it.

Decisions Can Move Faster

An operator can ask which practices are falling behind, examine the measures contributing to the gap, and investigate related trends in the same conversation.

A decline in production can lead directly to questions about completed appointments, provider availability, or treatment scheduling.

The team spends less time waiting for another report and more time understanding the problem.

That is where speed becomes useful: the organization can respond while there is still an opportunity to influence the result.

Prioritization Can Become More Systematic

AI can help organize issues across the portfolio by the scale of the change, its persistence, the number of patients affected, and estimated financial impact.

With those inputs available, a regional team can work from a more focused review rather than relying on whichever problem was raised most recently.

The direction is toward increasingly automated prioritization. The operator remains responsible for weighing the evidence, local circumstances, and practical ability to respond.

Smaller problems become easier to identify before they grow.

Operating Knowledge Can Become More Accessible

Experienced operators can document their reasoning and incorporate it into the system.

That includes which metrics to review together, what questions to ask when a trend changes, and which workflows have helped in comparable situations.

A new regional manager can begin with that context instead of rebuilding the investigation from scratch.

This does not eliminate the need for experience. It makes the organization’s existing experience easier to use.

Successful Processes Can Spread Faster

Shared analytics makes it easier to identify where a location improved and investigate what changed.

The organization can then document the process, test it in suitable practices, and measure the result.

A top-performing office becomes a source of useful operating knowledge. Differences in patient mix, staffing, and care model still matter when applying its approach elsewhere.

Practice growth becomes less dependent on each manager independently discovering the same solution.

New Practices Can Be Understood Earlier

Once system access and connections are established, a new practice can enter the group’s reporting and review process.

The regional manager can investigate its performance, compare relevant measures, and develop an initial action plan.

That accelerates the analytical part of integration and gives the team more time to work on the people and processes that require direct attention.

Marketing and Operations Can Work From the Same Patient Journey

Connected data lets the organization examine which campaigns generate bookings, which bookings become attended visits, and what treatment and collections follow.

Marketing can make budget decisions with more downstream context. Operations can identify where demand encounters friction.

The discussion becomes more specific: does this location need more inquiries, better booking conversion, stronger follow-up, or additional capacity?

Both teams can work toward the same business outcome.

Dental Analytics Software Is Only Part of the Redesign

Ghodsi’s example matters because faster code alone did not solve the entire problem. The surrounding work needed to change.

The same principle applies to dental practice management.

If a team gains a faster analytical tool but still waits for the monthly meeting before investigating an issue, much of the original delay remains.

The operating process needs to give people permission and responsibility to act sooner.

Practice managers can investigate local changes before requesting regional support. Regional managers can prepare focused questions before a review. Leadership can use meeting time to resolve decisions and evaluate actions already underway.

Dental software creates more value when it changes how work moves through the organization.

Custom Integrations Connect the Gaps Between Systems

Some delays depend on the systems a DSO uses.

A marketing team may repeatedly combine campaign and practice reports. An operations manager may manually prepare the same weekly summary. A scheduling issue may need to be passed between platforms before someone can respond.

Root Data offers custom AI automations and integrations by request to address these kinds of recurring workflows.

The project starts with the operational problem: what information needs to move, who needs it, and what should happen next?

Our practice management software integrations currently support Open Dental, with additional PMS connections coming soon. Custom work can extend the analysis where other systems and data sources are needed.

This is another application of the Databricks lesson: examine the entire workflow and remove the steps that unnecessarily slow the result.

The Future DSO Powered by AI Is Closer Than It Looks

The broader vision is a dental organization where performance questions can be investigated quickly and useful operating knowledge is available throughout the group.

Root Data gives DSO operators and practice owners a way to ask questions about connected practice information in plain English.

Instead of waiting for someone to prepare every report variation, the operator can explore a question, review the supporting information, and decide what to investigate next.

An estimated dollar impact can help focus attention when its assumptions are clear. The team then brings its knowledge of the practice to the response.

That change makes further improvements possible. Operators spend less time gathering information and more time supporting practices, coaching employees, and resolving problems.

Root Data was built alongside a 50-practice DSO, with input from people using the platform in daily operations. That experience helps shape the questions, views, and workflows the product supports.

The objective is to bring useful analysis closer to the people responsible for results.

Stop Letting the Reporting Schedule Set Your Operating Speed

Databricks' lesson is to reconsider the process around the technology.

For a DSO, that means examining every handoff between a performance change and the team’s response.

Where are people waiting? Which reports are repeatedly rebuilt? Which questions could practice managers answer themselves? What operating knowledge should be accessible across the organization?

Groups that improve those workflows can spend more of their time acting on information while it is still useful.

Get started with Root Data and bring a recurring operational question your team should be able to answer faster.

Want more insights like this?

Connect your practice management system to Root Data and get clear, actionable insights on your production, collections, and hygiene.

Explore Root Data