Service · Websites and web apps

UI/UX design

A good interface starts with the question of what the user came to do; the colour palette comes much later. A patient wants to book a clinic appointment in two minutes, a warehouse worker wants to confirm a delivery with one thumb, and the bookkeeper at your customer wants the invoice without hunting for it. A gorgeous layout that hides the “Order” button does more harm than a plain one, because the attractive picture hides the problem and makes it harder to challenge.

Wireframes
before visuals
Mobile first
on every project
Design system
rather than loose screens
5 people
are enough for a test

Included in this service

We design two layers: behaviour and appearance. Behaviour comes first, and its mistakes are the costly ones because they only surface once development begins.

Talk the scope through with an engineer

Discovery

We look at Google Analytics 4 data, session recordings and customer service tickets, and talk to a handful of users. The aim is to find the points where people give up.

Information architecture

Menus and section names follow the words your users use, not your organisation chart. Online card sorting helps us get there.

Wireframes

Grey boxes with no colours or typefaces. They are easy to argue about and reworking them takes minutes rather than days.

Figma design

Key screens drawn in all their states, from empty and loading to error, zero results and an absurdly long product name. Developers never have to guess.

Design system

Buttons, fields, grid, spacing and type styles built as components with variants, so a new page can be assembled from ready parts without calling in a designer.

Accessibility

Contrast, visible focus, comfortable touch targets on mobile and clear error messages in line with WCAG 2.1 AA belong in the design from the outset rather than being bolted on later.

User testing

Five members of your audience work through tasks on a clickable prototype; we observe quietly over a video call and record the moments they hesitate.

How we work together

A large share of the time goes on wireframes. That time is recovered during development because late changes to live code disappear.

01

Workshop and data

Business objectives, user scenarios, any statistics you already have, plus a remote workshop with your people.

02

Wireframes and flows

Layout and step order get approved while everything is still grey.

03

Visual design

Screens plus a Figma component library covering all states and mobile layouts.

04

Handover

Developer-ready files describing how elements behave, how animations run and how fields are validated. We stay available throughout the build.

The most expensive design flaw is a form nobody tested. A postcode field that rejects the format 00-950, a date that must be typed in an unusual order, a message that just says “An error occurred”. Each of these small things costs you orders, yet analytics only ever shows an abandoned basket. That is why we specify validation and error wording as carefully as the home page.

Questions and answers

For a simple brochure site that is often fine. Custom design earns its cost where the interface departs from the usual patterns: a product configurator, a booking system, an app for field staff, wholesale ordering. Making an “About us” page one of a kind seldom justifies the spend.

You. We move the Figma files into an account owned by your company, and the transfer of copyright is set out in the contract. Lacking source files, any future agency begins again from nothing and you end up paying twice.

Seldom. It usually works better to improve, one by one, the journeys where data shows you are losing people: sign-up, basket, enquiry form. Changing everything at once makes it hard to tell what worked and forces regular users to relearn the site.

Not necessarily. We recruit five people from your target group, each session lasts about 45 minutes over a video call, participants receive a small fee, and after the sessions you get a report with clips of the key moments.

Yes. The same principles apply to phone apps, admin panels and internal tools. For mobile apps we follow iOS and Android guidelines so that users are not asked to learn unfamiliar gestures.

Get an interface people can actually use

Explain the product and the jobs people do with it. We will begin with wireframes and data, not a moodboard.

Hours
Mon-Fri 8:00-18:00 CET, reply within one working day
Meetings
Online via Teams or Google Meet

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.