Master service agreement template
Stop renegotiating liability and IP on every project. goHeather builds an MSA that settles the legal terms once, so each new engagement is a one-page statement of work instead of a three-week negotiation.
Any country or jurisdiction you tell it- Liability cap and carve-outs you can explain
- Built to sit above your statements of work
- Written for wherever you operate
Recognized by
What is a Master Service Agreement?
The legal terms, agreed once, for everything that follows
A master service agreement is the umbrella contract between a service provider and a client. It settles the terms that do not change from project to project — liability, indemnity, intellectual property, confidentiality, insurance, payment mechanics, termination — and leaves the commercial specifics of each engagement to a separate statement of work.The point is speed. Once an MSA is signed, starting a new project means agreeing a scope, a price and a date on one or two pages. Nobody has to relitigate the liability cap. For a provider running many clients, or a client using the same agency repeatedly, that is the difference between a week and a quarter.An MSA on its own does not commit either side to any work. It is a framework. The obligation to do something, and to pay for it, comes from the SOW underneath it.
What often goes wrong in a MSA
Patterns that come up again and again, and how goHeather handles them.
Signing the vendor's MSA as sent
- The liability cap is three months of fees on a twelve-month commitment
- An indemnity for anything "arising out of or relating to" the agreement, which sits outside the cap
- Bespoke deliverables stay with the provider and you get an internal-use license
- No order of precedence, so a project manager's SOW can override the negotiated terms
- Auto-renewal with ninety days' notice that nobody diaries, so you renew by accident
Building it with goHeather
- goHeather shows the cap against the contract value and explains what it leaves exposed
- Indemnities are tied to specific fault-based triggers, with the cap relationship made explicit
- Deliverables created for you transfer to you; the provider keeps its own tooling
- An order-of-precedence clause protects the terms you negotiated
- Renewal dates and notice windows are tracked so the deadline does not pass unnoticed
From blank page to signed MSA
goHeather is not a template download. It is a contract builder that walks you through the document, powered by the latest AI models.
- Start
Start from scratch or from a template
Describe the deal in your own words, or pick a Master Service Agreement template and work from there. Either way goHeather builds the document with you rather than handing you a file to fill in.
- Answer
Answer questions as it drafts
goHeather asks who the parties are, what the deal covers and where you operate, and writes each clause around your answers as you go.
- Review
See every clause explained
Each clause comes with a plain-English summary of what it does, so you know what the document says before you send it.
- Negotiate
Check what comes back
Upload the other side’s edits and goHeather shows each change against the version you sent, flagged by risk.
- Sign
Send it for signature
Collect e-signatures and keep the executed copy, the key dates and the renewal terms in one place.
20,000+
SMBs and small law firms trust goHeather
$1,419
Average saving vs. a lawyer per deal
10,500+
Lawyer-made templates to draft from
25+
Enterprise-grade security controls
Who needs a Master Service Agreement
Where this document usually shows up, and what else goHeather covers there.
- Procurement
One framework for all vendor spend
Put every engagement with a supplier under one set of negotiated terms, and make each new project a one-page SOW.
See contract AI for procurement
- Professional services
Agencies and consultancies
If you sign repeat clients, your MSA is your most-negotiated document. Review what each client sends back against your own position.
See contract AI for professional services - In-house legal
Reviewing inbound vendor paper
Most MSAs arrive on the other side's template. Get the risky clauses flagged in minutes rather than reading twenty-two pages.
See contract AI for in-house counsel - Review
Check an MSA you were sent
Upload the vendor's master agreement and goHeather flags the cap, the indemnities, the IP split and the renewal trap, with suggested edits.
See how AI contract review works
Your contracts stay yours
A Master Service Agreement carries names, numbers and terms you would not want shared. goHeather protects every document you draft or upload with enterprise-grade controls, end-to-end encryption and trusted AI providers.
Learn more about security
Contracts encrypted with gold-standard protection- Database provider meets bank-grade security
- Your documents and data will never be sold
- We do not use your data to train our models
How MSAs are usually structured
goHeather is a technology company, not a law firm, and this page is not legal advice. It describes what our software does. Nothing here states the law or tells you what your contract needs — for that, talk to an attorney licensed where you operate.
An MSA earns its keep on the second project, not the first. The whole design goal is to move every clause that does not change into a document signed once, so the things that do change can be agreed in a page. The sections below cover how to split the two, where the real risk sits, and the clauses that most often get signed without being understood. None of this is legal advice.
What goHeather covers in a Master Service Agreement
These are the parts of a Master Service Agreement goHeather asks you about while it builds one, and the parts it looks at when you upload one somebody else sent. It is a description of what the product does — not a checklist for your document, and not a view on what yours needs.
- Structure and order of precedence. Says how the MSA and each statement of work fit together, and which wins when they conflict. goHeather flags: Without an order-of-precedence clause, a SOW drafted by a project manager can silently override the liability cap the lawyers negotiated.
- Services and statements of work. Explains that work is performed under SOWs, what a SOW normally contains, and how one is executed. goHeather flags: An MSA that allows work to start on a purchase order or an email leaves the scope undefined and the change control meaningless.
- Fees, invoicing and expenses. Payment mechanics that apply across every SOW: invoicing cycle, payment window, late interest, expense approval and rate changes. goHeather flags: Annual rate increases pegged to nothing, or tied to an index with no cap, compound quietly over a multi-year relationship.
- Intellectual property. Splits ownership between the provider's pre-existing materials and the deliverables created specifically for the client. goHeather flags: Vendor paper often gives the client only a license to bespoke work, so you pay for custom development and do not own it.
- Limitation of liability. Caps each side's exposure, usually at a multiple of fees, and excludes indirect and consequential losses. goHeather flags: A cap measured in months rather than the annual contract value, or one that is mutual on paper but paired with a one-sided indemnity.
- Indemnities. Fault-based promises to cover the other side's losses, typically for IP infringement, data breach and gross negligence. goHeather flags: An indemnity for claims "arising out of or relating to" the agreement is not fault-based and can swallow the liability cap entirely.
- Confidentiality and data. Protects each side's information and sets out how client data is handled, secured and returned. goHeather flags: If personal data is involved you usually need a data processing addendum as well; the MSA confidentiality clause is not a substitute.
- Insurance. Requires the provider to carry stated coverage — commercial general liability, professional liability, cyber — at agreed limits. goHeather flags: An indemnity backed by no insurance requirement is only worth what the counterparty can pay.
- Term, renewal and termination. How long the framework runs, whether it renews, and what happens to open SOWs when it ends. goHeather flags: Terminating the MSA while SOWs are running is a common gap; the agreement normally says whether they survive or fall away.
What goes in the MSA and what goes in the SOW
The rule of thumb: if it would be the same on every project, it belongs in the MSA. If it changes, it belongs in the statement of work. Liability, indemnity, IP, confidentiality, insurance and termination are MSA material. Scope, deliverables, timeline, price, acceptance criteria and named personnel are SOW material.
The clause that makes the structure work is order of precedence. It says which document controls when they conflict — normally the MSA wins on legal terms and the SOW wins on commercial specifics. Without it, a SOW written by someone who has never read the MSA can accidentally rewrite the liability cap.
Be explicit about what a valid SOW looks like and who can sign one. A great many disputes start with work performed on the strength of an email that nobody treated as a contract.
- MSA: liability, indemnity, IP, confidentiality, insurance, term, governing law
- SOW: scope, deliverables, acceptance, schedule, price, key personnel
- Order of precedence, so the SOW cannot override the legal terms by accident
- A named signature authority for SOWs, and a written change-control process
The cap, the carve-outs, and how indemnities get around both
Almost every MSA caps liability at some multiple of the fees. Twelve months of fees paid in the period before the claim is the most common position. Anything measured in weeks or in a handful of months on an annual contract leaves most of the value unprotected.
Then come the carve-outs — the things the cap does not apply to. Typically confidentiality breaches, IP infringement, gross negligence, wilful misconduct, fraud, death or personal injury, and sometimes data breach. Each carve-out is a hole in your cap, so the list is where the negotiation actually happens.
Indemnities are the part people miss. An indemnity is a promise to pay the other side's losses on a specified trigger, and if the drafting does not say the indemnity is subject to the cap, it frequently is not. That is how a contract with a tidy twelve-month cap ends up with unlimited exposure. Read the indemnity and the cap together, always.
Splitting background IP from deliverables
Service providers arrive with things they already own: frameworks, code libraries, methodologies, templates. Those are background IP and they normally stays with the provider, licensed to the client as needed to use the deliverable.
What the provider builds specifically for the client is a different question, and it is the one worth arguing about. If you are paying for bespoke development, an internal-use license is usually not what you thought you were buying — it stops you from selling the business unit, sublicensing to an affiliate, or moving to another supplier and taking the work with you.
A common middle ground is an assignment of the client-specific deliverables, a perpetual license back to the provider for its background materials embedded in them, and a clear statement that generic know-how the provider picks up along the way stays theirs.
Renewal traps and what happens to live projects
Automatic renewal with a ninety-day notice window is standard and catches people constantly. The renewal date passes, nobody diarised the notice deadline, and the contract rolls for another year at rates that may have risen. If you sign an auto-renewing MSA, the notice date belongs in a calendar the moment the ink dries.
The other commonly missed clause is what happens to open statements of work when the MSA terminates. Three answers are possible: the SOWs terminate too, the SOWs survive to completion under the MSA terms, or the parties negotiate. Only one of those is good for a client mid-project, and it is worth checking which one the agreement picks.
Finally, look for transition assistance. A provider who holds your data, your environment or your source code has practical leverage at the exit that no termination clause fixes on its own. A defined wind-down period at agreed rates is worth having before you need it.
Why goHeather asks where both parties operate
An MSA is usually the longest-lived contract in a commercial relationship, so the choice of which state's law governs it carries further than it does in a one-off agreement — it shapes how the liability cap, the indemnities and the exclusions get read years later. Some states are chosen routinely for commercial work because the ground is well trodden there. goHeather asks where both parties operate, what the services involve and whether personal data is in scope, then builds to those answers and prompts for a data processing addendum where one belongs. It does not tell you which governing law to pick, or how a cap would be interpreted under it. On an MSA that will carry significant spend, that is worth a commercial attorney's view before signature.
Before you go. goHeather is a technology company, not a law firm. We do not provide legal advice, legal opinions, or any view on whether a contract or a clause will hold up. Everything above describes what our software does when you build or upload a document. Rules differ from state to state and change over time, and what is right for your business depends on facts we do not have. Have an attorney licensed where you operate review anything that matters.
Other contracts goHeather builds
goHeather drafts any business contract. These are the ones that usually travel with this one.
- Projects
Statement of Work template
Define one project: what gets built, by when, for how much, and how you know it is done.
See the SOW template - Services
Service Agreement template
One engagement, start to finish: what you will do, what you get paid, and what happens if it goes wrong.
See the service agreement template - Software
SaaS Agreement template
Sell or buy hosted software: subscription terms, uptime commitments, data ownership and what happens at the exit.
See the SaaS agreement template
Need a different contract?
goHeather drafts any business contract, not just the ones listed here. Browse every template or start from a blank brief.
MSA template questions
What people ask before they build a Master Service Agreement.
Still have questions?
Build a MSA and see what goHeather produces, or book a short demo and we will go through one of your own documents with you.
Trusted by 20,000+ SMBs and small law firms
Get your MSA settled once
Build a master service agreement you can reuse for every project, or upload the one a vendor sent and see what goHeather flags in the cap and the indemnities.
Free to try