How to negotiate a managed services agreement

Document the actual operating estate: users, devices, locations, applications, tickets, incidents, assets, supported hours, language needs, security requirements, and work that is currently performed outside the proposed scope. Define what each unit means and whose data governs it. A rate without a stable unit definition is not a comparable commercial position.

Do not let transition-period performance become the permanent baseline. Sourcing guidance notes that baselining service performance during transition can be unfavorable for customers. Agree which historical data is credible, what will be measured during transition, and when the parties will reset the operating baseline.

Business volumes change. Sites consolidate, users join or leave, automation removes work, and a transformation can shift demand between towers. Consider volume bands, unit rates, adjustment cadence, and a defined mechanism for demand falling as well as rising. CIO's sourcing guidance highlights tiered pricing and periodic baseline adjustments as ways to avoid paying for an obsolete footprint.

For each volume driver, determine whether it is under the provider's control, the customer's control, or neither. Then evaluate who benefits from productivity improvement and what happens when automation changes the labor or unit-cost assumption. Gartner's recent research specifically identifies AI-driven efficiencies as a reason to revisit FTE-heavy pricing models.

Focus service levels on the outcomes that matter to the business: availability, response, resolution, request fulfillment, incident quality, or other agreed measures. Define the measurement, exclusions, reporting source, remedy, and escalation path. WorldCC notes that SLA credits are typically the primary remedy for ordinary failures, with additional remedies such as termination for chronic failure requiring specific definition.

Credits should not be treated as a substitute for a workable operating model. Test whether the service-level measures are within the provider's control and whether the reporting gives the customer enough evidence to challenge performance and invoice accuracy.

Terms, indexation, benchmarking, transformation commitments, and termination assistance should be considered together. Network-services sourcing guidance explains that volume or revenue commitments can limit exit, and that a practical agreement needs transition assistance extending beyond expiration or termination. The exact rights and fees are deal-specific, but an exit plan should not be an afterthought.

Where the term is long or the service is strategic, consider a transparent benchmark process, a way to address material out-of-market performance or pricing, and an approach for sharing documented productivity gains. Do not assume a generic benchmark clause will work. Define the services, comparison methodology, access to data, timing, and consequence of the result before signature.