


Norml designs product and website interfaces around real user tasks. Roles, onboarding, empty screens and error recovery are part of the design so engineering receives a usable description of the workflow.
A few clients we’ve worked with




















UX/UI design for SaaS companies: task and role mapping, screen and state design, interactive handoff.
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.
The scope below applies to the agreed SaaS website or product workflow. We confirm the source material and responsible owners before work begins.
“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.”
“And, you know, the great part about the fact that you hit the goal, it's not that you had to compromise anything that you were doing, because, honestly, the end result far exceeded what we could have imagined.”
“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
“Norml Studio's professionalism and responsiveness were impressive.”
The handoff records the product and release boundaries agreed for this work.
Explore the wider scope behind the website.
Explore the scope, deliverables and process for each part of the website.
Our process
Map the selected tasks with the product owner and identify rule gaps.
Design the main flows alongside empty, denied and recovery scenarios.
Review the prototype with stakeholders and document the implementation decisions.
No account layer between you and them. These are the Norml specialists this work runs through.

“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 startedDiscuss the UX/UI design scope, source material and dependencies for your SaaS website.