Research
Who arrives, with which task, and where they drop off in the current solution. We draw on analytics, interviews and what your support team hears.
The work begins by asking what the user needs to accomplish on the page; appearance comes afterwards. A beautiful interface where nobody can find the order button is worse than a plain one, because the problem hides behind a pleasant picture.
There is designing behaviour and there is visual design. The first comes earlier, and mistakes there cost more than mistakes in the second.
Who arrives, with which task, and where they drop off in the current solution. We draw on analytics, interviews and what your support team hears.
No colours or fonts. They are cheap to debate and easy to change.
Key pages in every state: empty, loading, error and overflowing with content.
Buttons, fields, spacing and typography as components, so new pages can be assembled without the designer.
WCAG-compliant contrast, focus indicators and touch targets are part of the design from the start.
Five people from the target group get a task, and we quietly watch where they get stuck. Sessions run online.
Three to five weeks for a typical site. Half goes on wireframes, and that time is repaid during development.
Business goals and user scenarios, analytics where available and an online workshop with your team.
Structure and flow are approved before any graphics are drawn.
Design and a component library in Figma covering every state.
Figma files ready for development, with notes on how each element behaves.
Designs approved on the managing director's taste tend to lose. Whether anyone likes it is the wrong question. The right one is whether users can complete their task. Give five people from the target group a job to do and see if they manage. It is cheap and almost always uncovers something obvious.
For a simple site, yes. Custom design pays off where the interface is not standard: customer portals, B2B ordering or complex product selection. For a page about your company, paying extra for uniqueness is rarely worth it.
You do, and the contract should say so. The Figma files are transferred to your own account. Without source files, the next supplier starts from scratch and you pay for the design twice.
Not by the calendar, but by symptoms: the interface fails on new screens, the structure has been outgrown, or the numbers show people are not reaching their goal. Redesigning just to look fresh often confuses loyal users.
Tell us about the product and what users need to do. We begin with wireframes, not pictures.
Thank you for getting in touch
One of our consultants already has it. Expect a reply within the working day; anything urgent goes straight to an engineer.
That city is not on our list. Check the spelling or pick the nearest larger town.