New pages stop starting from zero
A component system means the next landing page is assembled from approved parts instead of being designed, argued over and built again.
Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

We create responsive catalogue, capability and enquiry layouts in Figma using approved specifications and realistic document examples.
A few clients we’ve worked with




















We create responsive catalogue, capability and enquiry layouts in Figma using approved specifications and realistic document examples.
Comparable fields need consistent units and meanings.
An RFQ confirmation must not imply that the manufacturer accepted an order.
Design is where the website stops being a list of pages and becomes a system. The decisions made here set what every later page costs to produce.
A component system means the next landing page is assembled from approved parts instead of being designed, argued over and built again.
Page hierarchy and navigation are designed around what buyers look for, so the work the homepage does is not undone two clicks later.
Handoff includes states, components and responsive rules, so the built page matches the design instead of being reinterpreted.
The work uses approved product and capability records. Engineering and commercial owners verify specifications, document revisions and the permitted use of business systems.
Present comparable fields with their units and conditions.
Make datasheets, drawings and revision information understandable.
Design the required specification fields, attachment guidance and completion states.
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.”
The agreed engagement includes the relevant outputs below.
Responsive Figma designs.
Reusable product components.
An RFQ interface specification.
Explore the wider scope behind the website.
Develop the positioning, messaging, and visual identity your website needs.
Update an existing website while accounting for its content, URLs, integrations, and publishing workflow.
Where generative tools genuinely speed up brand and interface work, where they must not be used, and who signs off.
Plan user flows, screens, interface states, and design systems for websites and web products.
Explore the scope, deliverables and process for each part of the website.
Our process
Select product records, documents and enquiry scenarios for the design.
[ 01 ]Build product layouts and RFQ states using actual content variations.
[ 02 ]Document table behaviour, file handling and errors before developer handoff.
[ 03 ]No account layer between you and them. These are the Norml specialists this work runs through.

Co-founder · Design & Strategy

UI/UX Designer

UI/UX Designer

Junior Designer

“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