Design
The interface your people actually use, not the one that goes down well in a meeting
Research with real users, a prototype tested before code, an independent audit and a design system only when it genuinely pays off, from a team that builds and maintains its own software products.
- You have a digital product with real users, but you do not know why they abandon a flow
- You want to validate a new concept before investing in production code
- The team has grown and every designer builds the interface differently
01 · What it costs you today
You changed how it looks, and the numbers did not move
A visual redesign can look better and, statistically, move no business indicator at all. Without testing with real users, 'nicer' and 'more effective' stay different things.
You do not know whether accessibility is a legal obligation for you
Romanian Law 232/2022 has applied since 28 June 2025 to ecommerce, banking, telecom and passenger transport. Fines start at 2,500 lei, and 9 out of 10 companies checked were not yet compliant.
Nobody can prove the interface is the problem
The team feels something is wrong, but impressions do not convince leadership. With no before and after measurement, any UX conversation stays one opinion against another.
The product grows, the consistency disappears
Several people make interface decisions independently, and the product ends up looking like three applications stitched together. With no system, every new screen reinvents the wheel.
02 · What you get
Research with real users, not internal assumptions
Interviews and usability testing with a real target group, sized around what has to be validated, not around a myth that 'five users are enough'.
A prototype tested before production code
Wireframes, then a clickable prototype, validated with real users before a single line of code ships. A wrong assumption caught here costs days, not months.
A UX audit delivered independently
An evaluation of an existing product, with problems prioritised by severity and estimated impact. You get the report, and what you do next, with us or with somebody else, is your decision.
Accessibility checks, with the right nuances
WCAG 2.1 AA applies to text, forms and functional interface components. The contrast required for a logo is not the one required for a button, a frequent confusion we clear up in the first conversation.
A design system only past the real economic threshold
We recommend a component system when you already have more than one product or a growing design team, not as a reflex. Below that threshold, we say plainly that the investment is for later.
Before and after measurement, on real indicators
Task success rate, drop-off rate on the critical steps, time to completion. Numbers from your product, not an aggregate study you cannot verify.
03 · How we work
- 01
Qualification
A free conversation where we establish whether the problem is UX, content or something else. We do not sell research where the answer is already clear and cheap.
- 02
Research
Interviews and usability testing with a real target group, sized around what has to be validated rather than around a fixed rule.
- 03
Synthesis and prototype
Problems and opportunities ordered by impact, then wireframes and a clickable prototype, tested iteratively before any decision is called final.
- 04
Delivery and validation
A report, a documented design system or a prototype handed to the development team. Optionally, we check after implementation that the change had the intended effect, with data rather than assumptions.
04 · Results
- luxeria.roLuxeria
The website and CRM interface, designed for an order flow with many variables.
- KJ CenterERP, POS and HR
The interface for a system used daily by different teams, with distinct roles and permissions.
- Memento Groupbooking platform
The search and booking experience for a platform with several operators.
These are the figures reported by the clients themselves, for their own accounts, over the periods shown. We do not turn them into derived percentages and we do not present them as reproducible.
05 · What people usually ask us
- “A test with 5 users is enough, that is what everyone writes.”
- Nielsen's rule applies strictly to qualitative testing on a homogeneous group. Laura Faulkner tested 60 people and drew random sets of 5: some caught 99% of the real problems, others only 55%. For an important decision tested once, we recommend more.
- “Do we really need this design system or is it a fashion?”
- Only if you already have more than one digital product or a team of over 3 people making interface decisions independently. If discovery shows you have not reached that threshold, we tell you, we do not sell you a system you will never fully use.
- “Research is expensive, let us go straight to the solution.”
- Only 20% of organisations run discovery on every project, but projects with discovery report an 83% success rate against 52% without. The difference is not cosmetic, it shows directly in the failure rate.
06 · Frequently asked questions
- What is the difference between UI and UX, concretely?
- UI is the visual layer, how a button, a colour or a typeface looks. UX is the decision behind it, why the button is there and how many steps the user needs to reach their goal. You can have beautiful UI with bad UX.
- How many users are actually enough for research?
- For a quick qualitative test on a homogeneous group, 5 can be enough. But the research shows real variability, some random sets of 5 caught only 55% of problems, others 99%. For an important decision with a single round of testing we recommend at least 8-10, and for quantitative validation at least 20.
- Can we buy an audit without hiring you for the redesign?
- Yes. The audit is an independent deliverable, with problems prioritised by severity. What you do next with the report, with us or with somebody else, is your decision.
- Does a logo have to meet the same contrast requirement as text, for accessibility?
- No. WCAG sets no contrast threshold for logos as such, the requirement applies to text and to functional interface components. It is a frequently mistaken distinction, and it matters for an audit's credibility.
- Are we legally required to be accessible?
- If you operate in ecommerce, consumer banking, telecommunications or passenger transport, most likely yes, since 28 June 2025. The exemption applies strictly to service microenterprises, under 10 employees and under 2 million EUR turnover.
Shall we talk about your project?
Tell us where you stand. If we are not the right answer for you, you will hear it in the first conversation.
Request a quote