In short
A master services agreement (MSA) sets the legal and commercial terms that govern an ongoing relationship, while individual statements of work (SOWs) capture the scope, price and timeline for each project underneath it. This structure avoids renegotiating liability, IP and payment terms every time new work is scoped, and is the standard structure for repeat engagements and enterprise procurement.
Why split the agreement in two
Businesses that run repeat projects with the same client — software development, marketing retainers, consulting programs — waste time renegotiating the same liability and payment terms on every new engagement. An MSA fixes the framework once: liability, IP, confidentiality, dispute resolution, termination. Each SOW then only needs to cover what's actually different — scope, deliverables, fees and timeline for that project.
This structure is also what most enterprise procurement teams expect. Larger clients frequently issue their own MSA and ask suppliers to sign onto it, so understanding how to negotiate MSA terms — and knowing which clauses to push back on — protects margin across every SOW signed under it, not just the current deal.
Getting the precedence clause right
The MSA needs an explicit order of precedence clause stating that, where a SOW conflicts with the MSA, the MSA prevails unless the SOW expressly states otherwise for that clause. Without this, ambiguity in a hastily drafted SOW can unintentionally override carefully negotiated liability caps in the master agreement.
SOW template and scope discipline
We build a standard SOW template with mandatory fields — deliverables, acceptance criteria, milestones, fees, key personnel and a variation mechanism — so project managers on both sides can issue new SOWs quickly without legal involvement each time, while staying within the guardrails set by the MSA.
Liability aggregation across multiple SOWs
One of the most contested points in MSA negotiations is whether the liability cap applies per SOW or in aggregate across all SOWs signed in a 12-month period. An aggregate cap can leave you exposed once several projects are running concurrently; we typically negotiate for per-SOW caps, or an aggregate cap that resets annually, depending on your risk appetite.
Termination of individual SOWs versus the whole relationship
The MSA should distinguish between terminating a single SOW for that project's non-performance and terminating the master relationship entirely. We draft so that a dispute or failure on one project doesn't automatically unwind every other active engagement, unless that's genuinely what both parties want.
Fitting in with procurement and vendor onboarding
For businesses selling into larger organisations, we also review the client's own MSA paper when they insist on their template, focusing on liability, IP assignment, audit rights and payment terms, and negotiate the specific clauses that create disproportionate risk relative to the value of the engagement.
What the fixed fee covers
- Master services agreement covering liability, IP, confidentiality and dispute resolution
- Standard statement of work (SOW) template with variation mechanism
- Order of precedence and liability aggregation clauses
- Termination structure distinguishing SOW-level and relationship-level exit
- Review of counterparty MSA paper where the client supplies their own template
- One round of negotiation support
Mistakes we see
- No precedence clause, so a poorly drafted SOW accidentally overrides the MSA's liability cap
- Liability caps aggregated across all SOWs, exposing the business once multiple projects run concurrently
- SOW templates missing acceptance criteria, leading to payment disputes over 'done'
- Terminating the whole MSA when only one underperforming SOW needed to end
- Signing a client's MSA without review because the individual project value looks small
Who this is for
- Software development and IT services providers with repeat client engagements
- Marketing and creative agencies on retained programs of work
- Consulting firms delivering multiple concurrent projects to the same client
- Businesses selling into enterprise procurement processes
Frequently asked questions
- Do I need a lawyer to review every SOW once the MSA is in place?
- No — that's the point of the structure. Once the MSA is settled, SOWs using the agreed template can generally be issued and signed by commercial teams without legal review, provided they don't attempt to vary the MSA's core terms.
- What if the client sends back a heavily marked-up SOW?
- If the mark-up only changes scope, price or timeline, that's a commercial negotiation your team can handle. If it attempts to change liability, IP or termination terms, it's effectively trying to amend the MSA through the back door and should come back to us before signing.
- Can an MSA cover work in multiple jurisdictions across Australia?
- Yes. We include a governing law and jurisdiction clause, generally NSW or Victoria depending on where the business operates, and the MSA applies nationally to all SOWs issued under it unless a specific SOW states otherwise.
- What happens if we never sign a formal MSA and just keep emailing SOWs?
- Without a master agreement, each SOW is potentially a standalone contract with no consistent liability cap, IP position or dispute process, and gaps get filled by default legal rules that rarely favour the service provider. We regularly get called in after a dispute arises specifically because this happened.
- Should the MSA have a fixed term or run indefinitely?
- Most MSAs run indefinitely subject to termination on notice, since the relationship is intended to be ongoing. We build in periodic review triggers so commercial terms like rate cards can be revisited without terminating the whole agreement.
Related