Your DSO Is Growing. Why Isn’t Your EBITDA?
Same-store growth requires looking closely at the business already in place. Where are patients dropping off? Where is diagnosed treatment going unscheduled? Where are completed services turning into overdue balances?

A full schedule can hide a lot of problems.
Patients are coming in. Treatment is getting completed. Production looks healthy. Meanwhile, unpaid balances are growing, employees are spending hours chasing information, and managers are dealing with the same issues every month.
Adding more patients to that system can create more work without delivering the improvement in profitability you expected.
For DSOs focused on EBITDA and same-store growth, the opportunity starts with understanding what is happening inside the practices they already own.
Bill Neumann, host of the Group Dentistry Now Show, explored this in the DSO Study Club discussion, “Fueling Same-Store Growth: How DSOs Are Standardizing Patient A/R.” The conversation included Opal Anderson, COO of Dental Associates Group, and Kristel Stiles, Director of Revenue Cycle Management at Riccobene Associates Family Dentistry. Their examples showed how collections, accountability, and everyday workflows influence practice performance.
The discussion also points to a broader opportunity for dental analytics and AI: help teams find problems sooner, resolve them with less manual effort, and apply successful improvements across the group.
Start with the revenue leaks inside your existing practices
Acquisitions add locations. They also add workflows, reporting differences, and operational problems that someone has to manage.
If follow-up is inconsistent in ten practices, adding ten more does little to resolve it. The same problem can become larger and harder to see.
Same-store growth requires looking closely at the business already in place. Where are patients dropping off? Where is diagnosed treatment going unscheduled? Where are completed services turning into overdue balances?
In the Group Dentistry Now discussion, Stiles emphasized “collectible production.” Producing more dentistry has limited value if the organization lacks reliable processes for collecting what it is owed.
That makes revenue leakage a useful place to begin. Look at patient balances, insurance aging, adjustments, and recurring reasons claims remain unresolved. Then investigate the process behind the numbers.
A collection gap is not automatically lost revenue. Payment timing, contractual adjustments, and legitimate billing corrections all matter. But a persistent pattern deserves an explanation.
The same approach applies earlier in the patient journey. A practice may be generating enough leads but struggling to book them. Another may book consultations successfully but lose patients before treatment.
Both can look like marketing problems if nobody connects the data.
Useful DSO analytics should help distinguish those situations. Otherwise, the default response is often to spend more money before understanding what is preventing the existing investment from producing results.
Give someone responsibility for what the data reveals
One of the strongest examples in the discussion involved a simple daily report.
Anderson described reviewing the patient portion that went uncollected and requiring offices to explain why payment had not been collected. She reported that an uncollected daily amount of roughly $3,500 fell to around $200 within a week after that accountability was introduced.
That was an example from her organization, but the management lesson applies more broadly: the information became useful because someone had to respond to it.
A report showing overdue balances is a starting point. The next questions are more practical. What happened? Who will investigate? What needs to change? When will we check again?
This is where dental practice management can become more consistent. Instead of discussing a disappointing number at every monthly meeting, the team agrees on a specific action and follows through.
For example, an office manager might discover that patients are leaving without understanding their expected payment. The response could involve clearer treatment estimates, staff training, and a consistent checkout process. The following review should assess whether those changes reduced the problem.
The purpose of dental analytics is to support that cycle. Find the issue, understand it, assign the work, and check the result.
Use AI to shorten the distance between a problem and a decision
Across a DSO, even finding the right problem can take considerable time.
Someone pulls reports from the practice management system. Someone else checks marketing or scheduling data. A regional manager combines the information, asks follow-up questions, and prepares a summary.
By the time the group discusses the issue, another week may have passed.
AI can help reduce that delay when it has reliable data and a clearly defined job. Practical uses include summarizing performance changes across locations, flagging unusual patterns, and helping managers identify which offices deserve a closer look.
An operator should be able to ask questions such as:
Which practices have declining collections despite stable production?
Where are new patient bookings increasing while completed visits remain flat?
Which locations have experienced a sustained drop in treatment acceptance?
What changed after we introduced a new follow-up process?
The answer should help someone investigate and act. A confident explanation without supporting data creates another problem to untangle.
This is the direction we are building toward with Root Data’s custom DSO analytics and integrations: connecting operational information so teams can ask better questions, understand performance, and identify their next priorities. The relevant systems and workflows depend on the organization.
Once a workflow is understood, routine tasks such as reporting, reminders, and internal follow-up become candidates for automation. Exceptions still need someone who can investigate, communicate with patients, or make a judgment.
Be specific about how the improvement reaches EBITDA
The financial case for AI needs more discipline than “we saved everyone some time.”
EBITDA measures earnings before interest, taxes, depreciation, and amortization. Improving it requires a change in operating economics.
Collecting an existing receivable sooner improves cash flow. Under accrual accounting, it does not automatically create additional revenue or EBITDA. Similarly, freeing five hours of administrative work does not automatically reduce payroll expense.
Those improvements still matter. The next step is deciding how the organization will use them.
Time saved could reduce overtime, limit the need for an additional administrative hire, or allow staff to help more patients complete necessary treatment. Better collection processes may reduce bad-debt expense. More completed treatment can contribute to earnings after accounting for the additional costs of delivering it.
The technology and implementation costs belong in that calculation, too.
For each project, define what success should look like. Perhaps it is fewer unresolved balances, less overtime, more completed appointments, or lower administrative cost per location. Measure that outcome alongside the time saved.
That gives the DSO a clearer basis for deciding which improvements are worth expanding.
Fix recurring problems before they become monthly cleanup work
The speakers repeatedly returned to the value of daily review.
If an adjustment needs to be made, leaving it unresolved can make accounts receivable harder to interpret. If a claim is missing information, allowing the same omission to continue creates more work for the billing team.
Waiting until month-end means someone has to reconstruct what happened weeks earlier.
Earlier visibility makes the investigation easier. The people involved are more likely to remember the interaction, the documentation is easier to locate, and the team can correct the process before repeating the mistake.
This is a practical reason to care about the speed of information.
A manager does not need a constant stream of notifications. They need timely notice of changes that deserve attention, with enough context to decide what to do.
For a DSO, that might mean identifying a developing pattern at one location before it spreads, or spotting a deterioration in performance before it becomes the new normal.
The value comes from getting a useful signal to the person who can act on it.
Make each practice’s lessons useful to the rest of the group
One advantage of operating multiple practices is the opportunity to learn across them.
In the discussion, the speakers described identifying recurring claim requirements and updating processes across offices. Knowledge gained in one location could prevent repeated mistakes elsewhere.
The same principle applies to patient scheduling, treatment follow-up, and practice management.
If one office improves appointment attendance, investigate what changed. If another consistently resolves balances faster, understand its workflow. Then test whether that approach works in comparable locations.
Reliable comparisons matter here. Practices differ in provider capacity, procedure mix, patient population, and size. A higher production total alone does not prove that one office has a better process.
Shared definitions also matter. Teams need to agree on what counts as a new patient, which production figure they are using, and how they are measuring collections.
Root Data’s DSO analytics brings office comparisons and operational signals together to support this work. The goal is to help managers understand where to focus and which improvements merit a closer look.
As successful changes spread, the group becomes better at operating the practices it already has.
Patient understanding belongs in the profitability conversation
Revenue problems sometimes begin with a conversation that never happened.
A patient may not understand why treatment is needed, what insurance is expected to cover, or what they will owe. That uncertainty can affect treatment acceptance and create difficult billing conversations later.
Anderson and Stiles emphasized explaining both the clinical need and the financial expectations. When patients have questions, someone needs to take the time to answer them.
Data can help identify where those conversations may be breaking down. A decline in treatment acceptance or a recurring pattern of disputed balances gives the team a reason to investigate. It does not explain the patient’s experience by itself.
Automation can help by reducing the administrative work surrounding those interactions. That leaves staff with more time to explain treatment, resolve confusion, and help patients navigate their options.
Improving efficiency is valuable partly because it creates room for the work that requires a person.
Build a more profitable DSO from the practices you already have
Same-store growth means increasing revenue from a consistent group of existing practices. Improving the profitability of those practices is a related goal, and both deserve attention.
The work starts with specific questions. Where is revenue leaking? Which process keeps failing? What takes too much staff time? Which improvement would make the biggest difference?
Root Data’s aim is to build the intelligence layer that helps DSOs answer those questions faster. That means bringing data together, making performance easier to understand, and helping teams focus their effort on what needs to change.
Our vision for the self-operating dental practice extends that work into connected workflows and targeted automation, giving teams more capacity to serve patients and improve the business.
Start boosting your EBITDA and optimizing for same-store growth with Root Data. Find the revenue leaks, prioritize the work, and measure the improvement across your existing practices.
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