SOW generator. Scope of work.
Build a statement of work with deliverables, milestones, acceptance criteria, and priced phases. Download a multi-page branded PDF. Browser-only; nothing leaves your device.
Parties, scope, milestones, price.
Engagement total.
An SOW is the contract underneath the project.
A statement of work is a structured scope document defining what a vendor will deliver, how, by when, and for how much. Unlike a quote (which is a price for a scope), an SOW names the deliverables individually, sets acceptance criteria, maps milestones to a timeline, and anchors the payment schedule to named events. It is the document that turns a handshake into an enforceable service contract. Most mid-market service disputes reduce to: "what did the SOW actually say?" A written SOW answers the question; a verbal agreement does not.
The most valuable section in any SOW is the one most vendors skip: "Out of scope." Naming what you will NOT deliver closes the largest source of service-engagement friction - the gap between what the client assumed was included and what the SOW actually covers. For a brand-identity SOW, out-of-scope might include: video production, print collateral, website redesign, ongoing brand maintenance. The client reads the list, sees what needs a separate engagement, and either accepts the boundary or adds budget before the SOW is signed. The alternative - discovering the scope gap mid-engagement - is always more expensive than naming it up front.
Pricing structure matters more than the total. Three patterns: fixed price (vendor absorbs scope risk), milestone-based (the most common mid-market pattern, typically 30/40/30 or similar), and time-and-materials (client absorbs scope risk). Mature service vendors default to milestone-based fixed pricing with a separate T&M clause for out-of-scope change requests. This transfers the predictable work to a fixed price the client can budget against, while preserving a clean billing path for the unpredictable parts. Reference documents in the ALA's MSA+SOW guidance and tools like DocuSign have standardized the countersignature flow.
Acceptance criteria are the habit that separates professional service contracts from amateur ones. Every deliverable gets a specific, testable bar: Design system delivered in Figma with components, color tokens, and type scale documented; approved by named stakeholder. Software feature shipped to production passing 12 named test cases; signed off by PM. Without these, the client can delay "acceptance" indefinitely and push the invoice to the right of the calendar. With them, both sides know exactly when the milestone is complete and when the money moves.
Related tools: Quote generator for shorter engagements where a full SOW is overkill. Invoice generator for milestone billing. Purchase order generator for the buyer side. Receipt generator for payment acknowledgment.
Seven answers.
What is a statement of work and when do I need one?
A statement of work (SOW) is a detailed scope document that defines what a vendor will deliver, how, by when, and for how much. It is more comprehensive than a quote (which is a price for a scope) and more specific than a master services agreement (which is the umbrella contract). You need an SOW any time the engagement lasts longer than 60 days, involves multiple deliverables or milestones, or has acceptance criteria the client will check against. Below that threshold a priced quote is usually sufficient.
What sections belong in an SOW?
Seven sections. Project background (one paragraph on why the work exists). Objectives (2-4 bullets on what success looks like). In-scope and out-of-scope lists. Deliverables (named, with acceptance criteria). Milestones with dates. Pricing (fixed or phased). Assumptions and dependencies. Optionally an eighth section for change-control language. The single most-skipped section is out-of-scope. Naming what you will NOT deliver closes the largest source of service-engagement disputes - the gap between what the client assumed and what the SOW covered.
What is the difference between an MSA and an SOW?
A master services agreement (MSA) is the contract framework: legal terms, IP ownership, liability, termination, indemnification, payment norms. It is signed once and governs the relationship. A statement of work (SOW) is issued per engagement under the MSA, naming the specific project scope, deliverables, and price. A typical mid-market engagement has one MSA and many SOWs over time. For a first-time engagement with a new client, a single SOW document can include abbreviated MSA-style terms and serve both functions.
Should pricing be fixed, milestone-based, or time-and-materials?
Three patterns with distinct trade-offs. Fixed price transfers scope risk to the vendor - the vendor absorbs any overage on a scope that cannot change. Milestone-based splits the total into discrete drops (30/40/30 at kickoff / mid / final is common) - this is the most common mid-market pattern. Time-and-materials (T&M) bills hourly against an estimate and puts the cost risk on the client - used when scope is genuinely unknown at signing (research, discovery, production ops). Most mature service vendors default to milestone-based fixed pricing with a separate T&M clause for out-of-scope change requests.
What are acceptance criteria and why do they matter?
Acceptance criteria are the specific tests a deliverable must pass for the client to accept it (and for the vendor to invoice against it). For a design deliverable: Final artwork delivered in PDF and AI formats, Lighthouse a11y score above 95, approved by named stakeholder. For a software deliverable: Feature shipped to staging, passes 12 named test cases, signed off by PM. Without acceptance criteria, the client can delay acceptance indefinitely (which delays payment). With them, both sides have a clear bar to hit and the invoice schedule becomes enforceable.
How do I handle scope changes after the SOW is signed?
Include a change-control clause. Standard language: Any change to the scope, deliverables, milestones, or price described in this SOW requires a written change order, signed by both parties, before work on the change begins. The change order itself is a one-page addendum: what changed, why, impact on deliverables, impact on timeline, impact on price, both signatures. The habit that pays off for service businesses is: every change request, no matter how small, gets a change order even if priced at zero. This is what prevents scope creep from eating margin silently.
Does this tool save my SOWs?
No. Every value you enter lives in memory for this browser tab only. Nothing is transmitted to a server, stored in a database, or synced across devices. Close the tab and the data is gone. The Download PDF button builds the file in your browser using jsPDF and saves it to your device; that file is the only record.
Contracts are operational design.
Our SaaS and growth-strategy engagements ship SOW + MSA templates tuned to your business, change-control workflow, and a billing model your team can execute. Scoped quote in 48 hours.