Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

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










UX/UI design for websites and web products: user flows, information architecture, wireframes, prototypes, interface systems, and developer handoff.
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.
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.
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
An agreed screen inventory and behaviour means engineers implement decisions instead of making product decisions in code review.
Patterns designed once hold when the roadmap adds a role, a plan tier or a new workflow.
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.
Review stakeholder input, existing research, product behavior, and user feedback to define the tasks the interface must support.
Organize screens, navigation, content, and role-specific journeys so the required actions have a clear sequence.
Explore screen structure, content priority, and interaction patterns before committing to visual detail.
Design the approved screens with responsive behavior and the loading, empty, validation, and error states they require.
Connect key flows in an interactive prototype and use agreed review or testing sessions to identify confusing steps.
Prepare reusable components, variants, tokens, interaction notes, and implementation reviews for the development team.
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.”
“They were proactive in suggesting improvements we hadn't considered.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
The agreed scope identifies which of these deliverables your project needs.
An agreed user-task and screen inventory.
Information architecture and user-flow diagrams.
Wireframes for the journeys in scope.
High-fidelity screens and interface states.
A prototype and testing findings where included.
A Figma component system and developer handoff.
Our process
Review the product goals, user roles, current behavior, technical constraints, and evidence already available.
[ 01 ]Organize the journeys and screen structure, including decision points and edge cases.
[ 02 ]Develop wireframes and visual screens using the approved brand and interaction direction.
[ 03 ]Walk through key flows, collect user or stakeholder feedback, and resolve issues within the agreed scope.
[ 04 ]Document components, states, and responsive rules, then support implementation review where included.
[ 05 ]No account layer between you and them. These are the Norml specialists this work runs through.
Norml plans, writes, designs, builds and maintains websites. Each service can be taken on its own, or combined into one engagement.
See all services
“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