Scope of work (SOW)

A scope of work is the written agreement of exactly what a project includes, deliverables, timeline, and what's out of scope. A clear one is the single best defence against surprise costs and 'that wasn't included' fights.

A scope of work (SOW) is the document that spells out exactly what a project covers: the deliverables, the timeline and milestones, what each side is responsible for, and, just as importantly, what’s not included. It turns a hopeful conversation into a shared, written understanding both parties can point to.

Its real job is preventing the two most common ways projects go sour: scope creep, where “just one more thing” quietly doubles the work, and the mismatch where a client expected something the studio never planned to build. A good SOW is specific enough that nobody is surprised at the invoice, and honest about the boundaries so the relationship stays healthy. Vague scopes protect no one, least of all the client.

We tighten scope during discovery, before anyone commits. How we structure and price engagements is on pricing.

Quick recall

What is a scope of work? A written agreement of a project’s deliverables, timeline, responsibilities, and exclusions.

Why does it matter? It prevents scope creep and “that wasn’t included” surprises on both sides.

What makes one good? Specific deliverables and clearly stated boundaries, vague scopes protect no one.