Your interface stops drifting
Consolidated components mean two pages built a year apart still look like the same product.
Give specification pages and enquiry screens reusable design rules.
We create Figma components that preserve technical context across product families and content variations.
A few clients we’ve worked with
What we do
We create Figma components that preserve technical context across product families and content variations.
Decisions that shape this work.
Visual consistency must not erase measurement conditions or revision context.
Long part identifiers and dense tables need explicit layout rules.
What repeated decisions cost you.
Every time a team re-decides a button, a form field or a card, it pays for that decision twice — once in design and once in code. A system is how you stop paying.
Design and code agree
One library, with practical examples of how the parts work together, removes the gap between what was designed and what shipped.
Onboarding is shorter
A new designer or developer has a reference instead of needing someone to explain the unwritten rules.
What design systems include.
The work uses approved product and capability records. Engineering and commercial owners verify specifications, document revisions and the permitted use of business systems.
Technical components
Define specification tables, document references and product facts.
Interaction patterns
Specify filters, comparison controls and RFQ states.
Usage guidance
Document units, missing fields and responsive behaviour.
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
A component library.
- 02
Shared visual values.
- 03
Technical content guidance.
Our process
How the work runs.
Inventory catalogue patterns
Review representative product families, document links and enquiry screens.
[ 01 ]
Build reusable variations
Define components for actual content lengths and successful, empty and invalid states.
[ 02 ]
Document technical use
Explain field presentation and responsive rules so designers and developers preserve meaning.
[ 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 startedDesign systems for manufacturers: questions.
Can the system support several product families?
Yes, with shared rules and family-specific fields where required.
Will a shared layout mean products are interchangeable?
No. The information and relationships must preserve actual technical distinctions.
Website 2.0 combines strategy, design, development and launch in one engagement.