Read the Exit Clause Twice: Five Questions That Reveal a Managed Services Provider's True Intentions
Photo: Governor Tom Wolf from Harrisburg, PA, CC BY 2.0, via Wikimedia Commons
Managed services agreements are sold on capability and priced on scope, but they are won or lost on clauses. By the time a CIO discovers what the contract actually says — about exit, staffing, or accountability — the provider is embedded, the knowledge transfer has flowed one direction, and the switching costs have quietly compounded.
The evaluation process, then, should be less about the capabilities deck and more about how a provider answers five uncomfortable questions. The answers matter less than the quality of the answer. Vagueness at the negotiating table becomes opacity in year two.
1. What Exactly Happens in the First 90 Days After We Terminate?
Every provider will describe a smooth transition. Few will volunteer specifics. Push for a documented exit plan: knowledge transfer deliverables, documentation standards, transition staffing, and who pays for it. A provider that has never written down its exit process is telling you it doesn't expect to leave — and that its business model depends on making departure expensive.
Watch especially for exit fees buried in transition costs. Some are legitimate; many are structured to make the threat of leaving financially irrational. Ask to see the exit language from two comparable client agreements. A confident provider shows you. A defensive one explains why it can't.
2. Who Actually Delivers the Work — and Where Are They?
The team presented in the sales process is rarely the team that shows up. Ask for named individuals on the account, their committed allocation percentages, and the provider's policy on replacing them. Then ask about subcontractors and offshore delivery centers, including turnover rates in each.
The signal to watch for is the word "resources." Providers who talk about resources are telling you they staff engagements interchangeably, and that the engineer who learns your environment this year may be gone by the next. Insist on key-personnel clauses with named roles, minimum tenures, and a genuine remedy — not a substitution right — when your critical people rotate off the account.
3. How Are Your Incentives Aligned With Our Outcomes?
Most managed services agreements pay for activity, not results: hours logged, tickets closed, SLAs met on metrics the provider itself defines. Ask what happens financially when your business does poorly under their watch. If the honest answer is "nothing," you have a cost center with a service wrapper, not a partner.
Look for meaningful skin in the game — a percentage of fees at risk against outcomes you define, not they do. A provider that resists any at-risk compensation is signaling that its pricing model assumes problems are your problem.
4. What Do You Do When Your Recommendation Conflicts With Your Revenue?
This is the question providers hate, which is why it's essential. A provider that resells licenses, staffs projects, and manages infrastructure has a structural conflict of interest on every architecture decision: the answer that generates fees may not be the answer your enterprise needs.
Ask directly how they handle it. Do they disclose conflicts in writing? Will they support a decision that shrinks their own scope — say, recommending you exit a service line they provide? The best answer includes documented governance: independent advisory channels, transparent billing, and a track record of clients who downsized the relationship and stayed anyway.
5. What Does This Agreement Look Like in Year Four?
Multi-year terms with automatic renewal and escalation clauses are standard — and standard is the problem. Ask for a full financial projection across the term: escalators, true-ups, minimum commitments, and what triggers them. Then ask what happens if your volume drops 30 percent. Some agreements flex. Others guarantee the provider's revenue regardless of your reality.
Also ask what happens when the technology changes. If the agreement locks you into a specific platform stack, a major vendor shift can turn a reasonable contract into a stranded asset. Flexibility provisions — the right to renegotiate scope on defined triggers — are worth more than a discount.
The Pattern Behind the Questions
Notice what all five have in common: each tests whether the provider is structurally prepared to be accountable to you, or merely contracted to bill you. No answer will be perfect. But a provider that answers specific questions specifically, discloses limitations voluntarily, and puts its own fees at risk has told you something no reference call can. A provider that answers everything with reassurance has told you something, too.