How to Write a Scope of Work for a Graphic Design Company
Learn how to write a scope of work for a graphic design company that caps revision rounds, locks usage rights, and looks like your craft.
How Waxe writes your graphic design scope of work
- 1
Capture the engagement
Tell Waxe the client, the brand stage, and what they think they are buying. Waxe turns 'just a logo' into the real engagement: discovery workshop, design direction, logo suite, and a full visual system, so the objectives reflect the strategy behind the work.
- 2
Itemise the workstreams
Waxe breaks the project into the workstreams your studio actually runs and tags effort against each one. The creative brief, moodboards, brand mark variations, and guidelines document each appear as a line a client can read, making the fixed project fee feel earned rather than arbitrary.
- 3
Cap the rounds and acceptance
Waxe writes deliverables with revision caps and acceptance criteria that define exactly what a round is. 'Done' becomes a checklist, not an opinion, so unlimited-revision creep is closed off before the project even starts and your margin stays intact.
- 4
Lock rights and exclusions
Waxe states usage rights, source files, and the final artwork licence in plain language, tied to milestone payment. The out-of-scope and exclusions list captures everything outside the brief, so ownership and extra requests are never contested after handoff.
- 5
Design it like brand work
Waxe renders the scope of work in your colour, typography, and logo system, so it looks like a sample of your craft rather than a plain quote. You review the designed document, adjust a line if needed, and send. The whole pass takes about five minutes for a few cents.
What goes into a Scope of Work
- 1Project summary & objectives
Project summary & objectives frames what the client is really buying, turning 'just a logo' into a strategy-led identity engagement with clear goals.
- 2Itemised workstreams & effort
Itemised workstreams & effort lists each phase, from discovery workshop to brand guidelines, with effort tagged so the fixed project fee is visibly justified.
- 3Deliverables
Deliverables names exactly what you hand over: the logo suite, colour and typography system, guidelines document, asset templates, and final artwork.
- 4Milestones & timeline
Milestones & timeline paces the project against discovery, concepts, and final artwork, tying each stage to a payment point in your fixed-fee model.
- 5Acceptance criteria
Acceptance criteria defines what 'approved' means for each deliverable and what counts as one revision round, removing the ambiguity that drives disputes.
- 6Assumptions & dependencies
Assumptions & dependencies records what you rely on from the client, such as brand inputs, timely feedback, and the licence and source-file transfer terms.
- 7Out-of-scope & exclusions
Out-of-scope & exclusions states plainly what the engagement does not cover, so extra concepts and rounds become priced add-ons rather than unpaid work.
What's included in your scope of work
- Objectives that reframe 'just a logo' as a strategy-led identity engagement
- Itemised workstreams with effort, from discovery workshop to final artwork
- Deliverables covering the logo suite, visual system, and guidelines document
- Revision caps with a clear definition of what counts as one round
- Acceptance criteria that make approval a checklist, not an opinion
- Usage rights, licensing, and source-file transfer stated upfront
- An explicit out-of-scope and exclusions list to protect your margin
- A designed layout in your colour, typography, and logo system
The old proposal vs the waxTable way
Why studios write their scope of work in waxTable
Revision caps that hold
Every deliverable carries an explicit round limit and a definition of what one round is. Extra requests fall into exclusions and become priced add-ons. Unlimited revisions stop quietly draining the margin on your fixed project fee.
Rights settled upfront
Usage rights, the final artwork licence, and source-file transfer are written in plain language and tied to milestone payment. Ownership is agreed before kickoff, so nobody disputes who owns what long after the project ships.
A document that shows your craft
The scope of work renders in your colour, typography, and logo system instead of plain text. The proposal becomes the first sample of your quality, so a visual studio is no longer undercut by a grey quote.
Value the client can see
Itemised workstreams expose the discovery, strategy, and rounds behind 'just a logo'. Effort against each line justifies the fee, so a bespoke identity engagement stops being compared to a template marketplace on price alone.
Minutes, not two days
Waxe drafts the full itemised, designed scope of work from a short brief. What used to take two days of copy-paste and reformatting now takes about five minutes for a few cents, leaving you time to design.
Our promise
I turn 'just a logo' into an itemised, designed scope of work that caps the rounds and locks the rights. The proposal looks like your brand work, so the client sees craft before they see a price. That is how a studio stops competing with template marketplaces.Waxe, your AI operations manager
Questions, answered
What should a graphic design scope of work actually define?
It draws the boundary of the engagement so nobody argues later. The document opens with project objectives, then itemises each workstream with effort, the deliverables you hand over, and the milestones that pace the project. It states acceptance criteria so 'done' is not a feeling, lists the assumptions and dependencies you rely on, and ends with an explicit out-of-scope list. For a studio, that last list is where 'just add another logo concept' stops eroding your margin.
How does the scope of work stop unlimited revisions from killing margin?
Most disputes start because the proposal never said what a round is. waxTable writes the deliverables and acceptance criteria to cap rounds explicitly, naming how many revisions each concept includes and what counts as one round. Anything past the cap moves into the out-of-scope and exclusions section, so extra work becomes a priced add-on instead of unpaid labour. Because your model is a fixed project fee by scope and rounds, the scope and the fee finally agree with each other.
Can the scope of work spell out usage rights and source files?
Yes, and it should be settled before kickoff, not contested at handoff. The deliverables section names the logo suite, the colour and typography system, the brand guidelines, and the final artwork, while the acceptance and assumptions sections fix when the usage licence and source files transfer. waxTable states ownership and licensing in plain language tied to milestone payment. That removes the awkward email six months later when a client assumes they bought everything outright.
Why does a visual studio need a designed scope of work, not a plain quote?
A text-heavy quote undercuts a studio whose entire value proposition is visual craft. waxTable generates the scope of work as a designed document with moodboard-grade layout, your colour and typography system, and a logo lockup, not a wall of grey text. Waxe pulls your discovery workshop, design direction, and deliverables into the page so it reads like the brand work itself. The proposal becomes the first sample of the quality you are selling.
How does this help when prospects compare us to template marketplaces on price?
Knowing how to write a scope of work for a graphic design company is what separates a bespoke identity engagement from a cheap template marketplace. The itemised workstreams show the strategy, discovery, and rounds behind 'just a logo', so the client sees craft instead of a line item. Effort against each workstream justifies the fixed project fee by scope and rounds. When the value is visible on the page, the conversation stops being only about price.
Your next scope of work, in five minutes
Tell Waxe about the client and get a complete, on-brand scope of work to review — the work of two days for a few cents. There is no blank page to start from and nothing to format by hand; you answer a short brief, Waxe does the drafting, and you keep full control of the final document in the editor.