You spend the budget where it pays
Findings are tied to the journeys that matter, so the work queue starts with the pages costing you enquiries.
Find obstacles in catalogue lookup and specification enquiries.
We inspect the agreed website tasks with representative records, separating interface findings from engineering judgements.
A few clients we’ve worked with
What we do
We inspect the agreed website tasks with representative records, separating interface findings from engineering judgements.
Decisions that shape this work.
A successful search is not useful if it returns the wrong revision without context.
Form simplification should not remove information sales needs to assess the enquiry.
What an audit tells you before you rebuild.
A working page can still make a task harder than it needs to be. Finding out which pages, and why, is cheaper than redesigning everything and hoping.
Opinions become evidence
Interface inspection combined with your own analytics separates observed problems from the ones someone assumes exist.
A redesign stops being a gamble
The audit is the brief. The next project starts from known problems instead of a general feeling that the site is tired.
What UX audit includes.
The work uses approved product and capability records. Engineering and commercial owners verify specifications, document revisions and the permitted use of business systems.
Lookup review
Check product finding, filters and document access.
RFQ inspection
Review units, attachments, errors and completion behaviour.
Issue reporting
Describe reproducible problems and expected corrections.
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
An annotated task review.
- 02
A prioritised issue list.
- 03
Implementation recommendations.
Our process
How the work runs.
Choose representative tasks
Agree specification lookup and RFQ scenarios with engineering and sales.
[ 01 ]
Inspect the live behaviour
Record navigation, filter, document and form issues with evidence.
[ 02 ]
Prioritise actionable changes
Explain each failure and expected behaviour so developers can implement and retest it.
[ 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 audit for manufacturers: questions.
Does this certify that a product is suitable?
No. The audit reviews the interface and information presentation, not engineering suitability.
Can legacy document archives be included?
Yes, where their discovery and access are part of the authorised website scope.
Website 2.0 combines strategy, design, development and launch in one engagement.