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 decisions behind shipment and application forms.
We map visitor tasks and the screens needed to collect usable information, explain errors and reach the correct team.
A few clients we’ve worked with
What we do
We map visitor tasks and the screens needed to collect usable information, explain errors and reach the correct team.
Decisions that shape this work.
Shipment measurements need explicit units and field meanings.
An interrupted application needs agreed storage behaviour before a resume option is promised.
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 follows the company’s actual services and approved public information. Operations and recruiting retain ownership of factual requirements and system-access decisions.
Audience journeys
Separate shipping enquiries from recruitment or carrier participation.
Question logic
Design conditional fields based on approved dispatch and recruiting requirements.
Recovery states
Specify validation, interruption and next-step behaviour.
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.
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
Identify each audience’s decisions and the information the receiving team requires.
[ 01 ]
Prototype question sequences
Connect fields and conditional states using synthetic representative examples.
[ 02 ]
Review failures and completion
Walk through mobile scenarios and specify errors, interruptions and destination messaging.
[ 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 logistics companies: questions.
Can the same form handle applicants and shippers?
Only if the interface still separates their questions, data handling and destinations clearly.
Will UX design define hiring eligibility?
No. Recruiting supplies the approved criteria; the design expresses that process.
Website 2.0 combines strategy, design, development and launch in one engagement.