Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Make the first enquiry easier to complete.
A visitor may know what happened without knowing which practice area covers it. We review how the website helps that person find the right information and make an enquiry, then prototype the steps your intake team can support.
A few clients we’ve worked with
What we do
UX/UI design for law firm websites: practice selection, enquiry forms, confirmation screens and responsive interaction states.
Where an enquiry journey can become unclear.
Navigation asks visitors to choose legal categories before explaining the situations they cover.
The first form requests more information than the intake team needs to decide the next step.
A confirmation screen gives no clear indication of what happens after submission.
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 the work includes.
The scope is agreed against the firm’s current website, available content and team responsibilities.
Practice selection
Map the entry points for the situations the firm actually handles. Test navigation labels and links using those scenarios, including visitors who arrive directly on a practice page.
Enquiry flow
Agree the information intake needs for an initial enquiry. Design the sequence, optional fields and conditional questions around that decision.
Form states
Specify field labels, helper text, validation, loading, failure and success states. Show how visitors can correct a mistake without re-entering the whole form.
Mobile interaction
Review tap targets, keyboard behaviour, long selections and contact options on small screens. Keep the next action visible in the context of the page.
Confirmation and follow-up
Design a clear receipt message using the contact process the firm approves. Describe an expected response time only when the team can commit to it.
Prototype review
Use a clickable prototype to walk through agreed visitor scenarios with the firm and intake team. Record open decisions, then hand over the approved behaviour for development.
Selected website projects across our wider practice
All case studies
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“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.”
“Norml Studio's professionalism and responsiveness were impressive.”
What you receive.
The handoff covers the page types and visitor scenarios agreed at the start.
- 01
A journey map for the agreed practice and enquiry scenarios.
- 02
Wireframes and a clickable Figma prototype.
- 03
An enquiry-field specification agreed with intake.
- 04
Desktop and mobile UI states, including errors and confirmation.
- 05
A handoff checklist covering behaviour and unresolved integration decisions.
Our process
How the work runs.
Understand intake
Review the current enquiry process and the information the team needs.
[ 01 ]
Map the journeys
Describe the visitor’s entry point, decisions and next action for each agreed scenario.
[ 02 ]
Prototype
Build the practice-selection and enquiry flows before development.
[ 03 ]
Review with the team
Walk through successful submissions, incomplete information and failure states.
[ 04 ]
Specify implementation
Document the approved screens and acceptance criteria for the developer.
[ 05 ]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 law firms: questions.
Does this include a CRM connection?
The design specifies the information and destination the flow needs. Implementing and testing a CRM or practice-management connection is a separate development scope.
Do you need access to client files?
The design can start with anonymised scenarios and a description of the intake process. Real matter details are not needed in design prototypes.
Can you improve a form without redesigning the whole site?
Yes. The scope can cover the enquiry flow and its surrounding screens while using the site’s current visual components.
Will you test the prototype with prospective clients?
Participant research can be included when recruitment and consent are agreed. A review with the firm’s team is a separate activity and is not presented as user testing.
Do you guarantee more enquiries?
No. The deliverables are an agreed flow, prototype and implementation specification. Measuring changes after launch requires a baseline and a separately agreed measurement plan.
Website 2.0 combines strategy, design, development and launch in one engagement.