I design B2B/SaaS and data-heavy products with complex logic, multiple roles and large volumes of data
I work from problem framing and product structure through to user flows, interface and handoff to engineering
Two projects that best show how I handle complexity: product architecture, user flows and large volumes of data
Product Designer · Oct ’25 — present
I design a B2B/B2C platform that connects companies with industrial safety specialists. I built the role model and the key flows: posting and finding orders, responding, choosing a contractor, specialist profiles, specialisations and pricing plans.
The goal is to make the different interests of both sides part of one coherent product system.
Product Designer · Aug ’25 — Feb ’26
I reworked an unfinished design concept for a B2B platform that verifies logistics companies. I rebuilt the structure and hierarchy of a large data set: from registration details and executives to finances, court cases and connections.
The main goal was to help users not just see dozens of parameters, but understand faster where the potential risk is.
Not every project needs a full case study. These are more compact pieces where I designed mobile-first products, content services and corporate B2B interfaces
Jun ’26
Jul ’26
Jul ’26
Apr ’25 — May ’25
Jun ’25 — Jul ’25
Jun ’25
I clarify the task, the constraints, the roles, the entities and the main user flow. I don't start with screens until I understand what exactly we are designing
1
I look for places where the user has to remember too much, make non-obvious decisions or jump between unrelated sections
2
I think not only about the happy path, but also about states, errors, empty data, constraints and alternative actions
3
I work with components and responsive layouts, discuss the solution with the team, gather feedback and prepare the designs for implementation
4
I like products you have to figure out first
I'm drawn to complex B2B and SaaS systems: lots of data, several roles, connected flows and constraints.
What I enjoy most is the moment when a clear product structure starts to emerge from a pile of requirements.
I'm comfortable with iteration and rework, and I prefer to justify a decision by the user's task rather than by “it looks nicer this way”.
