How it works
One project, one visible path from files to final delivery.
You do not need to understand the internal engine. You need to know what to provide, what is missing, what is being reviewed and what you will receive next.
The path
Two lanes, one delivery.
The client lane and the studio lane move in step, from intake to approved delivery.
Site + files → brief → concept → review → delivery.
Client
Define the decision and share the files you already have.
Answer questions about inputs and constraints.
Send corrections or continue with a stated limitation.
Review the private draft in the Review Room.
Request revisions or approve.
Receive the approved delivery.
Studio
Secure intake with a receipt and recorded purpose.
Verify inputs and flag any limitations.
Build evidence and landscape direction.
Complete named design and evidence review.
Keep revision lineage and run release QA.
Hand over a controlled, labelled package.
Illustrative workflow for selected engagements
Illustrative deliverable anatomy — no client data
Corrections
A correction is a plain-language request, not an error code.
If a file cannot support its stated purpose, you see clearly what to do next.
Please upload the issued scaled base plan with a visible revision date. This affects the concept-plan placement page. Work can continue on visual direction, but scaled placement remains unavailable.
Corrections create a new version. Superseded records stay traceable rather than silently overwritten.
Ready when you are
Start the path with the files you already hold.
Share the site and the decision you need to support; the first review is a conversation.