Service · Websites and web apps

UI/UX design

An interface can be corrected at three moments, and the price swings by a factor of a hundred. On a wireframe, moving a button takes five minutes. After development you reopen the code, redo the checks and republish. After release you must also explain the change to the people using it. Take a fleet management software vendor that had six drivers try its data entry screen before a line was written, and removed two fields out of five. That is exactly the outcome we are after.

Clickable prototype
tried before development
Components
picked up unchanged by developers
WCAG 2.1 AA
checked on the wireframes
5 to 8 people
enough for a useful session

Where this service reaches

We do not draw isolated screens. We build journeys, then the components that let you make more of them without coming back to us.

Put your scope to an engineer

Understanding real use

Conversations with a handful of genuine users and a look at existing statistics: where people give up, which pages loop, which questions reach support. Internal opinion comes after the evidence.

Journeys and architecture

We describe the main routes before drawing anything: what the person wants to do, in how many steps, with which information in front of them at each moment.

Grey wireframes

No colour, no imagery, so structure is judged rather than looks. This is the stage where internal disagreement resolves fastest, because nobody argues about a shade of blue.

Clickable prototype

A navigable sequence put into the hands of five to eight people. Obstacles surface within an hour of sessions and are mended the same day.

Final interface and library

Colours, type, button states, error messages, empty states and mobile versions, collected into a documented library rather than a pile of pictures.

Accessibility built in

Measured contrast, target sizes, tab order and form labels decided while drawing, following WCAG 2.1 AA and RGAA 4.1 on public sector work.

Handover to developers

Source files, spacing and behaviour specifications, exported assets and a questions session. Your in-house team can carry on without us.

The way an engagement runs

Duration follows the number of journeys and how easily users can be reached. A single screen takes days; a full business application needs several rounds.

01

Discovery

Goals, users, technical constraints and existing measurements. We list the questions the design has to answer.

02

Structure

Journeys and grey wireframes, reviewed with you until the sequence feels obvious.

03

Sessions

The clickable prototype meets real users, with a written account of obstacles ranked by severity.

04

Finishing

Final interface, component library, documentation and a proper handover to the development team.

Five people are enough to expose most of the obstacles in a journey. Many companies skip sessions because they imagine a heavy, costly and lengthy protocol. One hour over video, during which somebody attempts a task while you keep quiet, reveals more than three internal meetings. Keeping quiet is the hardest and the most profitable part of the exercise.

Questions and answers

You can, and many do. The cost resurfaces later as change requests during development, longer training and more support calls. On a small presentation site the saving is defensible. On a tool twenty people open every day, it is not.

Often, yes. We start from usage statistics, support feedback and a screen-by-screen review. Fixes are ranked by expected gain against effort, which lets you tackle part of the list without rebuilding everything.

Real people from the target audience: clients, staff, engineers, applicants. Not your marketing colleagues, who already know the house vocabulary and guess where to click. We help with recruitment and run the sessions remotely.

The design files with access rights in your name, the navigable prototype, the documented library, exported assets and the session write-up. All of it is usable by an agency other than ours.

By fixing the markers beforehand: task completion rate, time taken, error count, support calls on that subject. We record those values on the current version, then again after release. Without a starting figure, comparison is reduced to everyone impressions.

Have your interface tried before it is coded

Describe the product or site to be designed and the people who will use it. We propose an approach and a number of rounds.

When we are around
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Talking it through
A call on Teams or Google Meet, whenever writing is not enough

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.