Flamingo Raises $4.5M Seed Round

Skip to content

Managed services agreement: the clauses that decide who pays

Best Practices
MSP
Business
Aliaska VarievaAliaska Varieva
November 9, 2026
14 views
Managed services agreement: the clauses that decide who pays

What a managed services agreement is, how it differs from a SOW and an SLA, the clauses that decide disputes (scope, SLAs, pricing, liability caps, termination, data ownership, offboarding) and the red flags for MSPs and for clients.


Updated: November 2026

A managed services agreement gets read twice: once when it's signed, and once when something goes wrong and everyone wants to know who pays. The second reading is the one it should be written for. This guide covers what an MSA is, the clauses that decide the outcome, how it fits with the SOW and SLA, and the red flags on both sides of the table.

TL;DR

  • The definition. A managed services agreement (MSA) is the contract that sets the legal terms for ongoing IT services between an MSP and a client.
  • The stack. MSA for legal terms, SOW for the work, SLA for response times.
  • The clauses that bite. Scope, liability caps, auto-renewal, termination and data return.
  • For MSPs. Cap liability, list exclusions, and match the cap to your insurance.
  • For clients. Read the exit before the price.

What a managed services agreement is

A managed services agreement is the contract an MSP and a client sign before any ongoing work starts. It covers what's included, what it costs, how fast the MSP responds, who's liable for what, and how either side walks away. One-off projects can live on a quote. Recurring work, with remote access to every device the client owns, needs more.

You'll see "MSA" used for two things. A managed services agreement is often one document with everything inside. A master services agreement is a frame that holds only the legal terms, with services added through schedules or statements of work. Some MSPs use the master version and call it a managed services agreement anyway. What matters is that the legal terms sit in one place and the changeable parts (devices, prices, services) sit somewhere easy to update.

Not legal advice, by the way. This is how the clauses work in practice. Have a lawyer who knows your state and your services review the final version.

MSA vs SOW vs SLA

Three documents, three jobs. Mixing them up is how a response-time promise ends up buried in a liability clause nobody reads.

DocumentWhat it answersHow often it changesExample line
MSA (managed or master services agreement)The legal relationship: liability, term, termination, data, payment termsRarely, maybe once a year"Liability is capped at fees paid in the prior 12 months."
SOW (statement of work)The specific work: services, devices, users, deliverables, priceEvery new service or project"Monitoring and patching for 45 workstations and 2 servers."
SLA (service level agreement)How fast and how well: response times, priorities, uptime, remediesWhen service tiers change"Priority 1 tickets get a response within 1 hour, 24x7."

The SLA can sit inside the MSA as a schedule or stand alone. Either works, as long as the MSA says which document wins when they conflict. Our guide to what an SLA is covers how to write the targets themselves.

The clauses that matter

Contracts run long because lawyers like completeness. A handful of clauses decide how the relationship goes, and the rest is plumbing.

Scope of services

Scope is where the arguments start. "All-inclusive IT support" sounds generous until the client asks you to move their office, build a new website and fix the CEO's home printer.

Write the inclusions as outcomes and the exclusions as a list. Projects, hardware, third-party software support, after-hours work and on-site visits are the usual exclusions. Name the rate for out-of-scope work so nobody negotiates it mid-crisis. Tie the price to counts (users, devices, sites) and say how often you true them up.

Toolsets are a scope question too. Should the MSA name every tool you run, or describe the service and keep the stack flexible? This r/msp thread works through it, from naming sub-processors on a public page to "we sell outcomes, not a toolset."

The pattern that holds up: describe the service in the MSA, keep a sub-processor list on a page the MSA points to, and commit to notice before a tool that touches client data changes.

Service levels and remedies

Promise response times, not resolution times. You control when a tech picks up a ticket. You don't control when a SaaS vendor fixes its outage. Define the priorities in plain words ("Priority 1: the whole office can't work") so the client can't label every ticket urgent.

Then say what happens when you miss. Service credits are common, usually a percentage of that month's fee, and the MSA should say whether credits are the client's only remedy. Without that line, a missed SLA can turn into a breach-of-contract claim.

Pricing, increases and true-ups

The price itself goes in the SOW. The MSA sets the rules around it: payment terms, late fees, and how prices change. Vendors raise prices mid-term, and your contract needs a way to pass that through. A fixed annual increase or a CPI-linked cap is easier to sell than an open "we may adjust pricing."

Add a true-up clause. Count users and devices monthly or quarterly and bill the difference. Our MSP pricing models guide covers per-user, per-device and tiered pricing, and which one keeps true-ups simple.

Liability caps and indemnity

This is the clause that matters most when a client gets breached. Without a cap, an MSP that bills $3,000 a month can face a claim for the client's whole loss.

Caps are usually tied to fees. One structure from MSP-focused law firm Scott & Scott caps the MSP's liability at the greater of its professional liability insurance proceeds or six months of client payments. Twelve months of fees is another common anchor. Pair the cap with an exclusion of indirect and consequential damages, like lost profits.

Carve-outs come next. Gross negligence, wilful misconduct and breach of confidentiality are often uncapped or carry a higher "super-cap." Clients push hardest on data breaches, so expect to negotiate that one. Indemnity should run both ways. The client covers claims from its own users and data, and you cover claims from your own negligence.

The cap only protects you if insurance stands behind it. Check your E&O and cyber limits against the cap before you sign. Our guide to cyber insurance requirements covers what carriers ask for in 2026.

Term, renewal and termination

Initial terms usually run one to three years, with auto-renewal for the same period. The renewal clause sets a notice window, often 30 to 90 days before the end date. Miss it and you're signed up for another year.

Termination has two doors. Termination for cause lets either side leave after a material breach the other side doesn't fix within a cure period, often 30 days. Termination for convenience lets a side leave without a reason, usually with notice and sometimes a fee. Spell out what happens when a client stops paying: when you can suspend service, and what you keep doing during the dispute.

That last scenario is the one that ends up in court. In this episode of From the Trenches, MSP attorney Tom Fafinski and MSP founder Alexander Caplan walk through collections, why a 28-page MSA can kill its own deal, and what happens when a client stops paying.

Data ownership and security responsibilities

The client owns its data. The MSP owns its own scripts, documentation templates and tools. Write both down, because a fight over who owns the documentation always comes up at offboarding.

Security responsibilities need the same clarity. Say which controls you run, which ones the client has to buy, and what happens if the client refuses a recommended control. A signed risk acceptance for a declined MFA rollout or a declined backup upgrade is cheap insurance. Clients in regulated industries need an addendum on top, like a HIPAA business associate agreement or a GDPR data processing agreement.

The clauses nobody reads until they matter

Some clauses look like boilerplate and still decide real disputes. Non-solicitation stops the client from hiring your tech after you've trained them on their environment. It usually runs during the term plus 12 months, often with a placement fee instead of a ban.

Confidentiality protects both sides. The client's data stays private, and so do your internal processes and pricing. Governing law and dispute resolution decide where a fight happens and how: a court in your county, or arbitration. For a small MSP, a dispute in the client's state three time zones away costs more than the invoice.

Client insurance belongs here too. The same Scott & Scott structure asks the client to carry its own cyber coverage, so its policy pays first when it gets breached. Add a clause for changes in law, so a new regulation that changes the work becomes a scope change, not free labor. And add an order-of-precedence line that says which document wins when the MSA, SOW and SLA disagree.

Offboarding and transition

Every MSA ends, and the clause on how it ends decides whether the client leaves on good terms. Commit to transition assistance at stated rates. List what gets handed over: admin credentials, documentation, domain and DNS access, license ownership, and backup copies. Set a timeline and an order for the steps.

Don't hold data hostage over an unpaid invoice. It feels like a bargaining chip. In practice it creates a liability bigger than the invoice, and in regulated industries it can breach the client's own legal duties. Settle the money through the payment terms and hand the data back. Our client offboarding checklist has the full step list for the MSP side.

Offboarding is also where tool lock-in shows. Agents you can remove by script and data you can export in open formats turn a handover into a day's work. That's part of why we built OpenFrame on open-source components: nobody, client or MSP, should need a hostage negotiation to leave.

Red flags for MSPs writing an MSA

An MSA with no liability cap is the big one. So is a cap with nothing behind it, set at $1 million while your E&O policy covers half that.

Vague scope comes next. "All IT needs" with no exclusion list turns every project into free work. Missing price-change language means you eat every vendor increase until renewal.

Watch your own vendor terms too. If your RMM, EDR or backup contract runs three years with a cancellation fee and your client contract runs one, a client leaving early leaves you holding the bill. Line up your client terms with your vendor commitments, or price the gap in.

Finally, don't copy a template from the internet and ship it. Templates are a starting point. Your services, your state and your insurance are specific, and the contract should be too.

Red flags for clients buying managed services

If you're on the buying side, check these before the price:

  • auto-renewal with a 90-day or longer notice window and no reminder;
  • an early termination fee equal to every remaining month of the term;
  • admin credentials, domains or licenses registered to the MSP, not to you;
  • no clause on data return, format and timeline at exit;
  • an SLA with targets but no remedy when they're missed;
  • liability capped at one month of fees, with data breaches not carved out;
  • price increases at the MSP's discretion, with no cap.

None of these alone means walk away. Three or more means negotiate before you sign. Our list of questions to ask an MSP before signing covers the conversation around the contract.

The short version

The MSA holds the legal terms, the SOW holds the work, and the SLA holds the clock. Get scope, liability, renewal, data ownership and offboarding right, and the rest mostly takes care of itself.

For MSPs, the contract is the one tool that protects margin when everything else fails. For clients, it's the exit plan you hope you never need. Write it for the day things go wrong, because that's the only day anyone reads it.

Aliaska Varieva

Aliaska Varieva

VP of Engineering

Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.

Related Content

Frequently Asked Questions

/blog/managed-services-agreement

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions