Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

UX/UI design for websites and web products.

Norml designs the journeys, screens, and interface systems people use to complete tasks. We work on B2B websites, dashboards, and web products, connecting user requirements with layouts, interactions, and developer-ready designs.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

UX/UI design for websites and web products: user flows, information architecture, wireframes, prototypes, interface systems, and developer handoff.

Useful interfaces need decisions about tasks and behavior.

  • A product needs a clear sequence for onboarding, searching, or completing a workflow.

  • Different user roles need different access, actions, and views.

  • An interface needs loading, empty, error, and success states alongside its main screens.

  • New features need to fit an existing component system.

  • Developers need responsive rules and interaction details before implementation.

What interface decisions cost when nobody makes them.

Interfaces are not decorated; they are decided. When the tasks, roles and states are never agreed, they get invented during development — one screen at a time.

Fewer support requests

Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.

Development stops guessing

An agreed screen inventory and behaviour means engineers implement decisions instead of making product decisions in code review.

The product survives its next feature

Patterns designed once hold when the roadmap adds a role, a plan tier or a new workflow.

What our UX/UI design services include.

We agree the users, tasks, screen inventory, and available evidence before detailed design. Research, usability testing, and design QA are included according to the needs and access available for the project.

User and task research

Review stakeholder input, existing research, product behavior, and user feedback to define the tasks the interface must support.

Information architecture and flows

Organize screens, navigation, content, and role-specific journeys so the required actions have a clear sequence.

Wireframes

Explore screen structure, content priority, and interaction patterns before committing to visual detail.

Interface and state design

Design the approved screens with responsive behavior and the loading, empty, validation, and error states they require.

Prototypes and testing

Connect key flows in an interactive prototype and use agreed review or testing sessions to identify confusing steps.

Design systems and handoff

Prepare reusable components, variants, tokens, interaction notes, and implementation reviews for the development team.

What clients say.

Reviews from the companies that hired us for this kind of work.

Read every review on Clutch
“We didn’t choose them to be impressed — we chose them because we knew they’d deliver high-level results with no risk. As a CTO myself, that’s exactly what I look for in a long-term partnership.”
Iryna MykytynFounder & CTO, COXIT.COClutch review
“They were proactive in suggesting improvements we hadn't considered.”
Lucas SeyhunCEO, The Farm SohoClutch review
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
Bret MillerManager, Door Knock ProClutch review

UX/UI design deliverables.

The agreed scope identifies which of these deliverables your project needs.

  1. 01

    An agreed user-task and screen inventory.

  2. 02

    Information architecture and user-flow diagrams.

  3. 03

    Wireframes for the journeys in scope.

  4. 04

    High-fidelity screens and interface states.

  5. 05

    A prototype and testing findings where included.

  6. 06

    A Figma component system and developer handoff.

Industries

Our process

How our UX/UI design process works.

Define the users and tasks

Review the product goals, user roles, current behavior, technical constraints, and evidence already available.

[ 01 ]

Map the experience

Organize the journeys and screen structure, including decision points and edge cases.

[ 02 ]

Design the interface

Develop wireframes and visual screens using the approved brand and interaction direction.

[ 03 ]

Review and test

Walk through key flows, collect user or stakeholder feedback, and resolve issues within the agreed scope.

[ 04 ]

Prepare the build

Document components, states, and responsive rules, then support implementation review where included.

[ 05 ]

The people who do this work.

No account layer between you and them. These are the Norml specialists this work runs through.

Meet the whole team
Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

Get started

UX/UI design questions.

Is this service for websites or applications?
Both. Website UX/UI focuses on content, navigation, and enquiry journeys. Product UX/UI covers task-based workflows, user roles, screens, and interface states.
Can you work with our developers?
Yes. We agree the component approach, technical constraints, and handoff format with your team so design decisions can be implemented consistently.
Do you conduct user testing?
Testing can be included when participants and a suitable method are available. We define the research questions and distinguish user findings from stakeholder feedback.
Can you extend an existing design system?
Yes. We review the current components and usage rules, reuse what fits, and document additions needed for the new screens.
Does a prototype include working software?
A design prototype demonstrates selected interactions. Production development, data connections, authentication, and deployment are separate implementation work.
Explore the product design work for Strem, an investment research platform by BRDGE Insights.

See a product interface in detail.

Explore the case study