You have thought about switching. Maybe not seriously – maybe just a passing thought after the third follow-up email about an invoice that still does not make sense, or after the renewal letter showed up with a 12% increase and no explanation, or after the outage that took six hours to resolve because your “dedicated” support team turned out to be a guy in another state who had never heard of your EMR. You thought about it. And then you thought about what switching would actually involve. The migration. The passwords. The contracts. The systems your current MSP set up that only they seem to understand. And the thought passed. That is not an accident. That is the product. Your MSP’s most valuable asset is not their engineering team or their security tools or their monitoring platform. It is your inability to leave. And the playbook they use to build that inability is remarkably consistent across the industry. Here are the five plays. 1. The Long-Term Contract With Teeth The most obvious play and somehow the one that still works. Your MSP locked you into a three-year agreement with an auto-renewal clause buried on page fourteen. The cancellation window is 90 days – but only during a specific 30-day period before the anniversary date. Miss that window and you are in for another year. You signed it because the per-user rate looked competitive at the time. What you did not calculate was the total cost of that commitment – not just in dollars, but in leverage. A vendor who knows you cannot leave for 36 months has no incentive to perform at the level they pitched during the sales process. The contract was not designed to protect you. It was designed to protect their recurring revenue. A month-to-month agreement feels risky to the vendor. That is precisely the point. If your technology partner needs a three-year contract to feel confident they can keep your business, ask yourself what that says about the quality of their service. 2. The Hostage Infrastructure This one is quieter and more effective than the contract play. Over time, your MSP has set up your systems in a way that only they can manage. The domain registrar is under their account. The SSL certificates are tied to their reseller portal. Your Microsoft 365 or Google Workspace tenant is provisioned through their CSP agreement. Your firewall is configured with their proprietary templates. Your backup solution runs on their infrastructure. None of this was presented as lock-in. It was presented as convenience. “We will handle all of that for you.” And they did. Now every piece of your infrastructure has a dependency on their account, their credentials, or their platform. Try to leave and the first question becomes: who actually owns what? The answer, in most cases, is more complicated than it should be. That complexity is not a byproduct of the setup. It is the architecture. If you asked your MSP today to provide a complete inventory of every account, license, credential, and configuration they manage on your behalf – along with documentation sufficient for another provider to assume management – how confident are you that they could produce it? How confident are you that they would? 3. The Knowledge Silo Your MSP has one engineer who knows your environment. Maybe two. They know where the workarounds are, which server has the legacy application that cannot be updated, and why the VPN drops every Thursday at 2 PM. None of this is documented. It lives in their heads. This is not negligence. It is strategy. An undocumented environment is an environment that cannot be transitioned. If every configuration, every exception, every workaround existed in a runbook that another provider could follow, switching would be a project. Without that documentation, switching is a crisis. The next time your MSP tells you they are “too busy” to update documentation, understand what they are actually too busy doing: building the moat. 4. The Escalating Renewal Year one, the price was competitive. Year two, there was a “modest adjustment” tied to cost of living. Year three, there was a new cybersecurity requirement that added a per-user surcharge. Year four, the compliance module became mandatory. Year five, the price is 40% higher than where you started and nobody in your organization can explain exactly why. Each individual increase was small enough to avoid a confrontation. That is the design. No single renewal triggers a vendor review. But compounded over five years, your practice is spending significantly more for what feels like the same service – or worse. When your CFO finally runs the numbers and asks whether it is time to look at alternatives, the conversation circles back to plays one through three. The contract. The infrastructure. The documentation. And the increase gets approved because the switching cost feels higher than the renewal cost. Your MSP knows this math better than you do. They built the model around it. 5. The Fear of Transition This is the play that ties the other four together. Even when the contract allows it, even when the infrastructure is sortable, even when the documentation exists – there is the fear. What if the new provider is worse? What if the migration breaks something? What if there is downtime during the transition? What about the EMR? These are legitimate concerns. But notice where they come from. In many cases, your current MSP is the one surfacing them. “Transitions are risky.” “You do not want to disrupt patient care.” “We have seen other practices try to switch and it did not go well.” The vendor who is failing you is also the one warning you about the danger of finding someone better. This is not a technical concern. It is a sales tactic. A competent technology partner can execute a transition without disrupting clinical operations. It is done routinely. The practices that are afraid to switch are not afraid because transitions are inherently dangerous. They are afraid