A design systemthat survivesits third year.
Identity, design systems and interface work built to be extended by your team, not re-bought from us. Governance and documentation are part of the deliverable, not an upsell.
Every team hasinvented its owninterface.
The tell: two buttons, four shades of the same blue.
Design debt is quieter than technical debt and just as expensive. It shows up as review cycles that take nine days, as a country team that forked the brand because the system did not cover their case, and as three different date pickers in one product.
We fix that at the system level. A component library with real governance, an identity that has been stress-tested against the awkward surfaces, and documentation written for the person who joins your team next year.
What a designengagement covers.
Design files, source components and the written rules that keep them consistent.
- Identity system and art direction across every surface
- Typography, colour and spacing scales with accessibility built in
- Component library in Figma, mapped one-to-one to code
- Interface and interaction design for the core journeys
- Motion language with easing and duration tokens
- Prototypes for the flows worth testing before build
- Governance model so teams can extend without forking
- Written documentation and a handover workshop
Stage by stage,with deliverables.
Each stage ends with something you can review and sign off — never a status update.
Audit
Every surface inventoried, every inconsistency catalogued. Most clients have not seen their product laid out in one place before.
- Surface inventory
- Debt catalogue
- Accessibility baseline
Direct
Art direction and system foundations — type, colour, spacing, motion — proven against the three hardest screens rather than a homepage mock.
- Art direction
- Token set
- Three proof screens
Systemise
The library gets built, documented and connected to code, shipping in tranches so your team is using it long before it is finished.
- Component library
- Code mapping
- Governance model
- Handover
See the systembefore you buy it.
We will run the audit against your live product and show you the debt catalogue before you commit to anything larger.
Where this workhas landed.
Engagements that ran end to end with the same team, from first workshop to live release.
We launched four markets in eleven months against a plan of two. The system did not slow anyone down, which is not something I had ever been able to say before.
Three ways in.
Whichever route you take, the same senior team stays on the project from the first call to handover.
Design audit
Three weeks. A full inventory of your surfaces, the debt catalogued, and a prioritised plan for paying it down.
Identity & system
Three to five months. Identity, design system, component library and the governance to keep it intact.
Embedded design
A senior designer inside your team on a rolling monthly basis, with an agreed capacity and a documented exit.
Before youget in touch.
Yes, and we hand over the files with edit access on day one rather than at the end. Component libraries are published to your organisation, not ours.
Usually, and it is often the better answer. Rebranding a business that already has equity is a decision we would want strong evidence for before recommending it.
Your team. The governance model and documentation exist precisely so that maintenance does not require us. Several clients have extended their systems twice without calling.