Ask Us Anything
Sukhi Hansra October 12, 2026
A managed services agreement is the contract between a managed service provider, or MSP, and the businesses whose technology it runs. It covers the monitoring, the maintenance, the help desk, the backups, and increasingly the security of everything the client depends on. If you operate an MSP or an IT services firm, this one agreement governs nearly every client relationship you have, which means every gap in it is a gap multiplied across your entire client base.
The fact that the managed services agreement determines the entire relationship with each customer is the reason we treat MSP agreements differently from ordinary service contracts. The managed services agreement is not paperwork for one deal. It is the operating system of your managed services business itself, and it deserves to be drafted the way a franchisor drafts a franchise agreement – meaning built once, carefully, to be signed many times and to survive the client relationship that eventually goes wrong.
Suppose you run an MSP, and your agreement bills your largest customer at the end of each month, after the services have already been delivered. That customer buys six figures of services a year. One month, the customer simply stops paying, and you fall into a loop: chasing the unpaid fees, trying to cut the customer off while still being contractually required to deliver, and watching your margins starve as you pay licensing costs out of pocket while your biggest account holds your cash.
Every week of services you keep providing digs the hole deeper, and your only leverage is a collections fight that costs money you are no longer collecting. We have seen this exact pattern play out over months, and the permanent fix was not the collections work. It was a more robust MSP agreement.
The lesson is quite straightforward, and it is the first thing we correct in most MSP agreements we review. If you provide the services first and bill after the fact, then you can easily become a hostage to your customers because if you cut them off then they are certainly not going to pay. Your only leverage in such a situation arrives after the harm has already occurred. Getting paid up front, before the service period rather than after it, changes who carries the risk of a bad month, and it is the single most valuable (and simple) structural change an MSP can make to avoid this common problem.
An MSP promises an always-on service, and always-on promises fail in ways ordinary contracts never contemplate. A missed delivery under a normal services agreement is a timing dispute. A missed response to a ransomware incident is a client’s business offline, and the first document anyone reads afterward is yours. This means that the clauses that matter most in a managed services agreement are the ones generic templates handle worst, and they are exactly where we spend the drafting effort:
What MSPs really care about is liability, and in a managed services agreement, liability almost always comes down to the intersection between the indemnity provisions and the insurance clause. The reason for this is that most MSP agreements require the MSP to indemnify the customer if the MSP causes a breach of the customer’s data, whether through faults in the MSP’s own stack, negligence, mistakes, or intentional misconduct. That obligation is quite reasonable on its face, and if it is structured without care it is dangerously incomplete, as the customer’s own conduct can cause or contribute to exactly the same harm.
This is where customer obligations and the dependency clauses do their best work for you. An MSP acts on the customer’s instructions and depends on certain things being true inside the customer’s business, from access and account hygiene to the security safeguards the customer agreed to maintain. The dependency clause writes those assumptions down as obligations. This means that where the customer has breached a dependency or a customer obligation, a well-structured managed services agreement will provide that the MSP does not have to indemnify for the harm that followed – which is the difference between owning your own failures and owning your customer’s too.
The usual agreement is mutual indemnification, and good practice takes it one step further: liability gets limited to the amount that either party can actually collect from the other party’s insurance. This is the number one point that we usually push for our clients when formulating managed services agreements.
With this in mind, it is important to ensure that the drafting is completed with the insurance policies open on the table – being what each side actually carries, what the policies genuinely cover, and whether the caps in the contract line up with the coverage in the real world. A cap set above your insurance limits is a scary promise that you might not be able to fund, and a cap set without checking the coverage is a guess wearing a number.
The consequences of getting this intersection wrong are grave. An MSP with the wrong insurance or the wrong indemnities is managing all of another company’s technology, licences, and data while personally carrying the tail risk of privacy-law breaches, loss of business revenue, and data loss, and that exposure can reach amounts no monthly service fee ever priced in. So you can see why we treat the indemnity, customer obligations clause, and the insurance requirements as one system, drafted together, on both sides of the agreement.
The economics of drafting follow the economics of the business. Because the agreement is signed across your whole client base, a clause that is off by a little is off everywhere. On the other hand, a clause negotiated well earns its keep on every customer deal that follows.
When we build managed services agreements, we build the agreement as a connected system: the master terms, the liability clauses, the unique customer dependencies, insurance limits, limitations on liability, the service schedules that vary by client tier, and the order form that sales can actually use without calling a lawyer for each signature. When a large client insists on their own agreement, we review it against your standard so you know exactly which risks you are absorbing to win the account.
We act on this side as well, though never for both sides of the same relationship. The review runs the same list in reverse: whether the SLA means anything, whether the liability cap leaves you a real remedy, what happens to your data when you leave, and whether the auto-renewal and termination terms let you leave at all. An MSP agreement is signed once and lived with for years, and the exit terms deserve more attention than the price.
Building or reviewing a managed services agreement is clearly-scoped work, so it is typically flat-fee, and you will have the exact number in writing after a free discovery call. That is our no surprise billing policy. Learn how our fees work.
A managed services agreement is the contract between a managed service provider and its client, covering ongoing IT services such as monitoring, maintenance, help desk, backups, and security. It defines the service levels, the remedies when they are missed, data custody, liability limits, and what happens when the relationship ends.
Defined service levels you can operationally meet (uptime, response times by severity), a measurement window, and service credits as the defined remedy for misses. The SLA should also say what is excluded, such as outages caused by the client’s own systems or third-party platforms, because an unqualified promise is a standing breach.
It depends on the agreement, which is exactly why the indemnity and dependency clauses deserve the hardest drafting. Most agreements land on mutual indemnification: the MSP answers for breaches its own stack, negligence, or misconduct caused, and the customer’s obligations and dependencies carve out the harms the customer caused itself. Good practice then limits liability to what each party’s insurance can actually pay.
Up front, before each service period, rather than billed after the services are delivered. Billing in arrears makes your largest customer your largest unsecured credit risk, and we have seen exactly that play out for months at six-figure scale. Pair advance payment with clear suspension rights, so a non-paying customer can be cut off without the MSP breaching its own agreement.
A template can cover the ordinary clauses, and it predictably fails on the ones that decide real disputes, being the SLA remedies, breach responsibility, the liability cap, and data offboarding. Because an MSP signs one agreement across its whole client base, a template’s gaps are multiplied by every client on the roster.
Reviewed by Sukhi Hansra, Business and Franchise Lawyer at Hansra Law.
Free discovery call
Tell us about your situation. We will tell you clearly what it needs and what it does not.
Book your free discovery callNo surprise billing
Written quotes on everything. Flat fees where the scope is clear.
See how our fees work →
SaaS Legal Launch Checklist
The legal items that need to exist before your product takes real users, as a free checklist.
Get the checklist
Most owners deal with the legal side only after something goes wrong. By that time, you could spend tens of thousands of dollars unwinding what a quick conversation could have prevented. It doesn’t have to be that way if you have the right lawyer in your corner!