01
Research and flows
Interviews, audits and journey maps that settle decisions before anyone draws a screen.
Research, flows and high-fidelity screens in Figma that engineers can build without a follow-up meeting. Hire us for design alone, or as the first phase of a build.
You probably need design help, not more development, if any of these are true.
From the first interview to a component library your engineers actually use.
Interviews, audits and journey maps that settle decisions before anyone draws a screen.
iOS and Android screens that respect platform conventions and every state.
Running at Nomad, wellbeing app redesignDense data made readable: tables, filters, statuses and bulk actions.
Running at Fix My DL adminHigh-fidelity screens for every state: empty, loading, error and success.
Running at E-Fire USA portal
Tappable flows for user testing and investor or stakeholder sign-off.
Running at Home OfferzTokens, components and documentation that survive contact with engineering.
Identity, packaging labels and print for e-commerce and local brands, designed by the same team that builds their stores.
For E-Fire USA we designed the admin portal, the user web app and the Flutter apps before a line of code was written. The same people then built them, so nothing was lost between design and development.
The same people stay with you from the first workshop to launch day. No handoffs between strategy, design and engineering.
Stakeholder interviews, user research and an audit of what exists today.
Information architecture, flows and low-fidelity wireframes.
High-fidelity screens, components and a clickable prototype.
A walkthrough with your engineers and two weeks of answers afterwards.
A single product area takes 4 to 6 weeks. A full product with a design system runs 8 to 10.
The number of unique screens, whether it is web, mobile or both, and how much research the decisions need.
We agree the screen and flow list up front, with two revision rounds included.
Our designers work next to the developers who build their screens, so files arrive buildable.
Empty, loading, error, permission denied. Designed, not left to whoever picks up the ticket.
Components and tokens from the first screen, so the tenth screen is faster than the first.
Many clients bring their own developers. We hand over clean Figma files and stay on call for questions.
Picked during scoping, based on your systems and who will maintain the product after us.
Methods chosen by the question.
Tools your engineers know.
For sign-off and testing.
Built to be built.
Yes. A good share of our design work is standalone, handed to the client’s own engineers as organised Figma files.
Yes: interviews, usability tests and audits, as a standalone project or as the first phase of a design engagement.
A live walkthrough of the Figma file, components and edge cases, then a two-week window where your engineers can message us directly.
Yes. We translate the brand into product UI without fighting the platform conventions users already know.
Yes, on a monthly retainer sized to how much design your roadmap needs.
You will speak with an engineer who has shipped this kind of work, and get a straight read on scope, timeline and whether we are the right fit.