Skip to content

Digital design: UX/UI for complex products

A product nobody understands how to use is no use to you.

The best technology in the world is useless if the user cannot use it. For us design is the part of a project that decides whether the product will be used or abandoned.

And we take care of it from the start, not when it is too late to change.

When do you need to work on design?

You need it when a product works but people struggle to use it: users get stuck, support keeps answering the same questions, nobody finds the features you built. You also need it before writing code, to anticipate errors and changes and cut project costs.

Netech had a banking platform for anti-money-laundering checks. The backend was solid, but the interface was not clear to users. We redid the UX and UI, and a complex tool finally became clear and usable.

Understand first, then design, then build

User research and testing

We talk to the people who will use the product, before designing it. That is where the real problem comes out, which is almost never the one you started from.

UI and UX

Fewer steps for the thing done a hundred times a day, and information where it is needed. On screens full of data, this is where you win or lose.

Design system

Components and rules written once: the fiftieth screen does not cost what the first did, and does not look designed by another company.

Clickable prototypes

A prototype you can click before writing code: changing a flow in Figma costs an hour, changing it in production costs a week.

For Satispay we gave shape to the digital home of a European fintech. For the Osservanza of Imola we built the identity of a place that is changing: a former asylum becoming an innovation park, to explore in 3D as well.

Watching someone use the product without explaining anything.

That is where you find out whether the design works.

We run tests with real users and check whether they get stuck, look for buttons in the wrong places, give up halfway. What a person says about an interface matters less than what they do when it is in front of them.

How we work with you

Designers and developers work in the same room: what we design is what can really be built, not a gorgeous, impossible mockup.

Our design is tied to development, it is not a PDF nobody then follows. We start from research and prototype, put them in front of real users, fix where they stall, and only then build. So what goes into production has already been tried by someone who is not us.

Who we build it for

We work with people who have a powerful product that is hard to use, and with those who have to simplify something intrinsically complex: financial platforms, healthcare tools, data-dense business systems, but also with those starting from zero who want to validate the idea before spending months of development on it.

The tools we use.

Miro for collaborative workshops, Figma for designing and prototyping, design systems and component libraries to keep everything consistent as the product grows. But tools are the easy part.

The difference is the method: design-driven and tied to development. We do not just hand over a file, we stay in the project until it goes into production. A design nobody can build the way you imagined it is not a good design, it is a nice drawing.

OUR CLIENTS

Satispay: Quinck clientProtesa: Quinck clientIMA: Quinck clientWEP: Quinck clientMottura: Quinck clientNuovo Circondario Imolese: Quinck clientBMI: Beauty Management Italia: Quinck clientSatispay: Quinck clientProtesa: Quinck clientIMA: Quinck clientWEP: Quinck clientMottura: Quinck clientNuovo Circondario Imolese: Quinck clientBMI: Beauty Management Italia: Quinck client
WORK

Digital design projects we have delivered

Frequently asked questions about UX/UI design

How much does UX/UI design work cost?
It depends on three things: how many flows need redoing, how complex they are and whether a design system also has to be built. Reviewing the most critical flow is one thing, redesigning a whole platform is another. The first step costs nothing: a free conversation, then a short analysis that ends with a precise quote. And if the project qualifies for a public grant the numbers change: some clients have gone from 40,000 to 20,000 euros out of their own pocket.
Do you only do UX/UI design, or also product development?
Both, and that is the point. We keep design tied to development so that what we design can really be built. We can take on just the design part if you already have people who develop, but our real value shows when the two travel together.
Is user research needed before designing an interface?
On a new product or a critical flow, yes, and a few tests with real users save months spent on the wrong thing. It depends on the risk, though: on a small tweak it is sometimes not needed, and we tell you instead of inflating the work.
What is a design system, and does my product need one?
It is the set of reusable rules and components that keep a product consistent as it grows. You need one when screens multiply and every piece starts to look made by different hands. On a small product much less can be enough: we do not propose one if it does not pay off.
Can you redesign a product that already exists?
Yes, it is a good part of what we do. We start by understanding where it stalls today and redo the experience without necessarily touching what already works underneath, as we did for Netech. A redesign should not throw away the good work already done.
Do you also design interfaces for business systems and data-dense dashboards?
Yes, and it is the bulk of our work: business systems, financial platforms, clinical tools, dashboards with hundreds of data points on one screen. These are the cases where design is not aesthetics but hierarchy: what is seen first, what can be hidden, how many decisions can be taken away from the person looking. Netech had a banking platform for anti-money-laundering checks with a solid backend and an interface users did not understand: we redid the UX and UI and the tool became usable, without touching what already worked underneath.
Do you hand over the Figma files and the design system, or do they stay with you?
They are yours: Figma files, design system and component library stay with the client, like the code. We hand over the design system documented, so that your team can add screens without calling us, and that is exactly why it is worth having one. If after the design you also trust us with the development, it works in your favour. But you are not obliged to: the files are yours and we do not hold them hostage.

Do you have a powerful product that users struggle to use? Let us start there. We will look at where they get stuck and what makes hard what should be obvious.

Let's talk Back to What we do