Services
Research, concept, UI.
In that order.
Seven ways to work together, with rates stated as ranges rather than hidden behind a call. Where a project starts depends on what you already know: most start with an audit or a research phase, because everything after that is cheaper when it does.
| Service | What it is | From | Timeline |
|---|---|---|---|
| UX audit | What is broken, prioritised by when to act, referenced to a standard. | €900 | 48 hours |
| UX strategy | Where the product should go, and what to build first. | from €4,500 | 2–4 weeks |
| User research | Interviews, usability tests, personas, journey maps. | from €3,500 | 2 weeks+ |
| Wireframing & prototyping | Flows, low- and high-fidelity screens, a clickable prototype. | from €3,000 | 2–3 weeks |
| Usability testing | Moderated sessions with 5–7 users, and what to do about them. | from €2,500 | 2 weeks |
| Product design | Information architecture, UI, design system, developer handoff. | from €6,500 | 3–5 weeks |
| Design-led AI MVP | Research, design and a working product, from one person. | from €4,500 | 2 weeks |
Rates are starting points for a typical scope. I quote a fixed price once I know the product. Nothing here is called Gold, Premium or Enterprise.
Engagement models
Three ways to bring me in.
-
Project-based design
A defined scope with a defined deliverable. Most of the services below work this way.
-
Embedded senior designer
I join your team for a stretch: standups, planning, the lot. Monthly, usually two to four days a week.
-
Strategy, audits and coaching
Shorter engagements for teams that have designers but need direction, an outside read, or someone to raise the level.
Process
User-centered design per DIN EN ISO 9241.
- ResearchUnderstand the context of use before proposing anything.
- ConceptStructure, flows and information architecture, cheap to change.
- PrototypeSomething clickable, early, that people can react to.
- TestReal users, real tasks, and a decision at the end of it.
- SpecifyDocumentation precise enough to build from without interpretation.
- ShipStay close to development until it is actually live.
Questions
Before you ask.
With a call and access to whoever talks to your users. I write a one-page brief from that, and we agree on it before anything gets designed.
Yes, and I prefer it. I have designed inside Storybook-backed systems at ZEISS and Uniper, and built new ones where none existed.
That is most of my work. I have been the embedded senior designer inside enterprise product teams for a decade.
Remote-first from Munich and Yerevan, on site across Europe and worldwide when research or workshops need it.
Always, before we talk specifics. Most of my client work is under one.
Tell me what's stuck.
Two or three sentences and a rough timeline. I reply within two working days.