1–2 weeks
UX audit
Find the usability issues costing you conversions.
UI/UX design for web apps, SaaS and mobile: user research, UX, UI and design systems from product designers who work hand in hand with our engineers.

We design products people understand on first use: user research, UX flows, UI design and design systems for web apps, SaaS and mobile. Our designers work alongside our engineers, so designs are built as intended and on time.
1–2 weeks
Find the usability issues costing you conversions.
4–8 weeks
Research to final UI for a new product or major feature.
4–6 weeks
Reusable components and guidelines for consistent UI.
Our design work ends in components engineers can ship, not a folder of static screens. Each step produces an artefact that the next step, and later the build, depends on.
01
We start with what already exists: analytics funnels, support tickets, session recordings and the objections your sales team hears. Then we run research sessions with current or target users. The output is a short findings document listing the problems worth solving, ranked by how often they occur and what they cost the business.
02
Before any visual work, we map user journeys, a screen inventory and the navigation structure, and test them with low-fidelity wireframes. This is where usability problems are cheapest to fix. You approve the flows and the screen list, which also gives engineering an early basis for estimates.
03
High-fidelity screens are designed in Figma on top of tokens for colour, type, spacing and elevation, and every component is specified with hover, focus, error, empty and loading states. Accessibility is checked as we go: contrast ratios, focus order, touch target sizes and how layouts behave when users enlarge text.
04
Clickable prototypes are tested with people from the target audience, using realistic tasks such as completing a purchase or setting up an account. We note where people hesitate, misread a label or give up, revise the design and retest where needed. You receive the session recordings and a summary of what changed and why.
05
Designers stay on the project while it is built. Tokens map to Tailwind or your own styling system, components are checked in the coded product, and deviations are caught in pull requests rather than after release. At the end you own the Figma files, the component library and its documentation.
Design time is charged at the same €45–65 hourly rate as engineering or included in a monthly squad from €15k, and every fixed-price MVP, from €15k, includes UX for its core journeys. Scope, more than the number of screens, sets the effort.
Portfolios show finished screens, not how decisions were made. These questions reveal whether an agency's work will hold up once it meets real users and real engineers.
The questions your legal, security and finance teams will ask, answered before the first line of code.
Both. You can work with us on design only, but most clients have the same team design and build, which avoids handover gaps.
Figma for design and prototyping, with design tokens that map directly to code components.
Yes. We start with a UX audit and user feedback, then redesign the flows with the biggest impact first.
Our designers sit in the same team as the engineers who build the product, so feasibility is checked while designs are drawn rather than afterwards. Components are specified in the terms the code uses, and designers review the pull requests that implement them. For you, that means fewer surprises between the approved design and the interface that ships.
Yes. We can add design capacity to your team for a period, work within your existing system and Figma libraries, or help tidy a system that has grown inconsistent. We adopt your naming, review routines and tooling, and document any new components so your own designers can maintain them once we step back.
Not the whole product. Engineering can begin once the flows for the first release are agreed and the core components are designed; later screens are then designed a sprint or two ahead of the build. Starting earlier risks rework, while waiting for every screen to be finished delays learning from real users.
Tell us what you need to build or scale. You will get a proposal and estimate within 24 hours.