Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Design product lookup and RFQ flows around the buyer’s task.
We map how users compare offerings, retrieve documents and provide specifications, then design the screens and states needed to complete those tasks.
A few clients we’ve worked with
What we do
We map how users compare offerings, retrieve documents and provide specifications, then design the screens and states needed to complete those tasks.
Decisions that shape this work.
Similar field names may use different units or measurement conditions.
Uploading a drawing does not establish that sales received or accepted the specification.
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.
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 UX/UI design includes.
The work uses approved product and capability records. Engineering and commercial owners verify specifications, document revisions and the permitted use of business systems.
Buyer journeys
Define routes for engineers, procurement and authorised channel users.
Catalogue interactions
Specify filters, comparisons and empty results using real fields.
Enquiry states
Design units, validation, attachments and next-step messages.
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“They delivered what they said they would, on time.”
“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.”
What you receive.
The agreed engagement includes the relevant outputs below.
- 01
Journey maps.
- 02
Interactive Figma flows.
- 03
A catalogue and form specification.
Our process
How the work runs.
Map the evaluation tasks
Identify lookup, document and enquiry decisions using actual buyer scenarios.
[ 01 ]
Prototype the interaction states
Connect filters, record views and RFQ questions with representative data.
[ 02 ]
Review completion and failure
Walk through missing records, invalid fields and upload errors before specifying implementation.
[ 03 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
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 startedUX/UI design for manufacturers: questions.
Can an interface compare incompatible products?
Comparison needs agreed fields and product relationships; the design should not imply interchangeability without approval.
Will the form validate engineering suitability?
It can validate required information, but technical suitability remains an expert decision unless separately defined and verified.
Website 2.0 combines strategy, design, development and launch in one engagement.