Process
Direction before decoration.
Five stages, in order. The work starts with what the piece has to do and ends with files named, sized, and exported for their actual use.
-
Brief
The brief determines the build.
Everything starts with what the piece has to do, who has to understand it, where it will run, and when it is due. The brief also fixes the practical facts: dimensions, formats, existing assets, copy status, and how the work will be used.
You bring
- Project type, audience, and purpose
- Deadline and placements
- Required dimensions and formats
- Existing assets and copy status
- Usage and any technical requirements
The studio does
- Confirms the scope in writing: project, deliverables, dimensions, placements, deadline, revision process, usage, licensing, source-file status, third-party costs, rush terms, payment terms, and delivery method
- Flags anything missing before design starts
Deliverable
A written scope with the price.
-
Direction
Direction before decoration.
Visual references, tone, hierarchy, and the creative lane are set before anything is built. The required information is listed, and so are the restrictions: brand rules, material limits, and what to avoid.
You bring
- References and tone
- Brand restrictions and required elements
- What to avoid
The studio does
- Establishes the visual direction, hierarchy, and lane
- Confirms the required information and the restrictions
Deliverable
An agreed direction. The number of directions explored is part of the scope, not a default.
-
Design
Build the hierarchy before the effects.
The approved direction becomes a complete asset or visual system. Every decision is checked against readability, hierarchy, placement, audience, format, and production.
You bring
- Timely answers on open questions
- Supplied assets in usable quality
The studio does
- Builds the approved direction into the finished asset or system
- Tests the read at distance, in detail, and across the agreed formats
Deliverable
A proof of the complete design for review.
-
Revision
Focused feedback improves the approved direction.
Revision refines the approved direction. Feedback is gathered and applied in focused rounds so the piece gets sharper rather than drifting. A change of direction is a different thing from a revision and may need a revised scope.
You bring
- Consolidated, specific feedback
- Sign-off when the piece is right
The studio does
- Applies the feedback to the approved direction
- Says clearly when a request is a change of direction
Deliverable
A revised proof. The revision process itself is defined in the written scope.
-
Delivery
Final files are named, sized, and exported for their actual use.
Delivery is the set of files agreed in the scope, each correctly named, correctly sized, correctly formatted, and organized for the placements it belongs to. Formats are not listed by default. The scope decides them.
You bring
- Confirms receipt and placement requirements were met
The studio does
- Exports and organizes the final files for the agreed placements
- Delivers through the method written into the scope
Deliverable
Final files for real use.
Prepare the brief
The brief determines the build.
The more of this the brief carries, the faster the scope comes back.
Confirm
- Project type, audience, and purpose
- Deadline and placements
- Required dimensions and formats
- Existing assets and copy status
- Usage and technical requirements
The scope then defines
- Project
- Deliverables
- Dimensions
- Placements
- Deadline
- Revision process
- Usage
- Licensing
- Source-file status
- Third-party costs
- Rush terms
- Payment terms
- Delivery method
Start a project
Ready to brief a project?
Scope, timing, deliverables, and price are confirmed for each project.