20 questions to ask before signing an MSP contract. What good answers look like.

An MSP contract is a formal services agreement that defines which technology functions a managed services provider will own, at what service level, and under what pricing, ownership, and exit conditions. The definition sounds clean. The execution is where the gaps appear.

Question 1. What services are explicitly listed in scope? The proposal and the signed contract are not the same document. Anything the sales team described that does not appear in the scope exhibit does not exist. Read the scope section carefully, then ask the provider to name three specific services that are explicitly not covered. Good providers answer this without hesitation. Vague ones reveal themselves in the pause.

Question 2. How are scope changes handled? Your environment will change. New software, acquisitions, headcount growth. Ask how out-of-scope work is priced, how it gets documented, and what lead time the provider requires. A clean answer includes a change order process and a published rate card for additional labor.

Question 3. What does "reasonable efforts" actually mean? This phrase appears in nearly every MSP contract and is meaningless without a definition. Ask what happens when reasonable efforts fail to resolve an issue. Who escalates? What is the next commitment? If the contract cannot answer these questions, the SLA has no teeth.

Question 4. Who decides when a ticket is closed? Some contracts let the provider close tickets unilaterally. Ask for language requiring customer confirmation before a ticket can be marked resolved, or at minimum a defined window within which the customer can reopen a closed issue.

SLA sections look reassuring in proposals. In practice, the specifics matter far more than the uptime percentage printed at the top.

Question 5. What is the difference between response time and resolution time in this contract? These are not the same thing. Response time is when someone acknowledges the ticket. Resolution time is when the problem is fixed. Most providers emphasize response time in their marketing and are far vaguer about resolution. Ask for both figures, by severity tier, in writing.

Question 6. How are SLA credits calculated, claimed, and capped? Many contracts include SLA credits but make them nearly impossible to claim. Ask for the exact calculation method, how a claim is submitted, and whether there is an annual cap on total credits. Credits are not a remedy for lost productivity, but the claims process tells you how the provider approaches accountability.

Question 7. What counts as downtime for SLA purposes? Scheduled maintenance windows, third-party outages, and issues caused by your own equipment are frequently excluded. Get the exclusion list before you sign.

Question 8. What are the SLA exclusions? Every MSP contract has them. Read this section carefully. Common exclusions include acts of nature, user error, and failures in third-party platforms the provider does not control. Know what you are accepting.

Pricing questions are the ones most buyers skip because they feel awkward to ask. They are also the ones that generate the most friction two years into the relationship.

Question 9. How does the monthly fee change as our headcount shifts? Most MSP contracts are priced per user or per endpoint. What happens when you add 30 employees? What happens when you reduce headcount by 20? Ask both directions. Many contracts have a floor, a minimum monthly fee below which the price does not decrease regardless of user count. Know where that floor is before you sign.

Question 10. Can the MSP raise rates during the contract term, and how? Many contracts include a CPI adjustment clause, tied to the U.S. Bureau of Labor Statistics Consumer Price Index, or a general rate increase provision that allows annual price increases with 30 to 90 days notice. Ask for the cap on annual increases and whether there is a right to terminate without penalty if the increase exceeds a defined threshold. This is a negotiable term, and most providers expect the conversation.

Question 11. What happens to pricing when scope decreases? Scope reductions, divesting a business unit, dropping a software platform, eliminating a location, are often treated differently than headcount changes. Ask specifically how scope decreases are priced and whether there is a notice period required to reduce. If your contract is silent on this, a scope reduction may not produce a price reduction at all.

If you are still evaluating whether to engage an MSP at all or determining what scope makes sense for your organization, the Seven Roots services overview describes how fractional technology leadership fits alongside or instead of a managed services relationship for mid-market companies.

The person who sold you the engagement is not the person who will manage it. The quality of your day-to-day experience will depend entirely on who that person is and what happens when they leave.

Question 12. Who is the named account manager, and what happens if they leave? Ask for the account manager to be named in the contract. Then ask what the provider's process is when that person departs. Is there a guaranteed handoff period? How long does the buyer have before a new account manager is assigned? Account manager turnover at mid-market MSPs is common. A contract that says nothing about this leaves you exposed to starting the relationship over, operationally, every time personnel changes.

Question 13. How does the provider handle knowledge transfer internally? What your account manager knows about your environment should not live only in their head. Ask whether the provider uses a documented environment profile, a ticketing system with full history, or an internal knowledge base for your account. When the answer is "our team is very collaborative," ask the follow-up: if three people who work on our account left in the same month, what would the replacement team have to work from?

Question 14. What is the escalation path beyond your account manager? For issues that standard support cannot resolve, you need a clear path to someone with authority to act. Ask for the escalation chain by name and role, not just by title. "We have senior engineers" is not an escalation path.

This is the section of the contract most buyers skip because it covers a scenario they are not yet thinking about: the end of the relationship. It is also where the most expensive surprises tend to live.

Question 15. Who owns the documentation, scripts, and runbooks the MSP builds? By default in most MSP contracts, the provider does. The environment documentation, automation scripts, monitoring configurations, and runbooks built during your engagement belong to them unless the contract explicitly says otherwise. Ask for language that assigns ownership to your organization or grants a perpetual, irrevocable license. Then ask about format: documentation accessible only through the provider's portal is not the same as documentation delivered to you in editable files you can hand to an incoming team.

Question 16. Where are credentials and access stored, and how are they structured? Your administrative credentials, vendor account logins, and access tokens should be stored in a system where you hold the master key, not in the MSP's password manager under their account. Ask how credentials are vaulted and whether you have independent access today, not only at offboarding.

Question 17. What exactly does the buyer receive when the relationship ends? Ask for a complete list. Network diagrams, device inventories, vendor contract schedules, licensing records, configuration backups, access credentials. If the provider cannot produce a handoff checklist during contract review, that is a signal about how seriously they take transition planning.

If you want a structured review of any MSP contract before you sign, Heartwood can walk through the ownership, exit, and SLA sections with you and flag the terms worth pushing back on.

The cleanest exits happen when exit terms were negotiated before the relationship began. These are the questions that protect you when circumstances change.

Question 18. What does offboarding actually look like? Ask the provider to describe their offboarding process step by step, as if you were leaving tomorrow. A provider with a mature offboarding process will describe it confidently: a transition checklist, a defined handoff period, a process for credential transfer, cooperation with an incoming provider. A provider without one will say something general about making the transition smooth. Those are different situations, and you should know which one you are signing with.

Question 19. How long does transition assistance run, and what does it cover? Most contracts include a transition period of 30 to 90 days. Ask what is included. Does it cover active cooperation with an incoming provider? Does it include documentation delivery? Does the provider's team remain available for questions after the formal transition period ends? Get this in writing. What a provider volunteers during transition when the relationship is ending tells you a great deal about how they operate when it is healthy.

Question 20. When is a multi-year contract actually worth signing? Multi-year terms typically produce pricing discounts of 5 to 15 percent below month-to-month rates. That trade makes sense when you have history with the provider, your environment is stable, and you are not anticipating significant organizational changes. It does not make sense when you are signing with a provider for the first time. A reasonable first term is 12 to 18 months, with a clearly defined renewal process and exit rights that do not require paying out the remaining term to leave.