Your interface stops drifting
Consolidated components mean two pages built a year apart still look like the same product.
Give product pages and request forms reusable design rules.
We create Figma components that handle agency content and interaction states consistently as the website expands.
A few clients we’ve worked with
What we do
We create Figma components that handle agency content and interaction states consistently as the website expands.
Decisions that shape this work.
Disclosure content must remain readable across component variants.
Conditional form patterns need states for skipped, required and invalid answers.
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 includes.
The scope uses the agency’s actual offerings and approved public information. Product statements and customer-data decisions stay with the agency’s authorised reviewers.
Content components
Define offering cards, producer profiles and disclosure presentations.
Form patterns
Specify conditional questions, validation, focus and completion states.
Usage guidance
Show how long product names and varying content fit the system.
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“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.”
“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.”
“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.”
What you receive.
The agreed engagement includes the relevant outputs below.
- 01
A component library.
- 02
Shared visual values.
- 03
Component usage guidance.
Our process
How the work runs.
Inventory repeated patterns
Review the offering, producer and form layouts used in the planned site.
[ 01 ]
Build reusable variations
Create components and shared values with representative content and interaction states.
[ 02 ]
Document correct use
Explain content limits and state behaviour so design and development can apply the library consistently.
[ 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 insurance agencies: questions.
Can the library cover an existing-customer portal?
Shared visual rules may help, but portal roles and workflows require their own requirements.
Does the design system include development?
It supplies design specifications; component implementation must be included separately.
Website 2.0 combines strategy, design, development and launch in one engagement.