What’s included
(05)A product that looked fine in the design file often falls apart in the build, because it was drawn with perfect data and no engineer in the room.
-
Designed with real data
We design with your actual records, names, numbers and documents, including the messy ones, so the layout survives contact with real use.
-
Your worst day
Heavy load, missing information, a payment that fails, a user with no permissions. We design for the day things go wrong, not only the demo.
-
Designers beside engineers
Design and engineering share the same week. Ideas that cannot be built are caught early, and constraints in the code shape the design rather than overrule it.
-
Roles and permissions
Platforms used by different kinds of people get a view for each: what an admin sees, what a team member sees, what a customer sees.
-
From first release to the next
We plan what goes in the first version and what waits, so the first release ships and later work has somewhere to go.
When you need it
- You are building a new app or platform and need it designed properly
- The product looks good in the file and breaks in the build
- Different users need different views and nobody has drawn them
- Your engineers are designing screens because nobody else is
How it runs
(04)You get a written scope, a fixed price and a start date before anyone begins.
-
Learn the product
Your data, your users, your roles and your rules. We find out what the product has to handle before we design it.
-
Prototype the core
The tasks that matter most, built as a clickable prototype and tried with real people.
-
Design with engineering
Screens and states drawn week by week alongside your engineers, so each part is checked for build before it is final.
-
Ship and review
We stay through the build, check what ships against the design and note what to improve next.
What you leave with
- A clickable prototype of the core tasks
- Final screens for every role and state
- A component library matched to the code
- Specs for edge cases and failure states
- A plan for the first release and what follows
Also in Design
Start your project with us
FAQ
Answered questions.
A product designer owns the whole thing working: what it does, for whom, in what order, and how each part looks. UI design is one piece of that. We do both.
Yes. We work in the same week as your engineers, hand over files that match the code and review what ships. If you have no engineers, our technology team can build it.
Yes. We designed the product UI for Maxiwise, an investing platform, on the identity we also designed. We also design, build and run our own software, Openn Invoice.
Yes. An AI feature is designed like any other: what the person asks, what comes back and what happens when it is wrong. See AI product experience.
