Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Design insurance request flows that explain the next step.
We map product discovery, new enquiries and existing-customer tasks, then design the screens and states needed for those journeys.
A few clients we’ve worked with
What we do
We map product discovery, new enquiries and existing-customer tasks, then design the screens and states needed for those journeys.
Decisions that shape this work.
New prospects and existing policyholders need different routes.
A conditional question can change what data is requested and how it must be handled.
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 scope uses the agency’s actual offerings and approved public information. Product statements and customer-data decisions stay with the agency’s authorised reviewers.
Task mapping
Separate quote requests, producer contact and support tasks.
Conditional interfaces
Design question sequences based on the agency’s approved information requirements.
Completion states
Explain receipt and next steps without presenting a request as an acceptance.
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
Journey maps.
- 02
Interactive Figma flows.
- 03
A form-state specification.
Our process
How the work runs.
Map visitor tasks
Define the agency’s quote, support and producer-contact journeys using representative scenarios.
[ 01 ]
Prototype the screen states
Connect product choices, questions, errors and completion messages in Figma.
[ 02 ]
Review complete flows
Walk through desktop and mobile scenarios with the responsible team and document the required behaviour.
[ 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 insurance agencies: questions.
Can a form recommend coverage?
A website can collect context; any recommendation requires the agency’s approved process and qualified personnel.
Must every visitor complete a long form?
Question depth follows the task. An initial contact route can differ from a separately scoped application process.
Website 2.0 combines strategy, design, development and launch in one engagement.