In plain English
An MSA sets the legal terms of the relationship, an order form specifies what is being bought and for how much, and a SOW describes the work to be delivered. Most SaaS deals use an MSA plus order forms; services deals add a SOW.
Educational only. Not legal advice.
By version90 staff Published Updated How this was made
Download: the one-page comparison chart (PDF). Free, no email required. Print it, pin it in the deal desk channel, or hand it to the new AE.
How do an MSA, a SOW, and an order form compare?
| MSA | Order form | SOW | |
|---|---|---|---|
| Purpose | Legal terms for the whole relationship | What is bought, how much, for how long | The work to be delivered, and how it is accepted |
| Who signs it | Someone with authority to bind the company, often a founder, CFO, or GC | Usually the budget owner or an authorized signer | Usually the project sponsor or an authorized signer |
| How often it changes | Rarely; renegotiated every few years | Every purchase, upsell, and renewal | Every project or phase |
| What it references | Nothing above it; it is the parent | The MSA it sits under, by name and date | The MSA it sits under, by name and date |
| Typical length | 10 to 30 pages | 1 to 3 pages | 3 to 15 pages |
The short version: the MSA holds the risk, the order form holds the money, and the SOW holds the work.
How do the three documents stack?
Picture a parent and its children. You sign the MSA once. Every purchase after that is an order form under it, and every project is a SOW under it. The children inherit the MSA's legal terms, so they can stay short.
Which document wins in a conflict?
The order of precedence clause decides. It is a short paragraph, usually in the MSA, that ranks the documents so a conflict has an answer before anyone argues about it. A common pattern:
- The order form, for the commercial terms it expressly covers (price, quantity, term).
- The SOW, for the scope it expressly covers.
- The MSA, for everything else.
Some companies flip it so the MSA always wins, which stops a SOW from quietly lowering a liability cap. Either approach works. What does not work is silence: without a precedence clause, a Net 30 in the MSA and a Net 60 in the order form leave you with two answers and no tiebreaker.
A useful refinement is to let child documents override the MSA only when they say so explicitly ("notwithstanding Section 9 of the MSA..."). That keeps casual drafting in an order form from rewriting legal terms by accident.
What is an MSA, and what should you track from it?
A master services agreement is the legal framework for everything you will ever buy from or sell to one counterparty. It covers liability and its cap, indemnity, IP ownership, confidentiality, data protection, warranties, termination, and governing law. It is drafted by whichever side has the stronger paper (usually the vendor in SaaS) and negotiated by legal or a founder.
The MSA should be boring. If you renegotiate it every quarter, something upstream is broken. For the full primer, see What Is an MSA?, and for a structured review pass, the Startup MSA Redline Checklist.
What to record from every MSA:
- Effective date and version, so every child document can cite the right one
- Term and termination rights, including termination for convenience
- Liability cap and what it is measured in (see how liability caps work for startups)
- Payment terms default, if the MSA sets one
- Precedence clause, and which way it runs
- Assignment and change of control, which matters the day you raise or get acquired
What is an order form, and what should you track from it?
An order form is the commercial snapshot of a single purchase: which products, how many seats or units, at what price, for what term, billed how. It is sometimes called an order schedule, sales order, or quote. Sales or deal desk drafts it, usually from a template in the CRM or CPQ tool, and the customer's budget owner signs it.
An order form is legally binding once signed. It is short because it incorporates the MSA by reference and leans on it for everything legal.
What to record from every order form:
- Start date, end date, and renewal type (auto-renew or manual)
- Notice period for non-renewal, which sets the real deadline, not the end date (more in auto-renewal clauses and notice windows)
- Contract value: ACV, TCV, and any ramp
- Payment terms and billing frequency
- Discounts and price-increase caps at renewal
- Which MSA it sits under, by name and date
What is a SOW, and what should you track from it?
A statement of work describes a specific piece of work: objectives, deliverables, milestones, timeline, who does what, assumptions, and how the customer accepts the result. It often carries its own fees, either fixed or time and materials. A services lead or solutions engineer drafts it, and it is signed at the start of each project or phase.
In sales, a SOW usually shows up for implementation, onboarding, custom development, or training that sits alongside a subscription. A good SOW makes "out of scope" obvious without a lawyer.
What to record from every SOW:
- Fees and payment milestones, especially anything tied to acceptance
- Acceptance criteria and deadline, since revenue recognition may depend on it
- Change-order process, so scope creep has a price
- End date, and whether the SOW can be extended
- Which MSA it sits under, by name and date
Which documents do you need for your deal?
| Deal type | Documents | Why |
|---|---|---|
| SaaS subscription | MSA + order form | The product is standard; only the commercial terms change per deal. |
| Services | MSA + SOW | The work is custom, so it needs a narrative scope and acceptance criteria. |
| Hybrid (software plus implementation) | MSA + order form + SOW | Risk in the MSA, money in the order form, work in the SOW. |
| Pilot or proof of concept | Short-form agreement, or MSA + order form with a pilot term | Keep it light, but do not sign a pilot on terms you would refuse for the full deal. The pilot paper often becomes the production paper. |
Some vendors use a single "subscription agreement" that folds the MSA and order form into one document. That is fine for small, one-off deals. It gets painful at the first upsell, when you have to decide whether to amend the whole thing or bolt on a new order form it never anticipated.
What mistakes do 100-person startups make with MSAs, SOWs, and order forms?
A SOW that contradicts the MSA. A project manager drafts the SOW from an old template, it says "Vendor's liability for this engagement is limited to fees paid under this SOW," and nobody notices that the MSA cap was twelve months of all fees. Depending on precedence, you may have just lowered your cap for this work.
No precedence clause. Every conflict becomes a negotiation after the fact, usually at the worst moment.
Order forms that restate legal terms. Sales adds "Customer may terminate at any time with 30 days' notice" to close a deal. That line now sits in a signed document that may override the MSA's termination section. Keep legal terms in the MSA; if a deal needs an exception, write it as an explicit exception.
Losing track of which MSA an order form belongs to. A customer signed your 2023 MSA, then a 2025 MSA when they switched entities. Your renewal order form says "subject to the Master Services Agreement between the parties." Which one? Cite the MSA by name and date every time.
Auto-renewal dates that live only in the PDF. The order form auto-renews with a 60-day notice window, and nobody put the notice date in a calendar or the CRM. You find out when the invoice arrives.
Signing the pilot on the customer's paper "just for now." The pilot terms quietly become the terms for the full rollout because nobody wants to reopen them.
About this page
Who. Written by version90 staff at Latent Ape LLC, the company that builds version90, working with AI tools. We build contract software and run our own contracts through it; we are not a law firm, and nothing here is legal advice.
How. Each piece starts from the review workflow version90 is built around. AI drafts and structures the text; staff edit, fact-check, and rewrite it before it is published, and we update the date shown above whenever the substance changes.
Why. The library exists to give founders and ops teams a shared standard for reviewing contracts without a legal department. If you spot an error, email [email protected] and we will fix the page.