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.
Check the catalogue and quoting workflow before specifying the website.
Discovery examines product data, documents and enquiry handling so the build brief reflects the manufacturer’s actual sources and systems.
A few clients we’ve worked with
What we do
Discovery examines product data, documents and enquiry handling so the build brief reflects the manufacturer’s actual sources and systems.
Decisions that shape this work.
The website may not be the authoritative source for stock, price or revision data.
A PDF archive does not by itself define a usable document catalogue.
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 work uses approved product and capability records. Engineering and commercial owners verify specifications, document revisions and the permitted use of business systems.
Catalogue inventory
Identify product records, revisions and their responsible owners.
Sales workflow
Trace a representative RFQ using synthetic or approved examples.
System dependencies
Review supported PIM, ERP, CRM or document-system interfaces where relevant.
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“They delivered what they said they would, on time.”
“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.”
What you receive.
The agreed engagement includes the relevant outputs below.
- 01
A source inventory.
- 02
An RFQ workflow diagram.
- 03
A requirements register.
Our process
How the work runs.
Inventory products and sources
List records, documents, versions and the people who maintain them.
[ 01 ]
Trace the enquiry process
Document how specifications reach sales and where staff handle missing information.
[ 02 ]
Define build requirements
Record templates, field rules and verified connection needs, assigning unresolved dependencies.
[ 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 manufacturers: questions.
Does discovery need confidential customer drawings?
Initial review can use synthetic or explicitly cleared examples.
Will our ERP necessarily support a website connection?
No. Interface capability, permissions and required actions must be checked.
Website 2.0 combines strategy, design, development and launch in one engagement.