Discipline · Product & design

Custom UX design.

UX design translates customer needs and business goals into a product that works clearly, accessibly and pleasantly. We combine research, information architecture, prototyping and visual design in a single engagement — and connect it directly to the team that builds it.

DisciplineUX + UI + research
ToolingFigma + FigJam
MethodSprint-based
AccessibilityWCAG 2.2 AA
Hand-offTo your own dev team
Lead timePer sprint

What is UX design — and what does it include?

UX design (user-experience design) is the design of how a product works for the people who use it. It is broader than an interface: it covers the research that comes first, the structure underneath and the iterations that follow after go-live.

A full UX engagement typically includes discovery and user research, information architecture, user flows, low-fi wireframes, mid-fi mock-ups, a clickable prototype, visual design based on a design system, interaction and motion design, an accessibility check and usability tests with real users. It ends with a hand-off to the developers: specified Figma components, design tokens and interaction notes.

We are a team of builders and designers in one studio. That means the UX designer is not designing for an outside party who has to make something of it later — the developer is at the table from the research stage. For scalable product families we work from a design system, so every subsequent screen is faster and more consistent.

This makes the biggest difference in the grey area between design and implementation: animations that look fantastic in Figma but cause a performance problem in code, interactions that work on a prototype but not in a mobile browser, or a visual pattern that scales to two screens but not to twenty-two. By putting designer and developer in the same sprint, we prevent such friction from only surfacing during the build phase.

Our clients are typically in the mid-market segment — scale-ups, SMEs with a digital product and mid-sized corporates with multiple internal tools. For some clients we deliver UX as a standalone service, for others it is built into a larger development engagement. Same discipline, different scope.

2.2 AA
WCAG level we use as our minimum — the EAA requires this for public-facing services from 2025
5-8
Participants per usability test round — enough for most patterns
3 layers
Wireframe, mid-fi mock-up, clickable prototype — before we move on to dev
1 team
Designers and developers in the same sprint — no hand-off via a spec document

When is a UX engagement relevant?

01
MVP

You are shaping a new product

Founders and product teams who want to validate an idea with a clickable prototype before a single line of code is written. UX determines whether the concept works for the target audience.

02
Rework

An existing product needs to get better

The feature set has grown, the screen has become cluttered and users drop off. A UX rework restructures flows, navigation and visual design without overhauling the backend.

03
Conversion

The funnel leaks at an unexplained point

Analytics shows that users drop off at a specific step, but it is unclear why. Usability research combines quantitative data with sessions and interviews to find the cause.

04
Scale

A portfolio of products needs to become consistent

Multiple apps or modules have grown organically and each looks slightly different. UX on top of a design system turns the portfolio into one coherent whole without redesigning every product.

05
Compliance

The law requires accessibility

Since 2025, the European Accessibility Act (EAA) requires public and commercial digital services to meet WCAG 2.2 AA. A UX audit with a remediation plan gets you there.

06
Capacity

Your in-house design team is too small for a peak

Software agencies and in-house product teams that need extra UX capacity for a limited time, for a release, a rebrand or a new market, either embedded or as a sub-project.

The three core tasks of a UX team.

Core task 01

Understanding

Stakeholder interviews, user interviews, competitor analysis and jobs-to-be-done. We map out who uses the product, in what context, and which problem it solves. Without that foundation, everything that follows is guesswork.

Core task 02

Designing

Information architecture, user flows, wireframes, mid-fi mock-ups and visual design. Iterative, with a clickable prototype that users can actually try out. Visual design is tied to a design system so it stays scalable.

Core task 03

Validating and handing over

Usability tests with real users, accessibility checks against WCAG 2.2 and a hand-off document with Figma specs, design tokens and component naming that the developer team can use directly.

Eight types of UX work we do.

From a short audit to a full product engagement: UX is rarely a one-size-fits-all assignment.

UX audit

Analysis only of an existing product, with a concrete report and priority list.

Design sprint

Discovery, ideation and a validated prototype in one focused working week.

End-to-end product UX

From research to dev hand-off. For MVPs and new product lines that still need to be designed.

UX rework

Rethinking an existing product, while keeping the existing backend and data models.

Design system + UX

For multi-product portfolios. One system, multiple products, a consistent experience.

Embedded UX designer

A UX designer as part of your own team for the duration of a release or programme.

Information architecture

Sitemap, taxonomy and navigation for portals, knowledge bases and complex catalogues.

Accessibility audit

WCAG 2.2 AA check including screen reader, contrast and keyboard navigation, with a remediation plan.

How a UX engagement works in practice.

A UX engagement rarely starts with design. It starts with a conversation about what needs to change and why. In the discovery phase we map out the context: who the users are, which jobs-to-be-done they need to complete, what the competitive landscape looks like, and which business goals underlie the project. We do this through internal stakeholder interviews (product owner, sales, support, sometimes a C-level sponsor) and external user interviews.

From that input we build the information architecture: the sitemap, navigation, taxonomy and content structure. This is the phase where most rediscoveries happen: almost every existing product has a navigation that has grown organically and no longer matches the user's mental model.

Next come the user flows and wireframes: screenless logic from entry point to conversion, then low-fi sketches to test patterns, then mid-fi mock-ups in which layout and hierarchy become visible. Only once the flow works do we apply visual design: typography, colour, components, micro-interactions, animation. Preferably built directly on a design system so that everything we make is component-based and reusable.

The clickable prototype in Figma is the first moment the design feels like a product. We use it for usability tests: typically a handful of moderated sessions with participants from the target group, or unmoderated sessions via Maze or UserTesting when the hypothesis is narrower. What we learn feeds into the next design iteration.

The final phase is the hand-off to development: Figma pages with component names that match the codebase, design tokens for colour and typography, an accessibility checklist per screen and a notes document covering interaction detail. In our model this hand-off is almost ceremonial, because the developer has been following along and knows what is coming.

How we compare to the alternatives.

Alternative 01

Freelance UX designer

Strong and flexible, but it's one person. There is often no dev hand-off and no sounding board within the design team. We bring team continuity and a direct bridge to the builders.

Alternative 02

Pure UX agency

Specialists in research and design, but with no developers on hand. The hand-off to an external build partner introduces loss in translation. We keep design and delivery within one team.

Alternative 03

Enterprise consultancy

A complete offering, but with pricing and a process that don't suit a scale-up or mid-market product team. We work pragmatically, with smaller teams and less delay between idea and delivery.

Accessibility isn't an extra, it's the foundation.

Since 28 June 2025, the European Accessibility Act has placed obligations on commercial digital services aimed at consumers. For public bodies, the Dutch Temporary Digital Accessibility Decree (Tijdelijk besluit digitale toegankelijkheid) has applied for longer. In practice, both come down to one technical baseline: WCAG 2.2 at level AA.

For our designs, that's the standard, even where the law doesn't require it. In concrete terms, that means sufficient contrast between text and background, keyboard navigation as a first-class right, screen-reader compatibility, visible focus states, forms with semantic labels, and error messages that are accessible both visually and programmatically. We use axe DevTools, WAVE and Lighthouse as automated checks, and manually walk through the most important flows with a screen reader.

Beyond WCAG, the wider compliance landscape also needs attention. The GDPR and the accompanying ePrivacy directives call for privacy by design. In a UX context, that mostly means choosing to design cookie consent as an honest flow rather than as a dark pattern. The AI Act requires transparency wherever AI functionality is visible to the end user, which means labels, explainability and opt-outs. Large platforms are also subject to the DSA and DMA, with specific UX requirements around recommendations, opt-outs and advertising transparency.

For clients in more heavily regulated sectors, such as finance, healthcare and government, we combine UX work with enterprise software development that supports the audit standards you need.

How do we measure whether UX delivers value?

Measure 01

Task success and time on task

In usability tests, we measure whether participants can complete a specific task and how long it takes. A conversion funnel with three drop-offs per round is a strong qualitative indicator, and you don't need statistical significance to see the cause.

Measure 02

Product metrics after launch

Activation rate, retention, completion rate per flow, support tickets per release. For every UX iteration, we define up front which metric should move, so the effect can be seen objectively afterwards in the analytics stack you already use.

Measure 03

Accessibility and performance

WCAG score per screen, contrast reports, Lighthouse scores and Core Web Vitals. UX work that would make accessibility or performance worse doesn't get through our own internal review.

Tooling: what we use, and why.

Figma and FigJam are the standard for design and collaboration. Components, variants, auto layout, design tokens and prototyping all live in the same tool, and it's easy for client stakeholders to follow along without installing anything.

For research synthesis and information architecture we switch between Notion, Miro and Whimsical, depending on what the client team already uses. We don't force a tool stack on clients who already have one.

Usability testing is done via Maze (for unmoderated, fast, prototype-accurate testing) or UserTesting (for moderated sessions with selected panels). For sessions on an existing product, Hotjar and Fullstory are the first stops — heatmaps, recordings and funnel reports.

For post-launch analytics we plug into what is already in place: PostHog, Mixpanel or Amplitude for product analytics, GA4 or Plausible for the web. We run accessibility checks with axe DevTools, WAVE and Lighthouse, supplemented by manual screen reader runs (VoiceOver on macOS, NVDA on Windows).

Where it adds value, we use AI tooling: Anthropic Claude for synthesising research transcripts and first-draft copywriting, Midjourney or Stable Diffusion for moodboards and visual exploration. Always transparent, always under human control, and, where relevant for end users, labelled in the interface as the AI Act requires.

Projects where UX makes the difference.

Founders · MVP

The first version of a SaaS product

A founder with a validated problem and an initial hypothesis. We turn the idea into a clickable prototype, test it with the target audience and keep building from there, as one team rather than a research phase, design phase and build phase invoiced separately.

Product team · Rework

An existing portal with growing pains

A product that has grown over five years through standalone features. We restructure navigation and flows, bring the visual design back to a single design system and run the migration screen by screen alongside the development team.

Enterprise · Multi-product

A portfolio in one visual language

Five internal tools, five interfaces. A shared design system with UX patterns, accessibility defaults and a component library, plus a redesign of the first product as a reference implementation.

Frequently asked questions.

What exactly is UX design, and how does it differ from UI design?
UX (user experience) is about how a product works: the flows, the structure, the research that determines which screens are needed in the first place. UI (user interface) is about how it looks: typography, colour, components, micro-interactions. In practice the two overlap and the same people do both. Good UX without UI feels messy; a beautiful UI without UX feels confusing. We treat them as a single discipline and deliver them together.
Does UX work without a design team of our own?
Yes. Most clients don't have a UX designer in-house, though they do have a product owner and sometimes a marketer with a good eye for visuals. We run the full process and involve your team at the moments that matter: discovery interviews, design reviews, usability tests. For clients with their own team, we work as an extension of it or take on just the research and hand-off.
Is accessibility (WCAG 2.2 / EAA) really mandatory?
For public services in the Netherlands, the Temporary Decree on Digital Accessibility (Tijdelijk besluit digitale toegankelijkheid) has applied for some time. Since 28 June 2025, the European Accessibility Act (EAA) has extended that scope to commercial digital services aimed at consumers: web shops, e-readers, banking services, ticketing. We apply WCAG 2.2 AA as standard, even where the law doesn't require it, because it simply makes most design decisions better.
Which tools do you use?
Figma and FigJam for design, prototyping and collaboration. Notion, Miro or Whimsical for research synthesis and information architecture. Maze or UserTesting for (un)moderated usability tests, Hotjar and Fullstory for session recordings of existing products, and PostHog, Mixpanel or Amplitude for post-launch analytics. For accessibility checks we use axe DevTools, WAVE and Lighthouse. Where it makes sense, we use AI tooling (Anthropic Claude for research synthesis, Stable Diffusion for moodboards) — always transparently and in line with the AI Act requirements.
How do you measure whether UX delivers results?
Before the engagement starts, we define which metrics should move: task success rate, time on task, completion rate of a specific funnel, NPS, support tickets per release, or business KPIs such as activated users. During usability tests we measure qualitatively (where do people drop off?), and after launch quantitatively via the analytics stack you already use. No vanity metrics — only what is tied to a product goal.
What does a UX engagement cost?
It depends on scope. A short audit is a smaller investment than an end-to-end product engagement, and an embedded designer is a different model again. We work with fixed sprint budgets and, after a planning phase, give you a concrete price that matches the depth of research you need, the number of flows and the degree of handover to development. For a good estimate we need a short intake call — no more than that.
How does a UX engagement start in practice?
With an intake call in which we go through the context, target groups and business context. Based on that, we propose a sprint plan that starts with discovery — usually a few working sessions with interviews, an audit of what already exists and a first set of hypotheses. From the first sprint a developer sits at the table, so technical constraints feed directly into the design choices. For larger engagements this also provides a direct bridge to web development or app development.
How are you different from a pure UX agency or a freelance designer?
A pure UX agency delivers designs and is then done; the implementation gets thrown over the fence to another team. A freelance UX designer can be excellent, but is one person — and therefore vulnerable to absence, holidays and a lack of sparring partners. We combine a dedicated UX team with the developers who build it. For more complex engagements, that also means a direct link to enterprise software development and to building a custom website with the same design language.

Talk to us about your UX challenge.

A half-hour introduction in which we go through the context, the target groups and the product — and look at whether an audit, a design sprint or a full engagement fits best. No obligation, no sales pitch.

Reply within 1 working day
No-obligation conversation
Westerdoksdijk 599, Amsterdam

Edit content