Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Design the steps between finding a project and sending a brief.
The interface needs to support project browsing and an enquiry with enough context for estimating. We map those tasks and design the page, filter and form states needed to complete them.
A few clients we’ve worked with
What we do
The interface needs to support project browsing and an enquiry with enough context for estimating. We map those tasks and design the page, filter and form states needed to complete them.
What needs to be clear before work begins.
Project filters need usable empty and reset states as well as a successful result.
Enquiry questions need an order that collects a useful brief without treating a submission as an accepted job.
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 work uses the company’s actual services and approved project material. The agreed brief identifies required access, decisions and review responsibilities.
Buyer journeys
Plan entry points for trade searches, sector browsing and repeat visitors seeking contact details.
Filter behaviour
Specify project filters, empty results and reset actions using the available portfolio fields.
Enquiry states
Design question order, validation and confirmation without implying that a submission is an accepted job.
Selected 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.
These outputs are prepared for the work included in the agreed scope.
- 01
Journey maps.
- 02
Interactive Figma flows.
- 03
A form and filter state specification.
Our process
How the work runs.
Map buyer tasks
Follow the routes for finding a relevant trade, comparing similar projects and contacting estimating.
[ 01 ]
Prototype the interactions
Connect portfolio filters, project detail screens and enquiry states in Figma using representative records.
[ 02 ]
Review complete flows
Walk through the prototype on desktop and mobile, then document corrections and implementation behaviour for each state.
[ 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 construction companies: questions.
Should every enquiry require document uploads?
Only if the estimating process needs them at that stage. Optional supporting documents can be separated from essential contact and project details.
Can this cover a contractor portal?
Yes, as a separately defined product flow with named user roles, permissions and data requirements.
Website 2.0 combines strategy, design, development and launch in one engagement.