UI/UX Design for software and web apps
We design the interfaces of digital products: screens, user journeys and component libraries. Drawn by the people who also build them, so buildable by definition.
We design interfaces, not brands. Screens, user flows, error states, tables that have to hold thousands of rows: the design of a product people will use to do their job every day. The advantage of doing it with the people who build it is that what you see in the prototype is what ends up in production, without the step where someone tells you it «can't be done that way». We work in systems: colors, typography, spacing and components defined once and reused everywhere, because that's the only way a product stays coherent as it grows. We don't do logos, marks or corporate visual identity, and we don't handle naming or tone of voice: if that's what you need, we'll tell you it isn't us.
Users get lost inside your app and ask you how to do something simple.
Every new screen looks like it was made by someone other than whoever made the last one.
The software works but your team avoids it and keeps using Excel.
You were handed a design your developers say they can't build.
Concrete, not slideware
UI Design
The product's screens, including the ones nobody usually draws: empty states, errors, loading, dense tables and different permissions per role.
Clickable prototypes
A prototype you can actually use, to test the journeys with the people who'll use the product before it becomes code.
UX & User Flow
We design simple user journeys, reducing friction and drop-off.
Design System
Color and typography tokens, reusable components and usage rules: a library that grows with the product instead of fragmenting.
Accessibility
Readable contrast, keyboard navigation, alt text and target sizes: project requirements, not final polish.
Responsive design
The same interface on the office monitor and on a phone in the field, without either being a fallback for the other.
Always included
Code you own, security by design, GDPR compliance.
Why M's Works
Drawn by the people who build it
No unbuildable prototypes and no negotiation between designers and developers: they're the same people.
Less friction, less support
An interface that explains itself cuts your team's questions and your support requests.
The system holds as you grow
With components and rules in place, screen number fifty costs far less than the tenth and looks like the rest.
For products already live
The work can be done on existing software too, without stopping it and without starting over.
A clear process, no surprises
01
Understand the work
Who will use the product, to do what, and how many times a day. A back-office design is decided here, not on the palette.
02
Flows
Journeys and screen structure first, in black and white: it's the part that's expensive to change later.
03
Interface and system
The finished screens and the component library that holds them together, with your feedback at every round.
04
Handover
Source files, components and usage rules. If we're building it too, there's no handover: we just continue.
Related services
Is your product hard to use?
Show us the screens that cause the most trouble, even if the software is already live. We'll tell you where users get lost and what we'd change first.