Concept artboards
Every screen drawn in your palette before a line of front-end code exists.
SERVICE 03 / UI/UX DESIGN
Concepts first, tokens second, then a component library your developers can implement — states and accessibility included.
Google Stitch / Penpot / Tailwind / Tokens
Fixed scope, agreed in writing before the build starts.
Every screen drawn in your palette before a line of front-end code exists.
Colour, type, spacing and radius as named values, so nobody hand-picks a hex.
Buttons, fields, cards and tables with every state drawn, not just the happy one.
Focus, hover, disabled, loading, error and empty — tested against WCAG AA.
A token file and a contract, not a screenshot in a chat thread.
A check that fails the build when a colour outside the token set appears.
STACK
What exists, what it must do, and who maintains it after handover.
A written scope and a fixed quote before anything is built.
Slices you can click in staging, with changes priced in writing.
Monitoring, updates, backups and support under a one-year warranty.
No. The person who will build the screens is in the concept review, which is why handoff has no surprises.
Yes. We port the brand into a token set first, then design inside it.
Artboards, the token file, the component library and the accessibility criteria each component must pass.
For one page, yes. The system exists for the second and third page, and for whoever edits them after us.