User-friendly interfaces that delight.

At DLM Digital a UX audit of an existing site starts at CHF 1,500. A UX/UI design sprint for a defined area such as a landing page or a sign-up flow starts at CHF 6,000, and a full product design with research, design system and usability testing at CHF 15,000. A complete website including implementation costs CHF 3,000 to CHF 25,000 depending on scope. Price is driven mainly by the number of distinct screens and the depth of research.

UX design determines how a product works: structure, navigation, the order of the steps. The guiding question is whether the person reaches their goal. UI design determines the visible surface on top: typography, colours, spacing, components and their states. The guiding question is whether it is legible, clear and consistent. UX comes first, UI builds on it. The glossary entry UX/UI Design covers this in full, with a comparison table.

An information architecture with page structure and naming, user flows for the business-critical tasks, wireframes, a pixel-accurate UI in Figma including error, loading and empty states, a clickable prototype, the usability test log with a prioritised action list, and a documented design system for development. On request we then implement the design ourselves in React and Tailwind.

A UX audit takes one to two weeks. A design sprint for a defined area takes two to three weeks. A full product design with research, several test rounds and a design system takes four to eight weeks. The biggest time factor is rarely the design work but the availability of test participants and decision-makers on your side — book fixed slots for that.

Usually not. For a five-page site with a clearly explainable offer a full UX process with research and test rounds is over-specified — a properly built standard layout plus good copy and photography delivers more. A dedicated UX project pays off as soon as users have to complete several steps in sequence: configuration, booking, ordering, sign-up or a self-service area.

In usability testing real people receive a real task and solve it on the prototype while we observe and do not help. Five participants uncover roughly 85 percent of the observable problems in a round, per Jakob Nielsen (Nielsen Norman Group, based on Nielsen and Landauer 1993). It is worthwhile wherever several steps have to be completed in sequence. It answers only whether someone can complete a task — not whether they want to buy the product.

Yes. Wireframes, UI design, the component library and the clickable prototype are built in Figma; you get access to the file and keep it after the project ends. If you already have a Figma setup or a design system, we continue inside it rather than building a second one alongside.

Yes, and it is the main reason clients buy design and development together from us. We build in React and Next.js with Tailwind, so components are not invented twice — once in Figma and once, slightly differently, in code. If you have your own development team, we deliver a documented design system with specifications instead and stay available for questions.

Then the concept changes. That is what testing is for, and it is why we test on the prototype rather than the finished product: in Figma a change costs hours, after development days to weeks. A test that finds nothing is not a good test — usually the tasks were set too easily.

It depends on the shape of the work, not on the budget. A single UX/UI designer is enough when one bounded area is being reworked — a form, a landing page, one screen — and somebody on your side carries the decisions and organises access to users. An agency pays off once several roles have to interlock: research, interface, design system and the implementation afterwards. The downsides belong in the picture: an agency costs more coordination, a freelancer has no cover when they are ill. In both cases ask who specifically will work on your file — with us it is the same person who sits in the first conversation.

No, it sits before it. Corporate design fixes the mark, colour palette, type system, imagery and the rules around them — for every channel, not only the screen. UI/UX design translates those rules into a product: structure, flows, components and their states. Where a workable corporate design exists, a UI/UX project starts by turning it into design tokens. Where it is missing, the order is brand first, interface second — otherwise the website's look becomes the retroactive standard for everything else without anyone ever deciding that. How we set up brand work is described on our corporate design agency page.

Yes, and it is often the cheapest next step. We take stock of the existing screens, extract design tokens for colour, typography, spacing and radii, resolve the contradictions and turn the result into a documented component library covering every state. The product does not look new afterwards, but every further screen gets built faster and stays consistent. For a single landing page it is not worth it — clean tokens are enough there. From roughly twenty screens, or from the second person who designs, it almost always pays for itself.