Stakeholders agree once
Sessions surface competing priorities while they are still cheap to reconcile, not after a design has been drawn to one of them.
Trace quote and application handling before specifying the build.
Discovery connects the website brief with dispatch, recruiting and the actual systems receiving their requests.
A few clients we’ve worked with
What we do
Discovery connects the website brief with dispatch, recruiting and the actual systems receiving their requests.
Decisions that shape this work.
A website form cannot promise an action the receiving system does not support.
Dispatch and recruiting may use different tools and review processes.
What discovery settles before design starts.
A project can be ready for discovery before it is ready for design. Finding the unresolved questions early is what keeps the build from pausing.
Dependencies appear early
Technical constraints and the systems the website has to live with are identified before they become a mid-build surprise.
The next stage can be scoped
A brief naming the decisions and open questions lets design, content and development be quoted against something real.
What website discovery 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.
Content inventory
List services, terminals, careers content and responsible owners.
Workflow review
Follow representative shipper and secondary-audience requests using synthetic examples.
System checks
Record supported TMS, CRM or recruiting interfaces and access requirements.
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
A content inventory.
- 02
A workflow diagram.
- 03
A requirements register.
Our process
How the work runs.
Inventory public information
Identify content sources, system documentation and the people responsible for them.
[ 01 ]
Trace the two workflows
Document how the relevant requests are received, assigned and handled when incomplete.
[ 02 ]
Define the build dependencies
Specify templates, fields and acceptance checks, assigning unresolved interface questions to owners.
[ 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 startedWebsite discovery for logistics companies: questions.
Can you assume our TMS accepts website submissions?
No. Its supported actions and access must be verified first.
Do you need real driver application records?
Initial discovery can use synthetic records and authorised workflow demonstrations.
Website 2.0 combines strategy, design, development and launch in one engagement.