Your users don't reach their goal.

The features are there, but hardly anyone finds them. Forms get abandoned, support explains the same steps every day, and internally people would rather use Excel than the tool that was built specifically for them.

What waiting costs you every month

Every drop-off is a customer you had already won. On top of that come support costs, training effort and development time for features nobody finds. With internal tools, you pay with your employees' working time, every single day. An AI chatbot that explains a confusing interface only moves the problem elsewhere. These costs grow with every new user.

Does this sound familiar?

  1. Users abandon sign-up, checkout or applications halfway through.

  2. Support keeps answering the same questions about how things work.

  3. New features get built but are hardly used.

Poor usability rarely comes from one big mistake. It grows with every feature that is squeezed in quickly and every decision made from the company's point of view instead of the user's. Eventually only your own team knows the shortcuts, and everyone else gets stuck. The catch: if you work with the product every day, you no longer see the hurdles.

That is why good usability is not a matter of taste. It can be observed and measured: where do users hesitate, where do they click into nothing, where do they give up? I make exactly these spots visible, with real users instead of opinions from the meeting room. AI does not replace this observation either: it knows common patterns, but not your users.

How I approach it

Analysis

I review your application with a UX audit and watch real users at work. I analyze large amounts of support tickets, feedback and analytics data with AI, so patterns become visible in hours instead of weeks. That way we see where things really get stuck instead of guessing.

Targeted improvements

I redesign the critical flows and, with the help of AI, quickly build working prototypes instead of static mockups. I test them with users and then implement them in the frontend. The biggest hurdles first, so the impact shows quickly.

Measure the impact

Drop-off rates, support requests and processing times show what the changes achieved. Your team gets clear guidelines so new features are easy to understand from the start.

Frequently asked questions

Do we need a complete redesign?

Usually not. Often a few flows cause most of the problems. I improve those specifically, without surprising your users with a completely new interface.

How do you find out where the problem is?

With a combination of a UX audit, existing data such as analytics or support tickets, and usability tests with real users. Just five tests uncover most of the hurdles.

Do you also implement the improvements?

Yes. As a designer and developer, I design the solution and build it directly in the frontend. Nothing gets lost in the handover between design and development.

Does this work for internal tools as well?

Especially there. Internal applications are often built without the users in mind, even though employees spend hours with them every day. Every minute saved pays off directly.

How quickly will we see results?

Within a few weeks, the analysis delivers a prioritized list of the biggest hurdles. First improvements can then be implemented and measured right away.

Can't AI just generate a better interface?

It generates interfaces that look good and follow familiar patterns. Whether your users reach their goal with them, it doesn't know, because that only shows in tests with real people. I use AI to build variants and prototypes faster. Observation and measurement decide which one works, and interpreting those results correctly is my job.

Let's talk about your situation

In a free initial call we take a look at your problem together. You get an honest assessment of whether and how I can help.