The Case Against Managed IT
Why most managed service providers create dependency instead of capability — and what to build instead.
Managed IT services work like this: you pay a monthly fee, they manage your systems, and you never learn how any of it works. When something breaks, you call them. When they raise their prices, you accept it or start over from nothing. When they go out of business, your infrastructure goes with them.
This is the model the industry built, because it’s profitable. It is not the model that serves you.
The dependency business model
The managed service provider (MSP) industry has a financial incentive to keep you dependent. An educated client who can handle their own systems is a client who doesn’t renew their contract.
This isn’t malicious — it’s structural. A company with monthly recurring revenue needs to protect that revenue. The way to protect it is to make the client need you next month and the month after that.
The result: MSPs often make decisions that maximize their control rather than your capabilities. Proprietary systems. Undocumented configurations. Vendor relationships that serve their margins, not your needs.
What actually resilient IT looks like
I’ve been in homes and offices on the North Shore where the IT was “managed” by a firm on the mainland. When I asked the owner basic questions — where are your backups, what’s your mail server, who controls your domain — they couldn’t answer any of them.
The MSP knew. The owner didn’t. That’s not IT management. That’s IT hostage-holding.
Resilient IT looks like this: you understand what you have. You know where your data is. You can find and read your backup files. You know your domain registrar login. In an emergency, you can act without calling anyone.
The knowledge transfer imperative
Every engagement I do ends with a knowledge transfer session. Before I leave, you run the backup manually. You restart the service. You know what the logs say when things are normal so you know what they say when things aren’t.
This is not optional. It’s the whole point.
The measure of a successful engagement is not that the systems work when I leave. It’s that they keep working — and that you know what to do when something goes sideways.
If I’ve done my job, you don’t need me back.
When you do need outside help
Complex infrastructure changes — major version upgrades, new system integrations, hardware failures — are reasonable things to hire out. Nobody needs to become a full-time sysadmin to have good digital hygiene.
The difference is: hire for specific work, not for indefinite management. Know what you’re hiring someone to do. Understand the outcome. Get the documentation when it’s done.
That’s a very different arrangement than “we manage your IT, here’s your monthly invoice.”
On Kauai specifically
The mainland-based MSP is particularly dangerous here. They don’t understand the grid. They don’t understand the bandwidth constraints. They don’t understand the physical reality of getting on-site help when something breaks.
Infrastructure built by someone who’s never dealt with a North Shore power outage will not be built to survive one.
This is why I work only here. Context matters.