If the MSA is the law, the SOW is the job. It names what will be delivered, by when, for how much, and on what basis it is accepted.
Almost every money dispute in a services relationship starts here rather than in the MSA. A vague SOW invites scope creep on one side and disappointed expectations on the other, and no amount of well-drafted legal boilerplate rescues a project where nobody wrote down what "done" looks like.
A tight SOW names specific deliverables rather than activities, states assumptions and dependencies, ties payment to identifiable milestones, and points at objective acceptance criteria. It should also say what is explicitly out of scope — that sentence prevents more arguments than any other.
"Deliverables: (1) migration plan, (2) migrated production environment, (3) two training sessions. Out of scope: ongoing support, third-party license fees."
Worried about this clause in your own contract?
Sidecar reads your vendor agreements and flags the clauses that put your business at risk — in plain English, before you sign. Your first review is free.
Definitions and negotiation guidance here are educational business decision support, not legal advice. Consult an attorney about how any clause applies to your own agreement.