UI/UX Design · 2024
A component library, documented states.
Every interactive state specced and handed off — not just the happy path.
03
Interfaces and design systems that reduce support tickets and engineering rework — not just a Figma file nobody opens.
Who it's for
01
Engineering rebuilds the same UI pattern differently every time because there’s no shared component library.
02
Support keeps getting tickets about the same confusing screen.
03
You've paid for a design system before, and it never got adopted — the file exists, nobody uses it.
What's included
- 01 Heuristic and accessibility review of existing screens
- 02 User flows and wireframes
- 03 High-fidelity UI with documented component states
- 04 A clickable prototype for validation
- 05 Developer handoff, with engineering-adoption sessions on the top tier
How this one runs
Audit & Research
Heuristic review, session-recording review where available, interviews if scoped.
Flows & Wireframes
The structure, before the visual layer.
High-Fidelity UI
Screens, states, and the component library.
Handoff & Adoption
Developer handoff plus (Design System Foundation) live sessions with your engineering team.
Packages
01
UX Audit & Roadmap
Delivery: 2 weeks
- A heuristic + accessibility review of up to 12 screens
- A session-recording review
- A prioritised issue log
- An annotated redesign of 3 key screens
- A 90-minute walkthrough
€2,400.00net, plus 19% VAT
Fixed price. What's included is listed above — no surprise line items.
02
Product Design Sprint
Delivery: 5 weeks
- Discovery interviews
- User flows, wireframes
- High-fidelity UI for up to 20 screens
- A clickable prototype
- Developer handoff
€7,800.00net, plus 19% VAT
Fixed price. What's included is listed above — no surprise line items.
03
Design System Foundation
Delivery: 8–10 weeks
- Token architecture
- 40+ components with states
- Responsive + accessibility specs
- A Figma library, a documentation site
- 2 engineering-adoption sessions
€14,500.00net, plus 19% VAT
Fixed price. What's included is listed above — no surprise line items.
Selected work
Adoption is a line item, not an assumption.
Design System Foundation includes two engineering-adoption sessions — working time with your developers to get the library actually implemented, not a link in a Slack message that never gets opened.
UI/UX Design questions
We already have a Figma file nobody uses — can you help?
Yes — Design System Foundation is built for exactly this. We audit what exists, keep what works, and rebuild the rest with adoption sessions included.
Do you write frontend code, or hand off specs?
We hand off specced, developer-ready components (redlines, states, tokens). We don't write production frontend code ourselves — that stays with your engineering team, where the accountability should sit.
What does an "adoption session" actually mean?
A working session with your developers, screen-sharing the library and the codebase together, so questions get answered while the library is fresh, not weeks later.
How many screens does a typical project cover?
UX Audit & Roadmap covers up to 12, Product Design Sprint up to 20. Design System Foundation is component-based rather than screen-based — scope is set by the number of components, not screens.