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.
Resolve the website brief before committing to the build.
Norml runs website discovery to define priorities, content needs, platform constraints, and responsibilities before design and development begin.
A few clients we’ve worked with
What we do
Norml runs website discovery to define priorities, content needs, platform constraints, and responsibilities before design and development begin.
A project can be ready for discovery before it is ready for design.
Your team knows the website needs work but has not agreed the scope.
Several stakeholders need different things from the same website.
Integrations or content migration could affect the build.
You need a documented brief to compare implementation options.
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 our website discovery services include.
Discovery combines stakeholder sessions with a review of the current website and available evidence. We identify decisions, dependencies, and unresolved questions, then prepare a brief that can guide the delivery team.
Stakeholder discovery
Discuss the business goals, audiences, internal publishing needs, and approval responsibilities.
Website review
Inspect representative pages, content, navigation, available analytics, and key conversion paths.
Technical constraints
Review the CMS, hosting, connected systems, data ownership, and likely migration requirements.
Scope definition
Describe the proposed page set, functional requirements, exclusions, dependencies, and acceptance criteria.
What clients say.
Reviews from the companies that hired us for this kind of work.
Read every review on Clutch“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
Website discovery deliverables.
The agreed scope identifies which of these deliverables your project needs.
- 01
A discovery findings document.
- 02
A prioritized requirements list.
- 03
A proposed page and content inventory.
- 04
A record of technical dependencies.
- 05
A delivery brief with open decisions.
Our process
How our website discovery process works.
Gather existing material
Review the website, analytics access, product material, and known requirements.
[ 01 ]
Explore the requirements
Discuss user needs and operational constraints with the relevant stakeholders.
[ 02 ]
Define the project
Document the recommended scope and distinguish requirements from optional additions.
[ 03 ]
Prepare the handover
Review decisions together and identify what the next phase needs to start.
[ 04 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Other services we offer.
Norml plans, writes, designs, builds and maintains websites. Each service can be taken on its own, or combined into one engagement.
See all services
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 questions.
Can discovery be a standalone engagement?
Yes. The brief can guide a later project with Norml or another delivery team.
Does discovery include a finished design?
It defines the requirements and direction. Detailed page design is a separate stage.
What if we already have a detailed brief?
We can review that brief, focus on unresolved dependencies, and avoid repeating completed research.
Will you quote the build during discovery?
The resulting scope supports a separate implementation estimate. Discovery itself does not establish an approved build price or delivery date.
See how this work fits into our website strategy service.