Hidden IT Costs in Dental Groups: Where DSO Margin Leaks in 2026

"This is a cost saving move." That is how a multi-office owner explained a practice-software switch on a dentists' forum in March 2026. At five or six offices, IT becomes a column nobody can explain: six support bills, four internet contracts, three backup products, a renewal every other week, and an ops lead who suspects waste but cannot point to it.

This guide is written for the ops or integration lead of a group with three to thirty offices who has to explain the IT column at a month-end or EBITDA review. It names where the cost hides, uses only what vendors publish on their own pages (read 6 November 2026), gives you a reconciliation template and a 30-day process, and ends with what to ask your IT provider. It does not price IT support; our dental IT support cost guide covers quotes for a single office.

Where does IT cost hide in a dental group?

It hides in the gap between what the group bought and what it uses, multiplied by the number of offices. The visible costs are the support contract, the internet bill and the hardware you can see. The hidden ones are seats, modules, circuits, servers and renewals each office carries alone because nobody looks across all of them.

The table is the map for the rest of this guide. Each row is a line that rarely has its own account code, with where it usually sits on the P&L, who tends to notice it first, and the one action that surfaces it.

Six of the twelve are software, three are hardware and storage, two are telecom and one is staff time. That is why licence sprawl gets the most space below. If you are about to buy another practice, the dental practice acquisition IT due diligence checklist catches most of these rows before closing, which is cheaper than finding them in month four.

Why does per-location IT cost rise as a group grows?

Because most dental software, hardware and connectivity is priced and built per office, and a group inherits one of everything with every acquisition. Size lowers the cost per office only when the group changes the architecture or renegotiates the contracts; left alone, the tenth office costs about what the first one did.

Practice management software shows the mechanism plainly, because one vendor publishes its fee page. Open Dental's fee schedule (read 6 November 2026) states that fees "vary depending on number of locations, number of providers, and any additional functionality required," and answers the multi-location question directly: "I am using Open Dental at multiple treatment locations but using just one database … Do I have to pay a monthly support fee for each location/office?" — "Yes. Our policy clearly states that fees are per location/office." The page adds that "Mobile treatment units are each treated as one physical location for billing purposes." Each licence "Covers all computers per location or office for up to 3 providers"; above that, "More than 3 providers per office or location (not counting hygienists)" is "$20/month/provider". Volume pricing exists ("4 - 9 offices $169/month/office or location"; "10+ offices Call us and ask for Management"), and the initial US rate is "$199/month/location or office", reduced to a "Current Reduced Rate: $149/month/location" after twelve consecutive months. The hidden-cost version of this page is a group that pays the initial rate at an office that has been on support for years because the account was never consolidated, or a merged office that still appears on the invoice.

Dentrix, Eaglesoft, Denticon and Curve publish no per-location prices, so you cannot check them against a page. You can still check them against your own invoice: ask each vendor for a statement per location and per provider, and compare the count of licensed providers with the providers who treated patients last month.

Architecture sets the per-office bill as much as the price list. Open Dental's own Multiple Locations manual lists nine ways to run more than one office, from a separate database at every location to one shared database behind a Middle Tier server, and says the shared-database-over-VPN option suits groups with fewer than five locations (its footnote adds that the number may vary). The table covers five of them. Each carries a different set of recurring costs, and the group pays for whichever one each office happened to arrive with.

The manual is also candid about who does the network work: "Open Dental Support cannot assist with network setup. It is recommended to have a capable IT set up and maintain any network settings." That is the point where a group either has one standard for connecting offices or pays for several.

How does licence sprawl start, and how do you find it?

Licence sprawl starts the day an acquired office keeps its own accounts. Subscriptions are bought per office, seats stay assigned after people leave, annual terms renew because nobody owns the calendar, and a module one office needed is billed to all. You find it by exporting every user list and matching it to payroll and your office list.

Four mechanics do most of the damage.

1. Seats that outlive the person. Every cloud product bills per assigned user. When a hygienist or front-desk lead leaves, the account is often disabled but the licence stays assigned. Microsoft documents the fix for its own products — admins can "assign or unassign licenses for users in the Microsoft 365 admin center" — but a group with six tenants, one per acquired office, has six places to do it and nobody doing it. The same control matters for security: the HIPAA Security Rule's administrative safeguards include "Termination procedures (Addressable). Implement procedures for terminating access to electronic protected health information when the employment of, or other arrangement with, a workforce member ends." A single leaver process that removes access and releases the seat covers both. Our guide to shared payer portal logins and MFA in dental groups covers the portal side of the same problem.

2. Annual commitments you cannot shrink mid-term. Many business subscriptions are sold on an annual term. Microsoft's own documentation is specific: "You can only cancel and receive a prorated credit or refund if you cancel within seven days after the start or renewal of your subscription." Miss that window and the seats you no longer need are paid for until the next renewal. The hidden cost is not the plan; it is the twelve months of seats nobody could remove.

3. Per-provider and per-location add-ons. Vendor fee pages price by office and by provider. Using Open Dental's published schedule as the example again: a fourth provider at an office is "$20/month/provider", and e-services are priced per location (the "eServices Bundle" is "$165/month/location"; the "ODTouch" tablet service is "$85/month/location. Includes up to 4 devices"). A group that enabled a bundle at every office because one office wanted texting is paying the per-location fee for offices that never send a text. Ask every vendor for module usage by office, then switch off what shows zero.

4. One tenant, one domain, one everything per office. Email tenants, password managers, remote-support tools, antivirus consoles and backup portals each arrive per office. Each has a minimum seat count, an admin account and a renewal. Consolidating tenants is a project; cataloguing them is an afternoon, and the catalogue is where the savings start.

Use this inventory for every subscription and licence in the group. One row per product per office; a group with eight offices and fifteen products has 120 rows, and that is the point.

Two checks are worth doing on the same day: compare "seats assigned" with the current payroll for that office, and compare the list of offices on each vendor invoice with the list of offices that saw patients last month. Both take under an hour per vendor with the exports in hand.

What does a per-location standard cost you when it does not exist?

A per-location standard is a written description of what every office runs: workstation and imaging PC, server or none, switch, firewall and Wi-Fi, backup, security agents, identity and email. Without one, every office is a special case, and special cases cost more to buy, support, replace and secure than a standard build does.

The cost of not having one is spread across three places: purchasing (no volume, no reuse of a tested build), support (every fix is a first-time fix at that office) and replacement (every office ages on its own schedule). The matrix below lists what the standard covers and where the cost shows up when it is missing.

The owner pages for three of these rows explain the technical side: dental office network setup for the switch, firewall and Wi-Fi standard, dental servers and workstations for the hardware decision, and dental data backup for the retention and restore-test policy. This article stays on the cost side.

One more cost belongs here: the standard has to be written before the next office joins, because applying it afterwards is a migration. A group that keeps acquiring without a document ends up with as many builds as it has offices, and the cost of fixing that is paid later in change projects. The acquisition diligence checklist linked above is where the standard gets applied for the first time at each new office.

Where do vendors overlap in a dental group?

Vendors overlap wherever two offices solved the same problem separately before they were one group. The common pairs are two backup products, two antivirus or endpoint tools, two remote-support tools, two patient-communication platforms, several internet providers and several phone systems. Each pair is a double payment and, more often than not, a double gap.

Overlap is harder to see than sprawl because the products have different names and sit on different invoices. The map below lists the functions where overlap is most common after acquisitions, with the question that decides which one survives.

A simple rule settles most rows. Keep the product that covers every office from one console and that your IT provider will stand behind. Consolidate when two products do the same job and one can take the other's offices without a migration project. Retire anything that no longer has an active office, an owner or a login. Downgrade when the edition exceeds the need, which is common with suites bought for one feature.

Apply the rule in writing, with a date for each retirement, because overlap returns at the next acquisition unless the standard says what the group uses.

How does lifecycle debt become emergency spend?

Lifecycle debt is the gap between the age of what each office runs and the date the vendor stops supporting it. It becomes emergency spend when a deadline passes unnoticed or a device fails outside any plan, and the group buys at the worst possible moment: in an outage, at retail, one office at a time.

The dates are public. Microsoft's lifecycle page states that "Windows 10 will reach end of support on October 14, 2025," so an office still running Windows 10 workstations has had no free security updates for over a year. Moving to Windows 11 is not always a free upgrade either: Microsoft's requirements list "Trusted Platform Module (TPM) version 2.0," which older PCs lack, so the real cost is replacement, not an update. On the server side, Microsoft's Windows Server release information lists "End of updates" for Windows Server 2016 as January 12, 2027. A group with a server per office may have several of them.

The fix is a lifecycle table of your own: every workstation, server, switch, firewall and imaging PC with purchase date, OS, warranty end and planned replacement year, grouped by office. Replacing by cohort — all of one office's Windows 10 machines in one planned visit — costs less than replacing them one failure at a time, and it is the table a lender or buyer asks for. Our guide on budgeting the Windows 10 to 11 transition walks through the workstation side.

How do you reconcile IT cost across locations in 30 days?

Reconcile it the way you would reconcile any other cost centre: build the inventory, match it to what the group uses, decide each row, and set an owner and a date. Thirty days is enough for a group of up to about fifteen offices if the exports are requested in week one.

1. 1. Week 1 — collect. Request a per-location statement from every software vendor, the user export from every admin console, the circuit and phone inventory from your telecom bills, and the asset list from your IT provider. Open a licence inventory with the columns above and a lifecycle table.
2. 1. Week 2 — match. Compare seats assigned with payroll per office; compare invoiced locations with active locations; compare provider counts on PMS invoices with providers who treated patients; count servers, backup jobs and security consoles against offices.
3. 1. Week 3 — decide. Mark every row keep, consolidate, retire or downgrade. Note the renewal date and the cancellation window next to each decision, because an annual term decides when the saving starts, not whether it exists.
4. 1. Week 4 — assign and report. Give every row an owner. Produce the reconciliation summary below for leadership, and put the renewal dates in a shared calendar with a reminder two weeks before each window.

The summary is the page a CFO wants. One row per category, visible and hidden spend separated, divided by offices so locations can be compared.

Two habits keep the number down afterwards. Repeat the "assigned vs active" check monthly, which takes minutes once the exports are routine. And make the inventory the first deliverable of every acquisition, so a new office is reconciled before its first renewal rather than after. The groups that publish office counts in the hundreds — the largest DSOs in the US — run this as a standing function; a six-office group can run it as a monthly checklist.

The IT side: what your IT provider sees that the P&L does not

Your IT provider holds the data that makes the reconciliation accurate: the asset inventory, which devices carry which agents, which backup jobs ran and restored, who has admin rights, which remote tools are installed, and how many tickets each office raises. If that information is not reaching you monthly, you are reconciling blind.

Ask for one monthly report for the group, by office, with at least these lines: device count and age distribution; operating-system versions and the count still on anything out of support; servers with OS and warranty end dates; security-agent coverage as a percentage of devices; backup job success and the date of the last tested restore per office; user accounts created and removed, and licences released on departure; remote-support tools present and who may use them; ticket volume and repeat issues per office. A provider that works across the group can produce this from its own tooling; one that works office by office cannot, and that gap is itself a cost.

Standardisation is where the provider earns its fee at group scale. With one build and one toolset, the inventory, the agents and the licence counts fall out of the monitoring platform instead of a spreadsheet, and the leaver process runs the same way at every office. That is what DSO IT support is for when it is done properly: one documented build standard, central visibility of patching, backup status and asset inventory, and joiners, movers and leavers handled as a routine request rather than an afterthought at each office.

Two cost habits distinguish providers. The first is separating recurring support from everything else on the quote, so you can see what the monthly fee covers and what is billed as a project; at Legend Networking, hardware procurement, major cabling projects and software licensing are quoted separately, so the licence column in your reconciliation stays visible instead of being folded into a support fee. The second is being willing to work co-managed with an internal IT lead where a group has one, with one escalation route so offices never have to work out whom to call. If the group is deciding whether to consolidate on a single provider, the questions in how to choose a dental IT company apply at group scale, and managed IT services for dental practices describes what the recurring relationship covers.

What to ask your IT provider about hidden cost

How Legend Networking works with growing groups

Legend Networking has served over 3,500 practices since 2004, with 22+ years in dental IT. Support is remote-first nationwide, with onsite dispatch by appointment across served dental markets, and for multi-office groups the conversation starts with the same items covered above: the build standard, central visibility and the leaver process. Legend supports the IT environment for the practice software Dentrix, Eaglesoft, Open Dental and Archy, and for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, which is where most per-location and per-provider fees in this guide live.

The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. For an example of group work, see a technology project for a dental group in Salem, Oregon, and for offices in a particular market, dental IT support by city.