July 13th, 2026
Outsourced IT vs. In-House vs. Break-Fix: The Real Cost for a Dental Group
Industry Research — DSO
There is a fork in the road that shows up once a practice grows past a couple of locations. The IT problems stop being occasional annoyances, and someone in the leadership meeting finally asks the real question: how should we actually buy IT?
There are three main ways to fund and staff technology support, and a fourth that most operators overlook. Break-fix, in-house, and outsourced IT support each carry a different cost structure, a different owner of accountability, and a different downtime risk. I have watched DSO clients pick the wrong one for their size and pay for it in margin and stress. This post is about which model you buy, not whether your current spend is leaking or your current vendor is failing. Those are separate questions with their own answers.
I run Medix Dental IT, and I work with multi-location groups every week. What follows is how I actually think through the decision, priced in general industry ranges, with the dental realities layered on top.
The Three Models, Plus the One Most Operators Miss
Before the math, get the definitions straight. The words matter because the accountability shifts with each one.
Break-Fix: Pay When It Breaks
Break-fix is reactive. You call someone when a workstation dies or a server goes down, they bill you by the hour, and the relationship goes quiet until the next fire. There is no continuous monitoring, no patching schedule, no one watching your systems overnight.
Industry hourly rates run roughly $75 to $200 per hour. It looks cheap because you only pay when something is on fire. The catch is that you keep accountability. When your practice management software goes down at 8 a.m. and the break-fix tech cannot get to you until noon, that is four hours of a full schedule sitting idle. Nobody was watching to prevent it.
In-House: Hire Your Own
You put IT on payroll. Full control, someone in the building, and a person who learns your systems intimately. A single all-in IT hire (salary, benefits, tools, training) typically runs $95,000 to $145,000 per year in the current market. Building out coverage that actually spans nights, weekends, and multiple sites can push past $300,000 per year once you add a second body and the software stack.
Outsourced / Managed IT: A Flat Monthly Subscription
Managed IT is proactive. You pay a flat monthly fee under a service level agreement, and the provider handles 24/7 monitoring, patching, security, and help desk. The accountability shifts to the provider. When something breaks, it is their problem to fix inside the SLA, and their job to prevent it in the first place. Industry surveys have long reported that a large majority of companies reduce IT costs after moving to a managed model, a CompTIA study being the most cited.
Co-Managed IT: The DSO Sweet Spot
This is the one most comparisons skip, and it is often the right answer for a multi-location group. Co-managed means you keep an internal person or small team for the day-to-day, hands-on work, and you bolt on an outsourced layer for monitoring, security, after-hours coverage, and strategic planning. The outsourced layer commonly prices around $75 per user per month because you are buying a slice of the stack, not the whole thing.
You get the on-site familiarity of in-house plus the depth, tooling, and coverage of an MSP. For groups in the awkward middle, that combination usually wins.
The Side-by-Side Comparison
Here is how the four models line up on the things a CFO or COO actually cares about.
| Model | Cost structure | Who is accountable | Downtime risk | Scalability across locations |
|---|---|---|---|---|
| Break-fix | Pay per incident, ~$75-$200/hr | You do | High (reactive, no monitoring) | Poor (each site is its own scramble) |
| In-house | Fixed salary, ~$95K-$145K+/yr per hire | You do, via your staff | Moderate (limited by hours and headcount) | Limited (each new site adds bodies) |
| Outsourced / managed | Flat monthly under SLA | The provider | Low (proactive, monitored) | Strong (add sites to the contract) |
| Co-managed | In-house cost plus ~$75/user/mo layer | Shared, defined by scope | Low (on-site plus 24/7 backup) | Strong (internal presence, MSP depth) |
Notice that the two cheapest-looking options on sticker price, break-fix and a single in-house hire, are also the two that leave accountability sitting on your side of the table. That is the part that does not show up on the invoice.
The Three MSP Pricing Models (and Why Per-Location Changes Your Math)
Not all managed contracts are priced the same way, and for a multi-site group the pricing model can swing the total more than the provider you pick.
Per-User
You pay a flat rate for each employee who uses technology, regardless of how many devices they touch. Full managed service runs roughly $100 to $250 per user per month, and can reach $400 with full cybersecurity and virtual CIO strategy included. One reference (encomputers) cites $125 to $220 per computer-using employee per month. This model is clean for planning because your cost tracks your staff, not your hardware count.
Per-Device
You pay per machine. Workstations commonly run $50 to $150 each per month, servers $150 to $500, with the full device range spanning about $30 to $300. This favors practices with few users but heavy hardware, and it can punish a dental group where every operatory has multiple devices.
Tiered, Bundled, or Flat-Fee
Some providers package everything into a per-location or flat monthly number. For a DSO, this is where the math gets interesting. Per-location pricing lets you forecast the exact IT cost of opening site number six before you sign the lease. That predictability is worth real money when you are modeling an acquisition or a de novo build, and it feeds directly into the IT due diligence you run before buying a practice. It is why I tell operators to ask for the per-location number even when the opening quote is per-user.
The In-House Break-Even Math
The honest question is not “is in-house good,” it is “are we big enough for it to pay off.” There is a rough industry ratio worth knowing: one IT staffer can reasonably support around 65 computer-using employees.
Below roughly 65 users, outsourcing is almost always cheaper than a full salary plus benefits plus tools, because you are paying six figures for a person who is idle much of the week and unavailable nights and weekends.
In-house starts to pencil out as you approach 75 to 100 or more employees, where the workload can actually keep a dedicated person (or team) busy and the per-user cost of that salary drops below what an MSP would charge. Talent and complexity can override headcount in either direction. A group with unusually demanding compliance or custom integrations may justify in-house earlier, and a group that cannot recruit good IT talent locally may stay outsourced far longer.
This break-even is also where co-managed earns its keep. You can hire one internal person for the hands-on work well before you could staff full 24/7 coverage, and let the MSP layer cover the gap.
The Dental Fit Layer
General IT ranges get you a budget. Dental realities decide whether the model actually fits. Three things change the calculation for a practice that a generic office does not face.
PMS Uptime Is Not Optional
Your practice management software is the business. If Open Dental, Dentrix, or Eaglesoft goes down, the schedule stops, and every idle chair is lost revenue you never recover. Break-fix cannot protect uptime because nobody is monitoring. This single dependency is why most growing groups eventually move off reactive support. If you want the fuller picture of where reactive spend quietly drains margin, I covered the hidden IT costs in a separate post.
HIPAA Adds Real Cost to Every Model
Dental groups are HIPAA-bound, and compliance is not free. Security and compliance packages typically add about 20 to 30 percent on top of the base managed fee. That is not padding. It is encryption, monitoring, documentation, and the controls that keep patient data defensible. Whatever model you pick, budget for it, and be honest that a bare-bones quote without a compliance layer is not really a dental-grade quote.
Multi-Op, Multi-Site Coverage
One tech cannot be in five buildings at once. As you add locations, the models diverge fast. Break-fix scales worst because each site becomes its own emergency. In-house scales by adding bodies. Managed and co-managed scale by contract, which is why they tend to win as the map fills in. For a deeper look at the specific pressures here, see the IT challenges for DSOs.
Total Cost of Ownership, Not Sticker Price
The mistake I see most often is comparing an hourly rate or a single salary against a monthly MSP fee as if they were the same thing. They are not.
A real comparison includes salary and benefits, the security and monitoring tools you would otherwise buy separately, the coverage gaps (who answers at 6 p.m. on a Friday), and the cost of downtime when nobody was watching. Once you add those, the cheap-looking options usually are not.
Break-fix has the lowest sticker price and the highest total cost, because you pay for every fire and eat the downtime. A lone in-house hire looks contained until you count the nights and weekends they cannot cover. Managed and co-managed cost more on paper and less in practice for most multi-location groups, because the accountability and the prevention are baked in.
If you are evaluating providers rather than models, I have written separately on the best IT provider for DSOs and the signs to switch providers. This post is only about the model. For a clean breakdown of the core tradeoff, this break-fix vs managed services reference is a solid starting point.
So Which Model Should You Buy?
My honest read, model by model. Break-fix works for a single practice with simple needs and a high tolerance for downtime, and it stops working the moment uptime matters. In-house pays off once you are past roughly 75 to 100 employees or you have complexity that demands someone in the building daily.
Outsourced managed IT is the right default for most small and mid-size groups that want predictable cost and someone else holding the accountability. And co-managed is the sweet spot for the DSO in the middle, big enough to want internal presence, not big enough to staff the whole stack. Match the model to your size and your uptime tolerance, and the budget follows.
Frequently Asked Questions
How much does managed IT cost for a dental group?
State it as an industry range, not a fixed number. Full managed service commonly runs $100 to $250 per user per month, reaching $400 with full cybersecurity and virtual CIO strategy. Per-device pricing spans about $30 to $300 per device. Dental groups should also budget a 20 to 30 percent add-on for HIPAA compliance and security. Your actual number depends on user count, device density, and coverage scope.
When does hiring in-house IT make financial sense?
A common industry ratio is one IT staffer per roughly 65 computer-using employees. Below that, outsourcing is usually cheaper than a full salary plus benefits plus tools. In-house starts to pencil out as you approach 75 to 100 or more employees, where the workload keeps a dedicated person busy. Complexity and local talent availability can move that line in either direction.
What is co-managed IT and why does it fit DSOs?
Co-managed keeps an internal person or small team for hands-on daily work while adding an outsourced layer for monitoring, security, after-hours coverage, and strategy. The outsourced slice often prices around $75 per user per month. It fits multi-location groups that want on-site familiarity plus MSP depth without paying to build full 24/7 coverage internally.
How do MSP pricing models differ for multiple locations?
Per-user pricing tracks your headcount, per-device tracks your hardware count, and flat or per-location pricing bundles a whole site into one number. For a multi-site DSO, per-location pricing is often the most useful because it lets you forecast the exact IT cost of opening a new site before you sign the lease. Always ask for the per-location figure when modeling growth.
Posted in DSO