Skip to content
Platform / Figma

Where the interface gets decided

Flows, states and a component set agreed in Figma before anything is built, so the argument about how it should work happens in a file that costs nothing to change.

At a glance
Used in 16 projects
Services 3
Handover Your file, yours
01 / What we build with it

Where Figma earns its place.

01

Flows before screens

The routes through the product agreed in low fidelity, while changing them still costs nothing.

02

A component set, not a picture

Variants, states and tokens, so the build starts from parts rather than from a screenshot.

03

Every state drawn

Empty, loading, error and too-much-data, not only the case that demos well.

04

A file a developer can read

Spacing, type and colour named, so nobody has to guess what a gap was meant to mean.

02 / Honestly

Why this, and when not.

Why we choose it

One link, one source of truth, and everyone looking at the same version. No files by email, no final-v3.

Taking projects for Q4

Designing something?

A 45-minute call with the designer who would do the work. You leave with a scope sketch either way.