SERVICE 03 / UI/UX DESIGN

Designed twice before it is built once.

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.

What this covers.

Concept artboards

Every screen drawn in your palette before a line of front-end code exists.

Design tokens

Colour, type, spacing and radius as named values, so nobody hand-picks a hex.

A component library

Buttons, fields, cards and tables with every state drawn, not just the happy one.

States and accessibility

Focus, hover, disabled, loading, error and empty — tested against WCAG AA.

Engineering handoff

A token file and a contract, not a screenshot in a chat thread.

A guarded build

A check that fails the build when a colour outside the token set appears.

STACK

Four stages, always in this order.

  1. STAGE 01

    Survey

    What exists, what it must do, and who maintains it after handover.

  2. STAGE 02

    Plan

    A written scope and a fixed quote before anything is built.

  3. STAGE 03

    Build

    Slices you can click in staging, with changes priced in writing.

  4. STAGE 04

    Maintain

    Monitoring, updates, backups and support under a one-year warranty.

Questions this page always gets.

Do you design without a developer in the room?

No. The person who will build the screens is in the concept review, which is why handoff has no surprises.

Can you work from our existing brand?

Yes. We port the brand into a token set first, then design inside it.

What do we receive?

Artboards, the token file, the component library and the accessibility criteria each component must pass.

Is a design system overkill for one page?

For one page, yes. The system exists for the second and third page, and for whoever edits them after us.

The rest of the sheet.

Scope it with a call, not a form war.