The process.
Six stages. Scope written before work begins. No surprises.
Order the service
Select a service or build a custom package on the website. Complete payment via Stripe. Confirmation email arrives immediately. The project brief template arrives within 1 business day.
We use a written brief system because phone calls and informal kickoffs produce vague projects. A brief forces clarity upfront. If we cannot write down what we are making, we should not start making it.
Complete the brief
Complete and return the project brief template. The delivery timeline begins from the date we receive your completed brief, not from the date of payment.
The brief asks for your business context, audience, competitor references, content, and any existing brand files. If you have brand guidelines, send them. If you do not have final copy, send draft copy. Placeholder text produces placeholder-quality design.
Positioning review
For Editorial Web Design and Digital Brand Experience projects, the brief is followed by a positioning review session by email. We review your market, audience, and competitive context before any visual work begins.
This step does not exist in most design workflows. It should. Design without positioning context produces work that looks fine but does not communicate the right thing to the right people.
Design delivery
You receive the complete Figma design files. Desktop, tablet, and mobile. All components annotated. Developer handover notes included. One revision round is included in every project.
The revision window is 5 business days from the date of delivery. Requests submitted after this window are treated as new scope and quoted separately. In-scope revisions are returned within 3 business days.
Revision round
We implement your revision feedback within scope. Changes to content, new pages not in the original brief, or structural redesign are outside scope and quoted separately.
Revisions are not renegotiations. They are adjustments within the agreed brief. We are direct about when a request falls outside scope. This keeps the project honest and the timeline intact.
Project close
Final annotated files delivered. Developer handover notes finalized. Project closed.
There is no formal support period after delivery. If you need additional design work, implementation support, or consulting after the project closes, it is available at the published hourly rate.