UI/UX design
UI/UX design for products people have to use, not just look at.
The screens, the route between them, and the arguments about what belongs in the first version. Design that ships, because the same team builds it.
Design that gets built
Design and engineering sit in the same team here, so the handover everyone complains about does not happen. The file is not the deliverable, the running product is, and a screen that cannot be built the way it was drawn surfaces in a week rather than in a quarter.
In practice that means fewer beautiful screens and more decided ones. What happens when the list is empty, when the name is too long, when the network drops.
The part before the screens
Most of what makes a product usable is decided before anyone opens a design tool: who it is for, what it does first, what it leaves out on purpose. That is the same work as the first product sessions, which is why design does not start as a separate phase.
It is also where the awkward constraints surface. An app used by children and paid for by their parents has to fit in one interface, and that is a structure question long before it is a visual one.
Brand, where a product needs one
Some products arrive with a brand and some do not. Where there is nothing yet, we build the identity alongside the interface: type, colour, the logo, and the rules that keep the two consistent once other people start adding screens.
Where a brand already exists, it stays. Redrawing a company's identity because it suits us better is not design work, it is a preference.
In this order
What happens, and where the cost sits.
The same three phases whatever we are building. What a first version costs is on the how we work page rather than here.
- 01
Two or three sessions, free
We sit down with you and structure the idea before anyone writes code. Who it is for, what the first version has to do, what it leaves out on purpose. Two or three sessions, and there is no invoice for them. You leave with the idea written down, whether or not we build it.
- 02
A first version
Then we build it. Not a clickable prototype: the design, the mobile or web app, and the backend it runs on, in a state real people can use.
- 03
Then reaching a market
Building the product is the part everyone talks about. Getting it in front of people who pay is the part that decides whether it lives. We have done that inside our own companies, and we are extending it to the products we build for founders. It is new for us, and we would rather say so than sell it as a finished service.
What's included
What you get, whatever the scope.
01
What the first version is for
Who it is for, what it does first, and what it leaves out on purpose.
02
The screens and the routes between them
Including the awkward ones: the empty list, the name that is too long, the network that drops.
03
The identity, where there is none yet
Type, colour, the logo, and the rules that keep them consistent once other people add screens.
04
The files, and the running product
Figma files along the way, which are yours, and the designed product in a repository, running.
Team
Meet the people you'll work with
No account managers in between. The people who design and build it are the people you talk to.
Oscar Fally
Founder · Product & development
Antoine Visart
Design
Elliot Verstraelen
Development
What people ask about design work.
Can we hire you for design only?
Yes, though it is not where we are most useful. The value of design and engineering in one team is that the drawing and the building correct each other, and that disappears when someone else builds it.
Do you do user research?
As much as the project can carry. For a first version that usually means talking to people who have the problem rather than running a formal study, and the first sessions are structured around exactly that.
What do we get?
A designed product, in a repository, running. There are Figma files along the way and they are yours, but the file is a means rather than the thing you paid for.
Do you redesign existing products?
Yes. It is usually two jobs: what is wrong with the interface, and what is wrong with the decisions underneath it. The second is the expensive one and the one worth doing.
Enough about us, what about you?
Looking for a partner to build your product? Or sitting on a market you know well and cannot build for? Either way, tell us what you are working on.
Let’s talk