Definition
A Statement of Work (SOW) is a formal, legally binding document that defines the project-specific activities, deliverables, timelines, and pricing for services provided by a vendor to a client. It is the operational blueprint that dictates exactly what constitutes project success and payment.
Explanation
In the B2B services sector (IT consulting, agencies, MSPs), the SOW is the single most critical commercial document you will sign.
While the proposal is a sales and marketing document designed to win the heart and mind of the buyer, the SOW is a risk-management document designed to protect the business. A poorly written proposal might cost you the deal; a poorly written SOW can cost you the business by locking you into unprofitable, endless work.
The SOW is the primary defense against [Scope Creep](/glossary/scope-creep) and [Margin Leakage](/glossary/margin-leakage). When a client inevitably asks for "one more feature," the SOW is the document the project manager points to when saying, "That sounds great, let's write a Change Order for that."
Critical Components of a Bulletproof SOW
A professional-grade SOW must contain the following sections to be commercially viable:
- Project Objectives: A high-level summary of the business goals the project achieves.
- Scope of Services: The specific tasks the vendor will perform (quantified wherever possible).
- Deliverables: Tangible outputs (e.g., "1x Figma Prototype containing 5 screens").
- Timeline & Milestones: When specific phases begin and end.
- Pricing & Payment Terms: How much it costs and when payments are triggered (e.g., "30% upfront, 40% at UAT, 30% at Go-Live").
- Assumptions & Client Responsibilities: What the vendor relies on the client to do (e.g., "Client will provide API access by Week 1").
- Exclusions (Out of Scope): Explicitly stating what is not included.
- Acceptance Criteria: The objective definition of "done" that triggers final payment.
SOW vs Proposal Diagram
```mermaid graph LR A[The Proposal] -->|Goal: Persuasion| B(Focus: Why choose us?) A -->|Tone: Marketing| C(Metrics: ROI & Value)
D[The SOW] -->|Goal: Protection| E(Focus: What exactly will we do?) D -->|Tone: Legal & Operational| F(Metrics: Deliverables & Milestones) ```
Commercial Checklist for SOW Review
Before signing, an SOW must pass these tests:
- The "How Many" Test: Are all deliverables quantified? (e.g., "Design 3 templates," not "Design templates").
- The "Delay" Test: If the client takes 3 weeks to review a document, does the SOW protect your timeline and prevent your team from sitting idle?
- The "Acceptance" Test: Can the client arbitrarily reject a deliverable, or are the criteria objective?
- The "Change" Test: Is the Change Order process explicitly stated?
Related Concepts
- [Scope Creep](/glossary/scope-creep)
- [Change Order](/glossary/change-order)
- [Deliverable](/glossary/deliverable)
- [MSA (Master Services Agreement)](/glossary/msa)
What is the difference between an SOW and an MSA?+
An MSA (Master Services Agreement) governs the overall legal relationship (liability, IP, payment terms, confidentiality) across all projects. An SOW (Statement of Work) is a child document governed by the MSA that defines the specific scope, deliverables, timeline, and pricing for a single project.
Is an SOW legally binding?+
Yes. Once signed by both parties, an SOW is a legally binding contract that dictates exactly what must be delivered and what must be paid.
Who should write the SOW?+
While Sales may draft the initial proposal, the final SOW should always be written or strictly reviewed by the Delivery team or Pre-Sales Engineers who are responsible for executing the work.
Gerelateerde dienst
Wilt u dat wij deze workflow voor uw kantoor uitrollen?