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 website scope against the firm’s working systems.
A website brief can depend on tools and content that have not yet been checked. We review the existing pages, editorial workflow and enquiry handling so the build has a concrete list of requirements and open questions.
A few clients we’ve worked with
What we do
Website discovery for law firms: content and access inventory, intake-system review, build requirements.
Decisions to settle before the work starts.
Which part of website discovery for law firms belongs in the current project, and what is outside it.
Who supplies the source material, grants system access and approves the completed work.
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.
Agree these work areas with the firm before implementation. Access, content approval and any external-system requirements are recorded in the scope.
Content and access inventory
List existing pages, assets, owners and systems. Note which materials can be reused and which require a new draft or approval.
Intake-system review
Document how enquiries enter the current CRM or practice-management system. Check available integration documentation and access requirements before promising a connection.
Build requirements
Turn the findings into page types, functional requirements and acceptance checks. Keep unknowns visible until the responsible person resolves them.
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 deliverables correspond to the work areas agreed for this engagement.
- 01
An inventory of content, assets and system access.
- 02
An intake-system dependency map.
- 03
A requirements document with acceptance checks and open questions.
Our process
How the work runs.
Agree the scope
Review the firm’s current website and the inputs needed for website discovery. Confirm the responsible people, access and acceptance criteria.
[ 01 ]
Carry out the work
List existing pages, assets, owners and systems. Note which materials can be reused and which require a new draft or approval. Document how enquiries enter the current CRM or practice-management system. Check available integration documentation and access requirements before promising a connection.
[ 02 ]
Review and hand over
Turn the findings into page types, functional requirements and acceptance checks. Keep unknowns visible until the responsible person resolves them. Record open decisions and the next action for each one.
[ 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 law firms: questions.
Will discovery include a technical prototype?
A small feasibility test can be included when a specific integration needs evidence. It is defined separately from a production implementation.
What do you need from our team?
A contact for the website, someone who understands intake, and access to the relevant documentation and approved content inventory.
Website 2.0 combines strategy, design, development and launch in one engagement.