05 · Service

Brand & UX

If the identity is vague, every page becomes a negotiation. We set type, colour, components, motion, and voice so design and engineering do not leak quality at the handoff. UX here means the actual path a person takes — on a marketing site, in a checkout, in an admin, in an app — not a stack of persona slides nobody opens twice.

Teams about to build (or rebuild) a site or product who do not want to invent the brand twice, and products whose interface is currently fighting the user.

When this is not the work. If you need a logo animation and a pitch deck only, we are the wrong studio. If the product is already in flight and you only need pixels on one page, we will still set the smallest system that stops the next page inventing a new UI. Print-first rebrands with no digital product are not this practice.

Start this work

Mapping a user flow on paper before it becomes a URL

What this usually fixes

Every page is a different company.

Type, colour, and buttons were improvised under deadline. We lock a small, strict language so page 24 still looks like page 1.

The Figma file cannot survive a table of data.

Pretty frames, empty states missing, error states guessed in engineering. We design with the stack: tokens, components, real content.

Nobody can say what you sell after one screen.

The identity is decoration. We test copy and structure on a stranger’s phone until the sentence is obvious.

The app, the site, and the store disagree.

Three interpretations of a PDF. We hand the same tokens to web, React Native, and marketing — not a costume per channel.

Pages and screens

What a buyer actually walks through — not a capability matrix.

The first screen

What a stranger reads. Type, photography, the sentence that has to land.

Navigation and wayfinding

How twenty pages (or twenty screens) stay one product.

Forms, tables, empty states

The unglamorous UI that is most of the product. Specified, not improvised.

Checkout, pay, confirm

Where trust is allowed to feel expensive. Errors that can be recovered.

Motion and voice

Transitions that explain. Words for homepage vs error vs push. Written down.

What we build

Digital identity

A small, strict visual language: type, colour, space, photography, logo rules. Enough to be recognisable. Not a costume.

Design systems

Buttons, forms, tables, navigation, empty states — in Figma and in code, so page 24 still looks like page 1.

Product UX

Flows for sign-up, pay, search, admin, onboarding. Prototyped against the real job, then built.

Voice

How the company speaks on a homepage versus an error versus a push notification. Written down.

How deep this goes

Interface that survives engineering

We design with the stack in mind: React components, tokens, dark/light if you need it, responsive behaviour specified — not a desktop frame dumped on a developer.

Tokens for colour, type, space that map to CSS variables
States: hover, disabled, loading, error, empty — specified, not improvised
Accessibility as a constraint from the first board, not a retrofit

Research without theatre

We sit with the people who sell, pack, or support. We watch a stranger try the current site. We do not produce a 40-page research artefact that never changes a pixel.

Task-based tests on real phones
Copy tests: can they say what you sell after one screen?
Decisions recorded so the next designer is not guessing

Motion and craft

Type that is set, not defaulted. Photography rules so every page is not a different photoshoot. Motion that explains a transition and then gets out of the way.

Web (CSS / JS) and app (native or RN) motion in the same language
Guidelines a new hire can follow without a call
Handoff into the website or product build — we do not throw files over a wall

Languages, platforms, tools

The names people search for belong on a service page, not in a footer buzzword strip. This is what we actually ship in.

Design

Figma
Design tokens
Component libraries
Prototyping

In production

React
React Native
Swift UI patterns
Jetpack Compose patterns
CSS / Tailwind

Quality

WCAG
Keyboard flows
Contrast
Content design

What you walk away with

Visual language

Type, colour, space, photography, logo use. A short board that can survive a product grid.

Component library

Specified in Figma and implemented in the product so the next page does not invent a new UI.

Key flows

The three journeys that matter, prototyped and then built — not forty unused frames.

Voice and handoff

How we speak, plus rules engineering can follow without a meeting.

How the work runs

A named owner, a written brief, and something you can click early. The longer studio sequence is on Approach.

01
Audit what exists
Brand files, the live site, the app, competitor noise. We keep what works.
02
Lock the system
A short board and a working page or screen. If it cannot survive a table of data, it is not a system yet.
03
Apply and document
Roll into the site or product. Leave a guide a new designer can follow.

Questions we hear

Is this a full rebrand?+

Only if you need one. Many engagements are a tighter system so the website or app can be built without inventing the brand twice.

Do you do print?+

Digital first. If print must match, we specify so a printer can follow it.

Can this land straight in code?+

Yes. The point of the system is that React, React Native, and the marketing site share tokens — not three interpretations of a PDF.

Do you only design, or do you also build?+

We design to be built, and we usually build. A board that cannot survive engineering is not the job. Website, store, software, and mobile are the other practices — same desk.

Can you work with our existing logo?+

Yes. Many engagements are a tighter system around a mark you already have. We will not invent a costume because a moodboard is fashionable.

Is this UX research with personas and journey maps?+

We sit with the people who sell, pack, or support. We watch a stranger try the current site. We do not produce a 40-page artefact that never changes a pixel.

Other capabilities

If this is the work, send the brief.

Contact